CN107343285B

CN107343285B - Management equipment and equipment management method

Info

Publication number: CN107343285B
Application number: CN201610273716.8A
Authority: CN
Inventors: 王国才; 王国俊
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2016-04-28
Filing date: 2016-04-28
Publication date: 2022-05-13
Anticipated expiration: 2036-04-28
Also published as: CN107343285A; WO2017185934A1

Abstract

The invention provides a management device and a device management method, which are applied to a converged communication RCS system, and the management device is applied to the converged communication RCS system and is characterized by comprising a service processor, a database and a plurality of interfaces; the service processor is used for issuing configuration information to the RCS terminal through an access network, and the database is used for storing account opening information and/or configuration information of the RCS terminal; the interface is used for communicating with systems other than the management device in the RCS system. The management equipment is used for specially processing account opening and configuration acquisition or configuration receiving of the client, so that the network pressure of an RCS (remote control system) or BOSS (business operating system) system can be reduced, and meanwhile, the whole network structure is clear and convenient to manage.

Description

Management equipment and equipment management method

Technical Field

The present invention relates to the field of rcs (rich Communication services) converged Communication, and in particular, to a management device and a device management method.

Background

The RCS (Rich Communication services) system defines a group of service capabilities based on an IMS core network and an existing mobile network, and provides functions of enhanced contacts, content sharing, file transfer machine enhanced messages and the like for mobile terminal users.

Several main new service functions provided by the RCS service are as follows:

the enhanced address book is evolved based on the existing address book of the mobile terminal, and the new address book not only provides basic personal information of the user, but also adds richer functions, such as personal service capability display, triggering of various contact ways (voice, video sharing, file transmission, short messages and the like), personal communication intention display, personal images, personal messages, personal connection, network address book and the like.

Content sharing provides users with the ability to exchange or share files, videos, pictures, etc. during a call. The users can share the content during the circuit domain voice call, which requires the terminal and the network to be able to provide the communication capability of voice and data at the same time. Any party of the call can share the content, and can choose to accept or reject the sharing invitation, and the sharing content can be stored in the local terminal.

File transfer can occur when a user is talking, meeting or idle, the format of the exchanged files is not limited at all, and the file transfer and the talking have no mutual influence. The file receiver can choose to accept or reject the file transmission, and the operator can set the size of the file transmission content according to the requirement. The enhanced message function provides 1 to 1 and 1 to more chat functions for users besides the contents of short messages and multimedia messages of the traditional mobile network, and users can invite a third party to chat according to needs.

All the functions are realized based on RCS client software, mobile phone terminal hardware and user mobile phone numbers, the software or hardware information can be accessed and used with RCS service only by opening an account and registering in an IMS core network, and simultaneously, the IMS core network also needs to synchronize the network and service information (such as user gray information) to the RCS client in time, so that the RCS service can better realize and better improve the user experience. Such functions can be implemented in the RCS system itself or the BOSS system, but not only the complexity of the existing system is increased, but also the BOSS system is strongly associated with a specific service system and does not meet the requirements of the mobile service system

Disclosure of Invention

In view of the above technical problems, the present invention provides a management device and a device management method, which are used to solve the problem of complex service flow of the conventional RCS system.

The technical scheme provides a management device, which is applied to a converged communication RCS system and comprises a service processor, a database and a plurality of interfaces; the service processor is used for issuing configuration information to the RCS terminal through an access network, and the database is used for storing account opening information and/or configuration information of the RCS terminal; the interface is used for communicating with systems other than the management device in the RCS system.

And the service processor is further configured to receive an account opening request or a configuration issuing request or a configuration updating request sent by the RCS terminal before issuing configuration information to the RCS terminal.

The management equipment further comprises a load balancing server, and the load balancing server distributes the received account opening request or the issued configuration request or the updated configuration request sent by the RCS terminal to the corresponding service processors in a round-robin manner.

The access network comprises a Packet Switching (PS) domain access network or a wireless fidelity (WIFI) access network; the RCS terminal comprises a native client or an app client.

