CN113163029A

CN113163029A - Network session account deployment method, device, terminal, server and storage medium

Info

Publication number: CN113163029A
Application number: CN202110554511.8A
Authority: CN
Inventors: 林炎章
Original assignee: Xiamen Yealink Network Technology Co Ltd
Current assignee: Xiamen Yealink Network Technology Co Ltd
Priority date: 2021-05-20
Filing date: 2021-05-20
Publication date: 2021-07-23
Anticipated expiration: 2041-05-20
Also published as: CN113163029B

Abstract

The application provides a network session account deployment method, device, terminal, server and storage medium, and relates to the technical field of network communication. The method comprises the following steps: the method comprises the steps of initiating a domain name query request to a domain name server by adopting at least two account numbers, receiving a domain name query result returned by the domain name server, sending a first registration subscription request to a first session server of a target internet protocol address in at least one internet protocol address by adopting at least two account numbers, so that the first session server registers the two account numbers and subscribes session resources, and receiving a first registration subscription response sent by the first session server. The method and the device can facilitate the domain name server to uniformly deploy and manage the network session terminal.

Description

Network session account deployment method, device, terminal, server and storage medium

Technical Field

The invention relates to the technical field of network communication, in particular to a network session account deployment method, a device, a terminal, a server and a storage medium.

Background

With the rapid development of Internet technology, the market demand of network session terminals based on Voice over Internet Protocol (VoIP) is increasing.

When an account in an existing network session terminal initiates registration to a session server, if the network session terminal comprises a plurality of accounts, a domain name server returns protocol addresses of session servers with different priorities based on a query request initiated by each account, so that different accounts in the same network session terminal are registered to different session servers based on a balance strategy of the domain name server.

Different account numbers in the same network session terminal are registered to different session servers, so that the domain name server needs to operate a plurality of session servers to complete the management of the network session terminal, and the management of the network session terminal by the domain name server is not facilitated.

Disclosure of Invention

The present invention provides a method, an apparatus, a terminal, a server, and a storage medium for deploying a network session account, so that the server can uniformly manage the terminal.

In order to achieve the above purpose, the technical solutions adopted in the embodiments of the present application are as follows:

in a first aspect, an embodiment of the present application provides a network session account deployment method, where the method includes:

initiating a domain name query request to a domain name server by adopting at least two account numbers, wherein the domain name query request comprises: a target domain name; the domain name query request is used for enabling the domain name server to analyze the target domain name to obtain at least one internet protocol address;

receiving a domain name query result returned by the domain name server, wherein the domain name query result comprises: the at least one internet protocol address;

sending a first registration subscription request to a first session server of a target internet protocol address in the at least one internet protocol address by adopting the at least two accounts, so that the first session server registers the two accounts and subscribes session resources;

receiving a first registration subscription response sent by the first session server, wherein the first registration subscription response comprises: and indicating information used for indicating whether the at least two accounts register subscription success at the first session server.

Optionally, the domain name query result further includes: a priority of the at least one internet protocol address;

before the sending, by using the two accounts, a first registration subscription request to a first session server of a target internet protocol address of the at least one internet protocol address, the method further includes:

and selecting a session server corresponding to the internet protocol address with the highest priority as the first session server according to the priority of the at least one internet protocol address.

Optionally, the sending, by using the two accounts, a first registration subscription request to a first session server of a target internet protocol address in the at least one internet protocol address includes:

sending a registration subscription request of an account to the first session server by adopting the account;

receiving a registration subscription response of the account sent by the first session server;

and if the registration subscription response of the account indicates successful registration subscription of the account, sending a registration subscription request of the other account to the first session server by adopting the other account.

Optionally, if the indication information indicates that the at least two accounts are successfully registered and subscribed, the registration and subscription response includes: the registration renewal duration of the at least two account numbers; the method further comprises the following steps:

if the registration renewal duration of a first account number in the at least two account numbers expires, the first account number is adopted to send a first registration request to the first session server again;

receiving a first registration response sent by the first session server;

if the first registration response indicates that the first session server is in a down state, sending a second registration subscription request to a second session server of another target internet protocol address in the at least one internet protocol address by using the first account, so that the second session server registers the first account and subscribes session resources;

and receiving a second registration subscription response sent by the second session server.

Optionally, the method further includes:

if the first account is detected to complete registration and subscription of session resources in the second session server, sending a third registration subscription request to the second session server by using the other accounts, so that the second session server registers the other accounts and subscribes the session resources;

and receiving a third registration subscription response sent by the second session server.

Optionally, the first registration response includes: a back-off time of the first account; the method further comprises the following steps:

if the rollback time of the first account is up, the first account is adopted to send a second registration request to the first session server again;

receiving a second registration response sent by the first session server;

if the second registration response indicates that the state of the first session server is recovered and the first account registration is successful, sending a unsubscribe request and a deregister request to the second session server in sequence by adopting the first account so that the second session server unsubscribes session resources and deregisters accounts in sequence on the first account;

adopting the first account to send a subscription request to the first session server again;

and receiving a subscription response sent by the first session server.

Optionally, the method further includes:

if the first subscription response indicates that the first account number is successfully subscribed, the other account numbers are sequentially adopted to sequentially send a unsubscribe request and a deregistration request to the second session server, so that the second session server sequentially unsubscribes session resources and deregisters the account numbers to the other account numbers;

adopting the other account numbers to send a fourth registration subscription request to the first session server again;

and receiving a fourth registration subscription response sent by the first session server.

In a second aspect, an embodiment of the present application further provides a network session account deployment method, where the method includes:

receiving domain name query requests of at least two accounts sent by a network session terminal, wherein the domain name query requests comprise: a target domain name;

analyzing the target domain name to obtain at least one internet protocol address;

and returning a domain name query result to the network session terminal, wherein the domain name query result comprises: the domain name query result is used for enabling the network session terminal to send a first registration subscription request to a first target session server of a target internet protocol address in the at least one internet protocol address by using the at least two account numbers, so that the first target session server registers the two account numbers and subscribes session resources.

