WO2019015382A1 - 一种别名管理方法及设备 - Google Patents

一种别名管理方法及设备 Download PDF

Info

Publication number
WO2019015382A1
WO2019015382A1 PCT/CN2018/086754 CN2018086754W WO2019015382A1 WO 2019015382 A1 WO2019015382 A1 WO 2019015382A1 CN 2018086754 W CN2018086754 W CN 2018086754W WO 2019015382 A1 WO2019015382 A1 WO 2019015382A1
Authority
WO
WIPO (PCT)
Prior art keywords
alias
user
identifier
function entity
management function
Prior art date
Application number
PCT/CN2018/086754
Other languages
English (en)
French (fr)
Inventor
葛翠丽
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2020501169A priority Critical patent/JP7036899B2/ja
Priority to EP18836132.3A priority patent/EP3644556B1/en
Priority to KR1020217039641A priority patent/KR20210149249A/ko
Priority to BR112020000874-5A priority patent/BR112020000874A2/pt
Priority to KR1020207004308A priority patent/KR102336553B1/ko
Publication of WO2019015382A1 publication Critical patent/WO2019015382A1/zh
Priority to US16/742,306 priority patent/US11483315B2/en
Priority to JP2022032738A priority patent/JP7260230B2/ja
Priority to US17/953,077 priority patent/US20230018257A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/30—Managing network names, e.g. use of aliases or nicknames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/30—Managing network names, e.g. use of aliases or nicknames
    • H04L61/3015—Name registration, generation or assignment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/062—Network architectures or network communication protocols for network security for supporting key management in a packet data network for key distribution, e.g. centrally by trusted party
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
    • G06F13/4204—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus
    • G06F13/4221—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus being an input/output bus, e.g. ISA bus, EISA bus, PCI bus, SCSI bus
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/30—Types of network names
    • H04L2101/365—Application layer names, e.g. buddy names, unstructured names chosen by a user or home appliance name
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/28—Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration

Definitions

  • the embodiment of the present invention relates to the field of communications, and in particular, to an alias management method and device.
  • the 3rd Generation Partnership Project (3GPP) standardizes a set of emergency mission services based on the 3GPP Long Term Evolution (LTE) system to support cluster communication in public security scenarios.
  • the emergency mission service may include basic services such as the Mission Critical Push To Talk (MCPTT) service, the Mission Critical Data (MCData) service, and the Mission Critical Video (MCVideo) service. Based on these basic services, other services such as railway applications and enterprise applications can also be constructed.
  • MCPTT Mission Critical Push To Talk
  • MCData Mission Critical Data
  • MCVideo Mission Critical Video
  • each user has an identity for uniquely identifying his or her identity.
  • the same user may use the same identifier or different identifiers for different services.
  • Each identifier of a user may correspond to one or more aliases.
  • An alias is a name other than the official legal or normative name of a person, thing, thing, or industry. It can be used in both written and spoken language. An alias can also be called a nickname. In the prior art, an alias refers to a name other than the identity of the user.
  • alias of a phone number format such as +86 130 xxxx xxxx
  • URI Uniform Resource Identifier
  • the alias of the text or symbol of the memory the specific can be combined with the user's identity, or the work unit, or location and other information to name, such as G20 train conductor, G20 ticket seller, Beijing South Station dispatcher.
  • the alias in the prior art is pre-configured in the user profile when the system is deployed.
  • the management of the alias such as registration, activation, deactivation, takeover, etc.
  • the user profile configuring the alias must be performed first.
  • Corresponding processing results in low efficiency of managing aliases and heavy system processing burden. For example, when a user needs to register a new alias, the user profile must be modified or a new user profile must be configured to complete the registration of the alias.
  • the embodiment of the present invention provides an alias management method and device, which solves the problem of low efficiency of alias management and heavy processing load of the system.
  • a first aspect of the embodiments of the present application provides an alias management method, including:
  • the alias management function entity receives a registration request message sent by the first client, where the registration request message includes the identifier of the user and the name of the alias requesting registration; when the user has the alias registration authority, the alias management function entity sends the registration to the first client.
  • the registration response message includes the identity of the user, the name of the alias that was successfully registered, and the identity of the alias that was successfully registered.
  • the alias management function entity receives the registration request message sent by the first client, including the identifier of the user and the name of the alias requested to be registered, and when the user has the alias registration authority, the alias management function entity The first client sends a registration response message including the identity of the user, the name of the registered successful alias, and the identifier of the registered successful alias. After receiving the registration request message sent by the first client, the alias management function entity returns an identifier including the requester to the first client after determining that the requester that requests the registration of the alias has the alias registration authority, and the registered alias is successfully registered.
  • the registration response message of the name and the identifier of the registered successful alias can realize the registration of the alias without the corresponding processing of the user profile configuring the alias, and solves the problem that the efficiency of the alias management is low and the system has a heavy processing load.
  • the alias management method may further include: the alias management function entity acquires the subscription information of the user according to the identifier of the user.
  • the subscription information includes indication information, where the indication information is used to indicate that the user has the alias registration authority; or the alias management function entity obtains the policy information, and determines, according to the obtained policy information, that the user has the alias registration authority, and the policy information includes the alias registration.
  • the alias management method may further include: when the user does not have the alias registration permission, the alias management function entity may send the failure to the first client. In response to the message, the failure response message may carry a failure reason, and the failure reason is used to indicate that the user's authorization check fails.
  • the alias management method may further include: when requesting the registered alias When the name is not registered, the alias management function entity assigns an identifier to the alias requesting registration, and the alias for the registration success is the alias for requesting registration.
  • the alias management method may further include: when the name of the alias requesting registration is already registered, the alias management function entity may be to the first client A failure response message is sent, and the failure response message may carry a failure reason, and the failure reason is used to indicate that the alias for requesting registration is registered.
  • the registration request message may further include at least one of the following: a service type of the alias requesting the registration, an attribute of the alias requesting the registration, and the request for registration.
  • a service type of the alias requesting the registration an attribute of the alias requesting the registration
  • the request for registration the request for registration.
  • the alias management method may further include: the alias management function entity sending a notification message to the second client, where the notification message may include the registration success.
  • the notification message may include the registration success. The name of the alias and the identifier of the alias that was successfully registered.
  • the alias management method may further include: the alias management function entity is urgent
  • the business service server sends a notification message, which may include the name of the alias that was successfully registered and the identifier of the alias that was successfully registered.
  • the notification message may further include at least one of the following: a service type of the registered alias, an attribute of the registered successful alias, and an alias of the successful registration.
  • a service type of the registered alias an attribute of the registered successful alias
  • an alias of the successful registration The scope of application, the effective time of the registered alias.
  • a second aspect of the embodiments of the present application provides an alias management method, including:
  • the alias management function entity receives an activation request message sent by the first client, where the activation request message includes an identifier of the user and an identifier of the alias requesting activation; when the user has the alias activation permission, the alias management function entity sends an activation to the first client.
  • the activation response message includes the identity of the user and an identification of the alias for which the activation was successful.
  • the alias management function entity receives an activation request message sent by the first client, including the identifier of the user and the identifier of the alias requested to be activated.
  • the alias management function entity The first client sends an activation response message including the identity of the user and the identity of the activated successful alias.
  • the alias management function entity After receiving the activation request message sent by the first client, the alias management function entity returns an identifier including the requester's identity and the activation success to the first client when determining that the requester requesting activation of the alias has the alias activation permission.
  • the activation response message of the identifier can activate the alias without the corresponding processing of the user profile configuring the alias, and solves the problem of low efficiency of the alias management and heavy processing load of the system.
  • the alias management method may further include: the alias management function entity acquires the subscription information of the user according to the identifier of the user.
  • the subscription information includes indication information, where the indication information is used to indicate that the user has the alias activation authority; or the alias management function entity obtains the policy information, and determines, according to the obtained policy information, that the user has the alias activation permission, and the policy information includes the alias activation permission.
  • the identity of the user includes: the alias management function entity acquires the subscription information of the user according to the identifier of the user.
  • the subscription information includes indication information, where the indication information is used to indicate that the user has the alias activation authority; or the alias management function entity obtains the policy information, and determines, according to the obtained policy information, that the user has the alias activation permission, and the policy information includes the alias activation permission.
  • the identity of the user is not limited to the user.
  • the alias management method may further include: when the user does not have the alias activation permission, the alias management function entity may send the failure to the first client. In response to the message, the failure response message may carry a failure reason, and the failure reason is used to indicate that the user's authorization check fails.
  • the active successful alias is An alias for requesting activation; or, when the alias requested to be activated is an alias that allows multiple users to activate at the same time, and the number of users successfully activating the alias requested to be activated is greater than 0 and less than the maximum number of activations, the activated successful alias is request activation.
  • the alias is an alias for requesting activation; or, when the alias requested to be activated is an alias that allows multiple users to activate at the same time, and the number of users who successfully activate the alias requested to be activated is greater than 0 and less than the maximum number of activations, and the alias of the request is activated A successful alias is activated when the service type is the same as the service type corresponding to the user ID. Requesting activation alias.
  • the activation request message may further include a service type of the alias requesting the activation.
  • the alias management method may further include: when the alias requested to be activated is not an alias that allows multiple users to be activated at the same time, but the alias for requesting activation has been When activated, the alias management function entity may send a failure response message to the first client, where the failure response message may carry a failure reason, the failure reason is used to indicate that the requested activation of the alias is activated; or when the request to activate the alias is allowed An alias that is activated by multiple users at the same time, but when the number of users who successfully activate the alias to be activated is greater than the maximum number of activations, the alias management function entity may send a failure response message to the first client, where the failure response message may carry the failure reason The reason for the failure is to indicate that the number of users who successfully activated the request-activated alias has reached the maximum number of activations.
  • the alias management method may further include: the alias management function entity stores an association relationship between the identifier of the user and the activated alias.
  • the alias management method may further include: the alias management function entity sends a notification message to the second client, where the notification message is used to notify the second client The end user successfully activates the alias that activated successfully.
  • the activation response message may further include a service type that activates a successful alias.
  • the alias management method may further include: the alias management function entity is urgent
  • the task service server sends an activation notification message including the identity of the user and an identification of the alias for successful activation.
  • a third aspect of the embodiments of the present application provides an alias management method, including:
  • the alias management function entity receives a deactivation request message sent by the first client, where the deactivation request message includes an identifier of the user and an identifier of the alias requested to be deactivated; when the user has an alias deactivation authority, the alias management function entity is first
  • the client sends a deactivation response message including the identity of the user and the identity of the alias for deactivating the success.
  • the alias management function entity receives the deactivation request message sent by the first client, including the identifier of the user and the identifier of the alias requested to be deactivated, and when the user has the alias deactivation authority, the alias management The functional entity sends a deactivation response message to the first client including the identity of the user and the identity of the deactivated successful alias.
  • the alias management function entity After receiving the activation request message sent by the first client, the alias management function entity returns the identifier including the requester and deactivates to the first client when determining that the requester requesting the deactivation of the alias has the alias deactivation authority.
  • the deactivation response message of the identifier of the successful alias can realize the deactivation of the alias without the corresponding processing of the user profile configuring the alias, and solves the problem that the efficiency of the alias management is low and the system has a heavy processing load.
  • the alias management method may further include: the alias management function entity acquires the user's subscription according to the identifier of the user.
  • the information includes the indication information, where the indication information is used to indicate that the user has an alias deactivation authority; or the alias management function entity obtains the policy information, and determines, according to the obtained policy information, that the user has an alias deactivation authority, and the policy information includes The ID of the user with the alias deactivation permission.
  • the alias management method may further include: when the user does not have an alias to activate the permission, the alias management function entity may send the first client to the first client.
  • a failure response message may be carried in the failure response message, and the failure reason is used to indicate that the user's authorization check fails.
  • the successfully activated alias is requested to be deactivated.
  • the deactivation request message may further include a service type of the alias requesting the deactivation.
  • the alias management method may further include: deleting, by the alias management function entity, an association relationship between the identifier of the user and the identifier of the activated alias.
  • the alias management method may further include: the alias management function entity sends a notification message to the second client, where the notification message is used to notify the second client The end user successfully deactivates and activates the successful alias.
  • the deactivation response message may further include deactivating a service type of the successful alias.
  • the alias management method may further include: the alias management function entity is urgent
  • the task service server sends a deactivation notification message including the identity of the user and an identification of the alias for deactivating the success.
  • a fourth aspect of the embodiments of the present application provides an alias management method, including:
  • the alias management function entity receives the takeover request message sent by the first client, where the takeover request message includes the identifier of the user and the identifier of the alias to be taken over; when the user has the alias takeover authority, the alias management function entity sends the takeover to the first client.
  • the takeover response message includes the identity of the user and an identification of the alias that successfully took over.
  • the alias management function entity receives the takeover request message sent by the first client, including the identifier of the user and the identifier of the alias to be taken over, and when the user has the alias takeover authority, the alias management function entity
  • the first client sends a takeover response message including the identity of the user and an identity that takes over the successful alias.
  • the alias management function entity After receiving the takeover request message sent by the first client, the alias management function entity returns an identifier including the requester's identity and the success takeover to the first client when determining that the requester requesting the takeover of the alias has the alias takeover authority.
  • the takeover response message of the identifier can implement the takeover of the alias without the corresponding processing of the user profile configuring the alias, and solves the problem of low efficiency of the alias management and heavy processing load of the system.
  • the alias management method may further include: the alias management function entity acquires the subscription information of the user according to the identifier of the user.
  • the subscription information includes indication information, where the indication information is used to indicate that the user has the alias takeover authority; or the alias management function entity obtains the policy information, and determines, according to the obtained policy information, that the user has the alias takeover authority, and the policy information includes the alias takeover authority.
  • the identity of the user is not limited to the user.
  • the alias management method may further include: when the user does not have the alias takeover authority, the alias management function entity may send the failure to the first client. In response to the message, the failure response message may carry a failure reason, and the failure reason is used to indicate that the user's authorization check fails.
  • the alias of the request takeover is an alias that allows to take over
  • the alias of the success takeover is an alias of the request to take over; or, when the request is taken over the alias If the service type of the alias to be taken over is the same as the service type of the user's identity, the success of the takeover is the alias of the request to take over.
  • the takeover request message may further include a service type of the alias requesting to take over.
  • the alias management method may further include: when the alias of the request takeover is not an alias that allows the takeover, the alias management function entity may provide the first client The terminal sends a failure response message, and the failure response message may carry a failure reason, and the failure reason is used to indicate that the alias to be taken over by the request is not an alias that allows the takeover.
  • the alias management method may further include: deleting, by the alias management function entity, the identifier of the successfully taken over alias and the identifier of the user using the second client Correlating the relationship, and sending a notification message to the second client, the notification message is used to notify the second client user to successfully take over the successful takeover alias or to notify the second client to activate the successful takeover alias, using the second client
  • the user is a user who successfully activates an alias that successfully takes over.
  • the takeover response message may further include a service type that takes over the successful alias.
  • the alias management method may further include: the alias management function entity sending a takeover notification message to the emergency task service server, where the takeover notification message includes the user's Identifies and identifies the identity of the successful alias.
  • the alias management method may further include: the alias management function entity sending a deactivation notification message to the emergency task service server, where the deactivation notification message includes Deactivate the identity of the alias that successfully took over and the identity of the user.
  • a fifth aspect of the embodiments of the present application provides an alias management function entity, including: a receiving unit, configured to receive a registration request message sent by a first client, where the registration request message includes an identifier of the user and a name of an alias requesting registration; And a sending unit, configured to send a registration response message to the first client when the user has the alias registration authority, where the registration response message includes the identifier of the user, the name of the alias successfully registered, and the identifier of the alias successfully registered.
  • the nickname management function entity may further include: an acquiring unit, configured to acquire subscription information of the user according to the identifier of the user received by the receiving unit, where the subscription information includes indication information, and the indication The information is used to indicate that the user has the alias registration authority; or the obtaining unit is configured to obtain the policy information, and the determining unit is configured to determine, according to the policy information acquired by the obtaining unit, that the user has the alias registration authority, and the policy information includes the user with the alias registration authority.
  • an acquiring unit configured to acquire subscription information of the user according to the identifier of the user received by the receiving unit, where the subscription information includes indication information, and the indication The information is used to indicate that the user has the alias registration authority
  • the obtaining unit is configured to obtain the policy information
  • the determining unit is configured to determine, according to the policy information acquired by the obtaining unit, that the user has the alias registration authority, and the policy information includes the user with the alias registration authority.
  • the alias management function entity may further include: an allocating unit, configured to request registration when the name of the alias requesting registration is not registered The alias is assigned an identifier.
  • the alias for successful registration is the alias for requesting registration.
  • the registration request message further includes at least one of the following: a service type of the alias requesting the registration, an attribute of the alias requesting the registration, and an alias requesting the registration.
  • a service type of the alias requesting the registration an attribute of the alias requesting the registration
  • an alias requesting the registration an alias requesting the registration.
  • the scope of application the effective time of the alias to request registration.
  • the sending unit is further configured to send a notification message to the second client, where the notification message includes the name of the successfully registered alias and the alias of the successful registration. logo.
  • the notification message further includes at least one of the following: a service type of the registered alias, an attribute of the registered successful alias, and an alias of the registered success.
  • a service type of the registered alias an attribute of the registered successful alias
  • an alias of the registered success The effective time of the application scope and the registered alias.
  • a sixth aspect of the embodiments of the present application provides an alias management function entity, including: a receiving unit, configured to receive an activation request message sent by a first client, where the activation request message includes an identifier of the user and an identifier of the alias requested to be activated;
  • the sending unit is configured to send an activation response message to the first client when the user has the alias activation permission, where the activation response message includes the identifier of the user and the identifier of the alias that is successfully activated.
  • the nickname management function entity may further include: an obtaining unit, configured to acquire subscription information of the user according to the identifier of the user received by the receiving unit, where the subscription information includes indication information, and the indication The information is used to indicate that the user has the alias activation authority; or the obtaining unit is configured to obtain the policy information, and the determining unit is configured to determine, according to the policy information acquired by the obtaining unit, that the user has the alias activation permission, and the policy information includes the user with the alias activation authority.
  • an obtaining unit configured to acquire subscription information of the user according to the identifier of the user received by the receiving unit, where the subscription information includes indication information, and the indication The information is used to indicate that the user has the alias activation authority
  • the obtaining unit is configured to obtain the policy information
  • the determining unit is configured to determine, according to the policy information acquired by the obtaining unit, that the user has the alias activation permission, and the policy information includes the user with the alias activation authority.
  • the active successful alias is An alias for requesting activation; or, when the alias requested to be activated is an alias that allows multiple users to activate at the same time, and the number of users successfully activating the alias requested to be activated is greater than 0 and less than the maximum number of activations, the activated successful alias is request activation.
  • the alias is an alias for requesting activation; or, when the alias requested to be activated is an alias that allows multiple users to activate at the same time, and the number of users who successfully activate the alias requested to be activated is greater than 0 and less than the maximum number of activations, and the alias of the request is activated A successful alias is activated when the service type is the same as the service type corresponding to the user ID. Requesting activation alias.
  • the nickname management function entity may further include: a storage unit, configured to store an association relationship between the identifier of the user and the alias that is successfully activated.
  • the sending unit is further configured to send a notification message to the second client, where the notification message is used to notify the second client user that the activation is successfully activated. Alias.
  • a seventh aspect of the embodiments of the present application provides an alias management function entity, including: a receiving unit, configured to receive a deactivation request message sent by a first client, where the deactivation request message includes an identifier of the user and an alias requested to be deactivated.
  • the sending unit is configured to send a deactivation response message to the first client when the user has the alias deactivation permission, where the deactivation response message includes the identifier of the user and the identifier of the alias for deactivating the success.
  • the nickname management function entity may further include: an obtaining unit, configured to acquire subscription information of the user according to the identifier of the user, where the subscription information includes indication information, where the indication information is used to indicate the user Having an alias deactivation authority; or an obtaining unit, configured to obtain policy information, the determining unit, configured to determine, according to the policy information acquired by the obtaining unit, that the user has an alias deactivation authority, and the policy information includes an identifier of the user having the alias deactivation authority .
  • the alias management function entity may further include: a deleting unit, configured to delete an association between the identifier of the user and the identifier of the alias that successfully deactivates .
  • the sending unit is further configured to send a notification message to the second client, where the notification message is used to notify the second client user that the user is successfully deactivated. Activate a successful alias.
  • An eighth aspect of the present application provides an alias management function entity, including: a receiving unit, configured to receive a takeover request message sent by a first client, where the takeover request message includes an identifier of the user and an identifier of the alias requested to be taken over; And a sending unit, configured to send a takeover response message to the first client when the user has the alias takeover authority, where the takeover response message includes the identifier of the user and an identifier of the alias that successfully takes over.
  • the nickname management function entity may further include: an obtaining unit, configured to acquire subscription information of the user according to the identifier of the user received by the receiving unit, where the subscription information includes indication information, and the indication The information is used to indicate that the user has the alias takeover authority; or the obtaining unit is configured to obtain the policy information, and the determining unit is configured to determine, according to the policy information acquired by the obtaining unit, that the user has the alias takeover authority, and the policy information includes the user with the alias takeover authority.
  • an obtaining unit configured to acquire subscription information of the user according to the identifier of the user received by the receiving unit, where the subscription information includes indication information, and the indication The information is used to indicate that the user has the alias takeover authority
  • the obtaining unit is configured to obtain the policy information
  • the determining unit is configured to determine, according to the policy information acquired by the obtaining unit, that the user has the alias takeover authority, and the policy information includes the user with the alias takeover authority.
  • the alias of the request takeover is an alias that allows to take over
  • the alias that succeeds in taking over is an alias for requesting to take over; or, when requesting to take over the alias If the service type of the alias to be taken over is the same as the service type of the user's identity, the success of the takeover is the alias of the request to take over.
  • the alias management function entity may further include: a deleting unit, configured to delete the identifier of the successfully taken over alias and the user who uses the second client The associated relationship is used by the user of the second client to successfully activate the user who successfully takes over the alias; the sending unit is further configured to send a notification message to the second client, where the notification message is used to notify the second client that the successful takeover succeeds.
  • a deleting unit configured to delete the identifier of the successfully taken over alias and the user who uses the second client The associated relationship is used by the user of the second client to successfully activate the user who successfully takes over the alias
  • the sending unit is further configured to send a notification message to the second client, where the notification message is used to notify the second client that the successful takeover succeeds.
  • a ninth aspect of the embodiments of the present application provides an alias management function entity, including at least one processor, and a memory; the memory is configured to store a computer program, such that when the computer program is executed by at least one processor, the first aspect or the A possible implementation of the aspect, or a possible implementation of the second or second aspect, or a possible implementation of the third or third aspect, or a possible implementation of the fourth or fourth aspect Any of the described alias management methods.
  • a tenth aspect of the embodiments of the present application provides a computer readable storage medium for storing a computer program for performing a possible implementation as in the first aspect or the first aspect, or the second aspect or the A possible implementation of the second aspect, or the third aspect or the possible implementation of the third aspect, or the instruction of the alias management method of any of the fourth aspect or the possible implementation of the fourth aspect.
  • An eleventh aspect of the embodiments of the present application provides a chip system, where the chip system includes a processor for supporting an alias management function entity to implement the functions involved in the foregoing aspects, for example, generating or processing the foregoing method. Data and / or information.
  • the chip system further includes a memory for storing program instructions and data necessary for the alias management function entity.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • FIG. 1 is a schematic diagram of an application architecture of an emergency task service based on a 3GPP LTE system provided by the prior art
  • FIG. 2 is a simplified schematic diagram of a system architecture provided by an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of an alias management function entity according to an embodiment of the present disclosure
  • FIG. 5 is a flowchart of another method for managing an alias according to an embodiment of the present application.
  • FIG. 6 is a flowchart of another method for managing an alias according to an embodiment of the present application.
  • FIG. 7 is a flowchart of another method for managing an alias according to an embodiment of the present application.
  • FIG. 8 is a flowchart of an alias-based addressed call method according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of another alias management function entity according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of another alias management function entity according to an embodiment of the present application.
  • the application architecture of the emergency mission service based on the 3GPP LTE system is shown in Figure 1.
  • the user profile is saved in the MC service user database, and the user profile includes the identifier of the user and one or more aliases corresponding to the identifier.
  • An alias is a name other than the official legal or canonical name. For different services, the same user can use the same identifier or different identifiers.
  • the user's ID is bound to the alias corresponding to the user's ID and is saved in the user profile.
  • the identifier of the user and the alias corresponding to the identifier of the user are bound, and for the MCData service, the identifier of the user is bound to the alias corresponding to the identifier of the user.
  • the user can use the user profile that contains the alias only if it is sent to the terminal used by the system by the system administrator through the Configuration Management Server (CMS) and the Configuration Management Client (CMC). When these aliases are used.
  • CMS Configuration Management Server
  • CMC Configuration Management Client
  • you need to manage the alias such as registration, activation, deactivation, takeover, etc.
  • the alias also has some information describing its characteristics, such as the alias unique in the system, the alias allows multiple users to use at the same time, the identifier of the user corresponding to the alias, and so on.
  • the alias information is specific:
  • An alias is an alias that a user can select, which is bound to the user's duties or tasks.
  • a user can activate one or more aliases at the same time. Each activated alias is unique and can be used as a user's service identifier to communicate and address the user corresponding to the alias, that is, the routing function can be supported.
  • an alias is used to identify the driver of a particular train. For example, there are two drivers on the TRAIN29 train. Driver 1 is aliased as Driver1_TRAIN29, and driver 2 is aliased as Driver2_TRAIN29. The alias Driver1_TRAIN29 can be addressed after successful activation. Driver 1 on the TRAIN 29 train, alias Driver2_TRAIN29 can be activated to the driver 2 on the TRAIN29 train.
  • An alias can be assigned to multiple users according to the service management configuration, or taken over by other authorized users according to the service management configuration. These two requirements are mutually exclusive, that is, if an alias is assigned to multiple users, the alias cannot be taken over.
  • the alias in the railway application requires the user to freely select, can be activated and deactivated flexibly, can support the routing function, can be taken over, can be newly registered, In this way, if the existing technology is still pre-configured in the user profile when the system is deployed, the efficiency of managing the alias is low, and the system has a heavy processing load.
  • the embodiment of the present application provides an alias management method.
  • the basic principle is that the alias management function entity receives the management request message sent by the first client, where the management request message includes The identifier of the user and the information of the alias requested for management.
  • the alias management function entity sends a management response message to the first client, where the management response message includes the identifier of the user and the information of the managed success alias.
  • the above management may be one or more of registration, activation, deactivation, takeover, and the like.
  • the alias management function entity After receiving the management request message sent by the first client, the alias management function entity returns an identifier including the requester's identity and the management success to the first client when determining that the requester that requests the management of the alias has the alias management authority.
  • the management response message of the information can realize the management of the alias without the corresponding processing of the user profile configuring the alias, and solves the problem of low efficiency of the alias management and heavy processing load of the system.
  • the alias may also be referred to as a functional alias.
  • a plurality in the embodiment of the present application may mean two or more.
  • FIG. 2 is a simplified schematic diagram of a system architecture to which embodiments of the present application may be applied.
  • the system architecture may include: a function alias management server, a function alias management client, and a functional entity in the architecture shown in FIG. 1.
  • the alias management function entity described in the embodiment of the present application may be integrated into the Mission Critical Service Server (MC Service Server/MC server) and the group management server included in the architecture shown in FIG. 1 .
  • Group management server configuration management server (Configuration management server), identity management server (Identity management server), key management server (Key management server), location management server (Location management server) can also be used in any one of the servers.
  • MC Service Server/MC server Mission Critical Service Server
  • Group management server configuration management server
  • Identity management server Identity management server
  • Key management server key management server
  • Location management server Location management server
  • the first client in the embodiment of the present application may be integrated into the Mission Critical Service Client (MC Service Client/MC client) included in the architecture shown in FIG. Any of the group management client, the configuration management client, the identity management client, the key management client, and the location management client. In a client, it can also be integrated in the Funical-Alias management client.
  • MC Service Client/MC client Mission Critical Service Client
  • the alias management function entity can provide storage and maintenance of the alias information of the system.
  • the alias information may include one or more of the following combinations: the name of the alias, the identifier of the alias, the attribute of the alias, the identifier of the user associated with the alias, the service type of the alias, the application scope of the alias, the effective time of the alias, and the like.
  • the alias management function entity can be used to receive or reject user-initiated alias registration, alias activation, alias deactivation, alias takeover, etc., and can also be used to notify the user of changes in the alias status, authorize the user operation alias, and maintain the alias and The association of the user's identity, etc.
  • the first client is configured to initiate an operation request for registration, activation, deactivation, takeover, and the like of the alias to the alias management function entity, and is also used to receive a message of the notification alias state change of the alias management function entity.
  • the emergency mission service server is primarily responsible for call control and media control, which is a logical entity. In a specific implementation, it may be an MCPTT server, an MCVideo server, or an MCData server.
  • the emergency task service client is an application layer entity that is peered with the emergency task service server and is mainly responsible for the processing of application layer transactions.
  • the group management server is mainly responsible for group management and group information maintenance in the system, such as group creation, dissolution, and group member changes.
  • the group management client is an application layer entity that is peered with the group management server, and is mainly responsible for initiating group creation, dissolving, group member operations, and updating group information.
  • the configuration management server is responsible for configuring the service information and user information in the system. For example, the user profile is delivered to the terminal used by the user.
  • the configuration management client is an application layer entity that is peered with the configuration management server and is responsible for receiving configuration information delivered by the configuration management server.
  • the identity management server is used to authorize and authenticate the identity of the user, determine that the user is a legitimate user, and distribute the service access token to the identity management client.
  • the identity management client is an application layer entity that is peered with the identity management server and is configured to receive the service access token during the authorization and authentication process of the identity management server.
  • the key management server is mainly responsible for the management of security keys, such as generation, distribution, and update.
  • the key management client is an application layer entity that is peered with the key management server and is mainly responsible for receiving and updating security keys.
  • the location management server is mainly responsible for the management of the user's location, such as receiving and saving the location information of the user, and providing the location information of the user to other authorized users.
  • the location management client is an application layer entity that is peered with the location management server. It is mainly responsible for reporting the location information of the user and obtaining the location information of other users from the location management server.
  • the function alias management server is mainly responsible for information maintenance and update of aliases in the system, such as adding aliases, removing aliases, updating aliases, retrieving aliases, and issuing aliases to users.
  • the function alias management client is mainly responsible for retrieving the alias in the system and receiving the alias delivered by the function alias management server.
  • the emergency task service server communicates with the emergency task service client using the MCX-1 interface, and the MCX-1 interface corresponding to different services may be an MCPTT-1 interface or an MCVideo-1 interface or an MCData-1 interface.
  • the functional entities can communicate with each other using the corresponding CSC interface.
  • the location management server communicates with the location management client using CSC-14, the alias management server and the alias management client communicate using CSC-xx, and the alias management server can also communicate with the emergency task service server using CSC-yy.
  • the system shown in FIG. 2 may be a system based on a Mission Critical Service System, and the embodiment of the present application is applicable to the MCPTT service, the MCData service, and the MCVideo service.
  • the application of the present application is not specifically limited herein.
  • FIG. 3 is a schematic diagram of a composition of an alias management function entity according to an embodiment of the present disclosure.
  • the alias management function entity may include at least one processor 21, a memory 22, a communication interface 23, and a communication bus 24.
  • the processor 21 is a control center of the alias management function entity, and may be a processor or a collective name of a plurality of processing elements.
  • the processor 21 is a central processing unit (CPU), may be an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • microprocessors Digital Signal Processors, DSPs
  • FPGAs Field Programmable Gate Arrays
  • the processor 21 can perform various functions of the alias management function entity by running or executing a software program stored in the memory 22 and calling data stored in the memory 22.
  • processor 21 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG.
  • the alias management functional entity may include multiple processors, such as processor 21 and processor 25 shown in FIG.
  • processors can be a single core processor (CPU) or a multi-core processor (multi-CPU).
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the memory 22 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • Memory 22 may be present independently and coupled to processor 21 via communication bus 24.
  • the memory 22 can also be integrated with the processor 21.
  • the memory 22 is used to store a software program that executes the solution of the present application, and is controlled by the processor 21 for execution.
  • the communication interface 23 uses a device such as any transceiver for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), Wireless Local Area Networks (WLAN), etc. .
  • the communication interface 23 may include a receiving unit that implements a receiving function, and a transmitting unit that implements a transmitting function.
  • the communication bus 24 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 3, but it does not mean that there is only one bus or one type of bus.
  • the device structure illustrated in FIG. 3 does not constitute a definition of an alias management function entity, and may include more or fewer components than those illustrated, or a combination of certain components, or different component arrangements.
  • the method for managing an alias provided by the embodiment of the present application may be applied to management operations such as registration, activation, deactivation, and takeover of an alias.
  • management operations such as registration, activation, deactivation, and takeover of an alias.
  • the present application uses the following embodiments. The alias management method is described in detail.
  • FIG. 4 is a flowchart of an alias management method according to an embodiment of the present application.
  • FIG. 4 is a method for managing an alias for requesting registration of an alias according to an embodiment of the present application. As shown in FIG. 4, the method may include:
  • the alias management function entity receives a registration request message sent by the first client.
  • the registration request message may include an identifier of a user and a name of an alias to be registered.
  • the registration request message is used to request registration of an alias.
  • the user refers to the user who uses the first client.
  • the above-mentioned user may be an authorized user, that is, the user has the alias registration authority, otherwise the authorization check may fail in the subsequent authorization check, and the registration process is terminated.
  • the user's identity refers to any combination of letters and/or numbers and/or special characters that uniquely identify the user.
  • the user's identity is MC service ID, MCPTT ID, MCVideo ID or MCData ID.
  • the first client used by the user may send a registration request message carrying the identifier of the user and the name of the alias requesting registration to the alias management function entity for requesting Alias is registered.
  • the first client may directly send a registration request message to the alias management function entity, or may indirectly send a registration request message to the alias management function entity through other functional entities, that is, the alias management function entity may directly receive the first client.
  • the registration request message sent may also receive the registration request message sent by the first client indirectly, and is not specifically limited herein.
  • a registration request message may carry one or more identifiers of the user, and different identifiers correspond to different service types, for example, basic service types such as MCPTT service, MCData service, and MCVideo service, railway applications, enterprise applications, and the like. Other business types.
  • a registration request message may also carry the name of one or more aliases that request registration. When a registration request message carries the names of multiple aliases requesting registration, the first client can request registration of multiple aliases by sending a registration request message.
  • the registration request message may further include at least one of the following: the service type of the alias requesting the registration, the attribute of the alias requesting the registration, the applicable scope of the alias requesting the registration, and the validity of the alias requesting the registration. Time (valid time).
  • the service type of the alias is used to identify the service type to which the alias can be applied, such as MCPTT service, MCVdieo service, MCData service, and railway application service.
  • the service type of the alias is the same as the service type corresponding to the user's identity, but it can also be different.
  • the attributes of the alias may include a combination of at least one or more of the following: an indication of whether multiple users are allowed to be activated simultaneously, a maximum number of activations when multiple users are allowed to be activated simultaneously, an indication of whether to allow takeover.
  • the scope of application of the alias is used to identify the scope of application of the alias, for example, which user can be activated by the alias.
  • the application scope of the alias may be a user list or a user role list, such as a train driver, a train ticket seller, and the like.
  • the registration request message does not include the parameter of the application scope of the alias, it may indicate that the alias is only applicable to the applicant itself, or may indicate that the alias is applicable to all users in the system, and the specific scope of application may be omitted by the system. Operator specified.
  • the effective time of the alias is used to identify the effective time of the alias.
  • the effective time of the alias can be implemented by a timer, or it can be permanent for an infinite time.
  • the registration request message does not include the parameter of the effective time of the alias, it can indicate that the validity time of the alias is infinite time, that is, permanent.
  • the name of the alias, the identifier of the alias, the attribute of the alias, the business type of the alias, the application range of the alias, and the specific example of the effective time of the alias are as shown in Table 1.
  • the name of the alias may be any combination of letters, Chinese characters, numbers, special characters, etc., which are easily recognized, understood, and memorized by the user, such as the G20 train master driver in Table 1 above.
  • the identifier of the alias can be the name of the alias, or a combination of numbers and/or letters and/or special symbols in a particular format.
  • the identifier of the alias may include an international code, a function address, and a function code; the international code is used to indicate the network that the user is currently signing, such as China 086, France 033.
  • the function address consists of the call type and the user number.
  • the call type is a prefix used to distinguish different types of user numbers. It is also an indication for the network how to interpret the received number. If it is considered that the number corresponds to the train number, or the control room number, or the engine number. .
  • the function code indicates the role associated with the function address.
  • the alias management function entity sends a registration response message to the first client.
  • the registration response message may include an identifier of the user, a name of the alias that is successfully registered, and an identifier (identification, ID) of the alias that is successfully registered.
  • the first client may activate the registered successful alias when the alias needs to be used, so that the user who uses the first client can be addressed according to the identifier of the alias that is successfully activated.
  • the name of the alias when the name of the alias is unique in the whole system, the name of the alias may be used as its identifier, or the alias may be assigned a system-wide unique identifier that can identify the alias.
  • the alias successfully registered may be an alias registered by the request.
  • the alias management function entity when the number of aliases requesting registration is 1, and the alias of the request registration is not registered, the alias management function entity registers the alias for the user, and at this time, the alias requesting registration becomes an alias for successful registration; or When the number of aliases requesting registration is greater than 1, and at least one unregistered alias exists in the alias requesting registration, the alias management function entity activates the at least one alias for the user, and at this time, at least one unregistered alias becomes An alias for registration success.
  • the registration response message may further include a service type of the registered alias.
  • the identifier of the successfully registered alias may be pre-assigned to the alias by the system, that is, the association between the name of the alias and the identifier of the alias is pre-stored in the alias management function entity, or may be assigned by the alias management function entity for the alias. For example, it is assigned when determining that a user has an alias registration permission to address the user based on the identity of the alias.
  • the alias management function entity in step 302 can determine that the user has the alias registration authority in the following manner, and is not limited.
  • the alias management function entity may carry the request according to the registration request. The identity of the user, knowing if the user has the alias registration permission.
  • the foregoing method may further include: the alias management function entity may perform an authorization check on the user.
  • the method further includes: the alias management function entity obtains the alias permission related information according to the identifier of the user, and determines, according to the information about the alias permission, whether the user has the alias registration authority.
  • the alias permission related information may be the subscription information of the user, or may be the policy information stored locally by the alias management function entity.
  • the nickname management function entity obtains the subscription information of the user according to the identifier of the user, and the subscription information of the user includes indication information, where the indication information is used to indicate whether the user has the privilege registration authority.
  • the alias management function entity can determine whether the user has the alias registration authority according to the user's subscription information. When the indication information included in the subscription information is used to indicate that the user has the alias registration authority, the alias management function entity may determine that the user has the alias registration authority; or, when the indication information included in the subscription information is used to indicate that the user does not have the alias registration authority The alias management function entity can determine that the user does not have alias registration rights.
  • 1 bit can be used to indicate whether the user has an alias registration authority, such as "1" indicates that the user has the alias registration authority, and "0" indicates that the user does not have the alias registration authority.
  • the subscription information not only can the user indicate whether the user has the alias registration authority, but also when the user has the alias registration authority, the user is instructed which alias (one or more aliases) has the alias registration authority.
  • only "1" in the subscription information indicates that the user has the alias registration authority. In this case, it can be implicitly indicated that the user has the alias registration authority for all the aliases.
  • the subscription information includes only the list of aliases that the user is allowed to register. At this time, it indicates that the user has the alias registration authority, and only has the alias registration authority for the alias in the alias list.
  • the alias management function entity obtains the policy information, and determines, according to the policy information, whether the user has the alias registration authority, and the policy information includes the identifier of the user with the alias registration authority.
  • the alias management function entity may obtain locally stored policy information, where the policy information includes an identifier of one or more users with alias registration rights, and then determines whether the identifier of the user included in the registration request message is included in the policy information. In it, you can determine if the user has alias registration rights. When the user's identity is included in the policy information, it is determined that the user has the alias registration authority; or, when the user's identity is not included in the policy information, it is determined that the user does not have the alias registration authority.
  • the policy information only the identity of the user may be included to indicate which users have alias registration rights.
  • the policy information only includes the list of identifiers of users with alias registration rights. In this case, it can be implicitly indicated that these users have alias registration rights for all aliases.
  • the policy information includes a list of identities with a list of aliases and their corresponding users with alias registration rights to indicate that these users only have alias registration rights for aliases in the list of aliases.
  • the authorization check of the user may be simultaneously performed according to the subscription information of the user and the policy information locally stored by the alias management function entity.
  • the method may further include: the alias management function entity may perform an authorization check on the user, and determine whether the alias requested to be registered is not registered.
  • the method further includes: when the number of the names of the aliases requesting to be registered is 1, the alias management function entity performs an authorization check on the user, and determines whether the alias requested to be registered is not registered.
  • step 302 is performed; or when the number of names of the alias requesting registration is greater than 1, the alias management function entity performs authorization check on the user and determines to request registration. If there is at least one unregistered alias in the alias, if the user authorization checks and there is at least one unregistered alias in the alias requested to be registered, step 302 is performed.
  • the alias management function entity determines that the user has registered the alias for a request. If the alias is registered, and the alias registered by the request is not registered, step 302 is performed; or, when it is determined that the alias registered by the user for a request does not have the alias registration authority, or the alias registered by the request is registered, the request is registered.
  • the alias does not allow registration, in which case a failure response message can be returned to the first client.
  • the alias management function entity receives the registration request message sent by the first client, including the identifier of the user and the name of the alias requested to be registered, and when the user has the alias registration authority, the alias management function entity The first client sends a registration response message including the identity of the user, the name of the registered successful alias, and the identifier of the registered successful alias. After receiving the registration request message sent by the first client, the alias management function entity returns an identifier including the requester to the first client after determining that the requester that requests the registration of the alias has the alias registration authority, and the registered alias is successfully registered.
  • the registration response message of the name and the identifier of the registered successful alias can realize the registration of the alias without the corresponding processing of the user profile configuring the alias, and solves the problem that the efficiency of the alias management is low and the system has a heavy processing load.
  • the alias for requesting registration has no binding relationship with the service type, and can be flexibly operated.
  • the method before the sending the registration response message to the first client, the method further includes:
  • the alias management function entity assigns an identifier to the alias registered by the request.
  • the alias management function entity may generate an identifier for the alias registered by the request and assign it to the alias of the request registration.
  • the identifier When the identifier is generated for the alias registered for the request, it may be generated according to the composition of the identifier.
  • the identifier of the alias is composed of three parts: an international code, a function address, and a function code. It should be noted that the descriptions of the international coding, the function address, and the function coding can be referred to in the description in step 301, and details are not described herein again.
  • the alias management function entity when the number of names of the alias requesting registration is 1, and the alias requesting registration is not registered, the alias management function entity assigns an identifier to the alias requesting registration; or, the number of names of the alias requesting registration When there is at least one unregistered alias in the alias requesting registration, the alias management function entity assigns an identifier to at least one unregistered alias.
  • the alias successfully registered in step 302 is the alias registered by the request.
  • the method may further include: the alias management function entity sending a notification message to the second client.
  • the notification message may include the name of the alias that is successfully registered and the identifier of the alias that is successfully registered.
  • the alias management function entity notifies the second client user to successfully register the successfully registered alias by sending a notification message including the name of the registered successful alias and the identifier of the registered successful alias to the second client.
  • the second client may be a client used by all users in the system, or may be a client used by users within the application scope of the registered successful alias.
  • the scope of the application may be carried in the registration request message, or may be assigned by the alias management function entity.
  • the alias management function entity may directly send a notification message to the second client used by the user in the user list, and when the application scope of the alias is a user role list, the alias The management function entity may send a notification message to the second client used by the user corresponding to the role in the user role list by forwarding of other functional entities, such as the emergency task service server.
  • the alias management function entity may further send, to the emergency task service server, a notification message including the name of the registered successful alias and the identifier of the registered successful alias, so that The urgent task service server can then identify the alias of the registration success, and then can address the user who activated the alias.
  • the notification message may further include at least one of the following: a service type of the registered successful alias, an attribute of the registered successful alias, an application range of the registered successful alias, and a valid time of the registered successful alias.
  • the parameters may be received by the first client, or may be allocated by the alias management function entity, and are not specifically limited herein.
  • the steps for replacing step 302 include:
  • the alias management function entity When the user does not have the alias registration authority, the alias management function entity returns a failure response message to the first client; or, when the user has the alias registration authority and the name of the alias requesting registration is registered, the alias management function entity is first The client returns a failure response message.
  • the failure response message may include a reason for failure. For example, when a user does not have alias registration rights, the reason for the failure is that the authorization check failed.
  • the first client may apply for a higher authority to enable the registration of the alias. For another example, when the user has the alias registration authority and the name of the alias requesting registration is registered, the reason for the failure is that the name of the alias requesting registration has been registered.
  • the first client may apply to register another alias.
  • FIG. 5 is a method for managing an alias for requesting activation of an alias according to an embodiment of the present disclosure. As shown in FIG. 5, the method may include:
  • the alias management function entity receives an activation request message sent by the first client.
  • the activation request message may include an identifier of the user and an identifier of the alias requested to be activated.
  • the activation request message is used to request activation of the alias.
  • the user refers to the user who uses the first client.
  • the first client used by the user may send an activation request message carrying the identifier of the user and the identifier of the requested activation to the alias management function entity for requesting the alias. Activate.
  • the first client may directly send an activation request message to the alias management function entity, or may send an activation request message to the alias management function entity indirectly through other functional entities, that is, the alias management function entity may directly receive the first client.
  • the activation request message sent may also receive the activation request message sent by the first client indirectly, and is not specifically limited herein.
  • an activation request message may carry one or more identifiers of the user, and different identifiers correspond to different service types, such as MCPTT services, MCData services, MCVideo services, and other basic service types, railway applications, enterprise applications, and the like. business type.
  • An activation request message may also carry an identifier of one or more aliases that are requested to be activated. When an activation request message carries an identifier of multiple aliases requesting activation, the first client may request activation of multiple aliases by sending an activation request message.
  • the activation request message may further include: a service type of the alias.
  • the alias management function entity When the user has the alias activation permission, the alias management function entity sends an activation response message to the first client.
  • the activation response message may include an identifier of the user and an identifier of the alias that is successfully activated.
  • the alias management function entity may send an activation response message carrying the identifier of the user and the identifier of the activation success to the first client, so that the identifier of the alias succeeded can be addressed according to the activation. Use the first client's user.
  • the activation response message may further include a service type that activates a successful alias.
  • the alias management function entity activates the alias for the user, and at this time, the alias requesting activation becomes successful.
  • the alias management function entity activates the alias for the user At this time, the alias requesting activation becomes an alias for successful activation; or, when the alias requested to be activated is not an alias that allows multiple users to activate at the same time, and the alias for requesting activation is not activated, and the service type of the alias requesting activation is related to the user's When the corresponding service type is the same, the alias management function entity activates the alias for the user.
  • the alias requested to be activated becomes an alias for successful activation; or, when the alias requested to be activated is an alias that allows multiple users to activate at the same time, and The number of users who successfully activate the request-activated alias is greater than 0 and less than the number Large activations, activation is requested alias identifier corresponding to service type and user service type is the same, to activate the management function entity alias alias for the user, time, requested to be activated to become activated alias alias successful.
  • the alias management function entity in step 402 can determine that the user has the alias activation permission in the following manner, and is not limited.
  • whether the alias activation permission is an attribute of the user, and the attribute is associated with the identifier of the user, and after receiving the activation request message, the alias management function entity may be carried according to the activation request.
  • the foregoing method may further include: the alias management function entity may perform an authorization check on the user.
  • the method further includes: the alias management function entity acquires the alias permission related information according to the identifier of the user, and determines, according to the information about the alias authority, whether the user has the alias activation authority.
  • the information about the alias permission may be the subscription information of the user, or may be the policy information stored locally by the alias management function entity.
  • the nickname management function entity obtains the subscription information of the user according to the identifier of the user, and the subscription information of the user includes indication information, where the indication information is used to indicate whether the user has the privilege activation authority.
  • the alias management function entity can determine whether the user has the alias activation authority according to the user's subscription information.
  • the indication information includes the indication information for indicating that the user has the alias activation authority
  • the alias management function entity may determine that the user has the alias activation authority; or, when the indication information included in the subscription information is used to indicate that the user does not have the alias activation permission,
  • the alias management function entity can determine that the user does not have alias activation rights.
  • the alias management function entity obtains the policy information, and determines whether the user has the alias activation authority according to the policy information and the identifier of the user, where the policy information includes the identifier of the user with the alias activation authority.
  • the identifier of the user is included in the policy information, it is determined that the user has the alias activation authority; or, when the identifier of the user is not included in the policy information, it is determined that the user does not have the alias activation authority.
  • the authorization check of the user may be simultaneously performed according to the subscription information of the user and the policy information locally stored by the alias management function entity.
  • the method may further include: the alias management function entity may perform an authorization check on the user, and after the authorization check succeeds, the alias management function entity may determine the alias to request activation. Whether it is an alias that allows multiple users to activate at the same time, and determines whether the alias activated by the request is not activated.
  • step 402 is performed; or, if the alias requested to be activated is an alias that allows multiple users to be activated at the same time, and is successfully activated If the number of users requesting the activated alias is greater than 0 and less than the maximum number of activations, step 402 may also be performed.
  • the service type of the alias to be activated may be further determined to be the same as the service type corresponding to the identifier of the user.
  • step 402 is performed; If the alias to be activated is an alias that allows multiple users to be activated at the same time, and the number of users who successfully activate the request-activated alias is greater than 0 and less than the maximum number of activations, the service type of the alias requested to be activated corresponds to the identifier of the user. If the service type is the same, step 402 is performed.
  • the implementation of the authorization check for the user in the third implementation manner is similar to that in the second implementation manner, and details are not described herein again.
  • step 402 is performed.
  • a failure response message may be returned to the first client.
  • the requested activation alias is to allow multiple users to activate the alias at the same time, when multiple users are allowed to activate the alias at the same time, the maximum number of activations allowed to be activated is included in the attribute of the alias requesting activation.
  • the alias management function entity can dynamically maintain an activated user information locally to be able to know the number of users who activate the alias at the current time, for example, an active user list that can be saved locally, for example, as shown in Table 2, for
  • the ID of the user indicating that the alias identified as xxx is successfully activated is user service ID1, user service ID2, and user service ID3, and the IDs of the users who successfully activate the alias identified as yyy are user service ID7, user service ID9, and user service ID10.
  • the alias management function entity receives an activation request message sent by the first client, including the identifier of the user and the identifier of the alias requested to be activated.
  • the alias management function entity The first client sends an activation response message including the identity of the user and the identity of the activated successful alias.
  • the alias management function entity After receiving the activation request message sent by the first client, the alias management function entity returns an identifier including the requester's identity and the activation success to the first client when determining that the requester requesting activation of the alias has the alias activation permission.
  • the activation response message of the identifier can activate the alias without the corresponding processing of the user profile configuring the alias, and solves the problem of low efficiency of the alias management and heavy processing load of the system. Moreover, since the alias for requesting activation is not bound to the user profile, the activation of the alias is not necessarily related to the activation of the user profile, so that the flexibility of the alias operation is improved.
  • the method may further include: the alias management function entity stores an association between the identifier of the user and the activated alias.
  • the alias management function entity may store the user's identity in the activated user information corresponding to the alias.
  • the identifier of the alias requested by the user is xxx
  • the identifier of the user is user service ID4.
  • the alias management function entity may add the identifier of the user user service ID4 to the activation list shown in Table 2. The corresponding location in .
  • the method may further include: the alias management function entity sending a notification message to the second client.
  • the alias management function entity may send a notification message to the second client to notify the second client that the user successfully activates the alias. And can be addressed to the user.
  • the second client may be a client used by a user who successfully activates the alias.
  • the user who successfully activates the alias may be in a state in which the alias is still activated, instead of the user who has activated the alias and subsequently activated the alias.
  • it may be a client used by the user corresponding to the identifier of another user included in the activation user information corresponding to the alias.
  • the alias management function entity may send an activation notification message to the emergency task service server.
  • the activation notification message may include an identifier of the activated activation alias and an identifier of the user, and the identifier of the activated successful alias is associated with the identifier of the user, so that the emergency mission service server can subsequently route and address the user.
  • the alias management function entity may send an activation notification message to the function alias management server, so that the alias management server performs maintenance and update of the information of the alias according to the receipt of the activation notification message.
  • the activation notification message is similar to the activation notification message sent by the alias management function entity to the emergency task service server when the alias management function entity is not configured in the emergency task service server, and details are not described herein again.
  • step 402 is replaced with the following steps:
  • the alias management function entity returns a failure response message to the first client when the user does not have the alias activation authority; or the alias management function entity when the user has the alias activation authority and the alias that is successfully activated does not exist in the alias requested to be activated A failure response message is returned to the first client.
  • an alias requesting activation is an alias that does not allow multiple users to activate at the same time, and the alias activated by the request is activated, the alias activated by the request becomes an alias that is not successfully activated.
  • the failure response message may include a reason for failure. For example, when a user does not have alias activation rights, the reason for the failure is that the authorization check failed.
  • the first client may apply for a higher authority to enable activation of the alias. For another example, when the user has the alias activation right, and the alias requesting activation is that the multiple users are not allowed to activate the alias at the same time and the alias requested to be activated is activated, the reason for the failure is that the alias requested to be activated is not allowed to activate the alias at the same time by multiple users. The alias requesting activation is activated.
  • the first client may request to take over the alias activated by the request to implement the alias.
  • Activation For another example, when the user has the alias activation right, and the alias requesting activation is an alias that allows multiple users to activate at the same time, and the number of users who successfully activate the alias requested to be activated is greater than the maximum activation number, the reason for the failure is successful activation request activation. The number of users of the alias is greater than the maximum number of activations.
  • the first client When the first client receives the failure reason that the number of users who successfully activate the request-activated alias is greater than the maximum activation number, the first client may apply for a higher alias priority right, thereby achieving the activation activation request activation of the alias. purpose.
  • FIG. 5 may be based on a pre-configured alias of the system, or based on the newly registered alias shown in FIG. 4, when the user needs to use an alias, the alias may be activated.
  • FIG. 6 is a method for managing an alias for deactivating an alias according to an embodiment of the present disclosure. As shown in FIG. 6, the method may include:
  • the alias management function entity receives a deactivation request message sent by the first client.
  • the deactivation request message may include an identifier of the user and an identifier of the alias requested to be deactivated.
  • the deactivation request message is used to request deactivation of the alias.
  • the user refers to the user who uses the first client.
  • the first client used by the user may send a deactivation request message carrying the identifier of the user and the identifier of the request to be deactivated to the alias management function entity for request. Deactivate the alias.
  • one deactivation request message may carry one or more identifiers of the user.
  • a deactivation request message may also carry the identifier of one or more aliases that are requested to be activated. Further, the deactivation request message may further include: a service type of the alias requesting the deactivation.
  • the alias management function entity sends a deactivation response message to the first client.
  • the deactivation response message may include deactivating the identifier of the successful alias and the identifier of the user.
  • the deactivation response message when the deactivation request message includes an identifier of multiple aliases that are requested to be deactivated, includes identifiers of all deactivated aliases in the plurality of aliases that are requested to be deactivated. Further, the deactivation response message may further include a service type for deactivating a successful alias.
  • the alias management function entity may send a deactivation response message carrying the identifier of the user and the identifier of the deactivated successful alias to the first client, so that the first client knows that the request is deactivated.
  • the alias has been successfully deactivated.
  • the nickname management function entity in step 502 can determine that the user has the alias deactivation authority in the following manner, and is not limited.
  • whether the alias deactivation permission is an attribute of the user, and the attribute is associated with the identifier of the user, and the alias management function entity may deactivate according to the deactivation request message after receiving the deactivation request message.
  • the foregoing method may further include: the alias management function entity may perform an authorization check on the user.
  • the method further includes: the alias management function entity acquires the alias permission related information according to the identifier of the user, and determines, according to the information about the alias permission, whether the user has the alias deactivation authority.
  • the alias permission related information may be the subscription information of the user, or may be the policy information stored locally by the alias management function entity.
  • the nickname management function entity obtains the subscription information of the user according to the identifier of the user, and the subscription information of the user includes indication information, where the indication information is used to indicate whether the user has an alias to activate the privilege.
  • the alias management function entity can determine whether the user has an alias to activate the permission according to the user's subscription information.
  • the alias management function entity may determine that the user has an alias deactivation authority; or, when the indication information included in the subscription information is used to indicate that the user does not have an alias When the permission is activated, the alias management function entity can determine that the user does not have an alias to activate the permission.
  • the alias management function entity obtains the policy information, and determines, according to the policy information and the identifier of the user, whether the user has an alias deactivation permission, where the policy information includes the identifier of the user with the alias deactivation authority. .
  • the identifier of the user is included in the policy information, it is determined that the user has an alias deactivation authority; or, when the identifier of the user is not included in the policy information, it is determined that the user does not have an alias deactivation authority.
  • the authorization check of the user may be simultaneously performed according to the subscription information of the user and the policy information locally stored by the alias management function entity.
  • the method may further include: the alias management function entity may perform an authorization check on the user. After the authorization check succeeds, the alias management function entity determines whether the service type of the alias requested to be deactivated is the same as the service type corresponding to the identifier of the user. For example, when the service type of the alias requesting the deactivation is the same as the service type corresponding to the identifier of the user, the alias requesting the deactivation is an alias for successful deactivation.
  • the alias management function entity receives the deactivation request message sent by the first client, including the identifier of the user and the identifier of the alias requested to be deactivated, and when the user has the alias deactivation authority, the alias management The functional entity sends a deactivation response message to the first client including the identity of the user and the identity of the deactivated successful alias.
  • the alias management function entity After receiving the activation request message sent by the first client, the alias management function entity returns the identifier including the requester and deactivates to the first client when determining that the requester requesting the deactivation of the alias has the alias deactivation authority.
  • the deactivation response message of the identifier of the successful alias can realize the deactivation of the alias without the corresponding processing of the user profile configuring the alias, and solves the problem that the efficiency of the alias management is low and the system has a heavy processing load.
  • the method further includes: deleting, by the alias management function entity, an association relationship between the identifier of the user and the identifier of the successfully activated alias.
  • the alias management function entity may delete the user's identity from the activated user information corresponding to the alias that successfully deactivated. For example, if the identifier of the alias requested by the user is xxx and the identifier of the user is user service ID1, the user service ID1 in Table 2 shown in another embodiment of the present application may be deleted.
  • the method further includes: the alias management function entity sending a notification message to the second client.
  • the alias management function entity may send a notification message to the second client to notify the second client user to successfully deactivate the deactivated successful alias.
  • the second client may be a client used by other users who successfully activate the deactivated successful alias.
  • the user who successfully activates the deactivated successful alias may be in a state that is still actively activating the alias, rather than the user who has activated the alias and subsequently activated the alias.
  • it may be a client used by the user corresponding to the identifier of another user included in the activation user information corresponding to the deactivated successful alias, and the activated user information refers to the activated user information at the current moment.
  • the alias management function entity may send a deactivation notification message to the emergency task service server. For example, after the emergency task service server receives the deactivation notification message, the control of the call and the control of the media may be performed according to the deactivation notification message.
  • the deactivation notification message may include an identifier of the deactivated successful alias and an identifier of the user, and the identifier of the deactivated successful alias is associated with the identifier of the user.
  • the alias management function entity may send a deactivation notification message to the function alias management server, so that the alias management server performs maintenance and update of the information of the alias according to the receipt of the deactivation notification message.
  • the deactivation notification message is similar to the deactivation notification message sent by the alias management function entity to the emergency task service server when the alias management function entity is not configured in the emergency task service server, and details are not described herein again.
  • step 502 may be replaced by the following steps:
  • the alias management function entity When the user does not have an alias deactivation authority, the alias management function entity returns a failure response message to the first client.
  • the failure response message may include a reason for failure.
  • the reason for the failure is that the authorization check fails.
  • the first client may apply for a higher authority to enable the deactivation of the alias.
  • the reason for the failure is that the alias requested to be activated is not allowed to be deactivated.
  • the alias may be deactivated by using the method shown in FIG. 6.
  • the method of deactivation may be performed on the basis of the method shown in FIG. 5, which is not limited.
  • the alias when the user needs to take over an alias, the alias can be taken over.
  • FIG. 7 is a method for managing an alias for requesting an alias to be taken according to an embodiment of the present disclosure. As shown in FIG. 7, the method may include:
  • the alias management function entity receives a takeover request message sent by the first client.
  • the takeover request message may include an identifier of the user and an identifier of the alias to be taken over.
  • the takeover request message is used to request that the alias be taken over.
  • the user refers to the user who uses the first client.
  • the first client used by the user may send a takeover request message carrying the identifier of the user and the identifier of the request to take over to the alias management function entity for requesting the alias. Take over.
  • the first client may directly send a takeover request message to the alias management function entity, or may indirectly send a takeover request message to the alias management function entity through other functional entities, that is, the alias management function entity may directly receive the first client.
  • the takeover request message sent may also receive the takeover request message sent by the first client indirectly, and is not specifically limited herein.
  • a takeover request message may carry one or more identifiers of the user, and different identifiers correspond to different service types, such as MCPTT services, MCData services, MCVideo services, and other basic service types, railway applications, enterprise applications, and the like. business type.
  • a takeover request message may also carry an identifier of one or more aliases requesting to take over.
  • the takeover request message may further include: a service type of the alias requesting to take over
  • the alias management function entity sends a takeover response message to the first client.
  • the takeover response message may include an identifier of the user and an identifier of the alias that successfully takes over.
  • the takeover response message includes identifiers of all the successfully succeeded aliases among the multiple aliases that are requested to be taken over.
  • the alias management function entity may send a takeover response message carrying the identifier of the user and the identifier of the successfully taken alias to the first client, so that the first client knows that the alias taken over by the request has been successfully taken over.
  • the subsequent identification of the alias based on the successful takeover can be addressed to the user who uses the first client.
  • the takeover response message may further include a service type that takes over the successful alias.
  • the alias of the request takeover when the alias of the request takeover is an alias that allows the takeover, the alias of the request takeover becomes an alias for successful takeover; or, when the alias of the request takeover is an alias that is allowed to take over, and the service type of the alias to be taken over is requested by the user When the corresponding service type is the same, the alias to be taken over is the alias for successful takeover.
  • the alias management function entity in step 602 can determine that the user has the alias takeover authority in the following manner, and is not limited.
  • the alias management function entity may carry the request according to the takeover request. The identity of the user, knowing if the user has alias takeover permissions.
  • the method further includes: the alias management function entity may perform an authorization check on the user.
  • the method further includes: the alias management function entity obtains the information about the alias authority according to the identifier of the user, and determines whether the user has the alias takeover authority according to the information about the alias authority.
  • the alias permission related information may be the subscription information of the user, or may be the policy information stored locally by the alias management function entity.
  • the nickname management function entity obtains the subscription information of the user according to the identifier of the user, and the subscription information of the user includes indication information, where the indication information is used to indicate whether the user has an alias takeover authority.
  • the alias management function entity can determine whether the user has the alias takeover authority according to the user's subscription information.
  • the alias management function entity may determine that the user has the alias takeover authority; or, when the indication information included in the subscription information is used to indicate that the user does not have the alias takeover authority
  • the alias management function entity can determine that the user does not have alias takeover rights.
  • the alias management function entity obtains the policy information, and determines, according to the policy information and the identifier of the user, whether the user has an alias takeover authority, where the policy information includes an identifier of the user having the alias takeover authority.
  • the policy information includes an identifier of the user having the alias takeover authority.
  • the method before the step 602 is performed, the method further includes: the alias management function entity performs an authorization check on the user, and determines whether the alias to be taken over is an alias that allows the takeover.
  • the method may further include: when the number of the identifiers of the aliases requested to be taken over is 1, the alias management function entity performs an authorization check on the user, and determines whether the alias to be taken over is an alias allowed to be taken over. If the authorization check for the user is passed, and the alias to be taken over is an alias that allows the takeover, step 602 is performed; or
  • the alias management function entity When the number of the identifiers of the aliases requested to be taken over is greater than 1, the alias management function entity performs an authorization check on the user, and determines whether there is at least one alias allowed to be taken over in the alias of the request to take over, and if the authorization check for the user passes, and the request is made If there is at least one alias that allows the takeover in the alias of the takeover, step 602 is performed.
  • the alias management function entity may further determine whether the service type of the alias to be taken over is the same as the service type corresponding to the identifier of the user.
  • step 602 is performed.
  • the foregoing determining operation may be performed for the identifier of the alias taken over for each request, and Step 602 is performed when the identifier of each request-taken alias performs the above-mentioned judging operation and there is an alias of at least one request takeover that is successfully taken over.
  • the failure response message may be returned to the first client.
  • the attribute of the alias of the request takeover may include indication information indicating whether the alias taken over by the request is an alias that allows the takeover.
  • the alias management function entity receives the takeover request message sent by the first client, including the identifier of the user and the identifier of the alias to be taken over, and when the user has the alias takeover authority, the alias management function entity
  • the first client sends a takeover response message including the identity of the user and an identity that takes over the successful alias.
  • the alias management function entity After receiving the takeover request message sent by the first client, the alias management function entity returns an identifier including the requester's identity and the success takeover to the first client when determining that the requester requesting the takeover of the alias has the alias takeover authority.
  • the takeover response message of the identifier can implement the takeover of the alias without the corresponding processing of the user profile configuring the alias, and solves the problem of low efficiency of the alias management and heavy processing load of the system.
  • the method further includes: deleting, by the alias management function entity, an association relationship between the identifier of the successfully taken over alias and the identifier of the user using the second client.
  • the user using the second client may be a user who successfully activates an alias that successfully takes over.
  • the alias management function entity determines that the user has the alias takeover authority, if the successfully taken alias is activated by another user (the client used by other users is the second client), the identifier of the successfully taken alias can be deleted and these The association of the user's identity.
  • the alias management function entity may delete the identifiers of other users who activate the alias from the activated user information corresponding to the successfully taken alias.
  • the association relationship between the identifier of the user and the alias that succeeds in taking over can be stored.
  • the alias can be activated by executing the alias management method shown in FIG. 5.
  • the alias management function entity may delete the identifier of a user who activates the alias from the activated user information.
  • the user may be the user who activates the alias at the earliest time based on the time sorting, or may be the user who activates the alias at the latest, or the user who activates the alias based on the user's priority, the user with the lowest priority, ie, from the activated user information. Delete the identity of the user.
  • the priority designation of a specific user is related to algorithm implementation, and the present invention is not limited.
  • the method further includes: the alias management function entity notifying the second client of the message.
  • the notification message is used to notify the second client user to successfully take over the successful alias of the takeover or to notify the second client to activate the alias of the successful takeover. For example, after receiving the notification message, the second client may deactivate the successfully taken alias.
  • the second client may refer to a client used by a user who has activated the alias.
  • the user who has activated the alias may be in a state that is still actively activating the alias, instead of the user who has activated the alias and subsequently activated the alias.
  • the alias management function entity sends a notification message for notifying the user to successfully take over the alias of the successful takeover to the second client, or sending a notification message for notifying the second client to activate the alias of the successful takeover, so as to
  • the second client can deactivate the alias by performing the alias management method shown in FIG. 6.
  • the notification message can be a cause code or a plain text string when it is implemented.
  • the alias management function entity may send a takeover notification message to the emergency task service server.
  • the takeover notification message may include an identifier of the successfully taken over alias and the identifier of the user, and the identifier of the successful alias is associated with the identifier of the user.
  • the identifier of the user corresponding to the identifier of the successfully succeeded alias may be one user or multiple users.
  • the alias management function entity may also send a deactivation notification message to the emergency task service server.
  • the deactivation notification message includes an identifier of the deactivated successful alias and an identifier of the user.
  • control of the corresponding call and control of the media can be performed.
  • the alias management function entity may send a takeover notification message and a deactivation notification message to the function alias management server, so that the alias management server performs corresponding alias information maintenance and update, wherein
  • the takeover notification message and the deactivation notification message are similar to the takeover notification message and the deactivation notification message sent by the alias management function entity to the emergency task service server when the alias management function entity is not configured in the emergency task service server, respectively. Let me repeat.
  • the nickname management function entity sends a notification message to the emergency task service server, where the notification message includes an identifier of the successfully taken over alias and the identifier of the user, and includes: an identifier of the activated alias and the identifier of the user.
  • the notification message includes an identifier of the successfully taken over alias and the identifier of the user, and includes: an identifier of the activated alias and the identifier of the user.
  • instructions can be used to indicate which aliases were taken over and which ones were deactivated.
  • aliases that allow takeovers are not allowed to be activated simultaneously by multiple users.
  • the alias allowed to be taken over is an alias that allows multiple users to activate at the same time, and there are other users who successfully activate the allowed alias for the current time, it is to take over the alias of all other users, or take over the alias of a certain user, and How to choose which user's alias to take over can be based on the implementation, or the operator can specify the rules.
  • step 602 may be replaced by the following steps:
  • the alias management function entity When the user does not have the alias takeover authority, the alias management function entity returns a failure response message to the first client.
  • the alias management function entity returns a failure response message to the first client.
  • the failure response message may include a reason for failure. For example, when a user does not have an alias takeover permission, the reason for the failure is that the authorization check failed.
  • the first client receives the failure response message that the reason for the failure of the license is the authorization check failure, the first client can apply for a higher authority, so that the alias can be taken over.
  • the reason for the failure is that the alias to be taken over is an alias that is not allowed to take over.
  • the foregoing activation notification message, the deactivation notification message, and the takeover notification message may be distinguished by using different types of notification messages. It is also possible to use the same type of notification message, but in this case, the notification message needs to carry an indication information, which is used to indicate the type of the message. For example, 3 bits can be used to indicate the type of the notification message, such as "001" indicates an activation notification message, "010" indicates a deactivation notification message, and "011” indicates a takeover notification message.
  • the notification message includes the identifier of the user 1 and the identifier of the alias 1, and the indication information is 001, indicating that the notification message is used to notify the user 1 that the alias 1 is successfully activated.
  • FIG. 8 is a flowchart of an alias-based addressed call method according to an embodiment of the present disclosure. As shown in FIG. 8, the method may include:
  • the emergency task service server receives a call request message sent by the first client.
  • the call request message includes an identifier of the calling user and an identifier of the alias of the requested call.
  • the identifier of the calling user may refer to the identifier of the user corresponding to the first client that initiates the calling party.
  • the alias of the requested call may refer to the alias of the called party, and the alias of the requested call may be activated by one or more users, and the users who activate the alias of the requested call are invited to join the call.
  • the identifier of the alias requesting the call refers to the name or identifier that uniquely identifies the alias.
  • the identifier of the alias should include the domain name, similar to the group identifier.
  • the emergency task service server determines, according to the identity of the calling user, that the calling user has an alias call right.
  • the emergency task service server determines that the calling user has the alias call right and can have the following implementation manners:
  • the emergency task service server obtains the subscription information of the calling user according to the identity of the calling user.
  • the subscription information of the calling user includes indication information, where the indication information is used to indicate whether the user has the alias call right.
  • the emergency task service server determines that the calling user has an alias call right according to the subscription information of the calling user.
  • the emergency task service server may determine that the calling user has the alias call right; or, when the indication information included in the subscription information is used to indicate the main When the calling user does not have an alias call right, the emergency task service server can determine that the user does not have an alias call right.
  • the emergency task service server obtains policy information, where the policy information includes an identifier of a user having an alias call right.
  • the emergency task service server determines whether the calling user has an alias call right according to the policy information and the identity of the calling user.
  • the calling user when the identity of the calling user is included in the policy information, it is determined that the calling user has an alias call right; or, when the identity of the calling user is not included in the policy information, it is determined that the calling user does not have an alias call. Permissions.
  • the emergency task service server acquires, from the alias management function entity, the activated user information corresponding to the identifier of the alias of the requested call.
  • the activation user information includes an identifier of a user who activates an alias of the requested call.
  • the emergency task service server may send a request message including an identifier of the alias requesting the call to the alias management function entity, so that the alias management function entity returns the activated user information corresponding to the identifier of the alias of the request call to the emergency task service server.
  • the alias management function entity returns the activated user information corresponding to the identifier of the alias of the request call to the emergency task service server.
  • the returned active user information is: user service ID1, user service ID2, and user service ID3.
  • the emergency task service server invokes activation of the user in the user information according to the activated user information corresponding to the identifier of the alias of the requested call.
  • the emergency task service server can call the client used by the user whose user ID is user service ID1, user service ID2, and user service ID3.
  • the calling user and the called user are served by different emergency task service servers, for each called user in the activated user information, it is assumed that the service provided by the calling user is the emergency task service server 1,
  • the called user provides the service as the emergency task service server 2, and the emergency task service server 1 sends a call request message to the emergency task service server 2, and the call request message may include the identity of the calling user, the identity of the called user, and the identifier of the alias.
  • the emergency task service server 2 then sends the call request message to the client used by the called user, wherein the identifier of the alias in the call request message is an option for indicating that the call is a call made by an alias.
  • the client used by the called user can send a call response message to the emergency mission service server 1 through the emergency mission service server 2 to indicate acceptance of the call.
  • the service provided by the calling user and the called user is the emergency task service server 1, and the emergency task service server 1 can directly The client used by the called user sends the call request message.
  • the emergency task service server sends a call response message to the first client.
  • the call response message may include: an identifier of the calling user, an identifier of the alias of the successful call, and an identifier of the user who successfully calls the identifier corresponding to the identifier of the successful call.
  • the emergency task service server receives a call request message sent by the first client, where the call request message includes an identifier of the calling user and an identifier of the alias of the requested call, when the calling party When the user has the alias call right, the emergency task service server calls the user who activates the alias of the requested call according to the activated user information corresponding to the alias of the requested call.
  • the emergency task service server After receiving the call request message sent by the first client, including the identifier of the calling user and the identifier of the alias requesting the call, the emergency task service server corresponds to the alias of the requested call when determining that the calling user has the alias call right.
  • the user who activated the alias implements an alias-based addressed call.
  • the method shown in FIG. 8 can be performed, and the method can be performed on the basis of the activation of the alias in the method shown in FIG. 5.
  • each network element such as an alias management function entity, a client, etc.
  • each network element includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in a combination of hardware or hardware and computer software in combination with the algorithmic steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application may divide the function module by using the alias management function entity according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 9 is a schematic diagram showing a possible composition of the alias management function entity involved in the foregoing and the embodiment.
  • the alias management function entity may include the following. : receiving unit 81 and transmitting unit 82.
  • the receiving unit 81 is configured to support the step 301 in the alias management method shown in FIG. 4, the step 401 in the alias management method shown in FIG. 5, and the step 501 in the alias management method shown in FIG. Step 601 in the alias management method shown in FIG.
  • the sending unit 82 is configured to support the step 302 of the alias management method shown in FIG. 4, the step 402 in the alias management method shown in FIG. 5, and the step 502 in the alias management method shown in FIG. Step 602 and/or other send operations in the illustrated alias management method.
  • the alias management function entity may further include an obtaining unit 83 and a determining unit 84.
  • the obtaining unit 83 is configured to support the alias management function entity to perform the obtaining operation in the alias management method shown in FIG. 4-7.
  • the determining unit 84 is configured to support the alias management function entity to perform the determining operation and/or the determining operation in the alias management method shown in FIG. 4-7.
  • the alias management function entity may further include an allocating unit 85 or a storage unit 86 or a deleting unit 87.
  • the allocating unit 85 is configured to support the alias management function entity to perform the allocation operation in the alias management method shown in FIG.
  • the storage unit 86 is configured to support the alias management function entity to perform the storage operation in the alias management method shown in FIG. 5.
  • the deleting unit 87 is configured to support the alias management function entity to perform the deleting operation in the alias management method shown in FIG. 6 and FIG. 7.
  • the alias management function entity provided by the embodiment of the present application is used to execute the above-mentioned alias management method, so that the same effect as the above alias management method can be achieved.
  • FIG. 10 shows another possible composition diagram of the alias management function entity involved in the above embodiment.
  • the alias management function entity may include a processing module 91 and a communication module 92.
  • the processing module 91 is for controlling management of actions of the alias management function entity and/or other processes for the techniques described herein.
  • the processing module 91 is configured to support the alias management function entity to perform the obtaining operation in the alias management method shown in FIG. 4-7, and the determining operation and/or the determining operation in the alias management method shown in FIG. 4-7
  • the alias management function entity performs the allocation operation in the alias management method shown in FIG.
  • Communication module 92 is used to support communication between the alias management function entity and other network entities, such as communication with the functional entities or network entities illustrated in Figures 1, 2.
  • the communication module 92 is configured to support the alias management function entity to perform step 301 and step 302 in the alias management method shown in FIG. 4, and step 401 and step 402 in the alias management method shown in FIG. Step 501 and step 502 in the management method, and step 601 and step 602 in the alias management method shown in FIG.
  • the to-be-accessed node may further include a storage module 93 for storing program codes and data of the alias management function entity. It is also used to support the alias management function entity to perform storage operations.
  • the processing module 91 can be a processor or a controller. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor can also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 92 can be a transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage module 93 can be a memory.
  • the processing module 91 is a processor
  • the communication module 92 is a communication interface
  • the storage module 93 is a memory
  • the alias management function entity involved in the embodiment of the present application may be the alias management function entity shown in FIG. 3.
  • the embodiment of the present application further provides a chip system, where the chip system may include a processor for supporting the functions of the foregoing alias management function entity to implement the method in any of the methods of FIG. 4-8. Further optionally, the chip system may further include a memory for storing program instructions and data necessary for the alias management function entity.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be another division manner for example, multiple units or components may be used.
  • the combination may be integrated into another device, or some features may be ignored or not performed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may be one physical unit or multiple physical units, that is, may be located in one place, or may be distributed to multiple different places. . Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a readable storage medium.
  • the technical solution of the embodiments of the present application may be embodied in the form of a software product in the form of a software product in essence or in the form of a contribution to the prior art, and the software product is stored in a storage medium.
  • a number of instructions are included to cause a device (which may be a microcontroller, chip, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例公开了一种别名管理方法及设备，涉及通信领域，以解决现有技术不能实现对别名的动态管理问题。具体方案为：别名管理功能实体接收第一客户端发送的管理请求消息，该管理请求消息包括用户的标识以及请求管理的别名的信息，当用户具有别名管理权限时，别名管理功能实体向第一客户端发送管理响应消息，该管理响应消息包括用户的标识和管理成功的别名的信息。上述管理可以是注册、激活、去激活、接管等中的一种或多种。本申请实施例用于对别名的管理过程中。

Description

一种别名管理方法及设备
本申请要求于2017年07月17日提交中国专利局、申请号为201710583363.6、申请名称为“一种别名管理方法及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，尤其涉及一种别名管理方法及设备。
背景技术
第三代合作伙伴项目(the 3rd Generation Partnership Project，3GPP)标准化了一组基于3GPP长期演进(Long Term Evolution，LTE)系统的紧急任务业务，用于支撑公共安全场景下的集群通信。紧急任务业务可以包括紧急任务即按即说(Mission Critical Push To Talk，MCPTT)业务，紧急任务数据(Mission Critical Data，MCData)业务和紧急任务视频(Mission Critical Video，MCVideo)业务等基础业务。基于这些基础业务还可以构建如铁路应用、企业应用等其他业务。
在现有基于3GPP LTE系统的紧急任务服务系统中，每个用户拥有用于唯一识别其身份的标识。其中，针对不同的业务，同一个用户可以采用相同的标识，也可以采用不同的标识。用户的每个标识可以对应一个或多个别名(alias)。别名，是一种人、事、物、业在官方法定或规范的名称以外的名称，可用于书面，也可用于口语，别名也可称为昵称。在现有技术中，别名指的是用户的除标识以外的名称。例如，可以是电话号码格式的别名，如+86 130 xxxx xxxx，或者，可以是统一资源标识符(Uniform Resource Identifier，URI)格式的别名，如username@domain，或者，还可以是由自然人容易识别和记忆的文字或者符号构成的别名，具体的可以结合用户的身份，或工作单位，或所处位置等信息进行命名，如G20列车长，G20售票员，北京南站调度员等。
现有技术中的别名是在系统部署时预先配置在用户配置文件中的，在需要对别名进行如，注册、激活、去激活、接管等管理时，必须先对配置该别名的用户配置文件进行相应的处理，导致管理别名的效率低，系统处理负担重。例如，在用户需要新注册别名时，必须修改用户配置文件或者配置新的用户配置文件才能完成别名的注册。
发明内容
本申请实施例提供一种别名管理方法及设备，解决了别名管理效率低，系统处理负担重的问题。
为达到上述目的，本申请实施例采用如下技术方案：
本申请实施例的第一方面，提供一种别名管理方法，包括：
别名管理功能实体接收第一客户端发送的注册请求消息，该注册请求消息包括用户的标识以及请求注册的别名的名称；当用户具有别名注册权限时，别名管理功能实体向第一客户端发送注册响应消息，该注册响应消息包括用户的标识，注册成功的别名的名称和注册成功的别名的标识。
本申请实施例提供的别名管理方法，别名管理功能实体接收第一客户端发送的包括用户的标识以及请求注册的别名的名称的注册请求消息，当用户具有别名注册权限时，别名管理功能实体向第一客户端发送包括用户的标识，注册成功的别名的名称和注册成功的别名的标识的注册响应消息。别名管理功能实体在接收到第一客户端发送的注册请求消息之后，在确定请求对别名进行注册的请求者具有别名注册权限时，向第一客户端返回包括请求者的标识，注册成功的别名的名称和注册成功的别名的标识的注册响应消息，无需对配置该别名的用户配置文件进行相应的处理，便能够实现对别名的注册，解决了别名管理效率低，系统处理负担重的问题。
结合第一方面，在一种可能的实现方式中，别名管理功能实体向第一客户端发送注册响应消息之前，该别名管理方法还可以包括：别名管理功能实体根据用户的标识获取用户的签约信息，该签约信息包括指示信息，指示信息用于指示用户具有别名注册权限；或者，别名管理功能实体获取策略信息，并根据获取到的策略信息确定用户具有别名注册权限，该策略信息包括具有别名注册权限的用户的标识。
结合第一方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理方法还可以包括：当用户不具有别名注册权限时，别名管理功能实体可以向第一客户端发送失败响应消息，该失败响应消息中可以携带失败原因，该失败原因用于指示用户的授权检查失败。
结合第一方面或上述可能的实现方式，在另一种可能的实现方式中，别名管理功能实体向第一客户端发送注册响应消息之前，该别名管理方法还可以包括：当请求注册的别名的名称未注册时，别名管理功能实体为请求注册的别名分配标识，该注册成功的别名为请求注册的别名。
结合第一方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理方法还可以包括：当请求注册的别名的名称已注册时，别名管理功能实体可以向第一客户端发送失败响应消息，该失败响应消息中可以携带失败原因，该失败原因用于指示请求注册的别名已注册。
结合第一方面或上述可能的实现方式，在另一种可能的实现方式中，注册请求消息还可以包括以下至少一种：请求注册的别名的业务类型、请求注册的别名的属性、请求注册的别名的应用范围、请求注册的别名的有效时间。
结合第一方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理方法还可以包括：别名管理功能实体向第二客户端发送通知消息，该通知消息可以包括注册成功的别名的名称和注册成功的别名的标识。
结合第一方面或上述可能的实现方式，在另一种可能的实现方式中，在别名管理功能实体未设置在紧急业务服务服务器中时，该别名管理方法还可以包括：别名管理功能实体向紧急业务服务服务器发送通知消息，该通知消息可以包括注册成功的别名的名称和注册成功的别名的标识。
结合第一方面或上述可能的实现方式，在另一种可能的实现方式中，通知消息还可以包括以下至少一种：注册成功的别名的业务类型、注册成功的别名的属性、注册成功的别名的应用范围、注册成功的别名的有效时间。
本申请实施例的第二方面，提供一种别名管理方法，包括：
别名管理功能实体接收第一客户端发送的激活请求消息，该激活请求消息包括用户的标识以及请求激活的别名的标识；当用户具有别名激活权限时，别名管理功能实体向第一客户端发送激活响应消息，该激活响应消息包括用户的标识以及激活成功的别名的标识。
本申请实施例提供的别名管理方法，别名管理功能实体接收第一客户端发送的包括用户的标识以及请求激活的别名的标识的激活请求消息，当用户具有别名激活权限时，别名管理功能实体向第一客户端发送包括用户的标识和激活成功的别名的标识的激活响应消息。别名管理功能实体在接收到第一客户端发送的激活请求消息之后，在确定请求对别名进行激活的请求者具有别名激活权限时，向第一客户端返回包括请求者的标识和激活成功的别名的标识的激活响应消息，无需对配置该别名的用户配置文件进行相应的处理，便能够实现对别名的激活，解决了别名管理效率低，系统处理负担重的问题。
结合第二方面，在一种可能的实现方式中，别名管理功能实体向第一客户端发送激活响应消息之前，该别名管理方法还可以包括：别名管理功能实体根据用户的标识获取用户的签约信息，该签约信息包括指示信息，指示信息用于指示用户具有别名激活权限；或者，别名管理功能实体获取策略信息，并根据获取到的策略信息确定用户具有别名激活权限，策略信息包括具有别名激活权限的用户的标识。
结合第二方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理方法还可以包括：当用户不具有别名激活权限时，别名管理功能实体可以向第一客户端发送失败响应消息，该失败响应消息中可以携带失败原因，该失败原因用于指示用户的授权检查失败。
结合第二方面或上述可能的实现方式，在另一种可能的实现方式中，当请求激活的别名不是允许多个用户同时激活的别名，且请求激活的别名未激活时，激活成功的别名为请求激活的别名；或者，当请求激活的别名是允许多个用户同时激活的别名，且成功激活请求激活的别名的用户的个数大于0且小于最大激活数时，激活成功的别名为请求激活的别名；或者，当请求激活的别名不是允许多个用户同时激活的别名，且请求激活的别名未激活，且请求激活的别名的业务类型与用户的标识对应的业务类型相同时，激活成功的别名为请求激活的别名；或者，当请求激活的别名是允许多个用户同时激活的别名，且成功激活请求激活的别名的用户的个数大于0且小于最大激活数，且请求激活的别名的业务类型与用户的标识对应的业务类型相同时，激活成功的别名为请求激活的别名。其中，激活请求消息中还可以包括请求激活的别名的业务类型。
结合第二方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理方法还可以包括：当请求激活的别名不是允许多个用户同时激活的别名，但请求激活的别名已激活时，别名管理功能实体可以向第一客户端发送失败响应消息，该失败响应消息中可以携带失败原因，该失败原因用于指示请求激活的别名已激活；或者，当请求激活的别名是允许多个用户同时激活的别名，但成功激活请求激活的别名的用户的个数大于最大激活数时，别名管理功能实体可以向第一客户端发送失败响应消息，该失败响应消息中可以携带失败原因，该失败原因用于指示成功激活请求激活的别名 的用户的个数已达到最大激活数。
结合第二方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理方法还可以包括：别名管理功能实体存储用户的标识与激活成功的别名的关联关系。
结合第二方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理方法还可以包括：别名管理功能实体向第二客户端发送通知消息，通知消息用于通知第二客户端用户成功激活激活成功的别名。
结合第二方面或上述可能的实现方式，在另一种可能的实现方式中，激活响应消息中还可以包括激活成功的别名的业务类型。
结合第二方面或上述可能的实现方式，在另一种可能的实现方式中，在别名管理功能实体未设置在紧急业务服务服务器中时，该别名管理方法还可以包括：别名管理功能实体向紧急任务服务服务器发送激活通知消息，该激活通知消息包括用户的标识以及激活成功的别名的标识。
本申请实施例的第三方面，提供一种别名管理方法，包括：
别名管理功能实体接收第一客户端发送的去激活请求消息，该去激活请求消息包括用户的标识以及请求去激活的别名的标识；当用户具有别名去激活权限时，别名管理功能实体向第一客户端发送去激活响应消息，该去激活响应消息包括用户的标识以及去激活成功的别名的标识。
本申请实施例提供的别名管理方法，别名管理功能实体接收第一客户端发送的包括用户的标识以及请求去激活的别名的标识的去激活请求消息，当用户具有别名去激活权限时，别名管理功能实体向第一客户端发送包括用户的标识和去激活成功的别名的标识的去激活响应消息。别名管理功能实体在接收到第一客户端发送的激活请求消息之后，在确定请求对别名进行去激活的请求者具有别名去激活权限时，向第一客户端返回包括请求者的标识和去激活成功的别名的标识的去激活响应消息，无需对配置该别名的用户配置文件进行相应的处理，便能够实现对别名的去激活，解决了别名管理效率低，系统处理负担重的问题。
结合第三方面，在一种可能的实现方式中，别名管理功能实体向第一客户端发送去激活响应消息之前，该别名管理方法还可以包括：别名管理功能实体根据用户的标识获取用户的签约信息，该签约信息包括指示信息，指示信息用于指示用户具有别名去激活权限；或者，别名管理功能实体获取策略信息，并根据获取到的策略信息确定用户具有别名去激活权限，该策略信息包括具有别名去激活权限的用户的标识。
结合第三方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理方法还可以包括：当用户不具有别名去激活权限时，别名管理功能实体可以向第一客户端发送失败响应消息，该失败响应消息中可以携带失败原因，该失败原因用于指示用户的授权检查失败。
结合第三方面或上述可能的实现方式，在另一种可能的实现方式中，当请求去激活的别名的业务类型与用户的标识对应的业务类型相同时，去激活成功的别名为请求去激活的别名。其中，去激活请求消息还可以包括请求去激活的别名的业务类型。
结合第三方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理方法还可以包括：别名管理功能实体删除用户的标识与去激活成功的别名的标识的关 联关系。
结合第三方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理方法还可以包括：别名管理功能实体向第二客户端发送通知消息，通知消息用于通知第二客户端用户成功去激活去激活成功的别名。
结合第三方面或上述可能的实现方式，在另一种可能的实现方式中，去激活响应消息还可以包括去激活成功的别名的业务类型。
结合第三方面或上述可能的实现方式，在另一种可能的实现方式中，在别名管理功能实体未设置在紧急业务服务服务器中时，该别名管理方法还可以包括：别名管理功能实体向紧急任务服务服务器发送去激活通知消息，该去激活通知消息包括用户的标识以及去激活成功的别名的标识。
本申请实施例的第四方面，提供一种别名管理方法，包括：
别名管理功能实体接收第一客户端发送的接管请求消息，该接管请求消息包括用户的标识以及请求接管的别名的标识；当用户具有别名接管权限时，别名管理功能实体向第一客户端发送接管响应消息，该接管响应消息包括用户的标识以及接管成功的别名的标识。
本申请实施例提供的别名管理方法，别名管理功能实体接收第一客户端发送的包括用户的标识以及请求接管的别名的标识的接管请求消息，当用户具有别名接管权限时，别名管理功能实体向第一客户端发送包括用户的标识和接管成功的别名的标识的接管响应消息。别名管理功能实体在接收到第一客户端发送的接管请求消息之后，在确定请求对别名进行接管的请求者具有别名接管权限时，向第一客户端返回包括请求者的标识和接管成功的别名的标识的接管响应消息，无需对配置该别名的用户配置文件进行相应的处理，便能够实现对别名的接管，解决了别名管理效率低，系统处理负担重的问题。
结合第四方面，在一种可能的实现方式中，别名管理功能实体向第一客户端发送接管响应消息之前，该别名管理方法还可以包括：别名管理功能实体根据用户的标识获取用户的签约信息，该签约信息包括指示信息，指示信息用于指示用户具有别名接管权限；或者，别名管理功能实体获取策略信息，并根据获取到的策略信息确定用户具有别名接管权限，策略信息包括具有别名接管权限的用户的标识。
结合第四方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理方法还可以包括：当用户不具有别名接管权限时，别名管理功能实体可以向第一客户端发送失败响应消息，该失败响应消息中可以携带失败原因，该失败原因用于指示用户的授权检查失败。
结合第四方面或上述可能的实现方式，在另一种可能的实现方式中，当请求接管的别名是允许接管的别名时，接管成功的别名为请求接管的别名；或者，当请求接管的别名是允许接管的别名，且请求接管的别名的业务类型与用户的标识对应的业务类型相同时，接管成功的别名为请求接管的别名。其中，接管请求消息中还可以包括请求接管的别名的业务类型。
结合第四方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理方法还可以包括：当请求接管的别名不是允许接管的别名时，别名管理功能实体可以 向第一客户端发送失败响应消息，该失败响应消息中可以携带失败原因，该失败原因用于指示请求接管的别名不是允许接管的别名。
结合第四方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理方法还可以包括：别名管理功能实体删除接管成功的别名的标识与使用第二客户端的用户的标识的关联关系，并向第二客户端发送通知消息，该通知消息用于通知第二客户端用户成功接管接管成功的别名或用于通知第二客户端去激活接管成功的别名，使用第二客户端的用户为成功激活接管成功的别名的用户。
结合第四方面或上述可能的实现方式，在另一种可能的实现方式中，接管响应消息还可以包括接管成功的别名的业务类型。
结合第四方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理方法还可以包括：别名管理功能实体向紧急任务服务服务器发送接管通知消息，该接管通知消息包括用户的标识和接管成功的别名的标识。
结合第四方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理方法还可以包括：别名管理功能实体向紧急任务服务服务器发送去激活通知消息，该去激活通知消息包括去激活接管成功的别名的标识和用户的标识。
本申请实施例的第五方面，提供一种别名管理功能实体，包括：接收单元，用于接收第一客户端发送的注册请求消息，注册请求消息包括用户的标识以及请求注册的别名的名称；发送单元，用于当用户具有别名注册权限时，向第一客户端发送注册响应消息，注册响应消息包括用户的标识，注册成功的别名的名称和注册成功的别名的标识。
结合第五方面，在一种可能的实现方式中，该别名管理功能实体还可以包括：获取单元，用于根据接收单元接收到的用户的标识获取用户的签约信息，签约信息包括指示信息，指示信息用于指示用户具有别名注册权限；或者，获取单元，用于获取策略信息，确定单元，用于根据获取单元获取到的策略信息确定用户具有别名注册权限，策略信息包括具有别名注册权限的用户的标识。
结合第五方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理功能实体还可以包括：分配单元，用于当请求注册的别名的名称未注册时，为请求注册的别名分配标识，注册成功的别名为请求注册的别名。
结合第五方面或上述可能的实现方式，在另一种可能的实现方式中，注册请求消息还包括以下至少一种：请求注册的别名的业务类型、请求注册的别名的属性、请求注册的别名的应用范围、请求注册的别名的有效时间。
结合第五方面或上述可能的实现方式，在另一种可能的实现方式中，发送单元，还用于向第二客户端发送通知消息，通知消息包括注册成功的别名的名称和注册成功的别名的标识。
结合第五方面或上述可能的实现方式，在另一种可能的实现方式中，通知消息还包括以下至少一种：注册成功的别名的业务类型、注册成功的别名的属性、注册成功的别名的应用范围、注册成功的别名的有效时间。
本申请实施例的第六方面，提供一种别名管理功能实体，包括：接收单元，用于接收第一客户端发送的激活请求消息，激活请求消息包括用户的标识以及请求激活的 别名的标识；发送单元，用于当用户具有别名激活权限时，向第一客户端发送激活响应消息，激活响应消息包括用户的标识以及激活成功的别名的标识。
结合第六方面，在一种可能的实现方式中，该别名管理功能实体还可以包括：获取单元，用于根据接收单元接收到的用户的标识获取用户的签约信息，签约信息包括指示信息，指示信息用于指示用户具有别名激活权限；或者，获取单元，用于获取策略信息，确定单元，用于根据获取单元获取到的策略信息确定用户具有别名激活权限，策略信息包括具有别名激活权限的用户的标识。
结合第六方面或上述可能的实现方式，在另一种可能的实现方式中，当请求激活的别名不是允许多个用户同时激活的别名，且请求激活的别名未激活时，激活成功的别名为请求激活的别名；或者，当请求激活的别名是允许多个用户同时激活的别名，且成功激活请求激活的别名的用户的个数大于0且小于最大激活数时，激活成功的别名为请求激活的别名；或者，当请求激活的别名不是允许多个用户同时激活的别名，且请求激活的别名未激活，且请求激活的别名的业务类型与用户的标识对应的业务类型相同时，激活成功的别名为请求激活的别名；或者，当请求激活的别名是允许多个用户同时激活的别名，且成功激活请求激活的别名的用户的个数大于0且小于最大激活数，且请求激活的别名的业务类型与用户的标识对应的业务类型相同时，激活成功的别名为请求激活的别名。
结合第六方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理功能实体还可以包括：存储单元，用于存储用户的标识与激活成功的别名的关联关系。
结合第六方面或上述可能的实现方式，在另一种可能的实现方式中，发送单元，还用于向第二客户端发送通知消息，通知消息用于通知第二客户端用户成功激活激活成功的别名。
本申请实施例的第七方面，提供一种别名管理功能实体，包括：接收单元，用于接收第一客户端发送的去激活请求消息，去激活请求消息包括用户的标识以及请求去激活的别名的标识；发送单元，用于当用户具有别名去激活权限时，向第一客户端发送去激活响应消息，去激活响应消息包括用户的标识以及去激活成功的别名的标识。
结合第七方面，在一种可能的实现方式中，该别名管理功能实体还可以包括：获取单元，用于根据用户的标识获取用户的签约信息，签约信息包括指示信息，指示信息用于指示用户具有别名去激活权限；或者，获取单元，用于获取策略信息，确定单元，用于根据获取单元获取到的策略信息确定用户具有别名去激活权限，策略信息包括具有别名去激活权限的用户的标识。
结合第七方面或上述可能的实现方式，在另一种可能的实现方式中，当请求去激活的别名的业务类型与用户的标识对应的业务类型相同时，去激活成功的别名为请求去激活的别名。
结合第七方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理功能实体还可以包括：删除单元，用于删除用户的标识与去激活成功的别名的标识的关联关系。
结合第七方面或上述可能的实现方式，在另一种可能的实现方式中，发送单元，还用于向第二客户端发送通知消息，通知消息用于通知第二客户端用户成功去激活去 激活成功的别名。
本申请实施例的第八方面，提供一种别名管理功能实体，包括：接收单元，用于接收第一客户端发送的接管请求消息，接管请求消息包括用户的标识以及请求接管的别名的标识；发送单元，用于当用户具有别名接管权限时，向第一客户端发送接管响应消息，接管响应消息包括用户的标识以及接管成功的别名的标识。
结合第八方面，在一种可能的实现方式中，该别名管理功能实体还可以包括：获取单元，用于根据接收单元接收到的用户的标识获取用户的签约信息，签约信息包括指示信息，指示信息用于指示用户具有别名接管权限；或者，获取单元，用于获取策略信息，确定单元，用于根据获取单元获取到的策略信息确定用户具有别名接管权限，策略信息包括具有别名接管权限的用户的标识。
结合第八方面或上述可能的实现方式，在另一种可能的实现方式中，当请求接管的别名是允许接管的别名时，接管成功的别名为请求接管的别名；或者，当请求接管的别名是允许接管的别名，且请求接管的别名的业务类型与用户的标识对应的业务类型相同时，接管成功的别名为请求接管的别名。
结合第八方面或上述可能的实现方式，在另一种可能的实现方式中，该别名管理功能实体还可以包括：删除单元，用于删除接管成功的别名的标识与使用第二客户端的用户的标识的关联关系，使用第二客户端的用户为成功激活接管成功的别名的用户；发送单元，还用于向第二客户端发送通知消息，通知消息用于通知第二客户端用户成功接管接管成功的别名或用于通知第二客户端去激活接管成功的别名。
本申请实施例的第九方面，提供一种别名管理功能实体，包括至少一个处理器、以及存储器；存储器用于存储计算机程序，使得计算机程序被至少一个处理器执行时实现如第一方面或第一方面的可能的实现方式，或者第二方面或第二方面的可能的实现方式，或者第三方面或第三方面的可能的实现方式，或者第四方面或第四方面的可能的实现方式中任一所述的别名管理方法。
本申请实施例的第十方面，提供一种计算机可读存储介质，用于存储计算机程序，该计算机程序用于执行如第一方面或第一方面的可能的实现方式，或者第二方面或第二方面的可能的实现方式，或者第三方面或第三方面的可能的实现方式，或者第四方面或第四方面的可能的实现方式中任一所述的别名管理方法的指令。
本申请实施例的第十一方面，提供一种芯片系统，该芯片系统包括处理器，用于支持别名管理功能实体实现上述方面中所涉及的功能，例如，例如生成或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存别名管理功能实体必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
附图说明
图1为现有技术提供的一种基于3GPP LTE系统的紧急任务服务应用层架构示意图；
图2为本申请实施例提供的一种系统架构的简化示意图；
图3为本申请实施例提供的一种别名管理功能实体的组成示意图；
图4为本申请实施例提供的一种别名管理方法的流程图；
图5为本申请实施例提供的另一种别名管理方法的流程图；
图6为本申请实施例提供的另一种别名管理方法的流程图；
图7为本申请实施例提供的另一种别名管理方法的流程图；
图8为本申请实施例提供的一种基于别名的寻址呼叫方法的流程图；
图9为本申请实施例提供的另一种别名管理功能实体的组成示意图；
图10为本申请实施例提供的另一种别名管理功能实体的组成示意图。
具体实施方式
基于3GPP LTE系统的紧急任务服务应用层架构如图1所示。其中，在紧急任务服务用户数据库(MC service user database)中保存有用户配置文件，该用户配置文件中包括用户的标识和与该标识对应的一个或多个别名。别名是官方法定或规范的名称以外的名称。针对不同的业务，同一个用户可以采用相同的标识，也可以采用不同的标识。用户的标识与该用户的标识对应的别名绑定，并保存在用户配置文件中。例如，针对MCPTT业务，用户的标识和与该用户的标识对应的别名绑定，针对MCData业务，用户的标识和与该用户的标识对应的别名绑定。只有当包含别名的用户配置文件由系统管理员通过配置管理服务器(Configuration Management Server，CMS)和配置管理客户端(Configuration Management Client，CMC)下发给该用户所使用的终端时，用户才能够使用这些别名时。并且，在需要对别名进行如，注册、激活、去激活、接管等管理时，必须先对包含该别名的用户配置文件进行相应的处理，如，动态临时在系统中注册一个别名时，必须先修改用户配置文件或配置新的用户配置文件才能完成别名的注册。
另外，别名还拥有一些描述其特征的信息，如别名在系统中唯一，别名允许多个用户同时使用，别名对应的用户的标识等。在铁路应用中，别名的信息具体的为：
1、别名是一个用户可以选择的别名，其与用户的职责或者任务绑定。
2、一个用户可以同时激活一个或者多个别名。每个激活的别名都是唯一的，可以作为用户的业务标识用于通信和寻址该别名对应的用户，即可以支持路由功能。示例性的，某个别名用于识别一个特定列车的司机，例如，TRAIN29列车上有两个司机，司机1的别名为Driver1_TRAIN29，司机2的别名为Driver2_TRAIN29，则别名Driver1_TRAIN29激活成功后便可以寻址到TRAIN29列车上的司机1，别名Driver2_TRAIN29激活成功后便可以寻址到TRAIN29列车上的司机2。
3、一个别名可以根据业务管理配置分配给多个用户使用，也可以根据业务管理配置被其他授权用户接管(taken over)。这两个要求是互斥的，即如果某个别名分配给多个用户使用，则该别名不能被接管。
4、授权用户可以注册新的别名。
综上，根据铁路应用中描述别名特性的信息可以得到的是，铁路应用中的别名要求用户可以自由选择，可以被灵活的激活、去激活，能够支持路由功能，可以被接管，可以新注册，这样，若仍采用现有技术将别名在系统部署时预先配置在用户配置文件中，则会导致管理别名的效率低，系统处理负担重。
为了解决别名管理效率低，系统处理负担重的问题，本申请实施例提供一种别名管理方法，其基本原理是：别名管理功能实体接收第一客户端发送的管理请求消息， 该管理请求消息包括用户的标识以及请求管理的别名的信息，当用户具有别名管理权限时，别名管理功能实体向第一客户端发送管理响应消息，该管理响应消息包括用户的标识和管理成功的别名的信息。其中，上述管理可以是注册、激活、去激活、接管等中的一种或多种。别名管理功能实体在接收到第一客户端发送的管理请求消息之后，在确定请求对别名进行管理的请求者具有别名管理权限时，向第一客户端返回包括请求者的标识和管理成功的别名的信息的管理响应消息，无需对配置该别名的用户配置文件进行相应的处理，便能够实现对别名的管理，解决了别名管理效率低，系统处理负担重的问题。
需要说明的是，在本申请实施例中，别名也可以称为功能别名(Functional alias)。且本申请实施例中的“多个”可以指两个或两个以上。
下面将结合附图对本申请实施例的实施方式进行详细描述。
图2示出的是可以应用本申请实施例的系统架构的简化示意图。如图2所示，该系统架构可以包括：功能别名管理服务器，功能别名管理客户端，以及图1所示的架构中的功能实体。
在具体实现中，本申请实施例中所述的别名管理功能实体可以集成在如图1所示的架构包括的紧急任务服务服务器(Mission Critical Service Server，MC Service Server/MC server)、组管理服务器(Group management server)、配置管理服务器(Configuration management server)、身份管理服务器(Identity management server)、密钥管理服务器(Key management server)、位置管理服务器(Location management server)中任意一个服务器中，也可以集成在功能别名管理服务器(Funcational-Alias management server)中。
在具体实现中，本申请实施例中所述的第一客户端可以集成在如图1所示的架构包括的紧急任务服务客户端(Mission Critical Service Client，MC Service Client/MC client)、组管理客户端(Group management client)、配置管理客户端(Configuration management client)、身份管理客户端(Identity management client)、密钥管理客户端(Key management client)、位置管理客户端(Location management client)中任意一个客户端中，也可以集成在功能别名管理客户端(Funcational-Alias management client)中。
其中，在本申请实施例中，别名管理功能实体能够提供系统的别名信息的存储和维护。别名信息可以包括以下一种或多种的组合：别名的名称、别名的标识、别名的属性、别名关联的用户的标识、别名的业务类型、别名的应用范围、别名的有效时间等。别名管理功能实体可以用于接收或拒绝用户发起的别名注册、别名激活、别名去激活、别名接管等操作，还可以用于通知用户其别名状态的变化，对用户操作别名进行授权，维护别名和用户的标识的关联关系等。第一客户端，用于向别名管理功能实体发起别名的注册、激活、去激活、接管等操作请求，还用于接收别名管理功能实体的通知别名状态变化的消息等。
另外，紧急任务服务服务器主要负责呼叫的控制和媒体的控制，其是一个逻辑实体。在具体实现中，可以是MCPTT server，MCVideo server或MCData server等。紧急任务服务客户端是与紧急任务服务服务器对等的应用层实体，主要负责应用层事务 的处理。
组管理服务器主要负责系统中群组的管理与群组信息的维护，如群组创建、解散、群组成员的变更等。组管理客户端是与组管理服务器对等的应用层实体，主要负责发起群组创建、解散、群组成员操作，更新群组信息等。
配置管理服务器主要负责对系统中的业务信息、用户信息进行配置，如向用户使用的终端下发用户配置文件。配置管理客户端是与配置管理服务器对等的应用层实体，主要负责接收配置管理服务器下发的配置信息。
身份管理服务器用于对用户的身份进行授权和鉴权，判断用户是一个合法的用户，并向身份管理客户端分发业务访问令牌。身份管理客户端是与身份管理服务器对等的应用层实体，用于在身份管理服务器对用户进行授权和鉴权过程中接收业务访问令牌。
密钥管理服务器主要负责安全密钥的管理，如生成、分发、更新等。密钥管理客户端是与秘钥管理服务器对等的应用层实体，主要负责接收、更新安全密钥等。
位置管理服务器主要负责用户位置的管理，如接收并保存用户的位置信息，将用户的位置信息提供给其他授权用户使用。位置管理客户端是与位置管理服务器对等的应用层实体，主要负责上报用户的位置信息，从位置管理服务器获取其他用户的位置信息。
功能别名管理服务器主要负责系统中别名的信息维护与更新，如增加别名，移除别名，更新别名，检索别名，向用户下发别名。功能别名管理客户端主要负责检索系统中的别名，接收功能别名管理服务器下发的别名。
紧急任务服务服务器与紧急任务服务客户端使用MCX-1接口通信，MCX-1接口对应不同的业务可以是MCPTT-1接口或MCVideo-1接口或MCData-1接口。功能实体之间可以采用相应的CSC接口进行通信。例如，位置管理服务器与位置管理客户端采用CSC-14进行通信，别名管理服务器和别名管理客户端采用CSC-xx进行通信，别名管理服务器还可以采用CSC-yy与紧急任务服务服务器进行通信。
需要说明的是，在本申请实施例中，图2所示的系统可以是基于紧急任务服务系统(Mission Critical Service System)的系统，且本申请实施例适用于MCPTT业务、MCData业务、MCVideo业务、铁路应用业务，或者其他类似业务，本申请实施例在此并不做具体限制。
图3为本申请实施例提供的一种别名管理功能实体的组成示意图，如图3所示，别名管理功能实体可以包括至少一个处理器21，存储器22、通信接口23、通信总线24。
下面结合图3对别名管理功能实体的各个构成部件进行具体的介绍：
处理器21是别名管理功能实体的控制中心，可以是一个处理器，也可以是多个处理元件的统称。例如，处理器21是一个中央处理器(Central Processing Unit，CPU)，也可以是特定集成电路(Application Specific Integrated Circuit，ASIC)，或者是被配置成实施本申请实施例的一个或多个集成电路，例如：一个或多个微处理器(Digital Signal Processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)。
其中，处理器21可以通过运行或执行存储在存储器22内的软件程序，以及调用 存储在存储器22内的数据，执行别名管理功能实体的各种功能。
在具体的实现中，作为一种实施例，处理器21可以包括一个或多个CPU，例如图3中所示的CPU0和CPU1。
在具体实现中，作为一种实施例，别名管理功能实体可以包括多个处理器，例如图3中所示的处理器21和处理器25。这些处理器中的每一个可以是一个单核处理器(single-CPU)，也可以是一个多核处理器(multi-CPU)。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
存储器22可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器22可以是独立存在，通过通信总线24与处理器21相连接。存储器22也可以和处理器21集成在一起。
其中，存储器22用于存储执行本申请方案的软件程序，并由处理器21来控制执行。
通信接口23，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(Wireless Local Area Networks，WLAN)等。通信接口23可以包括接收单元实现接收功能，以及发送单元实现发送功能。
通信总线24，可以是工业标准体系结构(Industry Standard Architecture，ISA)总线、外部设备互连(Peripheral Component，PCI)总线或扩展工业标准体系结构(Extended Industry Standard Architecture，EISA)总线等。该总线可以分为地址总线、数据总线、控制总线等。为便于表示，图3中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
图3中示出的设备结构并不构成对别名管理功能实体的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
需要说明的是，本申请实施例提供的别名管理方法，可以应用于对别名的注册、激活、去激活、接管等管理操作中，为了便于本领域技术人员的理解，本申请通过以下实施例对别名管理方法进行具体介绍。
图4-图7为本申请实施例提供的别名管理方法的流程图。图4为本申请实施例提供的请求对别名进行注册的别名管理方法，如图4所示，该方法可以包括：
301、别名管理功能实体接收第一客户端发送的注册请求消息。
其中，该注册请求消息可以包括用户(user)的标识和请求注册的别名的名称(name)。该注册请求消息用于请求对别名进行注册。
其中，用户指的是使用第一客户端的用户。
需要说明的是，上述用户可以是授权用户，即该用户具备别名注册权限，否则在 后续的授权检查中会导致授权检查失败，注册流程终止。
其中，用户的标识指的是唯一标识用户的字母和/或数字和/或特殊字符的任意组合。例如，用户的标识是MC service ID，MCPTT ID，MCVideo ID或MCData ID。
示例性的，当用户需要注册新别名时，用户所使用的第一客户端可以向别名管理功能实体发送携带该用户的标识和请求注册的别名的名称的注册请求消息，以用于请求对该别名进行注册。
需要说明的是，第一客户端可以直接向别名管理功能实体发送注册请求消息，也可以通过其他功能实体间接向别名管理功能实体发送注册请求消息，即别名管理功能实体可以直接接收第一客户端发送的注册请求消息，也可以间接接收第一客户端发送的注册请求消息，在此并不做具体限制。
在具体实现中，一个注册请求消息中可以携带用户的一个或多个标识，不同的标识对应不同的业务类型，例如，MCPTT业务、MCData业务、MCVideo业务等基础业务类型，铁路应用、企业应用等其他业务类型。一个注册请求消息中也可以携带一个或多个请求注册的别名的名称。当一个注册请求消息携带多个请求注册的别名的名称时，第一客户端通过发送一个注册请求消息，便可以请求对多个别名的进行注册。
进一步的，注册请求消息还可以包括以下至少一种：请求注册的别名的业务类型、请求注册的别名的属性(attribute)、请求注册的别名的应用范围(apply scope)、请求注册的别名的有效时间(valid time)。
其中，别名的业务类型用于标识该别名可以适用的业务类型，如MCPTT业务，MCVdieo业务，MCData业务，铁路应用业务等。通常情况下，别名的业务类型与用户的标识对应的业务类型相同，但是也可以不同。
别名的属性可以包括以下至少一种或多种的组合：是否允许多个用户同时激活的指示、允许多个用户同时激活时的最大激活数、是否允许接管的指示。
别名的应用范围用于标识该别名的应用范围，例如，该别名可以被哪些用户激活。在具体实现中，别名的应用范围可以是一个用户列表(user list)，也可以是一个用户角色列表(user role list)，如列车司机、列车售票员等。当然，当注册请求消息中未包括别名的应用范围这一参数时，可以表示该别名仅适用申请者自己，或者可以表示该别名适用于系统中的所有用户，缺失时具体的适用范围可以由系统运营者指定。
别名的有效时间用于标识该别名的有效时间，在具体实现中，别名的有效时间可以通过一个计时器实现，也可以是无限长时间即永久有效。当注册请求消息中未包含别名的有效时间这一参数时，可以表示该别名的有效时间是无限长时间，即永久有效的。
例如，别名的名称，别名的标识，别名的属性，别名的业务类型，别名的应用范围，别名的有效时间的具体的示例如表1所示。
表1
Figure PCTCN2018086754-appb-000001
Figure PCTCN2018086754-appb-000002
其中，别名的名称可以是用户易于识别、理解、记忆的字母、汉字、数字、特殊字符等的任意组合，如上表1中的G20列车主司机。
别名的标识可以是别名的名称，或者是特定格式的数字和/或字母和/或特殊符号的组合。例如，别名的标识可以包含国际编码、功能地址和功能编码；国际编码用于指示用户现在签约的网络，如中国086，法国033。功能地址由呼叫类型和用户号码组成。呼叫类型是一个前缀，用于区分不同类型的用户号码，对于网络来说也是一个指示如何解释所接收到的号码，如认为该号码对应着的是火车编号，或者是控制室编号，还是发动机编号。功能编码指示功能地址关联的角色。别名的标识可以用于通信与寻址用户，如别名的标识＝国际编码+功能地址(呼叫类型+用户号码)+功能编码＝049+2+0279+01。其中，国际编码＝049(049代表德国)，呼叫类型＝2(2代表火车)，用户号码＝0279(0279代表列出号码)，功能编码＝01(01代表主司机)。
302、当用户具有别名注册权限时，别名管理功能实体向第一客户端发送注册响应消息。
其中，注册响应消息中可以包括用户的标识，注册成功的别名的名称和注册成功的别名的标识(identify，ID)。
例如，第一客户端在接收到注册响应消息之后，当需要使用别名时，可以激活注册成功的别名，以便可以根据激活成功的该别名的标识寻址到使用第一客户端的用户。
需要说明的是，当别名的名称在全系统是唯一的时，可以将该别名的名称作为其标识，也可以为该别名分配能够识别该别名的全系统唯一的标识。
其中，当请求注册的别名的名称未注册时，注册成功的别名可以为该请求注册的别名。
示例性地，当请求注册的别名的个数为1，且该请求注册的别名未注册时，别名管理功能实体为该用户注册该别名，此时，请求注册的别名成为注册成功的别名；或者，当请求注册的别名的个数大于1，且请求注册的别名中存在至少一个未注册的别名时，别名管理功能实体为该用户激活该至少一个别名，此时，至少一个未注册的别名成为注册成功的别名。
进一步的，注册响应消息中还可以包括注册成功的别名的业务类型。
其中，注册成功的别名的标识可以是系统预先分配给该别名的，即别名的名称和别名的标识的关联关系预先存储在别名管理功能实体中，也可以是别名管理功能实体为该别名分配的，例如，在确定用户具有别名注册权限时分配的，以便根据别名的标识寻址该用户。
其中，步骤302中别名管理功能实体可以采用如下方式来确定用户具有别名注册权限，不予限制。
在第一种可能的实现方式中，是否具有别名注册权限是用户的一个属性，且该属性与用户的标识存在关联关系，别名管理功能实体在接收到注册请求消息之后，可以根据注册请求中携带的用户的标识，获知用户是否具有别名注册权限。
在第二种可能的实现方式中，在执行步骤302之前，上述方法还可包括：别名管理功能实体可以对用户进行授权检查。
具体的，在步骤302之前，还可以包括：别名管理功能实体根据用户的标识获取别名权限相关信息，并根据该别名权限相关信息判断用户是否具有别名注册权限。该别名权限相关信息可以是用户的签约信息，也可以是别名管理功能实体本地存储的策略信息。
在一个可能的具体实现方式中，别名管理功能实体根据用户的标识获取该用户的签约信息，用户的签约信息中包括指示信息，该指示信息用于指示用户是否具有别名注册权限。别名管理功能实体根据用户的签约信息便可以判断用户是否具有别名注册权限。当签约信息中包括的指示信息用于指示用户具有别名注册权限时，别名管理功能实体可以确定用户具有别名注册权限；或者，当签约信息中包括的指示信息用于指示用户不具有别名注册权限时，别名管理功能实体可以确定用户不具有别名注册权限。
示例性的，在签约信息中，可以用1比特来的指示用户是否具有别名注册权限，如“1”表示用户具有别名注册权限，“0”表示用户不具有别名注册权限。另外，在签约信息中，不仅可以指示用户是否具有别名注册权限，还可以在用户具有别名注册权限时，指示该用户是对哪些别名(一个或多个别名)具有别名注册权限。例如，签约信息中仅用“1”指示用户具有别名注册权限，此时可以隐含表示该用户对所有别名均有别名注册权限。再例如，签约信息中仅包括允许用户注册的别名列表，此时，表明该用户具有别名注册权限，且仅对别名列表中的别名具有别名注册权限。
在另一个可能的具体实现方式中，别名管理功能实体获取策略信息，并根据策略信息判断该用户是否具有别名注册权限，该策略信息中包括具有别名注册权限的用户的标识。
具体地，别名管理功能实体可以获取本地存储的策略信息，该策略信息中包括具有别名注册权限的一个或多个用户的标识，然后通过判断注册请求消息中包括的用户的标识是否包含在策略信息中，便可以确定出该用户是否具有别名注册权限。当用户的标识包含在策略信息中时，确定该用户具有别名注册权限；或者，当用户的标识未包含在策略信息中时，确定该用户不具有别名注册权限。
示例性的，在策略信息中，可以仅包括用户的标识以指示哪些用户具有别名注册权限。当然，还可以进一步的指示出具体针对哪些别名(一个或多个别名)用户具有别名注册权限。例如，策略信息中仅包括具有别名注册权限的用户的标识列表，此时，可以隐含表示这些用户对所有的别名均有别名注册权限。再例如，策略信息中包括具有别名列表及其对应具有别名注册权限的用户的标识列表，以表明这些用户仅对别名列表中的别名具有别名注册权限。
需要说明的是，在本申请实施例中，还可以同时根据用户的签约信息和别名管理功能实体本地存储的策略信息对用户的授权检查。
在第三种可能的实现方式中，在执行步骤302之前，还可以包括：别名管理功能 实体可以对用户进行授权检查，并判断请求注册的别名是否未注册。
具体的，在步骤302之前，还可以包括：当请求注册的别名的名称的个数为1时，别名管理功能实体对用户进行授权检查，并判断请求注册的别名是否未注册。
例如，若用户授权检查通过且请求注册的别名未注册，则执行步骤302；或者，当请求注册的别名的名称的个数大于1时，别名管理功能实体对用户进行授权检查，并判断请求注册的别名中是否存在至少一个未注册的别名，若用户授权检查通过且请求注册的别名中存在至少一个未注册的别名，则执行步骤302。
需要说明的是，在授权检查与判断请求注册的别名是否未注册的执行没有先后关系，此处不做具体限制。此外，在第三种实现方式中对用户进行授权检查的具体实现与第二种方式中的类似，在此不再一一赘述。
并且，当用户的签约信息或策略信息中不仅指示了用户是否具有别名注册权限，还指示了针对哪些别名具有别名注册权限的情况下，别名管理功能实体在确定用户针对某个请求注册的别名具有别名注册权限，且该请求注册的别名未注册时，执行步骤302；或者，在确定用户针对某个请求注册的别名不具有别名注册权限，或该请求注册的别名已注册时，表明该请求注册的别名不允许注册，此时可以向第一客户端返回失败响应消息。
本申请实施例提供的别名管理方法，别名管理功能实体接收第一客户端发送的包括用户的标识以及请求注册的别名的名称的注册请求消息，当用户具有别名注册权限时，别名管理功能实体向第一客户端发送包括用户的标识，注册成功的别名的名称和注册成功的别名的标识的注册响应消息。别名管理功能实体在接收到第一客户端发送的注册请求消息之后，在确定请求对别名进行注册的请求者具有别名注册权限时，向第一客户端返回包括请求者的标识，注册成功的别名的名称和注册成功的别名的标识的注册响应消息，无需对配置该别名的用户配置文件进行相应的处理，便能够实现对别名的注册，解决了别名管理效率低，系统处理负担重的问题。并且，请求注册的别名与业务类型没有绑定关系，能够被灵活操作。
可选地，在上述实施例的一种实现场景下，在步骤302中别名管理功能实体向第一客户端发送注册响应消息之前，上述方法还包括：
当请求注册的别名的名称未注册时，别名管理功能实体为该请求注册的别名分配标识。
示例性的，当请求注册的别名的名称未注册时，别名管理功能实体可以为该请求注册的别名生成一个标识，并分配给该请求注册的别名。在为该请求注册的别名生成标识时，可以根据标识的组成来生成，例如，别名的标识由国际编码、功能地址和功能编码三部分组成。需要说明的是，国际编码、功能地址和功能编码的相关描述可以参见步骤301中的描述，此处不再详细赘述。
示例性地，当请求注册的别名的名称的个数为1，且请求注册的别名未注册时，别名管理功能实体为请求注册的别名分配标识；或者，当请求注册的别名的名称的个数大于1，且请求注册的别名中存在至少一个未注册的别名时，别名管理功能实体为至少一个未注册的别名分配标识。
此时，步骤302中注册成功的别名则为该请求注册的别名。
可选地，在上述实施例的另一种实现场景下，在步骤302之后，上述方法还可以包括：别名管理功能实体向第二客户端发送通知消息。
其中，通知消息中可以包括注册成功的别名的名称和注册成功的别名的标识。
例如，别名管理功能实体通过向第二客户端发送包括注册成功的别名的名称和注册成功的别名的标识的通知消息，以通知第二客户端用户成功注册该注册成功的别名。
其中，第二客户端可以是系统中所有用户使用的客户端，也可以是属于注册成功的别名的应用范围内的用户使用的客户端。该应用范围可以是注册请求消息中携带的，也可以是别名管理功能实体为该别名分配的。
示例性的，当别名的应用范围是一个用户列表时，别名管理功能实体可以直接向用户列表中的用户使用的第二客户端发送通知消息，当别名的应用范围是一个用户角色列表时，别名管理功能实体可以经过其他功能实体，如紧急任务服务服务器的转发将通知消息发送给用户角色列表中角色对应的用户使用的第二客户端。
可选的，当别名管理功能实体未配置在紧急任务服务服务器中时，别名管理功能实体还可以向紧急任务服务服务器发送包括注册成功的别名的名称和注册成功的别名的标识的通知消息，以便于紧急任务服务服务器后续可以识别该注册成功的别名，进而可以寻址到激活了该别名的用户。
进一步的，通知消息还可以包括以下至少一种：注册成功的别名的业务类型、注册成功的别名的属性、注册成功的别名的应用范围、注册成功的别名的有效时间。其中，这些参数可以是由第一客户端处接收到的，也可以是别名管理功能实体分配的，此处不做具体限制。
作为上述实施例的一种可替代的方案，用于替换步骤302的步骤包括：
当用户不具有别名注册权限时，别名管理功能实体向第一客户端返回失败响应消息；或者，当用户具有别名注册权限，且请求注册的别名的名称已注册时，别名管理功能实体向第一客户端返回失败响应消息。
进一步的，该失败响应消息中可以包括失败原因。例如，当用户不具有别名注册权限时，失败原因为授权检查失败。第一客户端接收到携带失败原因是授权检查失败的失败响应消息时，第一客户端可以申请更高权限，以便能够进行别名的注册。再例如，当用户具有别名注册权限，且请求注册的别名的名称已注册时，失败原因为请求注册的别名的名称已注册。第一客户端在接收到失败原因是请求注册的别名的名称已注册时，第一客户端可以申请注册其他的别名。
需要指出的是，本申请涉及的名词在不同实施例之间可以相互借鉴。
图5为本申请实施例提供的请求对别名进行激活的别名管理方法，如图5所示，该方法可以包括：
401、别名管理功能实体接收第一客户端发送的激活请求消息。
其中，该激活请求消息可以包括用户的标识和请求激活的别名的标识。该激活请求消息用于请求对别名进行激活。
其中，用户指的是使用第一客户端的用户。
示例性的，当用户需要使用别名时，用户所使用的第一客户端可以向别名管理功能实体发送携带该用户的标识和请求激活的别名的标识的激活请求消息，以用于请求 对该别名进行激活。
需要说明的是，第一客户端可以直接向别名管理功能实体发送激活请求消息，也可以通过其他功能实体间接向别名管理功能实体发送激活请求消息，即别名管理功能实体可以直接接收第一客户端发送的激活请求消息，也可以间接接收第一客户端发送的激活请求消息，在此并不做具体限制。
在具体实现中，一个激活请求消息中可以携带用户的一个或多个标识，不同的标识对应不同的业务类型，例如MCPTT业务、MCData业务、MCVideo业务等基础业务类型，铁路应用、企业应用等其他业务类型。一个激活请求消息中也可以携带一个或多个请求激活的别名的标识。当一个激活请求消息携带多个请求激活的别名的标识时，第一客户端通过发送一个激活请求消息，便可以请求对多个别名的进行激活。
进一步的，激活请求消息还可以包括：别名的业务类型。
402、当用户具有别名激活权限时，别名管理功能实体向第一客户端发送激活响应消息。
其中，激活响应消息中可以包括用户的标识以及激活成功的别名的标识。
例如，当用户具有别名激活权限时，别名管理功能实体可以向第一客户端发送携带用户的标识和激活成功的别名的标识的激活响应消息，以便根据激活成功的别名的标识便可以寻址到使用第一客户端的用户。
进一步的，激活响应消息中还可以包括激活成功的别名的业务类型。
示例性地，当请求激活的别名不是允许多个用户同时激活的别名，且请求激活的别名未激活时，别名管理功能实体为该用户激活该别名，此时，请求激活的别名成为激活成功的别名；或者，当请求激活的别名是允许多个用户同时激活的别名，且成功激活请求激活的别名的用户的个数大于0且小于最大激活数时，别名管理功能实体为该用户激活该别名，此时，请求激活的别名成为激活成功的别名；或者，当请求激活的别名不是允许多个用户同时激活的别名，且请求激活的别名未激活，且请求激活的别名的业务类型与用户的标识对应的业务类型相同时，别名管理功能实体为该用户激活该别名，此时，请求激活的别名成为激活成功的别名；或者，当请求激活的别名是允许多个用户同时激活的别名，且成功激活请求激活的别名的用户的个数大于0且小于所述最大激活数，请求激活的别名的业务类型与用户的标识对应的业务类型相同时，别名管理功能实体为该用户激活该别名，此时，请求激活的别名成为激活成功的别名。
其中，步骤402中别名管理功能实体可以采用如下方式来确定用户具有别名激活权限，不予限制。
在第一种可能的实现方式中，是否具有别名激活权限是用户的一个属性，且该属性与用户的标识存在关联关系，别名管理功能实体在接收到激活请求消息之后，可以根据激活请求中携带的用户的标识，获知用户是否具有别名激活权限。
在第二种可能的实现方式中，在执行步骤402之前，上述方法还可包括：别名管理功能实体可以对用户进行授权检查。
具体的，在步骤402之前，还可以包括：别名管理功能实体根据用户的标识获取别名权限相关信息，并根据该别名权限相关信息判断用户是否具有别名激活权限。该别名权限相关信息可以是用户的签约信息，也可以是别名管理功能实体本地存储的策 略信息。
在一个可能的具体实现方式中，别名管理功能实体根据用户的标识获取该用户的签约信息，用户的签约信息中包括指示信息，该指示信息用于指示用户是否具有别名激活权限。别名管理功能实体根据用户的签约信息便可以判断用户是否具有别名激活权限。当签约信息中包括指示信息用于指示用户具有别名激活权限时，别名管理功能实体可以确定用户具有别名激活权限；或者，当签约信息中包括的指示信息用于指示用户不具有别名激活权限时，别名管理功能实体可以确定用户不具有别名激活权限。
在另一个可能的具体实现方式中，别名管理功能实体获取策略信息，并根据策略信息和用户的标识判断该用户是否具有别名激活权限，该策略信息中包括具有别名激活权限的用户的标识。当用户的标识包含在策略信息中时，确定该用户具有别名激活权限；或者，当用户的标识未包含在策略信息中时，确定该用户不具有别名激活权限。
需要说明的是，在本申请实施例中，还可以同时根据用户的签约信息和别名管理功能实体本地存储的策略信息对用户的授权检查。
在第三种可能的实现方式中，在执行步骤402之前，上述方法还可以包括：别名管理功能实体可以对用户进行授权检查，并在授权检查成功之后，别名管理功能实体可以判断请求激活的别名是否是允许多个用户同时激活的别名，并判断该请求激活的别名是否未激活。
例如，若请求激活的别名不是允许多个用户同时激活的别名，且请求激活的别名未激活，则执行步骤402；或者，若请求激活的别名是允许多个用户同时激活的别名，且成功激活请求激活的别名的用户的个数大于0且小于最大激活数，则也可以执行步骤402。
进一步的，在激活请求消息中包括请求激活的别名的业务类型时，还可以进一步的判断请求激活的别名的业务类型与用户的标识对应的业务类型相同。
例如，若请求激活的别名不是允许多个用户同时激活的别名，且请求激活的别名未激活，且请求激活的别名的业务类型与用户的标识对应的业务类型相同，则执行步骤402；或者，若请求激活的别名是允许多个用户同时激活的别名，且成功激活请求激活的别名的用户的个数大于0且小于所述最大激活数，请求激活的别名的业务类型与用户的标识对应的业务类型相同，则执行步骤402。
其中，在第三种实现方式中对用户进行授权检查的具体实现与第二种方式中的类似，此处不再一一赘述。
需要说明的是，在激活请求消息中包括两个或两个以上的请求激活的别名的标识时，可以在授权检查成功之后，针对每个请求激活的别名的标识执行上述判断操作，并在对每个请求激活的别名的标识执行了上述判断操作且存在至少一个请求激活的别名是成功激活的别名时，执行步骤402。另外，若请求激活的别名中不存在成功激活的别名，则可以向第一客户端返回失败响应消息。
示例性的，请求激活的别名是否是允许多个用户同时激活别名，当是允许多个用户同时激活别名时，允许激活的最大激活数包含在请求激活的别名的属性中。另外，别名管理功能实体可以在本地动态维护一个激活用户信息以便能够获知当前时刻激活别名的用户的个数，例如，可以在本地保存的一个激活用户列表，例如，如表2所示， 用于表示成功激活标识为xxx的别名的用户的标识为user service ID1、user service ID2以及user service ID3，成功激活标识为yyy的别名的用户的标识为user service ID7、user service ID9以及user service ID10。
表2
Figure PCTCN2018086754-appb-000003
本申请实施例提供的别名管理方法，别名管理功能实体接收第一客户端发送的包括用户的标识以及请求激活的别名的标识的激活请求消息，当用户具有别名激活权限时，别名管理功能实体向第一客户端发送包括用户的标识和激活成功的别名的标识的激活响应消息。别名管理功能实体在接收到第一客户端发送的激活请求消息之后，在确定请求对别名进行激活的请求者具有别名激活权限时，向第一客户端返回包括请求者的标识和激活成功的别名的标识的激活响应消息，无需对配置该别名的用户配置文件进行相应的处理，便能够实现对别名的激活，解决了别名管理效率低，系统处理负担重的问题。并且，由于请求激活的别名没有和用户配置文件绑定在一起，因此别名的激活与用户配置文件的激活与否没有必然联系，使得别名操作的灵活性得到提高。
可选的，在上述实施例的一种实现场景下，在步骤402之后，上述方法还可以包括：别名管理功能实体存储用户的标识与激活成功的别名的关联关系。
具体地，在别名管理功能实体确定用户具有别名激活权限时，还可以存储用户的标识与激活成功的别名的关联关系，即表示该用户成功激活该别名。示例性的，别名管理功能实体可以将用户的标识存储在与别名对应的激活用户信息中。例如，用户请求激活的别名的标识为xxx，用户的标识为user service ID4，当请求激活的别名激活成功时，别名管理功能实体可以将用户的标识user service ID4添加到表2所示的激活列表中的相应位置。
可选的，在上述实施例的另一种实现场景下，在步骤402之后，上述方法还可以包括：别名管理功能实体向第二客户端发送通知消息。
具体地，当请求激活的别名激活成功，且存在其他用户也同时成功激活了该别名时，别名管理功能实体可以向第二客户端发送通知消息，以通知第二客户端该用户成功激活该别名，进而可以寻址到该用户。
其中，第二客户端可以是成功激活该别名的用户使用的客户端。其中，成功激活该别名的用户可以是当前仍然处于保持激活该别名的状态，而不是曾经激活过该别名，后续又去激活该别名的用户。例如，可以是与该别名对应的激活用户信息中包括的其他用户的标识对应的用户使用的客户端。
进一步的，当别名管理功能实体未配置在紧急任务服务服务器中时，别名管理功能实体可以向紧急任务服务服务器发送激活通知消息。
其中，该激活通知消息可以包括激活成功的别名的标识和用户的标识，该激活成功的别名的标识与用户的标识存在关联关系，以便于紧急任务服务服务器后续可以消 息路由和寻址用户。
当别名管理功能实体未配置在功能别名管理服务器中时，别名管理功能实体可以向功能别名管理服务器发送激活通知消息，以便别名管理服务器根据接收到激活通知消息进行别名的信息维护与更新。该激活通知消息与当别名管理功能实体未配置在紧急任务服务服务器中时，别名管理功能实体向紧急任务服务服务器发送的激活通知消息类似，在此不再赘述。
作为上述实施例的一种可替代的方案，使用如下步骤替换步骤402：
当用户不具有别名激活权限时，别名管理功能实体向第一客户端返回失败响应消息；或者，当用户具有别名激活权限，且请求激活的别名中不存在成功激活的别名时，别名管理功能实体向第一客户端返回失败响应消息。
例如，当请求激活的别名是不允许多个用户同时激活的别名，且该请求激活的别名已激活时，该请求激活的别名成为未成功激活的别名。
进一步的，该失败响应消息中可以包括失败原因。例如，当用户不具有别名激活权限时，失败原因为授权检查失败。第一客户端接收到携带失败原因是授权检查失败的失败响应消息时，第一客户端可以申请更高权限，以便能够进行别名的激活。再例如，当用户具有别名激活权限，且请求激活的别名是不允许多个用户同时激活别名且请求激活的别名已激活时，失败原因为请求激活的别名是不允许多个用户同时激活别名且请求激活的别名已激活。第一客户端在接收到失败原因是请求激活的别名是不允许多个用户同时激活别名且请求激活的别名已激活时，第一客户端可以请求接管该请求激活的别名，以实现对该别名的激活。又例如，当用户具有别名激活权限，且请求激活的别名是允许多个用户同时激活的别名，且成功激活请求激活的别名的用户的个数大于最大激活数时，失败原因为成功激活请求激活的别名的用户的个数大于最大激活数。第一客户端在接收到失败原因是成功激活请求激活的别名的用户的个数大于最大激活数时，第一客户端可以申请更高的别名优先级权限，进而达到成功激活请求激活的别名的目的。
需要说明的是，本申请实施例中的具体描述可以参考本申请图4所示的实施例中对应内容的具体描述，仅将相应的“注册”替换为“激活”即可，本申请实施例在此不再详细赘述。
需要指出的是，图5所示实施例可以基于系统预先配置的别名，或者基于图4所示的新注册的别名，当用户需要使用别名时，可以对该别名进行激活。
图6为本申请实施例提供的请求对别名进行去激活的别名管理方法，如图6所示，该方法可以包括：
501、别名管理功能实体接收第一客户端发送的去激活请求消息。
其中，该去激活请求消息可以包括用户的标识和请求去激活的别名的标识。该去激活请求消息用于请求对别名进行去激活。
其中，用户指的是使用第一客户端的用户。
示例性的，当用户需要去激活别名时，用户所使用的第一客户端可以向别名管理功能实体发送携带该用户的标识和请求去激活的别名的标识的去激活请求消息，以用于请求对该别名进行去激活。
在具体实现中，一个去激活请求消息中可以携带用户的一个或多个标识。一个去激活请求消息中也可以携带一个或多个请求去激活的别名的标识。进一步的，去激活请求消息还可以包括：请求去激活的别名的业务类型。
502、当用户具有别名去激活权限时，别名管理功能实体向第一客户端发送去激活响应消息。
其中，去激活响应消息中可以包括去激活成功的别名的标识和用户的标识。
示例性的，当去激活请求消息中包括多个请求去激活的别名的标识时，该去激活响应消息中包括多个请求去激活的别名中所有去激活成功的别名的标识。进一步的，去激活响应消息中还可以包括去激活成功的别名的业务类型。
例如，当用户具有别名去激活权限时，别名管理功能实体可以向第一客户端发送携带用户的标识和去激活成功的别名的标识的去激活响应消息，以便第一客户端获知请求去激活的别名已成功去激活。
其中，步骤502中别名管理功能实体可以采用如下方式来确定用户具有别名去激活权限，不予限制。
在第一种可能的实现方式中，是否具有别名去激活权限是用户的一个属性，且该属性与用户的标识存在关联关系，别名管理功能实体在接收到去激活请求消息之后，可以根据去激活请求中携带的用户的标识，获知用户是否具有别名去激活权限。
在第二种可能的实现方式中，在执行步骤502之前，上述方法还可以包括：别名管理功能实体可以对用户进行授权检查。
具体的，在步骤502之前，还可以包括：别名管理功能实体根据用户的标识获取别名权限相关信息，并根据该别名权限相关信息判断用户是否具有别名去激活权限。该别名权限相关信息可以是用户的签约信息，也可以是别名管理功能实体本地存储的策略信息。
在一个可能的具体实现方式中，别名管理功能实体根据用户的标识获取该用户的签约信息，用户的签约信息中包括指示信息，该指示信息用于指示用户是否具有别名去激活权限。别名管理功能实体根据用户的签约信息便可以判断用户是否具有别名去激活权限。当签约信息中包括的指示信息用于指示用户具有别名去激活权限时，别名管理功能实体可以确定用户具有别名去激活权限；或者，当签约信息中包括的指示信息用于指示用户不具有别名去激活权限时，别名管理功能实体可以确定用户不具有别名去激活权限。
在另一个可能的具体实现方式中，别名管理功能实体获取策略信息，并根据策略信息和用户的标识判断该用户是否具有别名去激活权限，该策略信息中包括具有别名去激活权限的用户的标识。当用户的标识包含在策略信息中时，确定该用户具有别名去激活权限；或者，当用户的标识未包含在策略信息中时，确定该用户不具有别名去激活权限。
需要说明的是，在本申请实施例中，还可以同时根据用户的签约信息和别名管理功能实体本地存储的策略信息对用户的授权检查。
在第三种可能的实现方式中，当去激活请求消息中还包括请求去激活的别名的业务类型时，在执行步骤502之前，上述方法还可以包括：别名管理功能实体可以对用 户进行授权检查，并在授权检查成功之后，别名管理功能实体判断请求去激活的别名的业务类型与用户的标识对应的业务类型是否相同。例如，当请求去激活的别名的业务类型与用户的标识对应的业务类型相同时，请求去激活的别名成为去激活成功的别名。
本申请实施例提供的别名管理方法，别名管理功能实体接收第一客户端发送的包括用户的标识以及请求去激活的别名的标识的去激活请求消息，当用户具有别名去激活权限时，别名管理功能实体向第一客户端发送包括用户的标识和去激活成功的别名的标识的去激活响应消息。别名管理功能实体在接收到第一客户端发送的激活请求消息之后，在确定请求对别名进行去激活的请求者具有别名去激活权限时，向第一客户端返回包括请求者的标识和去激活成功的别名的标识的去激活响应消息，无需对配置该别名的用户配置文件进行相应的处理，便能够实现对别名的去激活，解决了别名管理效率低，系统处理负担重的问题。
可选的，在上述实施例的一种实现场景下，在步骤502之后，上述方法还包括：别名管理功能实体删除用户的标识与去激活成功的别名的标识的关联关系。
具体地，在别名管理功能实体确定用户具有别名去激活权限时，可以删除用户的标识与去激活成功的别名的标识的关联关系，即为该用户成功去激活该别名。示例性的，别名管理功能实体可以将用户的标识从与去激活成功的别名对应的激活用户信息中删除。例如，用户请求去激活的别名的标识为xxx，用户的标识为user service ID1，则可以将本申请另一实施例所示的表2中user service ID1删除。
可选的，在上述实施例的另一种实现场景下，在步骤502之后，上述方法还包括：别名管理功能实体向第二客户端发送通知消息。
例如，当去激活成功的别名被其他用户成功激活时，别名管理功能实体可以向第二客户端发送通知消息，以通知第二客户端用户成功去激活该去激活成功的别名。
其中，第二客户端可以是成功激活该去激活成功的别名的其他用户使用的客户端。成功激活该去激活成功的别名的用户可以是当前仍然处于保持激活该别名的状态，而不是曾经激活过该别名，后续又去激活该别名的用户。例如，可以是与去激活成功的别名对应的激活用户信息中包括的其他用户的标识对应的用户使用的客户端，且该激活用户信息指的是当前时刻的激活用户信息。
进一步的，当别名管理功能实体未配置在紧急任务服务服务器中时，别名管理功能实体可以向紧急任务服务服务器发送去激活通知消息。例如，在紧急任务服务服务器接收到去激活通知消息之后，可以根据去激活通知消息进行呼叫的控制和媒体的控制。
其中，该去激活通知消息可以包括去激活成功的别名的标识和用户的标识，该去激活成功的别名的标识与用户的标识存在关联关系。
当别名管理功能实体未配置在功能别名管理服务器中时，别名管理功能实体可以向功能别名管理服务器发送去激活通知消息，以便别名管理服务器根据接收到去激活通知消息进行别名的信息维护与更新。该去激活通知消息与当别名管理功能实体未配置在紧急任务服务服务器中时，别名管理功能实体向紧急任务服务服务器发送的去激活通知消息类似，在此不再赘述。
作为上述实施例的一种可替代的方案，可以采用如下步骤替换步骤502：
当用户不具有别名去激活权限时，别名管理功能实体向第一客户端返回失败响应消息。
进一步的，该失败响应消息中可以包括失败原因。例如，别名管理功能实体在确定用户不具有别名去激活权限时，失败原因为授权检查失败。第一客户端接收到携带失败原因是授权检查失败的失败响应消息时，第一客户端可以申请更高权限，以便能够进行别名的去激活。再例如，别名管理功能实体在确定用户具有别名去激活权限，且请求去激活的别名不允许去激活时，失败原因为请求激活的别名不允许去激活。
需要说明的是，本申请实施例中的具体描述可以参考本申请图5所示的实施例中对应内容的具体描述，仅将相应的“激活”替换为“去激活”即可，本申请实施例在此不再详细赘述。
需要指出的是，当用户需要去激活别名时，可以采用图6所示的方法对该别名进行去激活操作，该去激活的方法可以在图5所示的方法基础上执行，不予限制。
在本申请实施例中，当用户需要接管别名时，可以对该别名进行接管操作。
图7为本申请实施例提供的请求对别名进行接管的别名管理方法，如图7所示，该方法可以包括：
601、别名管理功能实体接收第一客户端发送的接管请求消息。
其中，该接管请求消息可以包括用户的标识和请求接管的别名的标识。该接管请求消息用于请求对别名进行接管。
其中，用户指的是使用第一客户端的用户。
示例性的，当用户需要接管别名时，用户所使用的第一客户端可以向别名管理功能实体发送携带该用户的标识和请求接管的别名的标识的接管请求消息，以用于请求对该别名进行接管。
需要说明的是，第一客户端可以直接向别名管理功能实体发送接管请求消息，也可以通过其他功能实体间接向别名管理功能实体发送接管请求消息，即别名管理功能实体可以直接接收第一客户端发送的接管请求消息，也可以间接接收第一客户端发送的接管请求消息，在此并不做具体限制。
在具体实现中，一个接管请求消息中可以携带用户的一个或多个标识，不同的标识对应不同的业务类型，例如MCPTT业务、MCData业务、MCVideo业务等基础业务类型，铁路应用、企业应用等其他业务类型。一个接管请求消息中也可以携带一个或多个请求接管的别名的标识。
进一步的，接管请求消息还可以包括：请求接管的别名的业务类型
602、当用户具有别名接管权限时，别名管理功能实体向第一客户端发送接管响应消息。
其中，接管响应消息中可以包括用户的标识以及接管成功的别名的标识。
示例性的，当接管请求消息中包括多个请求接管的别名的标识时，该接管响应消息中包括多个请求接管的别名中所有接管成功的别名的标识。
例如，当用户具有别名接管权限时，别名管理功能实体可以向第一客户端发送携带用户的标识和接管成功的别名的标识的接管响应消息，以便第一客户端获知请求接 管的别名已接管成功，后续根据接管成功的别名的标识便可以寻址到使用该第一客户端的用户。
进一步的，接管响应消息中还可以包括接管成功的别名的业务类型。
示例性的，当请求接管的别名是允许接管的别名时，请求接管的别名成为接管成功的别名；或者，当请求接管的别名是允许接管的别名，且请求接管的别名的业务类型与用户的标识对应的业务类型相同时，请求接管的别名成为接管成功的别名。
其中，步骤602中别名管理功能实体可以采用如下方式来确定用户具有别名接管权限，不予限制。
在第一种可能的实现方式中，是否具有别名接管权限是用户的一个属性，且该属性与用户的标识存在关联关系，别名管理功能实体在接收到接管请求消息之后，可以根据接管请求中携带的用户的标识，获知用户是否具有别名接管权限。
在第二种可能的实现方式中，在执行步骤602之前，上述方法还包括：别名管理功能实体可以对用户进行授权检查。
具体的，在步骤602之前，还可以包括：别名管理功能实体根据用户的标识获取别名权限相关信息，并根据该别名权限相关信息判断用户是否具有别名接管权限。该别名权限相关信息可以是用户的签约信息，也可以是别名管理功能实体本地存储的策略信息。
在一个可能的具体实现方式中，别名管理功能实体根据用户的标识获取该用户的签约信息，用户的签约信息中包括指示信息，该指示信息用于指示用户是否具有别名接管权限。别名管理功能实体根据用户的签约信息便可以判断用户是否具有别名接管权限。当签约信息中包括的指示信息用于指示用户具有别名接管权限时，别名管理功能实体可以确定用户具有别名接管权限；或者，当签约信息中包括的指示信息用于指示用户不具有别名接管权限时，别名管理功能实体可以确定用户不具有别名接管权限。
在另一个可能的具体实现方式中，别名管理功能实体获取策略信息，并根据策略信息和用户的标识判断该用户是否具有别名接管权限，该策略信息中包括具有别名接管权限的用户的标识。当用户的标识包含在策略信息中时，确定该用户具有别名接管权限；或者，当用户的标识未包含在策略信息中时，确定该用户不具有别名接管权限。
在第三种可能的实现方式中，在执行步骤602之前，上述方法还包括：别名管理功能实体对用户进行授权检查，并判断请求接管的别名是否是允许接管的别名。
具体的，在步骤602之前，还可以包括：，当请求接管的别名的标识的个数为1时，别名管理功能实体对用户进行授权检查，并判断请求接管的别名是否是允许接管的别名，若对用户的授权检查通过，且请求接管的别名是允许接管的别名，则执行步骤602；或者，
当请求接管的别名的标识的个数大于1时，别名管理功能实体对用户进行授权检查，并判断请求接管的别名中是否存在至少一个允许接管的别名，若对用户的授权检查通过，且请求接管的别名中存在至少一个允许接管的别名，则执行步骤602。
需要说明的是，在授权检查与判断请求注册的别名是否未注册的执行没有先后关系，此处不做具体限制。此外，在第三种实现方式中对用户进行授权检查的具体实现与第二种方式中的类似，在此不再一一赘述。
进一步的，当接管请求消息中还包括请求接管的别名的业务类型时，别名管理功能实体还可以进一步的判断请求接管的别名的业务类型与用户的标识对应的业务类型是否相同。
例如，当请求接管的别名是允许接管的别名，且请求接管的别名的业务类型与用户的标识对应的业务类型相同时，执行步骤602。
需要说明的是，在接管请求消息中包括两个或两个以上的请求接管的别名的标识时，可以在授权检查成功之后，针对每个请求接管的别名的标识执行上述判断操作，并在对每个请求接管的别名的标识执行了上述判断操作且存在至少一个请求接管的别名是成功接管的别名时，执行步骤602。另外，若请求接管的别名中不存在成功接管的别名，则可以向第一客户端返回失败响应消息。
示例性的，请求接管的别名的属性中可以包括用于指示该请求接管的别名是否是允许接管的别名的指示信息。
本申请实施例提供的别名管理方法，别名管理功能实体接收第一客户端发送的包括用户的标识以及请求接管的别名的标识的接管请求消息，当用户具有别名接管权限时，别名管理功能实体向第一客户端发送包括用户的标识和接管成功的别名的标识的接管响应消息。别名管理功能实体在接收到第一客户端发送的接管请求消息之后，在确定请求对别名进行接管的请求者具有别名接管权限时，向第一客户端返回包括请求者的标识和接管成功的别名的标识的接管响应消息，无需对配置该别名的用户配置文件进行相应的处理，便能够实现对别名的接管，解决了别名管理效率低，系统处理负担重的问题。
可选的，在上述实施例的一种实现场景下，在步骤602之后，上述方法还包括：别名管理功能实体删除接管成功的别名的标识与使用第二客户端的用户的标识的关联关系。
其中，使用第二客户端的用户可以是成功激活接管成功的别名的用户。
具体地，在别名管理功能实体确定用户具有别名接管权限时，若接管成功的别名被其他用户(其他用户使用的客户端是第二客户端)激活，则可以删除接管成功的别名的标识与这些用户的标识的关联关系。示例性的，别名管理功能实体可以从该接管成功的别名对应的激活用户信息中删除激活该别名的其他用户的标识。并且，可以存储该用户的标识与接管成功的别名的关联关系。另外，在请求接管的别名未激活的情况下，可以通过执行图5所示的别名管理方法激活该别名。
例如，在别名管理功能实体确定用户具有别名接管权限的情况下，当接管成功的别名被其他用户激活时，别名管理功能实体可以从激活用户信息中删除激活该别名的一个用户的标识。这个用户可以是基于时间排序最早激活该别名的用户，或者可以是最晚激活该别名的用户，或者是基于用户的优先级，用户优先级最低的激活该别名的用户，即从激活用户信息中删除该用户的标识。具体用户的优先级指定是算法实现相关，本发明不予限定。
可选的，在上述实施例的另一种实现场景下，在步骤602之后，上述方法还包括：别名管理功能实体向第二客户端通知消息。
其中，该通知消息用于通知第二客户端用户成功接管该接管成功的别名或用于通 知第二客户端去激活该接管成功的别名。例如，第二客户端接收到通知消息之后，可以对该接管成功的别名进行去激活。
其中，第二客户端可以指的是已激活该别名的用户使用的客户端。其中，已激活该别名的用户可以是当前仍然处于保持激活该别名的状态，而不是曾经激活过该别名，后续又去激活该别名的用户。
具体地，别名管理功能实体通过向第二客户端发送用于通知用户成功接管该接管成功的别名的通知消息，或发送用于通知第二客户端去激活该接管成功的别名的通知消息，以便第二客户端可以通过执行图6所示的别名管理方法对该别名进行去激活。通知消息在具体实现时可以是一个原因代码(cause code)，也可以是一个明文字符串。
进一步的，当别名管理功能实体未配置在紧急任务服务服务器中时，别名管理功能实体可以向紧急任务服务服务器发送接管通知消息。
其中，该接管通知消息可以包括接管成功的别名的标识和用户的标识，该接管成功的别名的标识与用户的标识存在关联关系。接管成功的别名的标识对应的用户的标识可以是一个用户的，也可以是多个用户的。
当别名管理功能实体未配置在紧急任务服务服务器中时，别名管理功能实体还可以向紧急任务服务服务器发送去激活通知消息。其中，该去激活通知消息包括去激活成功的别名的标识和用户的标识。
例如，在紧急任务服务服务器接收到接管通知消息和/或去激活通知消息之后，可以进行相应的呼叫的控制和媒体的控制。
当别名管理功能实体未配置在功能别名管理服务器中时，别名管理功能实体可以向功能别名管理服务器发送接管通知消息以及去激活通知消息，以便别名管理服务器进行相应的别名信息维护与更新，其中，该接管通知消息和去激活通知消息分别与当别名管理功能实体未配置在紧急任务服务服务器中时，别名管理功能实体向紧急任务服务服务器发送的接管通知消息和去激活通知消息类似，在此不再赘述。
需要说明的是，上述两个通知消息中所要发送的具体内容可以通过一条消息实现。例如，别名管理功能实体向紧急任务服务服务器发送通知消息，该通知消息中包括接管成功的别名的标识和用户的标识，还包括：去激活成功的别名的标识和用户的标识。当然，可以采用指示信息，来指示哪些别名是被接管了，哪些别名是被去激活了。
一般地，允许接管的别名是不允许多个用户同时激活的。但是，如果允许接管的别名是允许多个用户同时激活的别名，且当前时刻存在其他用户成功激活该允许接管的别名，则是具体接管其他所有用户的别名，还是接管某一用户的别名，以及如何选择接管哪个用户的别名可以基于实现，也可以由运营者自行指定规则。
作为上述实施例的一种可替代的方案，可以采用如下步骤替换步骤602：
当用户不具有别名接管权限时，别名管理功能实体向第一客户端返回失败响应消息。或者，当用户具有别名接管权限，且请求接管的别名是不允许接管的别名时，别名管理功能实体向第一客户端返回失败响应消息。
进一步的，该失败响应消息中可以包括失败原因。例如，当用户不具有别名接管权限时，失败原因为授权检查失败。第一客户端接收到携带失败原因是授权检查失败的失败响应消息时，第一客户端可以申请更高权限，以便能够进行别名的接管。再例 如，当用户具有别名接管权限，且请求接管的别名是不允许接管的别名时，失败原因为请求接管的别名是不允许接管的别名。
需要说明的是，本申请实施例中的具体描述可以参考本申请图4所示的实施例中对应内容的具体描述，仅将相应的“注册”替换为“接管”即可，本申请实施例在此不再详细赘述。
需要说明的是，在本申请实施例中上述激活通知消息、上述去激活通知消息以及上述接管通知消息可以采用不同类型的通知消息进行区分。也可以是采用相同类型的通知消息，但此时需要在通知消息中携带一个指示信息，该指示信息用于指示该消息的类型，示例性的，可以用3比特来指示通知消息的类型，如“001”指示激活通知消息，“010”指示去激活通知消息，“011”指示接管通知消息。例如，通知消息包括用户1的标识和别名1的标识，且指示信息为001，则表示该通知消息用于通知用户1成功激活别名1。
图8为本申请实施例提供的基于别名的寻址呼叫方法的流程图，如图8所示，该方法可以包括：
701、紧急任务服务服务器接收第一客户端发送的呼叫请求消息。
其中，该呼叫请求消息包括主叫用户的标识以及请求呼叫的别名的标识。
其中，主叫用户的标识可以指的是发起呼叫方的第一客户端对应的用户的标识。
其中，请求呼叫的别名可以指的是被叫方的别名，该请求呼叫的别名可以被一个或多个用户激活，这些激活该请求呼叫的别名的用户都被邀请加入呼叫中。请求呼叫的别名的标识指的是唯一能够识别该别名的名称或标识。
在本申请实施例中，为实现别名的寻址和呼叫功能，别名的标识应该包含域名，类似群组标识。
702、紧急任务服务服务器根据主叫用户的标识确定该主叫用户具有别名呼叫权限。
其中，紧急任务服务服务器确定主叫用户具有别名呼叫权限可以有以下实现方式：
方式一：紧急任务服务服务器根据主叫用户的标识获取该主叫用户的签约信息，主叫用户的签约信息中包括指示信息，该指示信息用于指示用户是否具有别名呼叫权限。紧急任务服务服务器根据主叫用户的签约信息确定该主叫用户具有别名呼叫权限。
例如，当签约信息中包括的指示信息用于指示主叫用户具有别名呼叫权限时，紧急任务服务服务器可以确定主叫用户具有别名呼叫权限；或者，当签约信息中包括的指示信息用于指示主叫用户不具有别名呼叫权限时，紧急任务服务服务器可以确定用户不具有别名呼叫权限。
方式二：紧急任务服务服务器获取策略信息，该策略信息中包括具有别名呼叫权限的用户的标识。紧急任务服务服务器根据策略信息和主叫用户的标识判断该主叫用户是否具有别名呼叫权限。
例如，当主叫用户的标识包含在策略信息中时，确定该主叫用户具有别名呼叫权限；或者，当主叫用户的标识未包含在策略信息中时，确定该主叫用户不具有别名呼叫权限。
还可以结合方式一和方式二对用户进行授权检查。
703、紧急任务服务服务器从别名管理功能实体获取与请求呼叫的别名的标识对应 的激活用户信息。
其中，激活用户信息中包括激活该请求呼叫的别名的用户的标识。紧急任务服务服务器可以向别名管理功能实体发送包含请求呼叫的别名的标识的请求消息，以便别名管理功能实体向紧急任务服务服务器返回与该请求呼叫的别名的标识对应的激活用户信息。例如，如本申请另一实施例中的表2所示，当别名的标识为xxx时，返回的激活用户信息为：user service ID1，user service ID2，user service ID3。
704、紧急任务服务服务器根据与请求呼叫的别名的标识对应的激活用户信息，呼叫激活用户信息中的用户。
按照步骤703中的例子，紧急任务服务服务器可以呼叫用户的标识为user service ID1，user service ID2以及user service ID3的用户所使用的客户端。
示例性的，当主叫用户与被叫用户由不同的紧急任务服务服务器提供服务时，对于激活用户信息中的每个被叫用户，假设为主叫用户提供服务为紧急任务服务服务器1，为该被叫用户提供服务为紧急任务服务服务器2，紧急任务服务服务器1向紧急任务服务服务器2发送呼叫请求消息，该呼叫请求消息可以包括主叫用户的标识、被叫用户的标识和别名的标识，然后紧急任务服务服务器2向被叫用户使用的客户端发送该呼叫请求消息，其中，呼叫请求消息中的别名的标识为可选项，其用于指示呼叫是通过别名进行的呼叫。若被叫用户接收呼叫，则被叫用户使用的客户端可以通过紧急任务服务服务器2向紧急任务服务服务器1发送呼叫响应消息，以指示接受呼叫。当然，当主叫用户与被叫用户由相同的紧急任务服务服务器提供服务时，假设为主叫用户和被叫用户提供服务均为紧急任务服务服务器1，则可以由紧急任务服务服务器1直接向被叫用户使用的客户端发送该呼叫请求消息。
705、紧急任务服务服务器向第一客户端发送呼叫响应消息。
其中，呼叫响应消息中可以包括：主叫用户的标识、呼叫成功的别名的标识以及与该呼叫成功的别名的标识对应的成功呼叫的用户的标识。
本申请实施例提供的基于别名的寻址呼叫方法，紧急任务服务服务器接收第一客户端发送的呼叫请求消息，该呼叫请求消息包括主叫用户的标识以及请求呼叫的别名的标识，当主叫用户具有别名呼叫权限时，紧急任务服务服务器根据请求呼叫的别名对应的激活用户信息，呼叫激活该请求呼叫的别名的用户。紧急任务服务服务器在接收到第一客户端发送的包括主叫用户的标识以及请求呼叫的别名的标识的呼叫请求消息之后，在确定主叫用户具有别名呼叫权限时，呼叫与请求呼叫的别名对应的激活该别名的用户，实现了基于别名的寻址呼叫。
需要指出的是，当用户需要基于别名进行寻址呼叫时，可以执行图8所示的方法，该方法可以在图5所示的方法对别名进行激活的基础上执行。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个网元，例如别名管理功能实体、客户端等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的 应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对别名管理功能实体进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图9示出了上述和实施例中涉及的别名管理功能实体的一种可能的组成示意图，如图9所示，该别名管理功能实体可以包括：接收单元81和发送单元82。
其中，接收单元81，用于支持别名管理功能实体执行图4所示别名管理方法中的步骤301，图5所示别名管理方法中的步骤401，图6所示别名管理方法中的步骤501，图7所示别名管理方法中的步骤601。
发送单元82，用于支持别名管理功能实体执行图4所示别名管理方法中的步骤302，图5所示别名管理方法中的步骤402，图6所示别名管理方法中的步骤502，图7所示别名管理方法中的步骤602和/或其他发送操作。
在本申请实施例中，该别名管理功能实体进一步的还可以包括，获取单元83、确定单元84。
获取单元83，用于支持别名管理功能实体执行图4-图7所示别名管理方法中的获取操作。确定单元84，用于支持别名管理功能实体执行图4-图7所示别名管理方法中的确定操作和/或判断操作。
在本申请实施例中，该别名管理功能实体进一步的还可以包括，分配单元85或存储单元86或删除单元87。
分配单元85，用于支持别名管理功能实体执行图4所示别名管理方法中的分配操作。
存储单元86，用于支持别名管理功能实体执行图5所示别名管理方法中的存储操作。
删除单元87，用于支持别名管理功能实体执行图6和图7所示别名管理方法中的删除操作。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
本申请实施例提供的别名管理功能实体，用于执行上述别名管理方法，因此可以达到与上述别名管理方法相同的效果。
在采用集成的单元的情况下，图10示出了上述实施例中所涉及的别名管理功能实体的另一种可能的组成示意图。如图10所示，该别名管理功能实体可以包括：处理模块91和通信模块92。
处理模块91用于对别名管理功能实体的动作进行控制管理和/或用于本文所描述的技术的其它过程。如，处理模块91，用于支持别名管理功能实体执行图4-图7所示别名管理方法中的获取操作，图4-图7所示别名管理方法中的确定操作和/或判断操作，支持别名管理功能实体执行图4所示别名管理方法中的分配操作。通信模块92用于支 持别名管理功能实体与其他网络实体的通信，例如与图1、图2中示出的功能实体或网络实体之间的通信。具体的，如通信模块92用于支持别名管理功能实体执行图4所示别名管理方法中的步骤301、步骤302，图5所示别名管理方法中的步骤401、步骤402，图6所示别名管理方法中的步骤501、步骤502，图7所示别名管理方法中的步骤601、步骤602。待接入节点还可以包括存储模块93，用于存储别名管理功能实体的程序代码和数据。还用于支持别名管理功能实体执行存储操作。
其中，处理模块91可以是处理器或控制器。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块92可以是收发器、收发电路或通信接口等。存储模块93可以是存储器。
当处理模块91为处理器，通信模块92为通信接口，存储模块93为存储器时，本申请实施例所涉及的别名管理功能实体可以为图3所示的别名管理功能实体。
另外，本申请实施例还提供一种芯片系统，该芯片系统可以包括处理器，用于支持上述别名管理功能实体实现图4-图8中任一所述的方法所涉及的功能。进一步可选的，该芯片系统还可以包括存储器，该存储器用于存储别名管理功能实体必要的程序指令和数据。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该软件产品存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者 光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (41)

  1. 一种别名管理方法，其特征在于，包括：
    别名管理功能实体接收第一客户端发送的注册请求消息，所述注册请求消息包括用户的标识以及请求注册的别名的名称；
    当所述用户具有别名注册权限时，所述别名管理功能实体向所述第一客户端发送注册响应消息，所述注册响应消息包括所述用户的标识，注册成功的别名的名称和所述注册成功的别名的标识。
  2. 根据权利要求1所述的方法，其特征在于，所述别名管理功能实体向所述第一客户端发送注册响应消息之前，还包括：
    所述别名管理功能实体根据所述用户的标识获取所述用户的签约信息，所述签约信息包括指示信息，所述指示信息用于指示所述用户具有别名注册权限；或者，
    所述别名管理功能实体获取策略信息，并根据所述策略信息确定所述用户具有别名注册权限，所述策略信息包括具有别名注册权限的用户的标识。
  3. 根据权利要求1或2所述的方法，其特征在于，所述别名管理功能实体向所述第一客户端发送注册响应消息之前，还包括：
    当所述请求注册的别名的名称未注册时，所述别名管理功能实体为所述请求注册的别名分配标识，所述注册成功的别名为所述请求注册的别名。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，所述注册请求消息还包括以下至少一种：所述请求注册的别名的业务类型、所述请求注册的别名的属性、所述请求注册的别名的应用范围、所述请求注册的别名的有效时间。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，所述方法还包括：
    所述别名管理功能实体向第二客户端发送通知消息，所述通知消息包括所述注册成功的别名的名称和所述注册成功的别名的标识。
  6. 根据权利要求5所述的方法，其特征在于，所述通知消息还包括以下至少一种：所述注册成功的别名的业务类型、所述注册成功的别名的属性、所述注册成功的别名的应用范围、所述注册成功的别名的有效时间。
  7. 一种别名管理方法，其特征在于，包括：
    别名管理功能实体接收第一客户端发送的激活请求消息，所述激活请求消息包括用户的标识以及请求激活的别名的标识；
    当所述用户具有别名激活权限时，所述别名管理功能实体向所述第一客户端发送激活响应消息，所述激活响应消息包括所述用户的标识以及激活成功的别名的标识。
  8. 根据权利要求7所述的方法，其特征在于，所述别名管理功能实体向所述第一客户端发送激活响应消息之前，还包括：
    所述别名管理功能实体根据所述用户的标识获取所述用户的签约信息，所述签约信息包括指示信息，所述指示信息用于指示所述用户具有别名激活权限；或者，
    所述别名管理功能实体获取策略信息，并根据所述策略信息确定所述用户具有别名激活权限，所述策略信息包括具有别名激活权限的用户的标识。
  9. 根据权利要求7或8所述的方法，其特征在于，
    当所述请求激活的别名不是允许多个用户同时激活的别名，且所述请求激活的别 名未激活时，所述激活成功的别名为所述请求激活的别名；或者，
    当所述请求激活的别名是允许多个用户同时激活的别名，且成功激活所述请求激活的别名的用户的个数大于0且小于最大激活数时，所述激活成功的别名为所述请求激活的别名；或者，
    当所述请求激活的别名不是允许多个用户同时激活的别名，且所述请求激活的别名未激活激活所述请求激活的别名的用户数等于0，且所述请求激活的别名的业务类型与所述用户的标识对应的业务类型相同时，所述激活成功的别名为所述请求激活的别名；或者，
    当所述请求激活的别名是允许多个用户同时激活的别名，且成功激活所述请求激活的别名的用户的个数大于0且小于所述最大激活数，且所述请求激活的别名是允许多个用户同时激活的别名，且所述请求激活的别名的业务类型与所述用户的标识对应的业务类型相同时，所述激活成功的别名为所述请求激活的别名。
  10. 根据权利要求7-9中任一项所述的方法，其特征在于，所述方法还包括：
    所述别名管理功能实体存储所述用户的标识与所述激活成功的别名的关联关系。
  11. 根据权利要求7-10中任一项所述的方法，其特征在于，所述方法还包括：
    所述别名管理功能实体向第二客户端发送通知消息，所述通知消息用于通知所述第二客户端所述用户成功激活所述激活成功的别名。
  12. 一种别名管理方法，其特征在于，包括：
    别名管理功能实体接收第一客户端发送的去激活请求消息，所述去激活请求消息包括用户的标识以及请求去激活的别名的标识；
    当所述用户具有别名去激活权限时，所述别名管理功能实体向所述第一客户端发送去激活响应消息，所述去激活响应消息包括所述用户的标识以及去激活成功的别名的标识。
  13. 根据权利要求12所述的方法，其特征在于，所述别名管理功能实体向所述第一客户端发送去激活响应消息之前，还包括：
    所述别名管理功能实体根据所述用户的标识获取所述用户的签约信息，所述签约信息包括指示信息，所述指示信息用于指示所述用户具有别名去激活权限；或者，
    所述别名管理功能实体获取策略信息，并根据所述策略信息确定所述用户具有别名去激活权限，所述策略信息包括具有别名去激活权限的用户的标识。
  14. 根据权利要求12或13所述的方法，其特征在于，
    当所述请求去激活的别名的业务类型与所述用户的标识对应的业务类型相同时，所述去激活成功的别名为所述请求去激活的别名。
  15. 根据权利要求12-14中任一项所述的方法，其特征在于，所述方法还包括：
    所述别名管理功能实体删除所述用户的标识与所述去激活成功的别名的标识的关联关系。
  16. 根据权利要求12-15中任一项所述的方法，其特征在于，所述方法还包括：
    所述别名管理功能实体向第二客户端发送通知消息，所述通知消息用于通知所述第二客户端所述用户成功去激活所述去激活成功的别名。
  17. 一种别名管理方法，其特征在于，包括：
    别名管理功能实体接收第一客户端发送的接管请求消息，所述接管请求消息包括用户的标识以及请求接管的别名的标识；
    当所述用户具有别名接管权限时，所述别名管理功能实体向所述第一客户端发送接管响应消息，所述接管响应消息包括所述用户的标识以及接管成功的别名的标识。
  18. 根据权利要求17所述的方法，其特征在于，所述别名管理功能实体向所述第一客户端发送接管响应消息之前，还包括：
    所述别名管理功能实体根据所述用户的标识获取所述用户的签约信息，所述签约信息包括指示信息，所述指示信息用于指示所述用户具有别名接管权限；或者，
    所述别名管理功能实体获取策略信息，并根据所述策略信息确定所述用户具有别名接管权限，所述策略信息包括具有别名接管权限的用户的标识。
  19. 根据权利要求17或18所述的方法，其特征在于，
    当所述请求接管的别名是允许接管的别名时，所述接管成功的别名为所述请求接管的别名；或者，
    当所述请求接管的别名是允许接管的别名，且所述请求接管的别名的业务类型与所述用户的标识对应的业务类型相同时，所述接管成功的别名为所述请求接管的别名。
  20. 根据权利要求17-19中任一项所述的方法，其特征在于，所述方法还包括：
    所述别名管理功能实体删除所述接管成功的别名的标识与使用第二客户端的用户的标识的关联关系，并向所述第二客户端发送通知消息，所述通知消息用于通知所述第二客户端所述用户成功接管所述接管成功的别名或用于通知所述第二客户端去激活所述接管成功的别名，所述使用第二客户端的用户为成功激活所述接管成功的别名的用户。
  21. 一种别名管理功能实体，其特征在于，包括：接收单元和发送单元；
    所述接收单元，用于接收第一客户端发送的注册请求消息，所述注册请求消息包括用户的标识以及请求注册的别名的名称；
    所述发送单元，用于当所述用户具有别名注册权限时，向所述第一客户端发送注册响应消息，所述注册响应消息包括所述用户的标识，注册成功的别名的名称和所述注册成功的别名的标识。
  22. 根据权利要求21所述的别名管理功能实体，其特征在于，还包括：
    获取单元，用于根据所述接收单元接收到的所述用户的标识获取所述用户的签约信息，所述签约信息包括指示信息，所述指示信息用于指示所述用户具有别名注册权限；或者，
    获取单元，用于获取策略信息，确定单元，用于根据所述获取单元获取到的所述策略信息确定所述用户具有别名注册权限，所述策略信息包括具有别名注册权限的用户的标识。
  23. 根据权利要求21或22所述的别名管理功能实体，其特征在于，还包括：
    分配单元，用于当所述请求注册的别名的名称未注册时，为所述请求注册的别名分配标识，所述注册成功的别名为所述请求注册的别名。
  24. 根据权利要求21-23中任一项所述的别名管理功能实体，其特征在于，所述注册请求消息还包括以下至少一种：所述请求注册的别名的业务类型、所述请求注册 的别名的属性、所述请求注册的别名的应用范围、所述请求注册的别名的有效时间。
  25. 根据权利要求21-24中任一项所述的别名管理功能实体，其特征在于，
    所述发送单元，还用于向第二客户端发送通知消息，所述通知消息包括所述注册成功的别名的名称和所述注册成功的别名的标识。
  26. 根据权利要求25所述的别名管理功能实体，其特征在于，所述通知消息还包括以下至少一种：所述注册成功的别名的业务类型、所述注册成功的别名的属性、所述注册成功的别名的应用范围、所述注册成功的别名的有效时间。
  27. 一种别名管理功能实体，其特征在于，包括：接收单元和发送单元；
    所述接收单元，用于接收第一客户端发送的激活请求消息，所述激活请求消息包括用户的标识以及请求激活的别名的标识；
    所述发送单元，用于当所述用户具有别名激活权限时，向所述第一客户端发送激活响应消息，所述激活响应消息包括所述用户的标识以及激活成功的别名的标识。
  28. 根据权利要求27所述的别名管理功能实体，其特征在于，还包括：
    获取单元，用于根据所述接收单元接收到的所述用户的标识获取所述用户的签约信息，所述签约信息包括指示信息，所述指示信息用于指示所述用户具有别名激活权限；或者，
    获取单元，用于获取策略信息，确定单元，用于根据所述获取单元获取到的所述策略信息确定所述用户具有别名激活权限，所述策略信息包括具有别名激活权限的用户的标识。
  29. 根据权利要求27或28所述的别名管理功能实体，其特征在于，
    当所述请求激活的别名不是允许多个用户同时激活的别名，且所述请求激活的别名未激活时，所述激活成功的别名为所述请求激活的别名；或者，
    当所述请求激活的别名是允许多个用户同时激活的别名，且成功激活所述请求激活的别名的用户的个数大于0且小于最大激活数时，所述激活成功的别名为所述请求激活的别名；或者，
    当所述请求激活的别名不是允许多个用户同时激活的别名，且所述请求激活的别名未激活，且所述请求激活的别名的业务类型与所述用户的标识对应的业务类型相同时，所述激活成功的别名为所述请求激活的别名；或者，
    当所述请求激活的别名是允许多个用户同时激活的别名，且成功激活所述请求激活的别名的用户的个数大于0且小于所述最大激活数，且所述请求激活的别名的业务类型与所述用户的标识对应的业务类型相同时，所述激活成功的别名为所述请求激活的别名。
  30. 根据权利要求27-29中任一项所述的别名管理功能实体，其特征在于，还包括：
    存储单元，用于存储所述用户的标识与所述激活成功的别名的关联关系。
  31. 根据权利要求27-30中任一项所述的别名管理功能实体，其特征在于，
    所述发送单元，还用于向第二客户端发送通知消息，所述通知消息用于通知所述第二客户端所述用户成功激活所述激活成功的别名。
  32. 一种别名管理功能实体，其特征在于，包括：接收单元和发送单元；
    所述接收单元，用于接收第一客户端发送的去激活请求消息，所述去激活请求消息包括用户的标识以及请求去激活的别名的标识；
    所述发送单元，用于当所述用户具有别名去激活权限时，向所述第一客户端发送去激活响应消息，所述去激活响应消息包括所述用户的标识以及去激活成功的别名的标识。
  33. 根据权利要求32所述的别名管理功能实体，其特征在于，还包括：
    获取单元，用于根据所述用户的标识获取所述用户的签约信息，所述签约信息包括指示信息，所述指示信息用于指示所述用户具有别名去激活权限；或者，
    获取单元，用于获取策略信息，确定单元，用于根据所述获取单元获取到的所述策略信息确定所述用户具有别名去激活权限，所述策略信息包括具有别名去激活权限的用户的标识。
  34. 根据权利要求32或33所述的别名管理功能实体，其特征在于，
    当所述请求去激活的别名的业务类型与所述用户的标识对应的业务类型相同时，所述去激活成功的别名为所述请求去激活的别名。
  35. 根据权利要求32-34中任一项所述的别名管理功能实体，其特征在于，还包括：
    删除单元，用于删除所述用户的标识与所述去激活成功的别名的标识的关联关系。
  36. 根据权利要求32-35中任一项所述的别名管理功能实体，其特征在于，
    所述发送单元，还用于向第二客户端发送通知消息，所述通知消息用于通知所述第二客户端所述用户成功去激活所述去激活成功的别名。
  37. 一种别名管理功能实体，其特征在于，包括：接收单元和发送单元；
    所述接收单元，用于接收第一客户端发送的接管请求消息，所述接管请求消息包括用户的标识以及请求接管的别名的标识；
    发送单元，用于当所述用户具有别名接管权限时，向所述第一客户端发送接管响应消息，所述接管响应消息包括所述用户的标识以及接管成功的别名的标识。
  38. 根据权利要求37所述的别名管理功能实体，其特征在于，还包括：
    获取单元，用于根据所述接收单元接收到的所述用户的标识获取所述用户的签约信息，所述签约信息包括指示信息，所述指示信息用于指示所述用户具有别名接管权限；或者，
    获取单元，用于获取策略信息，确定单元，用于根据所述获取单元获取到的所述策略信息确定所述用户具有别名接管权限，所述策略信息包括具有别名接管权限的用户的标识。
  39. 根据权利要求37或38所述的别名管理功能实体，其特征在于，
    当所述请求接管的别名是允许接管的别名时，所述接管成功的别名为所述请求接管的别名；或者，
    当所述请求接管的别名是允许接管的别名，且所述请求接管的别名的业务类型与所述用户的标识对应的业务类型相同时，所述接管成功的别名为所述请求接管的别名。
  40. 根据权利要求37-39中任一项所述的别名管理功能实体，其特征在于，还包括：
    删除单元，用于删除所述接管成功的别名的标识与使用第二客户端的用户的标识的关联关系，所述使用第二客户端的用户为成功激活所述接管成功的别名的用户；
    所述发送单元，还用于向所述第二客户端发送通知消息，所述通知消息用于通知所述第二客户端所述用户成功接管所述接管成功的别名或用于通知所述第二客户端去激活所述接管成功的别名。
  41. 一种计算机可读存储介质，用于存储计算机程序，其特征在于，所述计算机程序用于执行权利要求1-20中任一项所述的别名管理方法的指令。
PCT/CN2018/086754 2017-07-17 2018-05-14 一种别名管理方法及设备 WO2019015382A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
JP2020501169A JP7036899B2 (ja) 2017-07-17 2018-05-14 エイリアス管理方法およびデバイス
EP18836132.3A EP3644556B1 (en) 2017-07-17 2018-05-14 Alias management method and device
KR1020217039641A KR20210149249A (ko) 2017-07-17 2018-05-14 별명 관리 방법 및 기기
BR112020000874-5A BR112020000874A2 (pt) 2017-07-17 2018-05-14 método e dispositivo de gerenciamento de pseudônimo
KR1020207004308A KR102336553B1 (ko) 2017-07-17 2018-05-14 별명 관리 방법 및 기기
US16/742,306 US11483315B2 (en) 2017-07-17 2020-01-14 Alias management method and device
JP2022032738A JP7260230B2 (ja) 2017-07-17 2022-03-03 エイリアスベースのアドレス指定発呼方法および装置
US17/953,077 US20230018257A1 (en) 2017-07-17 2022-09-26 Alias management method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710583363.6 2017-07-17
CN201710583363.6A CN109274779B (zh) 2017-07-17 2017-07-17 一种别名管理方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/742,306 Continuation US11483315B2 (en) 2017-07-17 2020-01-14 Alias management method and device

Publications (1)

Publication Number Publication Date
WO2019015382A1 true WO2019015382A1 (zh) 2019-01-24

Family

ID=65015983

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/086754 WO2019015382A1 (zh) 2017-07-17 2018-05-14 一种别名管理方法及设备

Country Status (7)

Country Link
US (2) US11483315B2 (zh)
EP (1) EP3644556B1 (zh)
JP (2) JP7036899B2 (zh)
KR (2) KR20210149249A (zh)
CN (3) CN109274779B (zh)
BR (1) BR112020000874A2 (zh)
WO (1) WO2019015382A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111866765A (zh) * 2019-04-30 2020-10-30 成都鼎桥通信技术有限公司 功能号状态信息更新的同步方法和系统
WO2021155937A1 (en) * 2020-02-06 2021-08-12 Nokia Technologies Oy Apparatus, method and computer program
US20220198444A1 (en) * 2019-04-15 2022-06-23 nChain Holdings Limited Computer-implemented system and method for implementing alias-based addressing for a distributed ledger
US20230122665A1 (en) * 2021-10-14 2023-04-20 Motorola Solutions, Inc. Method and system for onboarding client devices to a key management server

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111757278B (zh) * 2019-03-27 2022-04-29 成都鼎桥通信技术有限公司 一种功能号查询方法和装置
CN111131250B (zh) * 2019-12-24 2022-04-26 杭州迪普科技股份有限公司 一种客户端识别方法及装置
US20230275945A1 (en) * 2020-08-12 2023-08-31 Samsung Electronics Co., Ltd. A method for sharing a recording status inside a mission critical video group call
WO2022033679A1 (en) * 2020-08-12 2022-02-17 Nokia Solutions And Networks Oy Mission critical push to talk private call initiation improvements
WO2022035290A1 (en) * 2020-08-13 2022-02-17 Samsung Electronics Co., Ltd. Methods and systems to share functional alias in mission critical video

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101360091A (zh) * 2007-07-30 2009-02-04 中国电信股份有限公司 一种实现会话初始协议终端入会的装置、系统和方法
US20100049654A1 (en) * 2008-08-25 2010-02-25 Bruno Pilo System and methods for a multi-channel payment platform
CN103348761A (zh) * 2011-12-23 2013-10-09 Lg电子株式会社 具有有限用户接口的设备的激活
CN107465546A (zh) * 2017-08-04 2017-12-12 北京中兴高达通信技术有限公司 功能别称的配置方法、装置及系统、服务器

Family Cites Families (46)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7231605B1 (en) * 2000-04-07 2007-06-12 Intel Corporation Method and apparatus for mapping electronic devices coupled to a wireless network
US7634568B2 (en) * 2002-02-07 2009-12-15 Sprint Spectrum L.P. Method and system for facilitating services in a communication network through data-publication by a signaling server
JP2004222117A (ja) 2003-01-17 2004-08-05 Nippon Telegr & Teleph Corp <Ntt> 双方向映像通信システム、管理サーバ、双方向通信サーバ、クライアント端末、双方向映像通信プログラム、及びこのプログラムを記録した記録媒体
US20050015499A1 (en) * 2003-05-15 2005-01-20 Georg Mayer Method and apparatus for SIP user agent discovery of configuration server
JP3938911B2 (ja) 2003-07-01 2007-06-27 松下電器産業株式会社 ゲートキーパ装置および通信制御方法
KR100640440B1 (ko) * 2004-08-10 2006-10-30 삼성전자주식회사 이동통신 시스템에서의 푸시투토크 방식의 통화 중 전화통화 연결 방법
CA2588611A1 (en) 2004-11-24 2006-06-01 Talkplus, Inc. User-controlled telecommunications system
US20060149811A1 (en) 2004-12-31 2006-07-06 Sony Ericsson Mobile Communications Ab Method for remotely controlling media devices via a communication network
JP4551866B2 (ja) 2005-12-07 2010-09-29 株式会社リコー 通信システムおよび呼制御サーバ装置およびプログラム
US8849278B2 (en) * 2007-01-07 2014-09-30 Jeffrey Bush Mobile device activation
US10089658B2 (en) * 2007-04-09 2018-10-02 Yellowpages.Com Llc Systems and methods to provide connections via callback acceptance cross-reference to related applications
CN101039322A (zh) * 2007-04-20 2007-09-19 华中师范大学 一种普适计算的动态访问控制方法
US8010158B2 (en) * 2007-12-21 2011-08-30 Nokia Corporation Synchronization of mobile terminals
US20090263139A1 (en) * 2008-04-16 2009-10-22 Tellabs Vienna, Inc. Method and apparatus for increasing voice service for an optical network terminal (ONT)
EP2112799A1 (en) * 2008-04-25 2009-10-28 Koninklijke KPN N.V. Service integrity handling in an IMS-based system
US20100036925A1 (en) * 2008-08-07 2010-02-11 Tactara, Llc Alias management platforms
CN101404684B (zh) * 2008-11-10 2012-05-23 中兴通讯股份有限公司 一种显示用户别名的系统和方法
JP5115746B2 (ja) * 2009-01-28 2013-01-09 Ｎｅｃビッグローブ株式会社 通信システム、サーバ装置、情報処理方法およびプログラム
US8620316B2 (en) * 2009-08-17 2013-12-31 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus in a telecommunications network
CN102111343B (zh) * 2009-12-28 2014-07-02 中兴通讯股份有限公司 即时通讯控制的实现方法和系统
US8704863B2 (en) * 2010-04-07 2014-04-22 Apple Inc. Transitioning between circuit switched calls and video calls
US8336088B2 (en) * 2010-04-19 2012-12-18 Visa International Service Association Alias management and value transfer claim processing
CN102244845B (zh) * 2010-05-11 2015-08-12 中兴通讯股份有限公司 访问im业务系统存储服务器的方法和im业务系统
US8774168B2 (en) * 2011-04-14 2014-07-08 Skype Communication system and method
CN103391539B (zh) * 2012-05-11 2016-06-22 中国移动通信集团上海有限公司 互联网协议多媒体子系统ims的开户方法、装置及系统
IN2015DN01634A (zh) * 2012-08-06 2015-07-03 Globalroam Pte Ltd
WO2014028516A1 (en) * 2012-08-16 2014-02-20 Kumar Himalesh Cherukuvada System and method for mobile or web-based payment/credential process
US20140101161A1 (en) * 2012-10-09 2014-04-10 Manah Khalil Method and system to manage privacy of shared contact information.
CN104704795B (zh) * 2012-10-19 2018-04-27 统一有限责任两合公司 通过使用具有webRTC功能的网络浏览器创建虚拟SIP用户代理的方法和系统
US20140257956A1 (en) * 2013-03-06 2014-09-11 Cable Television Laboratories, Inc. Coupon code redemption
GB2513125A (en) * 2013-04-15 2014-10-22 Visa Europe Ltd Method and system for transmitting credentials
US9497684B2 (en) * 2014-11-20 2016-11-15 Qualcomm Incorporated Radio access technology handover optimization in a push-to-talk session
US10447590B2 (en) * 2014-11-20 2019-10-15 Oath Inc. Systems and methods for dynamic connection paths for devices connected to computer networks
US10834149B2 (en) * 2014-12-15 2020-11-10 At&T Intellectual Property I, L.P. Method and system for routing of session-based services
US20160330601A1 (en) * 2015-05-06 2016-11-10 Vikas Srivastava Method and system for managing public safety in at least one of unknown, unexpected, unwanted and untimely situations via offering indemnity in conjunction with wearable computing and communications devices
US10182082B2 (en) * 2015-05-13 2019-01-15 Nokia Solutions And Networks Oy User identities for PTT and MCPTT
US9843885B2 (en) * 2015-08-12 2017-12-12 Apple Inc. Methods, procedures and framework to provision an eSIM and make it multi-SIM capable using primary account information
CN105162785B (zh) * 2015-09-07 2019-01-04 飞天诚信科技股份有限公司 一种基于认证设备进行注册的方法和设备
CN105306577A (zh) * 2015-11-10 2016-02-03 上海卓易科技股份有限公司 基于app的手持设备间的资料共享系统及方法
US10097968B2 (en) * 2015-12-22 2018-10-09 Elizabeth McHugh Event-based interactive device system
CN105657196A (zh) * 2016-01-22 2016-06-08 钟声 一种用电话别名拨打电话号码的方法
US9832308B1 (en) * 2016-05-12 2017-11-28 Google Inc. Caller preview data and call messages based on caller preview data
CN105933881A (zh) * 2016-06-21 2016-09-07 广州中国科学院计算机网络信息中心 电话号码别名的生成、处理方法和系统
ES2960631T3 (es) * 2016-06-21 2024-03-05 Nokia Solutions & Networks Oy Acceso a servicios locales por usuarios no autenticados
FR3056781A1 (fr) * 2016-09-29 2018-03-30 Orange Attribution de profils a une pluralite de terminaux a cartes sim implantees
US10225727B2 (en) * 2017-05-12 2019-03-05 Metaswitch Networks Ltd. Data processing

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101360091A (zh) * 2007-07-30 2009-02-04 中国电信股份有限公司 一种实现会话初始协议终端入会的装置、系统和方法
US20100049654A1 (en) * 2008-08-25 2010-02-25 Bruno Pilo System and methods for a multi-channel payment platform
CN103348761A (zh) * 2011-12-23 2013-10-09 Lg电子株式会社 具有有限用户接口的设备的激活
CN107465546A (zh) * 2017-08-04 2017-12-12 北京中兴高达通信技术有限公司 功能别称的配置方法、装置及系统、服务器

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220198444A1 (en) * 2019-04-15 2022-06-23 nChain Holdings Limited Computer-implemented system and method for implementing alias-based addressing for a distributed ledger
CN111866765A (zh) * 2019-04-30 2020-10-30 成都鼎桥通信技术有限公司 功能号状态信息更新的同步方法和系统
CN111866765B (zh) * 2019-04-30 2022-02-08 成都鼎桥通信技术有限公司 功能号状态信息更新的同步方法和系统
WO2021155937A1 (en) * 2020-02-06 2021-08-12 Nokia Technologies Oy Apparatus, method and computer program
US20230122665A1 (en) * 2021-10-14 2023-04-20 Motorola Solutions, Inc. Method and system for onboarding client devices to a key management server
US11824972B2 (en) * 2021-10-14 2023-11-21 Motorola Solutions, Inc. Method and system for onboarding client devices to a key management server

Also Published As

Publication number Publication date
CN112261166A (zh) 2021-01-22
CN111917895B (zh) 2022-01-11
KR102336553B1 (ko) 2021-12-06
JP2022084690A (ja) 2022-06-07
EP3644556A1 (en) 2020-04-29
JP2020526983A (ja) 2020-08-31
KR20200020965A (ko) 2020-02-26
CN109274779B (zh) 2020-09-25
JP7036899B2 (ja) 2022-03-15
CN111917895A (zh) 2020-11-10
EP3644556A4 (en) 2020-04-29
CN109274779A (zh) 2019-01-25
BR112020000874A2 (pt) 2020-07-21
EP3644556B1 (en) 2024-03-20
KR20210149249A (ko) 2021-12-08
JP7260230B2 (ja) 2023-04-18
US11483315B2 (en) 2022-10-25
US20230018257A1 (en) 2023-01-19
US20200153838A1 (en) 2020-05-14

Similar Documents

Publication Publication Date Title
JP7260230B2 (ja) エイリアスベースのアドレス指定発呼方法および装置
US9860234B2 (en) Bundled authorization requests
US9544294B2 (en) Pluggable authorization policies
WO2019042110A1 (zh) 一种订阅发布方法及服务器
WO2019037775A1 (zh) 下发业务配置文件
EP3226506B1 (en) Sophisitcated preparation of an authorization token
CN106878084B (zh) 一种权限控制方法和装置
JP6940240B2 (ja) 証明書取得方法、認証方法及びネットワークデバイス
WO2015042349A1 (en) Multiple resource servers with single, flexible, pluggable oauth server and oauth-protected restful oauth consent management service, and mobile application single sign on oauth service
WO2020083322A1 (zh) 一种呼叫方法、设备及系统
CN110049031B (zh) 一种接口安全认证方法及服务器、认证中心服务器
CN112352411A (zh) 利用不同的云服务网络的相同域的注册
US10268532B2 (en) Application message processing system, method, and application device
JP2011513848A (ja) セッション特有のｕｒｌおよび資源の実装
WO2009052735A1 (fr) Procédé, système et dispositif de gestion destinés à un paquet d&#39;apparence

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18836132

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020501169

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018836132

Country of ref document: EP

Effective date: 20200122

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020000874

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20207004308

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 112020000874

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200115