The management equipment is communicated with the BOSS system through a first interface; the management equipment is communicated with a Short Message Service Center (SMSC) gateway through a second interface; the management equipment communicates with a Session Border Controller (SBC) through a third interface; and the management equipment communicates with the security traversal gateway STG through a fourth interface.

When the RCS terminal does not open an account, the management equipment interacts with the BOSS through the first interface to complete an account opening process, and receives configuration information corresponding to the RCS terminal and sent by the BOSS.

The technical scheme also provides a device management method, which is applied to management devices in a converged communication RCS system and comprises the following steps:

the management equipment receives a configuration information issuing or updating request sent by a converged communication RCS terminal, wherein the RCS terminal is communicated with the management equipment through an access network;

if the RCS terminal has opened an account, the management equipment sends corresponding configuration information stored in a local database to the RCS terminal;

and if the RCS terminal does not open an account, the management equipment interacts with the BOSS system through the first interface to complete an account opening process, stores the configuration information sent by the BOSS system, and sends corresponding configuration information to the RCS terminal.

Wherein, the method also comprises:

after receiving an account opening success message sent by the BOSS system, the management device sends an activation request short message notification message to a Short Message Service Center (SMSC) gateway through a second interface, wherein the activation request short message notification message is used for requesting the SMSC gateway to send an account opening activation short message to the RCS terminal.

When the access network is a wireless fidelity (WIFI) access network and the RCS terminal is a native client, the method further comprises the following steps:

the management equipment receives a configuration information issuing or updating request of the RCS terminal through the WIFI access network;

when the request for issuing or updating the configuration information comprises token information and a configuration version number, the management equipment authenticates the token information;

under the condition that the authentication is passed, the management equipment issues configuration information to the RCS terminal according to the configuration version number;

under the condition that the authentication is not passed, the management equipment issues a response message containing cookie information to the RCS terminal and sends a dynamic password (OTP) request to an SMSC (short message service center), wherein the OTP request is used for triggering the SMSC to send a short message carrying OTP to the RCS terminal; the management equipment receives a configuration information request message retransmitted by the RCS terminal, the retransmitted configuration information issuing request message comprises the cookie information and the OTP, the cookie information is associated with the configuration information request issued by the RCS terminal last time, and after the OTP is verified, the configuration information is issued to the RCS terminal.

When the access network is a PS domain access network and the RCS terminal is an APP client, the method further includes:

the management equipment receives an account opening request sent by the RCS terminal;

according to the account opening request, the management equipment issues a response message containing cookie information to the RCS terminal;

when the response message indicates that the RCS terminal has opened an account, the management device sends corresponding configuration information to the RCS terminal after receiving a request which is sent by the RCS terminal and carries cookie information and issues or updates the configuration information;

when the response message indicates that the RCS terminal does not open an account, after receiving a configuration information issuing request which is sent by the RCS terminal and carries the cookie information, the management device interacts with the BOSS system through a first interface to complete an account opening process, stores account opening information and configuration information sent by the BOSS system, and sends corresponding configuration information to the RCS terminal.

When the access network is a WIFI wireless access network and the RCS terminal is an APP client, the method further comprises the following steps:

the management equipment receives a request of the RCS terminal for issuing or updating configuration information;

when the configuration information issuing or updating request comprises token information and an International Mobile Subscriber Identity (IMSI) authentication password, the management equipment judges whether the RCS terminal opens an account or not;

when the RCS terminal opens an account and the token information and the IMSI authentication password pass authentication, the management equipment sends corresponding configuration information stored in the database to the RCS terminal;

and when the RCS terminal does not open an account, the management equipment interacts with the BOSS system through the first interface to complete an account opening process, stores account opening information and configuration information sent by the BOSS system, and sends corresponding configuration information to the RCS terminal.

The management equipment and the equipment management method provided by the invention are independent of RCS and BOSS services, so that the skill meets the use requirement of the RCS services, the burden of the RCS and BOSS systems is reduced, and the network is simplified.

Drawings