Optionally, the receiving domain name query requests of at least two accounts sent by the network session terminal includes:

receiving the domain name query requests of the at least two accounts sent by the network session terminal in sequence;

the analyzing the target domain name to obtain at least one internet protocol address comprises:

under a domain name query process of an account corresponding to the received first domain name query request, analyzing the target domain name to obtain at least one internet protocol address;

and suspending the domain name query process of other accounts.

Optionally, before returning the domain name query result to the network session terminal, the method further includes:

calculating the priority of the at least one internet protocol address according to the session resource occupancy rate of at least one session server; the domain name query result further comprises: a priority of the at least one internet protocol address.

In a third aspect, an embodiment of the present application further provides a network session account deployment apparatus, where the apparatus includes:

a request initiating module, configured to initiate a domain name query request to a domain name server by using at least two account numbers, where the domain name query request includes: a target domain name; the domain name query request is used for enabling the domain name server to analyze the target domain name to obtain at least one internet protocol address;

a result receiving module, configured to receive a domain name query result returned by the domain name server, where the domain name query result includes: the at least one internet protocol address;

a first registration subscription request module, configured to send a first registration subscription request to a first session server of a target internet protocol address in the at least one internet protocol address by using the at least two accounts, so that the first session server registers the two accounts and subscribes to session resources;

a first registration subscription response module, configured to receive a first registration subscription response sent by the first session server, where the first registration subscription response includes: and indicating information used for indicating whether the at least two accounts register subscription success at the first session server.

Optionally, the domain name query result further includes: a priority of the at least one internet protocol address; before the first registration subscription request module, the apparatus further comprises:

and the session server selection module is used for selecting the session server corresponding to the internet protocol address with the highest priority as the first session server according to the priority of the at least one internet protocol address.

Optionally, the first registration subscription request module includes:

a first registration subscription request unit, configured to send a registration subscription request of one account to the first session server by using the one account;

a first registration subscription response unit, configured to receive a registration subscription response of the account sent by the first session server;

and a second registration subscription request unit, configured to send, by using another account, a registration subscription request for the another account to the first session server if the registration subscription response of the one account indicates that the one account is successfully registered and subscribed.

Optionally, if the indication information indicates that the registration and subscription of the at least two accounts are successful, the first registration and subscription response further includes: the registration renewal duration of the at least two account numbers; the device further comprises:

the first registration request module is used for sending a first registration request to the first session server again by adopting a first account number if the registration renewal duration of the first account number in the at least two account numbers expires;

the first registration response module is used for receiving a first registration response sent by the first session server;

a second registration subscription request module, configured to send a second registration subscription request to a second session server of another target internet protocol address in the at least one internet protocol address by using the first account if the first registration response indicates that the first session server is in a down state, so that the second session server registers the first account and subscribes session resources;

and the second registration subscription response module is used for receiving a second registration subscription response sent by the second session server.

Optionally, the apparatus further comprises:

a third registration subscription request module, configured to send a third registration subscription request to the second session server by using the other account if it is detected that the first account completes registration and subscription of session resources in the second session server, so that the second session server performs registration and subscription of session resources for the other account;

and the third registration subscription response module is used for receiving a third registration subscription response sent by the second session server.

Optionally, the first registration response includes: a back-off time of the first account; the device further comprises:

a second registration request module, configured to send a second registration request to the first session server again by using the first account if the rollback time of the first account is reached;

the second registration response module is used for receiving a second registration response sent by the first session server;

a first unsubscribe subscription module, configured to send an unsubscribe request and an unregister request to the second session server in sequence by using the first account if the second registration response indicates that the state of the first session server is recovered and the first account is successfully registered, so that the second session server unsubscribes session resources and unregisters accounts in sequence for the first account;

a subscription request module, configured to send a subscription request to the first session server again by using the first account;

and the subscription response module is used for receiving the subscription response sent by the first session server.

Optionally, the apparatus further comprises:

a second unsubscribe subscription module, configured to, if the first subscription response indicates that the first account is subscribed successfully, sequentially send a unsubscribe request and a deregister request to the second session server by using the other accounts, so that the second session server unsubscribes session resources and deregisters accounts for the other accounts sequentially;

the fourth registration subscription module is used for sending a fourth registration subscription request to the first session server again by adopting the other account numbers;

and the fourth registration subscription response module receives a fourth registration subscription response sent by the first session server.

In a fourth aspect, an embodiment of the present application further provides a network session account deployment apparatus, where the apparatus includes:

a request receiving module, configured to receive a domain name query request of at least two accounts sent by a network session terminal, where the domain name query request includes: a target domain name;

the resolution module is used for resolving the target domain name to obtain at least one internet protocol address;

a result returning module, configured to return a domain name query result to the network session terminal, where the domain name query result includes: the domain name query result is used for enabling the network session terminal to send a first registration subscription request to a first target session server of a target internet protocol address in the at least one internet protocol address by using the at least two account numbers, so that the first target session server registers the two account numbers and subscribes session resources.

Optionally, the request receiving module is configured to sequentially receive the domain name query requests of the at least two accounts sent by the network session terminal;

the parsing module includes:

the resolving unit is used for resolving the target domain name to obtain at least one internet protocol address under the domain name querying process of the account corresponding to the received first domain name querying request;

and the suspension unit is used for performing suspension operation on the domain name inquiry processes of other accounts.

Optionally, before the result returning module, the apparatus further includes:

the priority calculation module is used for calculating the priority of the at least one Internet protocol address according to the session resource occupancy rate of at least one session server; the domain name query result further comprises: a priority of the at least one internet protocol address.