FIG. 1 is a system framework diagram of a management device according to an embodiment of the present invention;

fig. 2 is a flow chart of opening an account and automatically acquiring configuration information after a PS domain of a Native terminal according to an embodiment of the present invention is accessed;

fig. 3 is a flowchart illustrating automatic acquisition of configuration information after WIFI access of a Native terminal according to an embodiment of the present invention;

fig. 4 is a flowchart illustrating automatic acquisition of configuration information after PS domain access of an APP terminal according to an embodiment of the present invention;

fig. 5 is a flowchart illustrating automatic acquisition of configuration information after WIFI access of an APP terminal according to an embodiment of the present invention.

Detailed Description

Example one

The embodiment of the invention provides a Management device, which is convenient to use, and temporarily sets a name DM (device Management System) to provide a user-level device Management function for an RCS (remote control system), so that a user has better RCS service experience.

The management device DM is applied to a converged communication RCS system and comprises a service processor, a database and a plurality of interfaces; the service processor is used for issuing configuration information to the RCS terminal through an access network, and the database is used for storing account opening information and/or configuration information of the RCS terminal; the interface is used for communicating with systems other than the management device in the RCS system.

As shown in fig. 1, a terminal refers to a terminal and a client (Native, App) that support converged communication service; the access network refers to PS domain wireless access or WIFI wireless access.

The DM is different for both traffic processing flows. And the native client or the app client accesses the IMS core network through the PS domain or accesses the IMS core network through WIFI.

The DM system needs to provide an interface with SBC (session border controller), STG (secure traversal gateway), BOSS Proxy (BOSS Proxy), and SMGW (short message gateway), which use SSH, SNMP, and HTTP, respectively.

The DM mainly provides the following four functions:

a Native client automatically opens an account and acquires a configuration flow under a PS domain;

a Native client automatically acquires a configuration (but not account opening) process under a WIFI environment;

the App client automatically opens an account and acquires a configuration flow in the PS domain;

and the App client automatically opens an account and acquires a configuration flow under the WIFI environment.

A service processor: the processor is responsible for processing the opening account and issuing configuration of the converged communication terminal. The service processor is realized by multiple modules, the service processing functions of each module are completely the same, and the load sharing of the service is realized. The account opening process is that the service processor interacts with the BOSS system, and an account is opened in the BOSS system, the service processor sends an account opening request to the BOSS system, wherein the request comprises information such as MSISDN, ue type, servicetype and the like; the BOSS system executes the account opening operation and then returns an account opening success message to the service processor, wherein the message contains account opening information and configuration information, and then the configuration information is stored in the database. Due to timeliness of the configuration information, the subsequent BOSS sends updated configuration information to the service processor at regular time, and when the client is powered on and the configuration is found to be overdue, the client actively requests to update the configuration.

A database: used for storing the relevant information after the client opens an account successfully. For the data processed by the DM, mainly the account opening information of the user, the data are single in nature and have no correlation with each other, so a non-relational database, such as MongoDB, can be used. Meanwhile, a sharing mode can be adopted to store data in different servers so as to support operation of massive data and high throughput. In order to ensure the safety of data, the Replica Set technology is adopted, so that the same data is simultaneously stored on at least two database servers, and the safety of the data is improved.

The system also comprises a load balancing server which is responsible for distributing the request message received by the access network to the corresponding service processor in a round-robin manner, namely, the request message can be used for opening an account or issuing a configuration request or updating the configuration request from the client to several DM service processors in a round-robin manner.

The selection strategy for SBC and STG also needs to be determined. The following strategy can be generally followed: the configuration information sent from the BOSS system may also include a URL of the RCS AS, which is the server address, or a URL of the STG or SBC. The RCS AS is a service platform for realizing RCS service; SBCs and STGs are network elements of an IMS core network, and an RCS client can implement an RCS service only through the IMS core network. For example, when the DM issues the server address, it issues the network element identifiers of 2 STGs and 2 SBCs, respectively, where the host name is selected according to a certain policy, and performs round selection from all existing STGs and from all existing SBCs. The round selection refers to selecting one SBC or STG among a plurality of SBCs or STGs according to a predetermined rule or by determining workload or round training of several SBCs or STGs. If a set of STGs or SBCs is permanently unavailable, the device hostname needs to be deleted at the DM. Because whether the STG or SBC is permanently unavailable can be judged only by people, and manual and automatic judgment through alarming and the like is unavailable, the management personnel can delete on the DM.

If a set of STGs or SBCs is temporarily unavailable, the terminal may initiate a query for a new address without maintenance on the DM.

In addition, in order to ensure the flexibility of selection, the configuration message sent by the DM to the terminal may further include an option of a priority relationship between the STG and the SBC, and the default is SBC priority. When a user is forced to access from an STG, STG priority may be set in the user's configuration information. The operation may be configured by the BOSS system and then sent to the service processor, or may be set in the DM.

After the terminal initiates an account opening request, the DM uses a protocol to initiate the account opening request to the BOSS. One of the following two communication protocols may be used between the BOSS and the DM:

the general protocol: SOAP over HTTP protocol. The initiator sends a request message by using an HTTP POST method and obtains a response message. The initiator serves as a SOAP/HTTP client, and the receiver serves as a server of the initiator.

And (4) safety protocol: SOAP over HTTPS protocol, using SSL2.0/3.0 transmission encryption. The receiving party provides the URL of access for the initiating party, and the initiating party sends a request message by using an HTTP POST method and obtains a response message. The initiator is used as a SOAP/HTTP client of the receiver, and the receiver is used as a SOAP/HTTP server of the initiator.

The account opening information comprises an MSISDN user mobile phone number, a terminal deployed RCS client type and an RCS service type; the configuration information includes the address of the STG or SBC, or the STG and SBC preference relationship, etc.

Namely, the account opening information mainly comprises the following contents: MSISDN, uetype, servicetype. MSISDN is the number of the user's mobile phone; the uetype represents whether the RCS client deployed by the terminal is a Native type or an APP type; the servicetype indicates whether a two-new or three-new service is opened. And secondly, new communication information is referred to, and thirdly, VoLTE service is newly added. The configuration information is typically provided by the BOSS, in the form of an XML file. The configuration information mainly contains the following contents in addition to the above-mentioned information: whether to automatically receive files, IM drawing capability, whether to automatically accept group chat invitations, maximum number of text bytes in a one-to-one session mode, maximum number of text bytes in a group chat mode, session timeout duration, maximum file transfer size, maximum group chat people group chat URI, and the like. Further, fields or contents may be added to the xml file of the configuration information to provide more corresponding functions. For example, the URLs of different access RCS AS, or STG, SBC, may be provided in the configuration, thereby allowing the user to access different RCS AS, or STG, SBC, implementing so-called grey-scale user functionality. The gray scale is to provide different functions for different users, and in this scheme, different access AS or SBC, STG are provided.

The account opening information is a basic condition that the user has RCS service capability, and the configuration information is a necessary condition that the user normally uses the RCS function.

The embodiment of the invention also provides a device management method, which is applied to the management device in the converged communication RCS system, wherein the management device receives a request for issuing or updating the configuration information sent by the converged communication RCS terminal, and the RCS terminal communicates with the management device through an access network;

The following describes each service flow and the DM processing procedure in detail with reference to the flow chart.

Example two

Fig. 2 is a flowchart for automatically acquiring PS domain account opening and configuration information (also referred to as configuration parameters) of a Native terminal according to an embodiment of the present invention.

The procedure of opening an account and automatically acquiring after the PS domain of the Native terminal is accessed is as follows:

s201: when a terminal supporting the converged communication service is started, a Native client initiates a request for automatic account opening and configuration, and the terminal sends a get request to a DM;

s202: GGSN/PGW inserts msisdn and IMSI information in http message;

s203, S204, S205: if the user opens an account, returning an HTTPS 200ok response to the terminal and carrying the configuration parameters;