In a fifth aspect, an embodiment of the present application further provides a network session terminal, including: the network session terminal comprises a processor, a storage medium and a bus, wherein the storage medium stores program instructions executable by the processor, when the network session terminal runs, the processor and the storage medium communicate through the bus, and the processor executes the program instructions to execute the steps of the network session account deployment method according to any one of the first aspect.

In a sixth aspect, an embodiment of the present application further provides a computer-readable storage medium, where the storage medium stores a computer program, and the computer program is executed by a processor to perform the steps of the network session account deployment method according to any one of the first aspect.

In a seventh aspect, an embodiment of the present application further provides a domain name server, including: a processor, a storage medium and a bus, wherein the storage medium stores program instructions executable by the processor, when the domain name server runs, the processor and the storage medium communicate with each other through the bus, and the processor executes the program instructions to execute the steps of the network session account deployment method according to any one of the second aspect.

In an eighth aspect, an embodiment of the present application further provides a computer-readable storage medium, where the storage medium stores a computer program, and the computer program is executed by a processor to perform the steps of the network session account deployment method according to any one of the second aspects.

The beneficial effect of this application is:

the application provides a network session account deployment method, a device, a terminal, a server and a storage medium, wherein at least two accounts are adopted to initiate a domain name query request to a domain name server, a domain name query result returned by the domain name server is received, at least two accounts are adopted to send a first registration subscription request to a first session server of a target internet protocol address in at least one internet protocol address, so that the first session server registers the two accounts and subscribes session resources, and receives a first registration subscription response sent by the first session server. According to the scheme provided by the application, different account numbers of the same network session terminal are registered in the same session server, so that the domain name server can conveniently carry out uniform deployment and management on the network session terminal.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.

Fig. 1 is a schematic structural diagram of a network session account deployment system according to an embodiment of the present disclosure;

fig. 2 is a schematic flowchart of a first network session account deployment method according to an embodiment of the present disclosure;

fig. 3 is a schematic flowchart of a second network session account deployment method according to an embodiment of the present application;

fig. 4 is a flowchart illustrating a third method for deploying a network session account according to an embodiment of the present application;

fig. 5 is a schematic flowchart of a fourth network session account deployment method according to an embodiment of the present application;

fig. 6 is a schematic flowchart of a fifth method for deploying a network session account according to an embodiment of the present application;

fig. 7 is a flowchart illustrating a sixth method for deploying a network session account according to an embodiment of the present application;

fig. 8 is a schematic flowchart of a seventh network session account deployment method according to an embodiment of the present application;

fig. 9 is an interaction diagram of a network session account deployment method according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a first network session account deployment device according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a second network session account deployment device according to an embodiment of the present application;

fig. 12 is a schematic diagram of a network session terminal according to an embodiment of the present application;

fig. 13 is a schematic diagram of a domain name server according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention.

Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In the description of the present application, it should be noted that if the terms "upper", "lower", etc. are used for indicating the orientation or positional relationship based on the orientation or positional relationship shown in the drawings or the orientation or positional relationship which is usually arranged when the product of the application is used, the description is only for convenience of describing the application and simplifying the description, but the indication or suggestion that the referred device or element must have a specific orientation, be constructed in a specific orientation and operation, and thus, cannot be understood as the limitation of the application.

Furthermore, the terms "first," "second," and the like in the description and in the claims, as well as in the drawings, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It should be noted that the features of the embodiments of the present application may be combined with each other without conflict.

The network session account deployment method provided in the embodiment of the present application is applied to a network session account deployment system having a network session account deployment function, and fig. 1 is a schematic structural diagram of the network session account deployment system provided in the embodiment of the present application, and as shown in fig. 1, the network session account deployment system includes: a network session terminal 10 configured with at least two accounts, a Domain Name server 20 (DNS), and two session servers 30. Fig. 1 shows only two session servers 30, but in actual practice there may be more session servers 30.

The network session terminal 10 is in communication connection with the domain name server 20 and the session server 30, respectively, and is configured to initiate a domain name query request to the domain name server, and initiate a registration subscription request to one session server by using at least two accounts based on a domain name query result.

The domain name server 20 is configured to resolve the domain name query request of the network session terminal 10 to obtain the internet protocol address of the session server 30, and return a domain name query result to the network session terminal 10, where the domain name query result includes: at least one internet protocol address.

The session server 30 is configured to receive a registration subscription request of at least two accounts in the network session terminal 10, accept or reject the registration subscription request, and return a registration subscription response to the network session terminal 10.

On the basis of the foregoing network session account deployment system, an embodiment of the present application further provides a network session account deployment method, where a network session terminal 10 in the foregoing network session account deployment system is applied, and fig. 2 is a schematic flow diagram of a first network session account deployment method provided in the embodiment of the present application, and as shown in fig. 2, the method may include:

s11: and initiating a domain name query request to a domain name server by adopting at least two account numbers.

Specifically, at least two accounts are pre-configured in the network session terminal 10, and when an account in the network session terminal 10 performs a session with an account in another network session terminal 10, a session connection needs to be established through the session server 30, so that in order to enable the account to perform a session with another account, the account needs to be registered in the session server first.

The network session terminal 10 initiates a domain name Query request DNS Query to a domain name server by using at least two accounts, where the domain name Query request includes: and the domain name query request is used for enabling the domain name server to analyze the target domain name to obtain at least one internet protocol address. After receiving the domain name query request including the target domain name, the domain name server 20 calls a domain name resolution function to resolve the target domain name to obtain at least one Internet Protocol Address (IP Address), and returns the at least one Internet Protocol Address to the network session terminal 10. For example, the target domain name may be a preconfigured Uniform Resource Locator (URL) address of the session server.

S12: and receiving a domain name query result returned by the domain name server.

Specifically, the network session terminal 10 receives a domain name query result returned by the domain name server 20, where the domain name query result includes: at least one internet protocol address.

S13: and sending a first registration subscription request to a first session server of a target internet protocol address in at least one internet protocol address by adopting at least two accounts, so that the first session server registers the two accounts and subscribes session resources.

Specifically, the network session terminal 10 selects a target internet protocol address from at least one internet protocol address, so that at least two accounts first send a registration signaling Register to a first session server corresponding to the target internet protocol address, so that the at least two accounts are registered on the first session server, and if the registration is successful, the first session server sends a registration response success signaling 200OK to the account which is successfully registered.

After receiving a response instruction of successful registration, at least two accounts send a subscription signaling Subscibe to the first session server, so that the at least two accounts subscribe the session resources on the first session server, and if the subscription is successful, the first session server sends a subscription response success signaling 200OK to the account which is successfully subscribed. For example, the protocol value Expires of the registration signaling Register is a number not equal to 0, and the protocol value Expires of the subscription signaling subscribe is also a number not equal to 0.

It should be noted that each account can send a subscription signaling subscribe to the first session server only after receiving a response instruction of successful registration.

S14: and receiving a first registration subscription response sent by the first session server.

Specifically, the first registration subscription response includes: and indicating information for indicating whether the at least two accounts register to subscribe successfully at the first session server.

If the at least two accounts register successfully on the first session server, each account receives a registration response success signaling 200OK sent by the first session server, and if the at least two accounts register unsuccessfully on the first session server, each account receives a registration failure response instruction sent by the first session server; if the at least two accounts subscribe successfully on the first session server, each account receives a subscription response success signaling 200OK sent by the first session server, and if the at least two accounts subscribe unsuccessfully on the first session server, each account receives a subscription failure response instruction sent by the first session server.

According to the network session account deployment method provided by the embodiment of the application, at least two accounts are adopted to initiate a domain name query request to a domain name server, a domain name query result returned by the domain name server is received, at least two accounts are adopted to send a first registration subscription request to a first session server of a target internet protocol address in at least one internet protocol address, so that the first session server registers the two accounts and subscribes session resources, and receives a first registration subscription response sent by the first session server. By the method provided by the embodiment of the application, different account numbers of the same network session terminal are registered in the same session server, so that the domain name server can conveniently carry out uniform deployment and management on the network session terminal.

On the basis of the foregoing embodiment, an embodiment of the present application further provides a network session account deployment method, where the domain name query result further includes: a priority of at least one internet protocol address; prior to S13 above, the method may further include:

and selecting a session server corresponding to the internet protocol address with the highest priority as a first session server according to the priority of at least one internet protocol address.

Specifically, to ensure that the session resources of the session servers 30 are balanced, the domain name server 20 further needs to determine the registration priority of each session server 30 according to the occupation situation of the session resources of the session servers 30, so as to determine the priority of the internet protocol address of each session server 30.

The network session terminal 10 selects a session server corresponding to an internet protocol address with the highest priority as a first session server according to the priority of at least one internet protocol address in the domain name query result returned by the domain name server 20, so that at least two accounts initiate a first registration subscription request to the first session server.

According to the network session account deployment method provided by the embodiment of the application, according to the priority of at least one internet protocol address, a session server corresponding to an internet protocol address with the highest priority is selected as a first session server. According to the method provided by the embodiment of the application, the session server is selected to register and subscribe the account number according to the priority, and the balance of session resources of the session server is ensured on the premise that all account numbers of one network session terminal are registered in the same session server.

On the basis of the foregoing embodiment, an embodiment of the present application further provides a network session account deployment method, and fig. 3 is a flowchart illustrating a second network session account deployment method provided in the embodiment of the present application, and as shown in fig. 3, the foregoing S13 includes:

s131: an account is adopted to send a registration subscription request of the account to a first session server.

Specifically, the network session terminal 10 selects an account from at least two accounts and sends a registration signaling Register to the first session server, so that the account is registered on the first session server, and if the registration is successful, the first session server sends a registration response success signaling 200OK to the account.

After receiving a response instruction of successful registration, the account sends a subscription signaling subscribe to the first session server, so that the account subscribes session resources on the first session server, and if the subscription is successful, the first session server sends a subscription response successful signaling 200OK to the account.

S132: and receiving a registration subscription response of an account sent by the first session server.

Specifically, if an account is successfully registered on the first session server, the account receives a registration response success signaling 200OK sent by the first session server, and if the account is unsuccessfully registered on the first session server, the account receives a registration failure response instruction sent by the first session server.

If the account number successfully subscribes on the first session server, the account number receives a subscription response success signaling 200OK sent by the first session server, and if the account number unsubscribes on the first session server, the account number receives a subscription failure response instruction sent by the first session server.

S133: and if the registration subscription response of one account indicates the successful registration subscription of the account, adopting other accounts to send registration subscription requests of other accounts to the first session server.

Specifically, if an account successfully registers in the first session server and completes subscription of session resources, other accounts on the network session terminal 10 also send a subscription registration request of other accounts to the first session server. The subscription process for registration of other accounts is the same as the subscription process for registration of one account in S131 to S132, and is not described herein again.

On the basis of any one of the foregoing embodiments, an embodiment of the present application further provides a network session account deployment method, where if the indication information indicates that the registration subscription of at least two accounts is successful, the first registration subscription response further includes: the registration renewal duration of at least two accounts. Fig. 4 is a flowchart illustrating a third method for deploying a network session account according to an embodiment of the present application, where as shown in fig. 4, the method may further include:

s21: and if the registration duration of the first account in the at least two accounts is expired, the first account is adopted to send the first registration request to the first session server again.

Specifically, in order to avoid that the first account occupies the session resources of the first session server because the account does not establish a session link with the accounts on other session servers for a long time after the account is registered in the first session server, the duration for which the first account can be registered on the first session server is indicated by configuring the registration duration for the first account, and after the registration duration expires, the first account needs to initiate registration to the first session server again.

The registration renewal duration of each account may be set when the account is configured on the network session terminal 10, or may be set on the session server 30 for the registration renewal duration of the account registered to the session server 30. If the registration duration is set on the session server 30, the first registration subscription response returned by the session server 30 to the network session terminal 10 further includes: the registration renewal duration of at least two accounts.

S22: and receiving a first registration response sent by the first session server.

Specifically, the first registration response includes: and indicating information whether the first account is successfully registered in the first session server. If the first account is successfully registered on the first session server, the indication information is a registration response success signaling 200OK sent by the first session server, and if the first account is unsuccessfully registered on the first session server, the indication information is a registration failure response instruction sent by the first session server.

S23: and if the first registration response indicates that the first session server is in a down state, sending a second registration subscription request to a second session server of another target internet protocol address in the at least one internet protocol address by using the first account, so that the second session server registers the first account and subscribes session resources.

Specifically, if the first account is not registered in the first session server, the registration response of the first account indicates that the first session server is in a down state, where the down state indicates that the account registered in the first session server has reached the threshold of the number of accounts, at this time, the network session terminal 10 selects another target internet protocol address from at least one internet protocol address, so that the first account sends a registration subscription request to a second session server of the another target internet protocol address, so that the second session server registers the first account and subscribes session resources. The priority of the second session server is lower than that of the first session server, the first session server is used as a main session server, the second session server is used as a standby session server, and the process of switching from the session server with high priority to the session server with low priority is called failover.

At this time, because the first session server is in a down state, the first account does not need to initiate a deregistration request and a unsubscribe request to the first session server, and can directly send a registration subscription request to the second session server, and the process of sending the registration subscription request to the second session server by the first account is the same as the process of sending the registration subscription request to the first session server by the first account in S13-S14, which is not described herein again.

In an optional implementation manner, if the first account fails to register on the first session server, the first account is adopted to send the first registration request to the first session server again for multiple times, and if the registration requests all fail for multiple times, it is determined that the first session server is in a down state.

S24: and receiving a second registration subscription response sent by the second session server.

Specifically, the second registration subscription response includes: and the indication information is used for indicating whether the first account is registered in the second session server and subscribed successfully. The specific indication information is the same as the content of S14, and is not described herein again.

In an alternative embodiment, the method may further comprise:

and if the first account number is detected to finish registration and subscription of session resources in the second session server, sending a third registration subscription request to the second session server by adopting other account numbers, so that the second session server registers other account numbers and subscribes session resources, and receiving a third registration subscription response sent by the second session server.

Specifically, the registration renewal duration of the first account and the other accounts may be different, and if the registration renewal duration of the first account is shorter than the registration renewal duration of the other accounts, it is detected that the first session server is down when the first account registers for renewal with the first session server, and since the other accounts are also registered on the first session server, in order to ensure effective use of the other accounts, the other accounts are also registered in the second session server.

The network session terminal 10 has an account management module, and the first account reports account status information to the account management module, where the account status information includes: the account number code and the internet protocol address of the session server to which the account number is registered.

When the first account number finishes registration and subscription of session resources in the second session server, the internet protocol address of the session server registered by the account number in the account number state information changes, and if the account number management module detects that the internet protocol address of the session server registered by the account number changes, other account numbers registered in the same session server with the first account number are triggered to send a third registration subscription request to the second session server, so that the second session server registers other account numbers and subscribes session resources. The process of sending the registration subscription request to the second session server by the other account is the same as the process of sending the registration subscription request to the first session server by the first account in S13-S14, which is not described herein again.

According to the network session account deployment method provided by the embodiment of the application, if the registration duration of a first account in at least two accounts is expired, the first account is adopted to send a registration request of the first account to a first session server again, a registration response of the first account sent by the first session server is received, and if the registration response of the first account indicates that the first session server is in a down state, the first account is adopted to send a second registration subscription request to a second session server of another target internet protocol address in at least one internet protocol address, so that the second session server registers the first account and subscribes session resources; and if the first account is detected to complete registration and subscription of session resources in the second session server, sending a third registration subscription request to the second session server by adopting other accounts, so that the second session server registers other accounts and subscribes session resources. By the method provided by the embodiment of the application, the registration can be continued again on the first account, but when the first session server is in a downtime state, the first account is switched to the second session server, and other accounts are simultaneously triggered to be synchronously switched to the second session server, so that the problem that the first account and other accounts cannot be used due to the downtime of the session server is avoided, and the effective utilization rate of the accounts is improved.

On the basis of the foregoing embodiment, an embodiment of the present application further provides a network session account deployment method, where the first registration response includes: a back-off time of the first account. Fig. 5 is a flowchart illustrating a fourth network session account deployment method provided in the embodiment of the present application, and as shown in fig. 5, the method may further include:

s31: and if the backspacing time of the first account is reached, the first account is adopted to send a second registration request to the first session server again.

Specifically, the back-off time is used to indicate a time for switching back to the first session server again after the first account is switched from the first session server to the second session server, and the back-off time of the account may be set when the account is configured in the network session terminal 10, or may be set in the second session server.

After the first account is registered to the second session server, the network session terminal 10 starts timing, and after the rollback time of the first account is reached, the network session terminal 10 uses the first account to send a second registration request to the first session server again. The process of switching from a low priority session server to a high priority session server is called failback.

It should be noted that, if the rollback time is 0, the first account is switched to another session server only when the second session server is in the down state, otherwise, the switching is not performed.

S32: and receiving a second registration response sent by the first session server.

Specifically, the second registration response includes: and indicating information whether the first account is successfully re-registered in the first session server. If the first account number is successfully re-registered on the first session server, the indication information is a registration response success signaling 200OK sent by the first session server, and if the first account number is failed to re-register on the first session server, the indication information is a registration response failure instruction sent by the first session server.

S33: and if the second registration response indicates that the state of the first session server is recovered and the first account registration is successful, adopting the first account to sequentially send a unsubscribe request and a deregister request to the second session server so that the second session server sequentially unsubscribes and deregisters the session resources of the first account.

Specifically, if the indication information is the registration response success signaling 200OK sent by the first session server, indicating that the state of the first session server is recovered, and the first account is successfully re-registered on the first session server, at this time, the network session terminal 10 needs to send the unsubscribe signaling unRegister to the second session server by using the first account, so that the second session server unsubscribes the session resources of the first account.

After unsubscribing is successful, the second session server returns unSubscribe response success signaling 200OK to the network session terminal 10, and then the network session terminal 10 sends unregistering signaling unSubscribe to the second session server by using the first account, so that the second session server performs account unregistration on for the first account.

S34: and sending the subscription request to the first session server again by adopting the first account.

Specifically, after the unregistering is successful, the second session server returns an unregistering response success signaling 200OK to the network session terminal 10, and then the network session terminal 10 sends a subscription request to the first session server again by using the first account, so that the first session server re-subscribes the session resource to the first account.

S35: and receiving a subscription response sent by the first session server.

Specifically, the subscription response includes: and indicating information used for indicating whether the first account is subscribed successfully at the first session server. If the first account number successfully re-subscribes on the first session server, the indication information is a registration response success signaling 200OK sent by the first session server, and if the first account number fails to re-subscribe on the first session server, the indication information is a registration response failure instruction sent by the first session server.

According to the network session account deployment method provided by the embodiment of the application, if the rollback time of the first account is up, the first account is adopted to send a second registration request to the first session server again, a second registration response sent by the first session server is received, if the second registration response indicates that the state of the first session server is recovered and the first account is successfully registered, the first account is adopted to send a unsubscribe request and a deregister request to the second session server in sequence, so that the second session server unsubscribes session resources and unregisters accounts to the first account in sequence, the first account is adopted to send a subscription request to the first session server again, and a subscription response sent by the first session server is received. The method provided by the embodiment of the application can re-register the first account to the first session server when the rollback time is up and the state of the first session server is recovered.

On the basis of the foregoing embodiment, an embodiment of the present application further provides a network session account deployment method, and fig. 6 is a flowchart illustrating a fifth network session account deployment method provided in the embodiment of the present application, and as shown in fig. 6, the method may further include:

s41: and if the first subscription response indicates that the first account number is successfully subscribed, sequentially adopting other account numbers to sequentially send a unsubscribe request and a deregistration request to the second session server, so that the second session server sequentially unsubscribes session resources and deregisters the account numbers to the other account numbers.

Specifically, after the first account is successfully re-registered in the first session server, because the account status information of the first account in the account management module in the network session terminal 10 changes, another account is triggered to re-initiate a registration subscription request to the first session server.

At this time, the second session server is still in a normal working state, and other accounts need to send an unsubscribe request and a deregistration request to the second session server first, so that the second session server performs unsubscribe and account deregistration on session resources for other accounts in sequence. The process of sending the unsubscribe request and the deregistration request to the second session server by the other account is the same as the process of sending the unsubscribe request and the deregistration request to the second session server by the first account in S33, and details are not described herein.

S42: and adopting other accounts to resend the fourth registration subscription request to the first session server.

Specifically, after the other account unsubscribes and deregisters successfully on the second session server, the network session terminal 10 sends the fourth registration subscription request to the first session server again by using the other account. The process of the other accounts retransmitting the registration subscription request to the first session server is the same as the process of the first account transmitting the registration subscription request to the first session server in S13-S14, which is not described herein again.

S43: and receiving a fourth registration subscription response sent by the first session server.

Specifically, the fourth registration subscription response sent by the first session server and received by the network session terminal 10 is the same as the first registration subscription response sent by the first session server and received in the above step S14, which is not described herein again.

According to the network session account deployment method provided by the embodiment of the application, if the first subscription response indicates that the first account is subscribed successfully, other accounts are sequentially adopted to sequentially send the unsubscribe request and the deregister request to the second session server, so that the second session server sequentially unsubscribes and deregisters session resources for other accounts, the other accounts are adopted to re-send the fourth registration subscription request to the first session server, and the fourth registration subscription response sent by the first session server is received. By the method provided by the embodiment of the application, when the first account returns to the first session server, other accounts can be triggered to be synchronously switched to the first session server, so that different accounts of the same network session terminal are always registered in the same session server, and the domain name server can conveniently carry out uniform deployment and management on the network session terminal.

On the basis of the foregoing network session account deployment system, an embodiment of the present application further provides a network session account deployment method, where a domain name server 20 in the foregoing network session account deployment system is applied, and fig. 7 is a schematic flowchart of a sixth network session account deployment method provided in the embodiment of the present application, and as shown in fig. 7, the method may include:

s51: receiving domain name inquiry requests of at least two accounts sent by a network session terminal.

Specifically, the domain name server 20 is communicatively connected to the network session terminal 10 to receive domain name query requests of at least two accounts sent by the network session terminal 10. The domain name query request includes: the target domain name.

S52: and resolving the target domain name to obtain at least one internet protocol address.

Specifically, after receiving the domain name query request including the target domain name, the domain name server 20 calls a domain name resolution function to resolve the target domain name, so as to obtain at least one internet protocol address.

S53: and returning a domain name query result to the network session terminal.

Specifically, the domain name query result obtained by the analysis is returned to the network session terminal 10, and the domain name query result includes: and the domain name query result is used for enabling the network session terminal to send a first registration subscription request to a first target session server of a target internet protocol address in at least one internet protocol address by adopting at least two account numbers, so that the first target session server registers the two account numbers and subscribes session resources.

The network session account deployment method provided by the embodiment of the application receives domain name query requests of at least two accounts sent by a network session terminal, analyzes a target domain name to obtain at least one internet protocol address, and returns a domain name query result to the network session terminal. By the method provided by the embodiment of the application, the domain name is inquired for a plurality of account numbers in the same network session terminal, and the domain name inquiry result is uniformly returned, so that the workload of a domain name server is reduced, and the working efficiency is improved.

In an optional implementation manner, fig. 8 is a schematic flowchart of a seventh network session account deployment method provided in an embodiment of the present application, and as shown in fig. 8, the step S51 includes:

s511: and sequentially receiving domain name query requests of at least two accounts sent by the network session terminal.

The S52 includes:

s521: and under the domain name query process of the account corresponding to the received first domain name query request, analyzing the target domain name to obtain at least one internet protocol address.

S522: and suspending the domain name query process of other accounts.

Specifically, since the network session terminal 10 sequentially sends the domain name query requests by using at least two account numbers, the domain name server starts to perform domain name query after receiving the domain name query request sent by the first account number, and at this time, if the domain name query requests sent by other account numbers are the update process for the same target domain name, the domain name query processes of other account numbers are suspended PENDDING DNS, so that the domain name server only needs to perform sequential domain name query for the same target domain name.

After the domain name query process of other account numbers is suspended, the domain name server performs domain name query on the account number corresponding to the first domain name query request, returns the domain name query result to the account number corresponding to the first domain name query request, and informs the other account numbers of the domain name query result by the account number corresponding to the first domain name query request.

The network session account deployment method provided by the embodiment of the application sequentially receives domain name query requests of at least two accounts sent by a network session terminal, analyzes a target domain name to obtain at least one internet protocol address under a domain name query process of an account corresponding to the received first domain name query request, and suspends domain name query processes of other accounts. According to the method provided by the embodiment of the application, when a plurality of accounts initiate query requests to the same target domain name, only the first domain name query request is subjected to domain name resolution, and the suspension operation is performed on the domain name query processes of other accounts, so that only sequential domain name resolution actions are performed on the same target domain name, the workload of a domain name server is reduced, and the working efficiency is improved.

In an alternative embodiment, prior to S53, the method may further include:

the priority of the at least one internet protocol address is calculated according to the session resource occupancy of the at least one session server.

Specifically, to ensure the session resources of the session servers 30 are balanced and avoid the situation that a plurality of network session terminals register to the same session server, the domain name server 20 may rank the registration priority of each session server 30 according to the occupation situation of the session resources of the session servers, so as to determine the priority of the internet protocol address of each session server 30. The domain name query result further comprises: a priority of at least one internet protocol address.

According to the network session account deployment method provided by the embodiment of the application, the priority of at least one internet protocol address is calculated according to the session resource occupancy rate of at least one session server. By the method provided by the embodiment of the application, the account numbers of a plurality of network session terminals can be prevented from being registered to the same session server, and the session resources of the session server are ensured to be balanced.

Fig. 9 is an interaction schematic diagram of a network session account deployment method provided in an embodiment of the present application, where the interaction process of network session account deployment among a first account, a second account, a domain name server, a first session server, and a second session server in a network session terminal is shown, and a specific deployment method flow refers to fig. 2 to fig. 8, which is not described herein again.

On the basis of the foregoing embodiment, an embodiment of the present application further provides a network session account deployment device, where the network session terminal 10 in the network session account deployment system is applied, and fig. 10 is a schematic structural diagram of a first network session account deployment device provided in the embodiment of the present application, and as shown in fig. 10, the device may include:

a request initiating module 101, configured to initiate a domain name query request to a domain name server by using at least two accounts, where the domain name query request includes: a target domain name; the domain name query request is used for enabling a domain name server to analyze a target domain name to obtain at least one internet protocol address;

the result receiving module 102 is configured to receive a domain name query result returned by the domain name server, where the domain name query result includes: at least one internet protocol address;

a first registration subscription request module 103, configured to send a first registration subscription request to a first session server of a target internet protocol address in at least one internet protocol address by using at least two accounts, so that the first session server registers the two accounts and subscribes to session resources;

a first registration subscription response module 104, configured to receive a first registration subscription response sent by the first session server, where the first registration subscription response includes: and indicating information for indicating whether the at least two accounts register to subscribe successfully at the first session server.

Optionally, the domain name query result further includes: a priority of at least one internet protocol address; before the first registration subscription request module 103, the apparatus further includes:

and the session server selection module is used for selecting the session server corresponding to the internet protocol address with the highest priority as the first session server according to the priority of at least one internet protocol address.

Optionally, the first registration subscription request module 103 includes:

a first registration subscription request unit, configured to send a registration subscription request of an account to a first session server by using the account;

the first registration subscription response unit is used for receiving a registration subscription response of an account sent by the first session server;

and the second registration subscription request unit is used for sending registration subscription requests of other accounts to the first session server by adopting other accounts if the registration subscription response of one account indicates successful registration subscription of one account.

Optionally, if the indication information indicates that the registration and subscription of the at least two accounts are successful, the first registration and subscription response further includes: registration renewal duration of at least two accounts; the device also includes:

the first registration request module is used for sending a first registration request to the first session server again by adopting the first account number if the registration continuation duration of the first account number in the at least two account numbers expires;

the second registration subscription request module is used for sending a second registration subscription request to a second session server of another target internet protocol address in the at least one internet protocol address by using the first account if the first registration response indicates that the first session server is in a down state, so that the second session server registers the first account and subscribes session resources;

Optionally, the apparatus further comprises:

a third registration subscription request module, configured to send a third registration subscription request to the second session server by using another account if it is detected that the first account completes registration and subscription of session resources in the second session server, so that the second session server performs registration and subscription of session resources for the other account;

Optionally, the first registration response includes: the rollback time of the first account; the device also includes:

the second registration request module is used for sending a second registration request to the first session server again by adopting the first account if the rollback time of the first account is reached;

the first de-registration subscription module is used for sending a de-subscription request and a de-registration request to the second session server in sequence by adopting the first account if the second registration response indicates that the state of the first session server is recovered and the first account is successfully registered, so that the second session server can perform de-subscription and account de-registration of session resources on the first account in sequence;

the subscription request module is used for sending a subscription request to the first session server again by adopting the first account;

Optionally, the apparatus further comprises:

the second unsubscribe subscription module is used for sequentially adopting other account numbers to sequentially send a unsubscribe request and a deregister request to the second session server if the first subscription response indicates that the first account number is successfully subscribed, so that the second session server can sequentially unsubscribe session resources and deregister the account numbers to the other account numbers;

the fourth registration subscription module is used for sending a fourth registration subscription request to the first session server again by adopting other account numbers;

On the basis of the foregoing embodiment, an embodiment of the present application further provides a network session account deployment device, where the domain name server 20 in the network session account deployment system is applied, and fig. 11 is a schematic structural diagram of a second network session account deployment device provided in the embodiment of the present application, and as shown in fig. 11, the device may include:

a request receiving module 201, configured to receive a domain name query request of at least two accounts sent by a network session terminal, where the domain name query request includes: a target domain name;

the resolution module 202 is configured to resolve the target domain name to obtain at least one internet protocol address;

a result returning module 203, configured to return a domain name query result to the network session terminal, where the domain name query result includes: and the domain name query result is used for enabling the network session terminal to send a first registration subscription request to a first target session server of a target internet protocol address in at least one internet protocol address by adopting at least two account numbers, so that the first target session server registers the two account numbers and subscribes session resources.

Optionally, the request receiving module 201 is configured to sequentially receive domain name query requests of at least two accounts sent by the network session terminal;

the parsing module 202 includes:

Optionally, before the result returns to the module 203, the apparatus further includes:

the priority calculation module is used for calculating the priority of at least one Internet protocol address according to the session resource occupancy rate of at least one session server; the domain name query result further comprises: a priority of at least one internet protocol address.

The above-mentioned apparatus is used for executing the method provided by the foregoing embodiment, and the implementation principle and technical effect are similar, which are not described herein again.

These above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), among others. For another example, when one of the above modules is implemented in the form of a Processing element scheduler code, the Processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

Fig. 12 is a schematic diagram of a network session terminal according to an embodiment of the present application, where the network session terminal 10 includes: a processor 11, a storage medium 12 and a bus, wherein the storage medium 12 stores program instructions executable by the processor 11, when the network session terminal 10 runs, the processor 11 communicates with the storage medium 12 through the bus, and the processor 11 executes the program instructions to execute the above-mentioned method embodiment applied to the network session terminal 10. The specific implementation and technical effects are similar, and are not described herein again.

Optionally, the present invention also provides a program product, such as a computer-readable storage medium, comprising a program which, when being executed by a processor, is adapted to carry out the above-mentioned embodiments of the method applied to the network session terminal 10.

Fig. 13 is a schematic diagram of a domain name server according to an embodiment of the present application, where the domain name server 20 includes: a processor 21, a storage medium 22 and a bus, the storage medium 22 storing program instructions executable by the processor 21, when the domain name server 20 is running, the processor 21 and the storage medium 22 communicate with each other via the bus, and the processor 21 executes the program instructions to execute the above-mentioned embodiment of the method applied to the domain name server 20. The specific implementation and technical effects are similar, and are not described herein again.

Optionally, the present invention also provides a program product, such as a computer-readable storage medium, comprising a program which, when being executed by a processor, is adapted to carry out the above-mentioned embodiment of the method applied to the domain name server 20.

In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and shall be covered by the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A network session account deployment method is characterized by comprising the following steps:

2. The method of claim 1, wherein the domain name query result further comprises: a priority of the at least one internet protocol address;

3. The method of claim 1, wherein sending a first registration subscription request to a first session server of a target one of the at least one internet protocol address using the two accounts comprises:

4. The method of claim 1, wherein if the indication information indicates that the at least two accounts are both successfully subscribed to be registered, the first subscription registration response further comprises: the registration renewal duration of the at least two account numbers; the method further comprises the following steps:

receiving a first registration response sent by the first session server;

5. The method of claim 4, wherein the method further comprises:

if the first account is detected to finish registration and subscription of session resources in the second session server, sending a third registration subscription request to the second session server by using other accounts, so that the second session server registers the other accounts and subscribes the session resources;

6. The method of claim 4, wherein the first registration response comprises: a back-off time of the first account; the method further comprises the following steps:

receiving a second registration response sent by the first session server;

and receiving a subscription response sent by the first session server.

7. The method of claim 6, wherein the method further comprises:

8. A network session account deployment method is characterized by comprising the following steps:

9. The method according to claim 8, wherein the receiving domain name query requests of at least two accounts sent by the network session terminal includes:

and suspending the domain name query process of other accounts.

10. The method of claim 8, wherein before returning the result of the domain name query to the network session terminal, the method further comprises:

11. A network session account deployment apparatus, the apparatus comprising:

the registration subscription module is used for sending a first registration subscription request to a first session server of a target internet protocol address in the at least one internet protocol address by adopting the at least two account numbers so as to enable the first session server to register the two account numbers and subscribe session resources;

a response receiving module, configured to receive a first registration subscription response sent by the first session server, where the first registration subscription response includes: and indicating information used for indicating whether the at least two accounts register subscription success at the first session server.

12. A network session account deployment apparatus, the apparatus comprising:

13. A network session terminal, comprising: a processor, a storage medium and a bus, wherein the storage medium stores program instructions executable by the processor, when the network session terminal runs, the processor communicates with the storage medium through the bus, and the processor executes the program instructions to execute the steps of the network session account deployment method according to any one of claims 1 to 7.

14. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, performs the steps of the network session account deployment method of any of claims 1 to 7.

15. A domain name server, comprising: a processor, a storage medium and a bus, the storage medium storing program instructions executable by the processor, the processor and the storage medium communicating via the bus when the domain name server is running, the processor executing the program instructions to perform the steps of the network session account deployment method according to any one of claims 8 to 10.

16. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, performs the steps of the network session account deployment method according to any one of claims 8 to 10.