s206: after receiving the request, the DM judges that 200ok is returned to the UE without opening an account, and the message carries cookie information;

s207: the terminal initiates an https request for obtaining configuration;

s208: after receiving the HTTPS request of the UE, the DM returns an HTTPS503Retry after response to the terminal if the user does not open an account;

s209: carrying out interactive execution on an opening process with the BOSS; the DM checks whether the MSISDN has "+" and if not, the MSISDN is added and then sent to the BOSS;

s210: after the account is opened, the DM sends a short message request to the SMSC gateway; in the process, the BOSS system needs to send account opening success response information and configuration information to the DM;

s211: SMSC sends down the short message notice of activation;

s212 to S215: the terminal restarts the acquisition configuration flow.

EXAMPLE III

As shown in fig. 3, the flowchart is a flowchart for automatically acquiring configuration information after WIFI access of a Native terminal according to an embodiment of the present invention;

the automatic acquiring process after the Native terminal WIFI access is as follows:

s301: a DM (direct memory access) initiates an HTTP request by a Native terminal at WiFi;

s302: the DM returns an HTTP 511Network Authentication Error rejection response;

s303: after receiving the 511 response, the Native terminal initiates an HTTPS message to the DM under WiFi access, wherein the HTTPS message needs to contain token information;

s304: and the DM judges whether the token is valid or not, if so, the authentication is passed, and judges whether the configuration is issued to the terminal or not according to the configuration version number, and the process is ended, wherein the configuration version number is a parameter ver brought by the terminal. The RCS client is installed, the version number of the RCS client cannot be changed, but ver changes;

s305: if token is invalid, DM sends 200 a cookie;

s306: the DM acquires MSISDN of the user according to user data such as IMSI and the like stored by the DM and initiates an OTP request to the SMSC for the terminal;

s307: SMSC sends short message to terminal, which carries OTP (one Time passed);

s308: the terminal receives the short message, automatically intercepts the OTP, and re-initiates an HTTPS request to the DM, wherein the HTTPS request carries Cookie and OTP information;

s309: the DM is associated with the previous request through the Cookie, the OTP password is sent to the mobile phone after verification, the mobile phone client is automatically filled or manually filled, the DM judges in the process of obtaining configuration, and then configuration data including newly distributed Token is sent to the terminal.

Example four

As shown in fig. 4, it is a flowchart for automatically acquiring configuration information after PS domain access of an APP terminal according to an embodiment of the present invention;

the automatic acquisition process after the PS domain access of the APP terminal is as follows:

s401: the terminal initiates a request for automatic account opening and configuration when starting, and the UE sends an HTTP GET request to the DM;

s402: GGSN/PGW inserts MSISDN and IMSI information in HTTP GET message;

s403: after receiving the request, the DM judges that the account is opened and sends back HTTP 200ok to the UE, and the message carries cookie information;

s404: the terminal initiates HTTPS GET, and requests DM for obtaining configuration, wherein the configuration contains cookie information;

s405: DM returns terminal configuration parameter to terminal;

s406: after receiving the request, the DM judges that the User Equipment (UE) does not open an account and returns HTTP 200ok, wherein the message carries cookie information;

s407: the terminal initiates HTTPS GET, and requests DM for obtaining configuration, wherein the configuration contains cookie information;

s408: the DM initiates an account opening request to the BOSS after receiving the HTTP GET request of the UE;

s409: after the BOSS account opening is successful, a response is returned to the DM; DM returns the terminal configuration parameter to the terminal.

EXAMPLE five

As shown in fig. 5, a flowchart is shown for automatically acquiring configuration information after WIFI access of an APP terminal according to an embodiment of the present invention;

the automatic acquisition process after the WIFI access of the APP terminal is as follows:

s501: the DM initiates an HTTP request when the APP terminal is in WiFi;

s502: the DM returns an HTTP 511Network Authentication Error rejection response;

s503: the terminal acquires a user identity IMSI authentication password from the unified authentication platform;

s504: the unified authentication platform returns the identity and IMSI authentication password to the terminal user;

s505: the terminal carries imsi and token to initiate an HTTPS request to the DM, if the user does not open an account, the DM triggers automatic account opening, and after the account opening is successful, configuration is returned to the terminal;

s506: if the user has opened an account, the DM returns the configuration directly to the terminal.

EXAMPLE six

There is also a business scenario. When the user successfully opens the account and successfully performs the RCS service, the RCS client in the terminal already stores the configuration information. There is a validity period field in this information. When the RCS client finds that the validity period is expired, it will actively initiate a process of acquiring the update configuration to the DM. The active acquisition update configuration has four ways according to different client types and access environments, but is similar to the automatic acquisition configuration process (although an automatic account opening process is lacked), and is not described again.

The above description only considers the basic functions of the DM, such as the functions of registering and updating an account or acquiring configuration information of two types of RCS clients (terminals) in two different access network scenarios, but the DM may also support operations such as charging. And is

The above is the main business process of the scheme. The DM system is used for specially processing the account opening and configuration acquisition or configuration receiving of the client, so that the network pressure of the RCS system or the BOSS system can be reduced, and the whole network structure is clear and convenient to manage.

In another embodiment, a storage medium is provided, in which the software is stored, and the storage medium includes but is not limited to: optical disks, floppy disks, hard disks, erasable memory, etc.

It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A management device is applied to a converged communication RCS system, is independent of the RCS and BOSS systems, and is characterized by comprising a service processor, a database and a plurality of interfaces; the service processor is used for issuing configuration information to the RCS terminal through the access network, and the database is used for storing account opening information and/or configuration information of the RCS terminal; the interface is used for communicating with systems other than the management device in the RCS system.

2. The management device according to claim 1, wherein the service processor is further configured to receive an account opening request or a configuration issuing request or a configuration updating request sent by the RCS terminal before issuing configuration information to the RCS terminal.

3. The management device according to claim 2, wherein there are a plurality of service processors, and the management device further includes a load balancing server, and the load balancing server distributes, in a round-robin manner, the received account opening request, or the received configuration issuing request, or the received configuration updating request sent by the RCS terminal to the corresponding service processor.

4. The management device of claim 1, wherein the access network comprises a packet-switched PS domain access network or a WIFI access network; the RCS terminal comprises a native client or an app client.

5. The management device of claim 1, wherein the management device communicates with a BOSS system through a first interface; the management equipment is communicated with a Short Message Service Center (SMSC) gateway through a second interface; the management equipment communicates with a Session Border Controller (SBC) through a third interface; and the management equipment communicates with the security traversal gateway STG through a fourth interface.

6. The management device according to claim 2, wherein when the RCS terminal does not open an account, the management device interacts with a BOSS system through a first interface to complete an account opening procedure, and receives configuration information corresponding to the RCS terminal sent by the BOSS system.

7. A device management method is applied to a management device in a converged communication RCS system, the management device is independent of the RCS and BOSS systems, and the method is characterized by comprising the following steps:

8. The device management method of claim 7, wherein the access network comprises a packet switched PS domain access network or a WIFI access network; the RCS terminal comprises a native client or an app client.

9. The device management method according to claim 8, wherein when the access network is a packet switched PS domain access network and the RCS terminal is a native client, the method further comprises:

after receiving the successful account opening message sent by the BOSS system, the management device sends a request activation short message notification message to a Short Message Service Center (SMSC) gateway through a second interface, wherein the activation short message notification message is used for requesting the SMSC gateway to send an account opening activation short message to the RCS terminal.

10. The device management method according to claim 8, wherein when the access network is a WIFI access network and the RCS terminal is a native client, the method further comprises:

under the condition that authentication is passed, the management equipment issues configuration information to the RCS terminal according to the configuration version number;

11. The device management method according to claim 8, wherein when the access network is a PS domain access network and the RCS terminal is an APP client, the method further comprises:

12. The device management method according to claim 8, wherein when the access network is a WIFI radio access network and the RCS terminal is an APP client, the method further comprises: