WO2018126980A1 - 一种角色寻址业务实现方法及系统 - Google Patents

一种角色寻址业务实现方法及系统 Download PDF

Info

Publication number
WO2018126980A1
WO2018126980A1 PCT/CN2017/119368 CN2017119368W WO2018126980A1 WO 2018126980 A1 WO2018126980 A1 WO 2018126980A1 CN 2017119368 W CN2017119368 W CN 2017119368W WO 2018126980 A1 WO2018126980 A1 WO 2018126980A1
Authority
WO
WIPO (PCT)
Prior art keywords
role
service
call
message
service message
Prior art date
Application number
PCT/CN2017/119368
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 中兴通讯股份有限公司
Publication of WO2018126980A1 publication Critical patent/WO2018126980A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • 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
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a method and system for implementing a role addressing service.
  • GSM-R Global System for Mobile Communications–Railway
  • GSM Global System for Mobile Communications
  • GSM Global System For Mobile Communications
  • Communication services to share railway management information.
  • 3GPP 3rd Generation Partnership Project
  • LTE Long Term Evolution
  • the present disclosure provides a method and system for implementing a railway role addressing service of a GCSE_LTE (Group Communications System Enablers for LTE) architecture under the 3GPP standard protocol system.
  • Embodiments of the present disclosure provide a method and system for implementing a role addressing service.
  • An embodiment of the present disclosure provides a method for implementing a role addressing service, including:
  • the client device sends a role registration service message to the intelligent network through the application server device, where the role registration service message includes a role name and a user identifier to be registered by the client device.
  • the intelligent network performs role registration on the client device according to the role registration service message.
  • the registered role attribute information includes: the role name, the call application number of the role, the user identifier of the role, and the user status of the role; and the application server device is applied to the client.
  • the device feedback includes a registration success response message of the calling application number;
  • the client device sends a role call service message including the call application number of the called role to the intelligent network through the application server device;
  • the intelligent network selects a user identifier whose user status is valid as the called user identifier is fed back to the application server device under the role corresponding to the call application number of the called role;
  • the application server device establishes a call service between the client device and the client device corresponding to the called user identifier.
  • the embodiment of the present disclosure further provides a role addressing service implementation system, including a client device, an application server device, and an intelligent network.
  • the client device includes a service initiation unit and a client service processing unit;
  • the service initiating unit is configured to send a role registration service message to the application server device, where the role registration service message includes a user identifier of the client device and a role name to be registered; and is configured to send the role call to the application server device after the registration is successful.
  • the service message, the role call service message includes the call application number of the called role;
  • the client service processing unit is configured to receive a registration success response message fed back by the application server device, the registration success response message includes a call application number of the registered role, and is configured to receive the application server device according to the role call service message acquired
  • the application server device includes a service receiving unit and a server service processing unit;
  • the service receiving unit is configured to receive a role registration service message sent by the client device, and set to receive a role call service message sent by the client device after the registration is successful;
  • the role registration service message includes a user identifier of the client device and a role to be registered Name;
  • the role call service message includes the call application number of the called role;
  • the server service processing unit is configured to send the role registration service message to the intelligent network, and send the registration success response message fed back by the intelligent network according to the role registration service message to the client device; and set the role call service message Sending to the intelligent network, establishing a call service with the client device according to the called user identifier selected by the intelligent network based on the call application number of the called role.
  • the intelligent network includes a message receiving unit and an intelligent network service processing unit;
  • the message receiving unit is configured to receive a role registration service message and a role call service message sent by the application server device from the client device;
  • the role registration service message includes a user identifier of the client device and a role name to be registered;
  • the role call service message includes The call application number of the called role;
  • the intelligent network service processing unit is configured to perform role registration on the client device according to the role registration service message, and feed back a registration success response message including the call application number to the application server device, where the registered role attribute information includes: role name and role The call application number, the user ID of the role, and the user status of the role; and the role corresponding to the call application number of the called role, and select a user ID whose user status is valid as the called user ID is fed back to the application server. Device.
  • Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions that, when executed by a processor, implement the character addressing service implementation method described above.
  • the client device sends a role registration service message to the intelligent network through the application server device, where the role registration service message includes the role name and the user identifier to be registered by the client device.
  • the intelligent network performs role registration on the client device according to the role registration service message.
  • the registered role attribute information includes: the role name, the call application number of the role, the user identifier of the role, and the user status of the role; and the application server device is applied to the client.
  • the device feeds back a registration success response message including a call application number; the client device sends a role call service message including the call application number of the called role to the intelligent network through the application server device; the intelligent network corresponds to the call application number of the called role Under the role, a user identifier whose user status is valid is selected as the called user identifier is fed back to the application server device; and the application server device establishes a call service between the client device and the client device corresponding to the called user identifier.
  • the service scope and type of the intelligent network service function addressing under the original GSM-R are expanded, and the role registration management through the client device is beneficial to improve the flexibility of the user equipment, and various user equipments can be selected, and Business expansion has also become easier.
  • Example 1 is a schematic flowchart of performing role registration by a client device according to Example 1 of the present disclosure
  • Example 2 is a schematic flowchart of a call service performed by a client device according to Example 1 of the present disclosure
  • Example 3 is a schematic flowchart of performing role subscription by a client device according to Example 2 of the present disclosure
  • Example 4 is a schematic structural diagram of a GCSE_LTE architecture of Example 2 of the present disclosure
  • Example 5 is a schematic structural diagram of a character addressing service implementation system according to Example 3 of the present disclosure.
  • Example 6 is a schematic structural diagram of a client device according to Example 3 of the present disclosure.
  • Example 7 is a schematic structural diagram of an application server device according to Example 3 of the present disclosure.
  • FIG. 8 is a schematic structural diagram of an intelligent network according to Example 3 of the present disclosure.
  • FIG. 1 is a schematic flowchart of a role registration process performed by a client device according to an example, including:
  • the client device sends a role registration service message to the intelligent network by using the server device;
  • the client device sends a role registration service message to the application server device.
  • the role registration service message includes the role name and the user identifier to be registered by the client device, and the application server device receives the role registration service message and sends the message to the intelligent network.
  • the client device may be a mobile phone, a radiotelephone, or a walkie-talkie, which is beneficial to increasing the selection range of the user terminal in the role addressing service system, and improving user equipment selection flexibility.
  • the user performs a role registration service message through the client device to implement a specific role business function. For example, when working as a user of a train driver, you can directly register your mobile phone as a train driver by character, and realize the corresponding business functions. It is not necessary to perform corresponding business functions through a specific communication device, which is more convenient. Fast.
  • the role names include, but are not limited to, train drivers, command and control rooms, flight attendants, security personnel, and cleaners. These roles correspond to multiple client devices.
  • 1162 train drivers may contain multiple drivers, and the driver who is currently driving 1162 times may be set as a valid driver (allowing multiple active drivers), and the remaining drivers are inactive.
  • the co-driver and driver are two different characters. It should be understood that the number of role types and the number of client devices corresponding to each role type in the railway communication system can be flexibly set according to actual conditions.
  • the role registration service message sent by the client device should also include the user identifier, which may be a unique identifier of the client device, such as the actual communication number of the client device, IMEI (International Mobile Equipment Identity, mobile device). International identification code, also known as the international mobile device identity). For example, when the client device is a mobile phone, it may be the mobile phone number of the mobile phone.
  • the user identifier may be a unique identifier of the client device, such as the actual communication number of the client device, IMEI (International Mobile Equipment Identity, mobile device). International identification code, also known as the international mobile device identity).
  • the client device is a mobile phone, it may be the mobile phone number of the mobile phone.
  • the client device sends a role registration service message to the application server device, and the application server device receives the role registration service message and sends the message to the intelligent network.
  • the application server device may receive the role registration service message sent by the client device.
  • the identity of the client device and whether it has the role registration service authority for authentication, the authentication uses the activated profile authentication authority of the client device.
  • the application server device sends the service message of the legitimate client device to the intelligent network. It should be understood that the service message for the illegal client device directly returns an error prompt or directly discards the processing.
  • S02 The intelligent network performs role registration on the client device.
  • the intelligent network receives the role registration service message sent by the application server device, and performs role registration processing on the client device.
  • the registered role attribute information includes, but is not limited to, the role name, the call application number of the role, the user ID of the role, and the user status of the role.
  • the client device is registered as a driver
  • the calling application number is 001
  • the user identification is the actual communication number (eg, phone number) of the client device
  • the user status is the registration status.
  • the call application number of the role assigns the same number to the same role.
  • all drivers have a call application number of 001 (but it should be understood that the call application number of the character may not be composed solely of the role number, such as a driver. It can also be composed of information such as the number of the train corresponding to the character.
  • the call application number of all flight attendants is 002
  • the call application number of all command dispatch rooms is 003
  • the call application number of all security personnel is 004.
  • the user status of a role includes, but is not limited to, a registration status, a logout status, and a forced logout status.
  • the intelligent network can store the processing result in the role database, and the final processing status of the role involved in the current service is recorded in the role database.
  • Table 1 For a better understanding of the present disclosure, please refer to Table 1:
  • the role attribute information may also include role information and role validity period associated with the role.
  • the role information associated with the command and dispatch room may be the role information of the driver. By associating the role information, some resources may be shared to facilitate railway communication.
  • the role validity period can be registered by the role. For example, if driver A's working time is 10 hours, the role validity period can be registered as 10 hours. After 10 hours, the driver user status of driver A is automatically set to the logout state. Instead of having to manually send the role logout service message through the client device to complete the role logout process, it is beneficial to improve the user experience.
  • the intelligent network can authenticate the validity of the role registration service message, for example, the role registration service. Whether the type of the message is reasonable and whether the service content of the role registration service message meets the corresponding rule. For example, the railway communication system sets four types of roles: driver, flight attendant, command and control room, and security personnel.
  • the role name of the role to be registered in the role registration service message sent by the client device is passenger, and the role registration service message is obviously illegal.
  • the intelligent network determines that the role registration service message is invalid. For an invalid role registration service message, the intelligent network may return an error prompt through the application server device, or directly discard the role registration service message and not process it.
  • the specific authentication principle or mechanism may adopt any manner capable of authenticating the identity legality of a certain device, for example, storing configuration file information required for authentication, and calling processing when performing authentication.
  • S03 The intelligent network feeds back the registration success response message to the client device by using the server device.
  • the application server device feeds back the registration success response message to the client device, where the registration success response message may include the call application number, and may of course not include the call application number.
  • the message type may be a request message, and the sending and receiving of the role registration service message may be sent or received using INVITE/REGISTER/INFO/MESSAGE/NOTIFY/401Unauthorized.
  • the client device may also send a role logout service message, a role forced logout service message, and a role query service message to the client device through the application server device, thereby implementing the corresponding role. Cancellation of business, role forced cancellation of business, role query business. It should be understood that the role registration process, role forced logout, and role query process also apply to the above role registration process.
  • This example can be applied to an LTE wireless network.
  • Data between the client and the application server can be transmitted through the LTE network, and each unit conforms to the GCSE_LTE architecture and the MCPTT protocol.
  • the application server may be the MCPTT Server, or the MCVideo Server.
  • the network protocol that can be used when the client device performs role registration includes but is not limited to SIP (Session Initiation Protocol). Adopt other protocols.
  • FIG. 2 is a schematic flowchart of a call service performed by a client device according to Example 1 of the present disclosure, including:
  • the client device sends a role call service message to the intelligent network by using the server device;
  • the client device sends a role call service message to the application server device, and the application server device receives the role call service message and sends the role call service message to the intelligent network.
  • the role call service message includes the call application number of the called role.
  • the application server device may authenticate the identity of the client device and whether or not the call service authority is available, in order to ensure the security of the railway communication system, and the authentication may adopt the Activated profile authentication permission for the client device.
  • the application server device sends the role call service message to the intelligent network only for the client device that is legally authorized and has the call service authority. For the client device whose identity is illegal or does not have the call service authority, the application device will not The role call service message is sent to the intelligent network, for example, the error message is directly returned or the role call service message is discarded.
  • the intelligent network selects a user identifier whose user status is valid as the called user identifier is fed back to the application server device;
  • the intelligent network After receiving the role call service message sent by the client device through the application server device, the intelligent network selects a user identifier whose user status is valid as the called user identifier feedback from the role corresponding to the call application number of the called role. Give the application server device.
  • the call application number 002 of the flight attendant role can be directly dialed through the client device; at this time, the application server device is applied.
  • the role call service message sent by the client device of the driver A may be received, where the message includes the call application number 002 of the called role, and the application server device may also detect that the identity of the client device of the driver A belongs to the driver, and to the flight attendant Having the call service permission, the application server device sends the role call service message to the intelligent network; the intelligent network receives the role call service message, and queries according to the call application number 002 of the called role included in the role call service message.
  • the corresponding flight attendant role in which the flight attendant C and the flight attendant D can be queried, and the user status of the flight attendant C and the flight attendant D is detected, and the user status of the flight attendant C is the logout state, and the user state of the flight attendant D is the registered state. It can be judged that the user status of flight attendant D is valid and should be Be appreciated that the valid user can actually state determination rules appropriate, for example, where the active state register state determination. After the intelligent network determines that the user status of the flight attendant D is valid, the user ID 11223344 (actual pass signal code or IMEI) of the flight attendant D is fed back to the application server device.
  • IMEI actual pass signal code
  • the intelligent network may flexibly select a called role to feed back to the application server device according to actual conditions, for example, may be randomly selected, or may be correspondingly The selection mechanism is selected; the number of all valid states can also be sent to the user to select and carry the difference information of the user.
  • the application server device establishes a call service between the client device and the client device corresponding to the called user identifier.
  • the application server device receives the user identifier of the called role fed back by the intelligent network, and establishes a call service between the client device and the client device corresponding to the called user identifier according to the user identifier, so as to implement a call connection between the two.
  • the message needs to conform to the network protocol SIP specification during the role call of the client device, and the message type includes but is not limited to the request message.
  • the sending and receiving of messages can be implemented by INVITE/100 Trying/180Ring/200ok.
  • character addressing service implementation method provided by this example is particularly applicable to railway communication systems, but is not limited to use in railway communication systems.
  • the example provides a method for implementing a role addressing service.
  • the client device sends a role registration service message to the intelligent network through the application server device, and the intelligent network registers the role of the client device according to the role registration service message, and applies the server device through the application server device.
  • the client device may send the role call service message to the intelligent network through the application server device; the role of the intelligent network from the call application number of the called role And selecting a user status (may select one or more) as a valid user identifier as the called user identifier is fed back to the application server device; and the application server device establishes a client device corresponding to the called user identifier by the client device Call business between.
  • the service scope and type of the intelligent network service function addressing under the original GSM-R are expanded, and the role registration management through the client device is beneficial to improve the flexibility of the user equipment, and various user equipments can be selected, and Business expansion has also become easier.
  • FIG. 3 is a schematic flowchart of a role subscription performed by a client device according to Example 2 of the present disclosure, including:
  • the client device sends a role subscription service message to the intelligent network by using the application server device;
  • the role subscription service message includes, but is not limited to, a subscribed role message, and the subscribed role message includes, but is not limited to, the subscribed role name and the subscribed role call application number. It should be understood that, after the application server device receives the role subscription service message, in order to better ensure the security and stability of the railway communication system, the identity of the client device that sends the role subscription service message and whether there is a subscription may be obtained.
  • the service authority is authenticated, and the authentication can authenticate the user authority according to the configuration file activated by the client device.
  • the identity of the client device and whether it has subscription service rights can also be verified by the role attribute information (the role name, the call application number of the role, the user ID of the role, and the user status of the role) registered by the client device on the intelligent network.
  • the application server device sends the service message to the intelligent network for the role subscription service processing.
  • the client device can feed back an error prompt or directly discard the processing.
  • the subscription service authority can be flexibly set according to the actual application situation of the railway communication system, for example, the command and dispatch room is an important command department of the railway system, and can perform various role subscriptions (driver role, flight attendant role, security Personnel role), to facilitate the stable and orderly work of the railway system, while the security personnel role can not subscribe to the command and dispatch room role business, because the security personnel role is only responsible for the corresponding railway security work, there is no need to control the operation of the command and control room.
  • role subscriptions driver role, flight attendant role, security Personnel role
  • FIG. 4 is a schematic structural diagram of the GCSE_LTE architecture provided by example 2 of the present disclosure, including:
  • UE User Equipment
  • eNodeB/eNB Evolved Base Station
  • EPC Evolved Packet Core
  • GCSE Application Server Application Service Equipment
  • the EPC includes MME (Mobility Management Entity, Mobile) Management Node), MBMS GW (Multimedia Broadcast Multicast Service GateWay), S-GW (Serving GateWay), P-GW (PDN GateWay), BM-SC (Broadcast Multicast Service) Cente, Broadcast Multicast Service Center).
  • MME Mobility Management Entity, Mobile
  • MBMS GW Multimedia Broadcast Multicast Service GateWay
  • S-GW Serving GateWay
  • P-GW P-GW
  • BM-SC Broadcast Multicast Service Cente, Broadcast Multicast Service Center
  • the intelligent network sends a status query message including the user identifier corresponding to the subscribed role to the application server device when the preset query condition is met;
  • the intelligent network receives the role subscription service message, and sends a status query message including the user identifier corresponding to the subscribed role to the application server device when the corresponding preset query condition is met.
  • the preset query conditions include, but are not limited to, a timed query and a query when the role information changes.
  • the preset query condition is a timed 1 minute query
  • the intelligent network sends a status query message including the user identifier corresponding to the subscribed role to the application server device every 1 minute; similarly, when the preset query condition is set to change the role information
  • the intelligent network sends the user corresponding to the subscribed role to the application server device.
  • the status query message for the identity.
  • the application server device queries the query item corresponding to the user identifier according to the status query message, and feeds the query result to the intelligent network.
  • the application server device queries the query item corresponding to the user identifier according to the status query message that includes the user identifier corresponding to the subscribed role.
  • the query item includes but is not limited to the user name query item, the call status query item, the call statistics query item, and the owner query item, and the query result (user name query result, call status query result, call statistics query result, and owner)
  • the result of the query is fed back to the intelligent network.
  • S24 The intelligent network generates a role subscription response message according to the query result and feeds back to the client device.
  • the intelligent network receives the query result fed back by the application server device, and generates a role subscription response message according to the feedback result, where the role subscription response message includes but is not limited to the user identifier of the subscribed role, the user name of the user identifier, and the user Identifies the owner, the call status of the user ID, the user status of the user ID, and the call statistics of the user ID.
  • the intelligent network feeds back the generated role subscription response message to the client device.
  • the client device feeds back to the user through the display interface or voice prompt, which greatly facilitates resource sharing and command scheduling of the railway communication system.
  • the intelligent network will feedback the role subscription response message to the command and dispatch room when the subscribed role information is changed, and the command and dispatch room can grasp the role information conveniently and quickly, thereby facilitating Dispatching command.
  • the role subscription service message needs to conform to the network protocol SIP specification, and the role subscription process may use INFO/MESSAGE/NOTIFY/OPTION to send and receive corresponding messages.
  • the present invention provides a role addressing service implementation method, which is based on the GCSE_LTE architecture, and the client device sends a role subscription service message including the call application number of the called role to the intelligent network through the application server device.
  • the intelligent network sends a status query message including the user identifier corresponding to the subscribed role to the application server device when the preset query condition is satisfied, and the application server device queries the query item corresponding to the user identifier according to the status query message, and queries the query.
  • the result is fed back to the intelligent network, and the intelligent network generates a role subscription response message according to the query result and feeds back to the client device.
  • the role subscription is performed by the client device, and the corresponding role subscription service is implemented for the relevant user, which is beneficial to improving the flexibility of the selection of the user device, selecting more user devices, and making the role subscription service more convenient, based on the GCSE_LTE architecture.
  • the railway role addressing service expands the service range and type of the intelligent network service function under the original GSM-R, which is beneficial to improve the user experience.
  • the present invention provides a role addressing service implementation system for implementing the role addressing service implementation method described in the first example and the second example, including the client device 1, the application server device 2, and the intelligent network 3. See the figure. 5 is a schematic structural diagram of a role addressing service implementation system provided by Example 3 of the present disclosure.
  • the client device 1 includes a service initiating unit 11 and a client service processing unit 12.
  • FIG. 6 is a schematic structural diagram of a client device according to Example 3 of the present disclosure.
  • the service initiating unit 11 is connected to the SIP uplink sending unit, and is configured to send a role registration service message to the application server device 2, where the role registration service message includes the user identifier of the client device 1 and the role name to be registered; and is set to be registered. After successful, the role server service message is sent to the application server device 2, and the role call service message includes the call application number of the called role;
  • the client service processing unit 12 is connected to the SIP downlink receiving unit, and configured to receive a registration success response message fed back by the application server device 2, the registration success response message includes a call application number of the registered role, and is configured to receive the application server device. 2, according to the role call service message, the call service establishment message sent after the called user identifier corresponding to the called role is obtained, and the client device corresponding to the called user identifier establishes a call service.
  • the service initiating unit 11 is further configured to send a role management service message to the application server device 2, where the role management service message includes but is not limited to a role logout service message, a role forced logout service message, and a role query service message.
  • the client service processing unit 12 is further configured to receive the role management response message fed back by the application server device 1, wherein the role management response message includes but is not limited to the role logout result, the role forced logout result, and the role query result. .
  • the service initiation unit 11 is further configured to send a role subscription service message to the application server device 2, wherein the role subscription service message includes a subscribed role message, the subscribed role message including the subscribed role name and/or the call application
  • the client service processing unit 12 is further configured to receive a role subscription response message fed back by the application server device 2, wherein the role subscription response message includes but is not limited to the user identifier of the subscribed role, the user name of the user identifier, and the user identifier.
  • the application server device 2 includes a service receiving unit 21 and a server service processing unit 22.
  • FIG. 7 is a schematic structural diagram of an application server device provided in Example 3 of the present disclosure.
  • the service receiving unit 21 is connected to the SIP uplink receiving unit, configured to receive the role registration service message sent by the client device 1, and configured to receive the role call service message sent by the client device 1 after the registration is successful;
  • the role registration service message includes a user identifier of the client device 1 and a role name to be registered;
  • the role call service message includes a call application number of the called role;
  • the server service processing unit 22 is connected to the SIP downlink sending unit, and is configured to send the role registration service message to the intelligent network 3, and send the registration success response message fed back by the intelligent network 3 according to the role registration service message to the client.
  • the terminal device 1 is configured to send a role call service message to the intelligent network 3, and establish a call service with the client device 1 according to the called user identifier selected by the intelligent network 3 based on the call application number of the called role.
  • the service receiving unit 21 is further configured to receive a role management service message initiated by the client device 1, where the role management service message includes but is not limited to a role logout service message, a role forced logout service message, and a role query service message.
  • the server service processing unit 22 is further configured to send the role management service message to the intelligent network 3, and send the role management response message fed back by the intelligent network 3 to the client device 1, wherein the role management response message This includes, but is not limited to, role logout results, role forced logout results, and role query results.
  • the service receiving unit 21 is further configured to receive a role subscription service message initiated by the client device 1, wherein the role subscription service message includes but is not limited to a subscribed role message, and the subscribed role message includes the subscribed role name and/or Or call the application number; it should be understood that at this time, the server service processing unit 22 is further configured to send the role subscription service message to the intelligent network 3, and to be configured to include the subscribed role according to the smart network 3 based on the role subscription service message. Corresponding to the status query message of the user identifier, querying the query item corresponding to the user identifier, and feeding back the query result to the intelligent network 3, and setting the role subscription response message generated by the intelligent network 3 according to the query result to the client device 1.
  • the query item includes, but is not limited to, a user name query item of the user identifier, a call status query item, a call statistics query item, and an owner query item.
  • the intelligent network 3 includes a message receiving unit 31 and an intelligent network service processing unit 32.
  • FIG. 8 is a schematic structural diagram of an intelligent network provided by Example 3 of the present disclosure.
  • the message receiving unit 31 is configured to receive a role registration service message and a role call service message from the client device 1 sent by the application server device 2; the role registration service message includes a user identifier of the client device 1 and a role name to be registered; The role call service message includes the call application number of the called role;
  • the intelligent network service processing unit 32 is configured to perform role registration on the client device 1 according to the role registration service message, and feed back the registration success response message including the call application number to the application server device 2, where the registered role attribute information includes: the role name The call application number of the role, the user ID of the role, and the user status of the role; and the role corresponding to the call application number of the called role, and selecting a user ID whose user status is valid as the called user identifier is fed back to the application.
  • Server device 2 the registered role attribute information includes: the role name The call application number of the role, the user ID of the role, and the user status of the role; and the role corresponding to the call application number of the called role, and selecting a user ID whose user status is valid as the called user identifier is fed back to the application.
  • Server device 2 the registered role attribute information includes: the role name The call application number of the role, the user ID of the role, and the user status of the role; and the role corresponding to the call application number of the called role, and selecting
  • the message receiving unit 31 is further configured to receive a role management service message from the client device 1 sent by the application server device 2, where the role management service message includes but is not limited to a role logout service message, a role forced logout service message, and The role queries business messages.
  • the intelligent network service processing unit 32 is further configured to perform management processing on the managed role requested by the role management service message, and it should be understood that the management process includes but is not limited to the role logout process and the role forced logout process. And the role query processing, and sending the processed role management response message to the application server device 2.
  • the message receiving unit 31 is further configured to apply the role subscription service message from the client device 1 sent by the server device 2, wherein the role subscription service message includes a subscribed role message, and the subscribed role message includes the subscribed role message.
  • the intelligent network service processing unit 32 is further configured to subscribe to the service message according to the role, and send the user corresponding to the subscribed role to the application server device 2 when the preset query condition is satisfied.
  • the status query message is set, and the query result is set to receive the feedback from the application server device 2, where the query result includes, but is not limited to, the user name query result of the user identifier, the call status query result, the call statistics query result, and the owner query result.
  • the role subscription response message includes but is not limited to the user identifier of the subscribed role, the user name of the user identifier, the user of the user identifier, the user Identified call status, the user The identified user status and the call statistics of the user ID.
  • the preset query conditions include, but are not limited to, a timed query and a query when the role information changes.
  • the preset query condition is a timed 5 minute query
  • the intelligent network 3 sends a status query message including the user identifier corresponding to the subscribed role to the application server device 2 every 5 minutes; similarly, when the preset query condition is set to the role
  • the intelligent network 3 transmits the included information to the application server device 2 when the role attribute information of the subscribed role, such as the role name, the call application number of the role, the user identification of the role, and the user status of the role change.
  • the subscription role corresponds to the status query message of the user ID.
  • the present example provides a role addressing service implementation system, including a client device 1, an application server device 2, and an intelligent network 3, wherein the client device 1 includes a service initiation unit 11 and a client service processing unit 12, and the application server device 2 includes a service receiving unit 21 and a server service processing unit 22, the intelligent network 3 includes a message receiving unit 31 and an intelligent network service processing unit 32; and the service initiating unit 11 of the client device 1 transmits a role registration service to the application server device 2
  • the message server, the application server device 2 accepts the role registration service message through the service receiving unit 21, and sends it to the intelligent network 3 through the server service processing unit 22, wherein the role registration service message includes the user identifier of the client device 1 and The registered role name; the intelligent network 3 receives the role registration service message through the message receiving unit 31, and performs role registration on the client device 1 through the intelligent network service processing unit 32, and feeds back the call application number to the application server device 2 Registration success response message, registered role attribute information includes: role name The call application number of the role, the user
  • the client device 1 transmits a role call service message to the application server device 2 through the service initiation unit 11, and the application server device 2 accepts the role call service message through the service receiving unit 21, and processes the service through the server.
  • the unit 22 sends it to the intelligent network 3, wherein the role call service message includes the call application number of the called role; the intelligent network 3 receives the role call service message through the message receiving unit 31, and is called from the called through the intelligent network service processing unit 32.
  • a user identifier whose user status is valid is selected as the called user identifier and fed back to the application server device 2, and the application server device 2 sends the identifier according to the called user identifier through the server service processing unit 22.
  • the client device 1 receives the call service setup message through the client service processing unit 12, and establishes a call connection of the client device corresponding to the called subscriber identity.
  • the service scope and type of the intelligent network service function addressing under the original GSM-R are expanded, and the role registration management through the client device is beneficial to improve the flexibility of the user equipment, and various user equipments can be selected, and Business expansion has also become easier.
  • Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions that, when executed by a processor, implement the character addressing service implementation method described above.
  • computer storage medium includes volatile and nonvolatile, implemented in any method or technology for storing information, such as computer readable instructions, data structures, program modules or other data. Sex, removable and non-removable media.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridge, magnetic tape, magnetic disk storage or other magnetic storage device, or may Any other medium used to store the desired information and that can be accessed by the computer.
  • communication media typically includes computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information delivery media. .
  • the client device sends a role registration service message to the intelligent network through the application server device, where the role registration service message includes the role name and the user identifier to be registered by the client device.
  • the intelligent network performs role registration on the client device according to the role registration service message.
  • the registered role attribute information includes: the role name, the call application number of the role, the user identifier of the role, and the user status of the role; and the application server device is applied to the client.
  • the device feeds back a registration success response message including a call application number; the client device sends a role call service message including the call application number of the called role to the intelligent network through the application server device; the intelligent network corresponds to the call application number of the called role Under the role, a user identifier whose user status is valid is selected as the called user identifier is fed back to the application server device; and the application server device establishes a call service between the client device and the client device corresponding to the called user identifier.
  • the service scope and type of the intelligent network service function addressing under the original GSM-R are expanded, and the role registration management through the client device is beneficial to improve the flexibility of the user equipment, and various user equipments can be selected, and Business expansion has also become easier.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

提供了角色寻址业务实现方法及系统，所述方法包括，客户端装置通过应用服务端装置向智能网发送角色注册业务消息；智能网根据角色注册业务消息对客户端装置进行角色注册；并通过应用服务端装置向客户端装置反馈包含呼叫应用号码的注册成功响应消息；客户端装置通过应用服务端装置向智能网发送角色呼叫业务消息；智能网从被呼叫角色的呼叫应用号码对应的角色下，选择一个用户状态为有效的用户标识作为被叫用户标识反馈给应用服务端装置；所述应用服务端装置建立客户端装置与被叫用户标识对应的客户端装置之间的呼叫业务。

Description

一种角色寻址业务实现方法及系统 技术领域
本公开涉及通信技术领域，尤其涉及一种角色寻址业务实现方法及系统。
背景技术
GSM-R(Global System for Mobile Communications–Railway，铁路综合专用数字移动通信系统)是基于GSM(Global System For Mobile Communications，全球移动通信系统)提出的一种铁路无线通讯系统，以便于铁路系统的调度通信服务，实现铁路管理信息的共享。随着通信技术的发展，3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)提出了新一代LTE(Long Term Evolution，长期演进)通信技术，但是目前并没有提出铁路业务相关的模型。本公开提供了3GPP标准协议体系下的GCSE_LTE(Group Communications System Enablers for LTE，支持LTE的组通信系统)架构的铁路角色寻址业务实现方法及系统。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本公开实施例提供了一种角色寻址业务实现方法及系统。
本公开实施例提供了一种角色寻址业务实现方法，包括：
客户端装置通过应用服务端装置向智能网发送角色注册业务消息，角色注册业务消息包括客户端装置待注册的角色名称以及用户标识；
智能网根据角色注册业务消息对客户端装置进行角色注册，注册的角色属性信息包括：角色名称、角色的呼叫应用号码、角色的用户标识以及角色的用户状态；并通过应用服务端装置向客户端装置反馈包含呼叫应用号码的注册成功响应消息；
客户端装置通过应用服务端装置向智能网发送包含被呼叫角色的呼叫应用号码的角色呼叫业务消息；
智能网从被呼叫角色的呼叫应用号码对应的角色下，选择用户状态为有效的用户标识作为被叫用户标识反馈给所述应用服务端装置；
应用服务端装置建立客户端装置与被叫用户标识对应的客户端装置之间的呼叫业务。
本公开实施例还提供了一种角色寻址业务实现系统，包括客户端装置、应用服务端装置和智能网。
客户端装置包含业务发起单元和客户端业务处理单元；
业务发起单元设置为向应用服务端装置发送角色注册业务消息，角色注册业务消息包括客户端装置的用户标识以及待注册的角色名称；以及设置为在注册成功后，向应用服务端装置发送角色呼叫业务消息，角色呼叫业务消息包括被呼叫角色的呼叫应用号码；
客户端业务处理单元设置为接收应用服务端装置反馈的注册成功响应消息，注册成功响应消息包含所注册角色的呼叫应用号码；以及设置为接收所述应用服务端装置根据角色呼叫业务消息获取到被呼叫角色对应的被叫用户标识后所发送的呼叫业务建立消息，与被叫用户标识对应的客户端装置建立呼叫业务。
应用服务端装置包含业务接收单元和服务端业务处理单元；
业务接收单元设置为接收客户端装置发送的角色注册业务消息，以及设置为接收客户端装置在注册成功后发送的角色呼叫业务消息；角色注册业务消息包括客户端装置的用户标识以及待注册的角色名称；角色呼叫业务消息包括被呼叫角色的呼叫应用号码；
服务端业务处理单元设置为将角色注册业务消息发送给智能网，并将智能网根据角色注册业务消息进行注册处理后反馈的注册成功响应消息发送给客户端装置；以及设置为将角色呼叫业务消息发送给智能网，根据智能网基于被呼叫角色的呼叫应用号码选择的被叫用户标识，与客户端装置建立呼叫业务。
智能网包含消息接收单元和智能网业务处理单元；
消息接收单元设置为接收应用服务端装置发送的来自客户端装置的角色注册业务消息以及角色呼叫业务消息；角色注册业务消息包括客户端装置的用户标识以及待注册的角色名称；角色呼叫业务消息包括被呼叫角色的呼叫应用号码；
智能网业务处理单元设置为根据角色注册业务消息对所述客户端装置进行角色注册，并向应用服务端装置反馈包含呼叫应用号码的注册成功响应消息，注册的角色属性信息包含：角色名称、角色的呼叫应用号码、角色的用户标识以及角色的用户状态；以及设置为从被呼叫角色的呼叫应用号码对应的角色下，选择一个用户状态为有效的用户标识作为被叫用户标识反馈给应用服务端装置。
本公开实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现以上描述的角色寻址业务实现方法。
根据本公开实施例提供的角色寻址业务实现方法及系统，客户端装置通过应用服务端装置向智能网发送角色注册业务消息，角色注册业务消息包括客户端装置待注册的角色名称以及用户标识；智能网根据角色注册业务消息对客户端装置进行角色注册，注册的角色属性信息包括：角色名称、角色的呼叫应用号码、角色的用户标识以及角色的用户状态；并通过应用服务端装置向客户端装置反馈包含呼叫应用号码的注册成功响应消息；客户端装置通过应用服务端装置向智能网发送包含被呼叫角色的呼叫应用号码的角色呼叫业务消息；智能网从被呼叫角色的呼叫应用号码对应的角色下，选择一个用户状态为有效的用户标识作为被叫用户标识反馈给所述应用服务端装置；应用服务端装置建立客户端装置与被叫用户标识对应的客户端装置之间的呼叫业务。扩充了原有GSM-R下的智能网业务功能寻址的业务范围和类型，通过客户端装置进行角色注册管理有利于提高用户设备的灵活性，可以选择各种各样的用户设备，而且使业务的扩展也变得更加容易。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图说明
图1为本公开示例一的客户端装置进行角色注册的流程示意图；
图2为本公开示例一的客户端装置进行呼叫业务的流程示意图；
图3为本公开示例二的客户端装置进行角色订阅的流程示意图；
图4为本公开示例二的GCSE_LTE架构结构示意图；
图5为本公开示例三的角色寻址业务实现系统的结构示意图；
图6为本公开示例三的客户端装置的结构示意图；
图7为本公开示例三的应用服务端装置的结构示意图；
图8为本公开示例三的智能网的结构示意图。
具体实施方式
下面通过具体实施方式结合附图对本公开实施例作详细说明。
示例一：
本示例提供一种角色寻址业务实现方法，请参见图1，图1为示例一提供的客户端装置进行角色注册的流程示意图，包括：
S01：客户端装置通过应用服务端装置向智能网发送角色注册业务消息；
客户端装置向应用服务端装置发送角色注册业务消息，角色注册业务消息中包括客户端装置待注册的角色名称以及用户标识，应用服务端装置接收该角色注册业务消息，并发送给智能网。
本示例中，客户端装置可以是手机、无线电话机、对讲机，有利于增加角色寻址业务系统中用户端的选择范围，提高用户设备选择灵活性。用户通过客户端装置进行角色注册业务消息，实现特定角色业务功能。例如，作为某一辆火车司机的用户工作时，可以直接将自己的手机通过角色注册成为该火车司机角色，实现相应的业务功能，不必通过特定的通信装置来进行相应的业务功能，这样更加方便快捷。
本示例中，角色名称包括但不限于火车司机、指挥调度室、乘务员、保安人员、清洁工。这些角色对应多个客户端装置，例如，1162次火车司机 可能包含多个司机，且可以设置当前驾驶1162次的司机为有效的司机(允许有多个有效司机)，其余司机为无效状态。副司机和司机是两个不同的角色。应当理解的是，铁路通信系统中角色种类和各角色种类对应的客户端装置数量可以根据实际情况灵活设定。
本示例中，客户端装置发送的角色注册业务消息中还应包括用户标识，用户标识可以是客户端装置的唯一识别码，例如客户端装置的实际通信号码、IMEI(International Mobile Equipment Identity，移动设备国际识别码，又称为国际移动设备标识)。例如客户端装置为手机时，可以是该手机的手机号码。
客户端装置向应用服务端装置发送角色注册业务消息，应用服务端装置接收该角色注册业务消息，并发送给智能网。应当理解的是，为了提高铁路通信系统的安全性，避免人为进行恶意地进行角色注册，影响铁路系统的正常运行，应用服务端装置在接收到客户端装置发送的角色注册业务消息时，可以对该客户端装置的身份以及是否拥有角色注册业务权限进行鉴权，鉴权使用该客户端装置的已激活配置文件鉴定权限。应用服务端装置将合法客户端装置的业务消息发送给智能网。应当理解的是，对于非法的客户端装置的业务消息直接返回错误提示或者直接丢弃不做处理。
S02：智能网对客户端装置进行角色注册；
智能网接收由应用服务端装置发送的角色注册业务消息，并对客户端装置进行角色注册处理。注册的角色属性信息包括但不限于角色名称、角色的呼叫应用号码、角色的用户标识以及角色的用户状态。例如，将该客户端装置注册为司机，呼叫应用号码为001，用户标识为该客户端装置的实际通信号码(例如电话号码)，用户状态为注册状态。
应当理解的是，角色的呼叫应用号码为同一角色分配相同的号码，例如，所有的司机的呼叫应用号码为001(但应当理解，角色的呼叫应用号码可以不单纯由角色的号码组成，比如司机，还可有该角色对应的车次号等信息组成)，所有的乘务员的呼叫应用号码为002，所有的指挥调度室的呼叫应用号码为003，所有的保安人员的呼叫应用号码为004。角色的用户状态包括但不限于注册状态、注销状态、强制注销状态。
应当理解的是，智能网可以将处理结果存储在角色数据库中，角色数据库中会记录当前业务所涉及角色的最终处理状态。为了更好的理解本公开，请参见表1：
表1
Figure PCTCN2017119368-appb-000001
应当理解的是，角色属性信息还可以包括本角色所关联的角色信息、角色有效期。例如，指挥调度室关联的角色信息可以是司机的角色信息，通过关联角色信息可以使部分资源共享，方便铁路通信使用。应当理解的是，角色有效期可以通过本角色注册，例如，司机A的工作时间为10小时，则可以将角色有效期注册为10小时，当10小时之后，司机A的角色用户状态自动设置为注销状态，而不必通过客户端装置手动发送角色注销业务消息来完成角色注销过程，有利于提高用户体验。
应当理解的是，为了更好的保证铁路通信系统的安全性，智能网在接收到由应用服务端装置发送的角色注册业务消息之后，可以鉴定角色注册业务消息的合法性，例如鉴定角色注册业务消息的类型是否合理、鉴定角色注册业务消息的业务内容是否符合相应规则。例如，铁路通信系统设定了司机、 乘务员、指挥调度室、保安人员四种类型角色，而客户端装置发送的角色注册业务消息中待注册的角色名称为乘客，该角色注册业务消息明显不合法，此时，智能网判断该角色注册业务消息不合法，对于不合法的角色注册业务消息，智能网可以通过应用服务端装置返回错误提示，或者直接丢弃该角色注册业务消息不作处理。
应当理解的是，具体的鉴定原则或者机制可以采用任意能够对某一设备身份合法性进行鉴权的方式，例如将鉴权需要的配置文件信息进行存储，在进行鉴权时调用处理。
S03：智能网通过应用服务端装置向客户端装置反馈注册成功响应消息。
智能网在处理角色注册业务消息成功之后，通过应用服务端装置向客户端装置反馈注册成功响应消息，其中注册成功响应消息中可以包括呼叫应用号码，当然也可以不包含呼叫应用号码。
本示例中，消息类型可以为请求消息，角色注册业务消息的发送和接收可以采用INVITE/REGISTER/INFO/MESSAGE/NOTIFY/401Unauthorized来发送或者接收。应当理解的是，当客户端装置角色注册成功后，客户端装置还可以通过应用服务端装置向客户端装置发送角色注销业务消息、角色强制注销业务消息以及角色查询业务消息，从而实现相应的角色注销业务、角色强制注销业务、角色查询业务。应当理解的是，对于角色注销、角色强制注销以及角色查询过程同样适用于上述角色注册过程。
本示例可以应用于LTE无线网络，客户端与应用服务器之间的数据可以通过LTE网络传输，各单元符合GCSE_LTE体系架构以及MCPTT协议的规定。又例如应用服务器的实例之一可以是MCPTT Server，也可以是MCVideo Server等,客户端装置进行角色注册时可采用的网络协议包括但不限于SIP(Session Initiation Protocol，会话初始协议)，当然也可以采用其他协议。
应当理解的是，客户端装置只有在进行角色注册成功之后，方可进行其他业务功能。例如呼叫业务、角色管理业务和角色订阅业务。下面针对铁路通信系统中的呼叫业务进行详细说明，请参见图2，图2为本公开示例一提供的客户端装置进行呼叫业务的流程示意图，包括：
S11：客户端装置通过应用服务端装置向智能网发送角色呼叫业务消息；
客户端装置向应用服务端装置发送角色呼叫业务消息，应用服务端装置在接收该角色呼叫业务消息，并将该角色呼叫业务消息发送给智能网。其中，角色呼叫业务消息包含被呼叫角色的呼叫应用号码。
应当理解的是，应用服务端装置在接收到该角色呼叫业务消息后，为了保证铁路通信系统的安全性，可以对客户端装置的身份以及是否拥有呼叫业务权限进行鉴权，鉴权可以采用该客户端装置的已激活配置文件鉴定权限。应用服务端装置仅对身份合法以及拥有呼叫业务权限的客户端装置，才会将角色呼叫业务消息发送给智能网处理，对于身份不合法或者不具有呼叫业务权限的客户端装置，则不会将角色呼叫业务消息发送给智能网，例如直接返回错误提示或者丢弃角色呼叫业务消息不作处理。
S12：智能网选择一个用户状态为有效的用户标识作为被叫用户标识反馈给应用服务端装置；
智能网接收到客户端装置通过应用服务端装置发送的角色呼叫业务消息后，智能网从被呼叫角色的呼叫应用号码对应的角色下，选择一个用户状态为有效的用户标识作为被叫用户标识反馈给应用服务端装置。
为了更好的理解本公开，请继续参见表1，例如，当司机A需要通过客户端装置呼叫乘务员时，可以直接通过客户端装置拨打乘务员角色的呼叫应用号码002；此时，应用服务端装置可以接收到司机A的客户端装置发送的角色呼叫业务消息，该消息中包含被呼叫角色的呼叫应用号码002，应用服务端装置也可以检测司机A的客户端装置的身份属于司机，且对乘务员拥有呼叫业务权限，此时，应用服务端装置向智能网发送该角色呼叫业务消息；智能网接收该角色呼叫业务消息，并根据该角色呼叫业务消息中包含的被呼叫角色的呼叫应用号码002查询对应的乘务员角色，其中可以查询到乘务员C和乘务员D，并检测乘务员C和乘务员D的用户状态，得到乘务员C的用户状态为注销状态，乘务员D的用户状态为注册状态，此时，智能网可以判断乘务员D的用户状态为有效，应当理解的是，有效的用户状态可以实际规则相应判定，例如这里将注册状态判定为有效状态。智能网判定乘务员D的用户状态为有效后，将乘务员D的用户标识11223344(实际通信号 码或者IMEI)反馈给应用服务端装置。应当理解的是，当智能网判定存在多个用户状态有效的被呼叫角色时，智能网可以根据实际情况灵活选择一个被呼叫角色反馈给应用服务端装置，例如，可以随机选择，也可以根据相应的选择机制进行选择；也可以选择将所有有效状态的号码发送给用户选择，携带用户的区别信息。
S13：应用服务端装置建立客户端装置与被叫用户标识对应的客户端装置之间的呼叫业务。
应用服务端装置接收智能网反馈的被呼叫角色的用户标识，并根据该用户标识建立客户端装置与被叫用户标识对应的客户端装置之间的呼叫业务，实现两者之间的呼叫连接。
应当理解的是，以客户端装置进行角色注册时采用的网络协议为SIP为例时，在客户端装置进行角色呼叫的过程中，消息需要符合网络协议SIP规范，消息类型包括但不限于请求消息，消息的发送和接收可以通过INVITE/100Trying/180Ring/200ok实现。
应当理解的是，本示例提供的角色寻址业务实现方法特别适用于铁路通信系统，但并不限于在铁路通信系统中使用。
本示例提供一种角色寻址业务实现方法，客户端装置通过应用服务端装置向智能网发送角色注册业务消息，智能网根据角色注册业务消息对客户端装置进行角色注册，并通过应用服务端装置向客户端装置反馈注册成功响应消息；在客户端装置角色注册成功之后，客户端装置可以通过应用服务端装置向智能网发送角色呼叫业务消息；智能网从被呼叫角色的呼叫应用号码对应的角色下，选择用户状态(可以选择一个者多个)为有效的用户标识作为被叫用户标识反馈给所述应用服务端装置；应用服务端装置建立客户端装置与被叫用户标识对应的客户端装置之间的呼叫业务。扩充了原有GSM-R下的智能网业务功能寻址的业务范围和类型，通过客户端装置进行角色注册管理有利于提高用户设备的灵活性，可以选择各种各样的用户设备，而且使业务的扩展也变得更加容易。
示例二：
本示例在示例一的基础上提出一种角色寻址业务实现方法，与示例一不同的是，本示例中的角色寻址业务实现方法还包括客户端装置进行角色订阅的过程，请参见图3，图3为本公开示例二提供的客户端装置进行角色订阅的流程示意图，包括：
S21：客户端装置通过应用服务端装置发送角色订阅业务消息给智能网；
角色订阅业务消息中包括但不限于被订阅角色消息，被订阅角色消息中包括但不限于被订阅角色名称、被订阅角色呼叫应用号码。应当理解的是，在应用服务端装置接收到角色订阅业务消息后，为了更好的保证铁路通信系统的安全及稳定性，可以对发送该角色订阅业务消息的客户端装置的身份以及是否具有订阅业务权限进行鉴权，鉴权可以根据该客户端装置已激活的配置文件鉴定用户权限。也可以通过客户端装置在智能网上进行注册的角色属性信息(角色名称、角色的呼叫应用号码、角色的用户标识以及角色的用户状态)来验证该客户端装置身份以及是否具有订阅业务权限。应用服务端装置对于合法的角色订阅业务消息将其发送给智能网进行角色订阅业务处理，对于不合法的角色订阅业务消息可以向客户端装置反馈错误提示或者直接丢弃不做处理。
应当理解的是，是否具有订阅业务权限可以根据铁路通信系统实际应用情况灵活设定，例如，指挥调度室由于是铁路系统的重要指挥部门，可以进行各种角色订阅(司机角色、乘务员角色、保安人员角色)，方便铁路系统的稳定有序的工作，而保安人员角色则不能进行订阅指挥调度室角色业务，因为保安人员角色仅负责相应的铁路安保工作，没有必要掌控指挥调度室的工作情况。
本示例中提供的角色寻址业务实现方法是基于GCSE_LTE架构的，GCSE_LTE架构请参见图4，图4为本公开示例二提供的GCSE_LTE架构结构示意图，包括：
UE(User Equipment，用户设备)、eNodeB/eNB(演进型基站)、EPC(Evolved Packet Core,分组核心演进)、GCSE Application Server(应用服务设备)，其中，EPC中包含MME(Mobility Management Entity，移动管理节 点)、MBMS GW(Multimedia Broadcast Multicast Service GateWay，多媒体广播多播业务网关)、S-GW(Serving GateWay，服务网关)、P-GW(PDN GateWay，PDN网关)、BM-SC(Broadcast Multicast Service Cente，广播组播业务中心)。
S22：智能网在预设查询条件满足时向应用服务端装置发送包含被订阅角色对应用户标识的状态查询消息；
智能网接收角色订阅业务消息，并在满足相应的预设查询条件时向应用服务端装置发送包含被订阅角色对应用户标识的状态查询消息。
应当理解的是，预设查询条件包括但不限于定时查询、角色信息改变时查询。例如，预设查询条件为定时1分钟查询，则智能网每间隔1分钟，向应用服务端装置发送包含被订阅角色对应用户标识的状态查询消息；同样，当预设查询条件设置为角色信息改变时查询时，则当被订阅角色的角色属性信息，例如角色名称、角色的呼叫应用号码、角色的用户标识、角色的用户状态改变时，智能网向应用服务端装置发送包含被订阅角色对应用户标识的状态查询消息。
S23：应用服务端装置根据状态查询消息对该用户标识对应的查询项进行查询，并将查询结果反馈给智能网；
应用服务端装置根据包含被订阅角色对应用户标识的状态查询消息，对该用户标识对应的查询项进行查询。其中，查询项包括但不限于用户名称查询项、呼叫状态查询项、通话统计查询项以及所属人查询项，并将查询结果(用户名称查询结果、呼叫状态查询结果、通话统计查询结果以及所属人查询结果)反馈给智能网。
S24：智能网根据查询结果生成角色订阅响应消息反馈给客户端装置。
智能网接收由应用服务端装置反馈的查询结果，并根据该反馈结果生成角色订阅响应消息，其中，角色订阅响应消息包括但不限于被订阅角色的用户标识、该用户标识的用户名称、该用户标识所属人、该用户标识的呼叫状态、该用户标识的用户状态、该用户标识的通话统计。智能网将生成的角色订阅响应消息反馈给客户端装置。客户端装置通过显示界面或者语音提示反 馈给用户，极大方便了铁路通信系统的资源共享与指挥调度。例如，当指挥调度室订阅各角色业务时，智能网将定时或者当被订阅角色信息改变时将反馈角色订阅响应消息给指挥调度室，指挥调度室可以方便快捷地掌握各个角色信息，从而有利于调度指挥。
应当理解的是，角色订阅业务消息需符合网络协议SIP规范，角色订阅过程中可以采用INFO/MESSAGE/NOTIFY/OPTION发送和接收相应消息。
本示例提供一种角色寻址业务实现方法，该角色寻址业务实现方法是基于GCSE_LTE架构的，客户端装置通过应用服务端装置发送包含被呼叫角色的呼叫应用号码的角色订阅业务消息给智能网，智能网在预设查询条件满足时向应用服务端装置发送包含被订阅角色对应用户标识的状态查询消息，应用服务端装置根据状态查询消息对该用户标识对应的查询项进行查询，并将查询结果反馈给智能网，智能网根据查询结果生成角色订阅响应消息反馈给客户端装置。通过客户端装置进行角色订阅，对相关用户实现相应的角色订阅业务，有利于提高用户设备的选择灵活性，可以选择更多的用户设备，也使角色订阅业务变得更加方便，基于GCSE_LTE架构的铁路角色寻址业务扩展了原有的GSM-R下的智能网业务功能寻址的业务范围和类型，有利于提高用户体验。
示例三：
本示例提供一种角色寻址业务实现系统，用于实现上面示例一和示例二所述的角色寻址业务实现方法，包括客户端装置1、应用服务端装置2和智能网3，请参见图5，图5为本公开示例三提供的角色寻址业务实现系统的结构示意图。
其中，客户端装置1包含业务发起单元11和客户端业务处理单元12，请参见图6，图6为本公开示例三提供的客户端装置的结构示意图。
业务发起单元11，与SIP上行发送单元相连，设置为向应用服务端装置2发送角色注册业务消息，角色注册业务消息包括客户端装置1的用户标识以及待注册的角色名称；以及设置为在注册成功后，向应用服务端装置2发送角色呼叫业务消息，角色呼叫业务消息包括被呼叫角色的呼叫应用号 码；
客户端业务处理单元12，与SIP下行接收单元相连，设置为接收应用服务端装置2反馈的注册成功响应消息，注册成功响应消息包含所注册角色的呼叫应用号码；以及设置为接收应用服务端装置2根据角色呼叫业务消息获取到被呼叫角色对应的被叫用户标识后所发送的呼叫业务建立消息，与被叫用户标识对应的客户端装置建立呼叫业务。
本示例中，业务发起单元11还设置为向应用服务端装置2发送角色管理业务消息，其中角色管理业务消息包括但不限于角色注销业务消息、角色强制注销业务消息以及角色查询业务消息。应当理解的是，此时客户端业务处理单元12还设置为接收应用服务端装置1反馈的角色管理响应消息，其中角色管理响应消息包括但不限于角色注销结果、角色强制注销结果以及角色查询结果。
本示例中，业务发起单元11还设置为向应用服务端装置2发送角色订阅业务消息，其中角色订阅业务消息包括被订阅角色消息，所述被订阅角色消息包含被订阅角色名称和/或呼叫应用号码；客户端业务处理单元12还设置为接收应用服务端装置2反馈的角色订阅响应消息，其中角色订阅响应消息包括但不限于被订阅角色的用户标识、该用户标识的用户名称、该用户标识所属人、该用户标识的呼叫状态、该用户标识的用户状态、该用户标识的通话统计。
应用服务端装置2包含业务接收单元21和服务端业务处理单元22，请参见图7，图7本公开示例三提供的应用服务端装置的结构示意图。
业务接收单元21，与SIP上行接收单元相连，设置为接收客户端装置1发送的角色注册业务消息，以及设置为接收客户端装置1在注册成功后发送的角色呼叫业务消息；角色注册业务消息包括客户端装置1的用户标识以及待注册的角色名称；角色呼叫业务消息包括被呼叫角色的呼叫应用号码；
服务端业务处理单元22，与SIP下行发送单元相连，设置为将角色注册业务消息发送给智能网3，并将智能网3根据角色注册业务消息进行注册处理后反馈的注册成功响应消息发送给客户端装置1；以及设置为将角色呼叫业务消息发送给智能网3，根据智能网3基于被呼叫角色的呼叫应用号码 选择的被叫用户标识，与客户端装置1建立呼叫业务。
本示例中，业务接收单元21还设置为接收客户端装置1发起的角色管理业务消息，其中角色管理业务消息包括但不限于角色注销业务消息、角色强制注销业务消息以及角色查询业务消息。应当理解的是，此时服务端业务处理单元22还设置为将角色管理业务消息发送给智能网3，以及将智能网3反馈的角色管理响应消息发送给客户端装置1，其中角色管理响应消息包括但不限于角色注销结果、角色强制注销结果以及角色查询结果。
本示例中，业务接收单元21还设置为接收客户端装置1发起的角色订阅业务消息，其中角色订阅业务消息包括但不限于被订阅角色消息，所述被订阅角色消息包含被订阅角色名称和/或呼叫应用号码；应当理解的是，此时服务端业务处理单元22还设置为将角色订阅业务消息发送给智能网3，以及设置为根据智能网3基于角色订阅业务消息发送的包含被订阅角色对应用户标识的状态查询消息，对该用户标识对应的查询项进行查询，并将查询结果反馈给智能网3，以及设置为将智能网3根据查询结果生成的角色订阅响应消息反馈给客户端装置1。
本示例中，查询项包括但不限于用户标识的用户名称查询项、呼叫状态查询项、通话统计查询项以及所属人查询项。
智能网3包括消息接收单元31和智能网业务处理单元32，请参见图8，图8本公开示例三提供的智能网的结构示意图。
消息接收单元31，设置为接收应用服务端装置2发送的来自客户端装置1的角色注册业务消息以及角色呼叫业务消息；角色注册业务消息包括客户端装置1的用户标识以及待注册的角色名称；角色呼叫业务消息包括被呼叫角色的呼叫应用号码；
智能网业务处理单元32，设置为根据角色注册业务消息对客户端装置1进行角色注册，并向应用服务端装置2反馈包含呼叫应用号码的注册成功响应消息，注册的角色属性信息包含：角色名称、角色的呼叫应用号码、角色的用户标识以及角色的用户状态；以及设置为从被呼叫角色的呼叫应用号码对应的角色下，选择一个用户状态为有效的用户标识作为被叫用户标识反馈给应用服务端装置2。
本示例中，消息接收单元31还设置为接收应用服务端装置2发送的来自客户端装置1的角色管理业务消息，其中角色管理业务消息包括但不限于角色注销业务消息、角色强制注销业务消息以及角色查询业务消息。应当理解的是，此时智能网业务处理单元32还设置为对角色管理业务消息所请求的被管理角色进行管理处理，应当理解的是，管理处理包括但不限于角色注销处理、角色强制注销处理以及角色查询处理，并将处理后得到的角色管理响应消息发送给应用服务端装置2。
本示例中，消息接收单元31还设置为应用服务端装置2发送的来自客户端装置1的角色订阅业务消息，其中角色订阅业务消息包括被订阅角色消息，所述被订阅角色消息包含被订阅角色名称和/或呼叫应用号码；应当理解的是，此时智能网业务处理单元32还设置为根据角色订阅业务消息，在预设查询条件满足时向应用服务端装置2发送包含被订阅角色对应用户标识的状态查询消息，以及设置为接收应用服务端装置2反馈的查询结果，其中查询结果包括但不限于用户标识的用户名称查询结果、呼叫状态查询结果、通话统计查询结果、所属人查询结果，以及设置为根据查询结果生成角色订阅响应消息发送给应用服务端装置2，其中角色订阅响应消息包括但不限于被订阅角色的用户标识、该用户标识的用户名称、该用户标识所属人、该用户标识的呼叫状态、该用户标识的用户状态、该用户标识的通话统计。
应当理解的是，预设查询条件包括但不限于定时查询、角色信息改变时查询。例如，预设查询条件为定时5分钟查询，则智能网3每间隔5分钟，向应用服务端装置2发送包含被订阅角色对应用户标识的状态查询消息；同样，当预设查询条件设置为角色信息改变时查询时，则当被订阅角色的角色属性信息，例如角色名称、角色的呼叫应用号码、角色的用户标识、角色的用户状态改变时，智能网3向应用服务端装置2发送包含被订阅角色对应用户标识的状态查询消息。
本示例提供一种角色寻址业务实现系统，包括客户端装置1、应用服务端装置2以及智能网3，其中客户端装置1包括业务发起单元11和客户端业务处理单元12，应用服务端装置2包括业务接收单元21和服务端业务处理单元22，智能网3包括消息接收单元31和智能网业务处理单元32；通过 客户端装置1的业务发起单元11向应用服务端装置2发送角色注册业务消息，应用服务端装置2通过业务接收单元21接受该角色注册业务消息，并通过服务端业务处理单元22将其发送给智能网3，其中角色注册业务消息包含客户端装置1的用户标识以及待注册的角色名称；智能网3通过消息接收单元31接收该角色注册业务消息，并通过智能网业务处理单元32对该客户端装置1进行角色注册，并向应用服务端装置2反馈包含呼叫应用号码的注册成功响应消息，注册的角色属性信息包含：角色名称、角色的呼叫应用号码、角色的用户标识以及角色的用户状态；应用服务端装置2通过业务接收单元21接收该注册成功响应消息，并通过服务端业务处理单元22反馈给客户端装置1，通过客户端业务处理单元12接收应用服务端装置2反馈的注册成功响应消息。在客户端装置1角色注册成功之后，便可进行其他业务处理，包括角色注销业务、角色强制注销业务、角色查询业务、角色呼叫业务、角色订阅业务。
当进行角色呼叫时，客户端装置1通过业务发起单元11向应用服务端装置2发送角色呼叫业务消息，应用服务端装置2通过业务接收单元21接受该角色呼叫业务消息，并通过服务端业务处理单元22将其发送给智能网3，其中角色呼叫业务消息包括被呼叫角色的呼叫应用号码；智能网3通过消息接收单元31接收该角色呼叫业务消息，并通过智能网业务处理单元32从被呼叫角色的呼叫应用号码对应的角色下，选择一个用户状态为有效的用户标识作为被叫用户标识反馈给应用服务端装置2，应用服务端装置2通过服务端业务处理单元22根据被叫用户标识发送呼叫业务建立消息，客户端装置1通过客户端业务处理单元12接收该呼叫业务建立消息，建立与被呼叫用户标识对应的客户端装置的呼叫连接。。扩充了原有GSM-R下的智能网业务功能寻址的业务范围和类型，通过客户端装置进行角色注册管理有利于提高用户设备的灵活性，可以选择各种各样的用户设备，而且使业务的扩展也变得更加容易。
本公开实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现以上描述的角色寻址业务实现方法。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
以上内容是结合具体的实施方式对本公开实施例所作的详细说明，不能认定本公开的具体实施只局限于这些说明。对于本公开所属技术领域的普通技术人员来说，在不脱离本公开构思的前提下，还可以做出若干简单推演或替换，都应当视为属于本公开的保护范围。
工业实用性
根据本公开实施例提供的角色寻址业务实现方法及系统，客户端装置通过应用服务端装置向智能网发送角色注册业务消息，角色注册业务消息包括客户端装置待注册的角色名称以及用户标识；智能网根据角色注册业务消息对客户端装置进行角色注册，注册的角色属性信息包括：角色名称、角色的呼叫应用号码、角色的用户标识以及角色的用户状态；并通过应用服务 端装置向客户端装置反馈包含呼叫应用号码的注册成功响应消息；客户端装置通过应用服务端装置向智能网发送包含被呼叫角色的呼叫应用号码的角色呼叫业务消息；智能网从被呼叫角色的呼叫应用号码对应的角色下，选择一个用户状态为有效的用户标识作为被叫用户标识反馈给所述应用服务端装置；应用服务端装置建立客户端装置与被叫用户标识对应的客户端装置之间的呼叫业务。扩充了原有GSM-R下的智能网业务功能寻址的业务范围和类型，通过客户端装置进行角色注册管理有利于提高用户设备的灵活性，可以选择各种各样的用户设备，而且使业务的扩展也变得更加容易。

Claims (13)

  1. 一种客户端装置(1)，包括：
    业务发起单元(11)，设置为向应用服务端装置发送角色注册业务消息，所述角色注册业务消息包括所述客户端装置(1)的用户标识以及待注册的角色名称；以及设置为在注册成功后，向所述应用服务端装置发送角色呼叫业务消息，所述角色呼叫业务消息包括被呼叫角色的呼叫应用号码；
    客户端业务处理单元(12)，设置为接收所述应用服务端装置反馈的注册成功响应消息，所述注册成功响应消息包含所注册角色的呼叫应用号码；以及设置为接收所述应用服务端装置根据所述角色呼叫业务消息获取到被呼叫角色对应的被叫用户标识后所发送的呼叫业务建立消息，与所述被叫用户标识对应的客户端装置建立呼叫业务。
  2. 如权利要求1所述的客户端装置(1)，其中，所述业务发起单元(11)还设置为向所述应用服务端装置发送角色管理业务消息，所述角色管理业务消息为角色注销业务消息、角色强制注销业务消息以及角色查询业务消息中的任意一种；
    所述客户端业务处理单元(12)还设置为接收所述应用服务端装置反馈的角色管理响应消息，所述角色管理响应消息包含角色注销结果、角色强制注销结果以及角色查询结果中的任意一种。
  3. 如权利要求1或2所述的客户端装置(1)，其中，所述业务发起单元(11)还设置为向所述应用服务端装置发送角色订阅业务消息，所述角色订阅业务消息包括被订阅角色消息，所述被订阅角色消息包含被订阅角色名称、或呼叫应用号码、或被订阅角色名称和呼叫应用号码；
    所述客户端业务处理单元(12)还设置为接收所述应用服务端装置反馈的角色订阅响应消息，所述角色订阅响应消息包含被订阅角色的用户标识、该用户标识的用户名称、该用户标识所属人、该用户标识的呼叫状态、该用户标识的用户状态、该用户标识的通话统计中的至少一种。
  4. 一种应用服务端装置(2)，包括：
    业务接收单元(21)，设置为接收客户端装置发送的角色注册业务消息， 以及设置为接收所述客户端装置在注册成功后发送的角色呼叫业务消息；所述角色注册业务消息包括所述客户端装置的用户标识以及待注册的角色名称；所述角色呼叫业务消息包括被呼叫角色的呼叫应用号码；
    服务端业务处理单元(22)，设置为将所述角色注册业务消息发送给智能网，并将所述智能网根据所述角色注册业务消息进行注册处理后反馈的注册成功响应消息发送给所述客户端装置；以及设置为将所述角色呼叫业务消息发送给所述智能网，根据所述智能网基于所述被呼叫角色的呼叫应用号码选择的被叫用户标识，与所述客户端装置建立呼叫业务。
  5. 如权利要求4所述的应用服务端装置(2)，其中，所述业务接收单元(21)还设置为接收所述客户端装置发起的角色管理业务消息，所述角色管理业务消息为角色注销业务消息、角色强制注销业务消息以及角色查询业务消息中的任意一种；
    所述服务端业务处理单元(22)还设置为将所述角色管理业务消息发送给所述智能网，以及将所述智能网反馈的角色管理响应消息发送给所述客户端装置；所述角色管理响应消息包含角色注销结果、角色强制注销结果以及角色查询结果中的任意一种。
  6. 如权利要求4或5所述的应用服务端装置(2)，其中，所述业务接收单元(21)还设置为接收所述客户端装置发起的角色订阅业务消息；所述角色订阅业务消息包括被订阅角色消息，所述被订阅角色消息包含被订阅角色名称、或呼叫应用号码、或被订阅角色名称和呼叫应用号码；
    所述服务端业务处理单元(22)还设置为将所述角色订阅业务消息发送给所述智能网，以及设置为根据所述智能网基于所述角色订阅业务消息发送的包含所述被订阅角色对应用户标识的状态查询消息，对该用户标识对应的查询项进行查询，并将查询结果反馈给所述智能网；以及设置为将所述智能网根据所述查询结果生成的角色订阅响应消息反馈给所述客户端装置；所述查询项包括用户标识的用户名称查询项、呼叫状态查询项、通话统计查询项以及所属人查询项中的至少一种。
  7. 一种智能网(3)，包括：
    消息接收单元(31)，设置为接收应用服务端装置发送的来自客户端装置的角色注册业务消息以及角色呼叫业务消息；所述角色注册业务消息包括所述客户端装置的用户标识以及待注册的角色名称；所述角色呼叫业务消息包括被呼叫角色的呼叫应用号码；
    智能网业务处理单元(32)，设置为根据所述角色注册业务消息对所述客户端装置进行角色注册，并向所述应用服务端装置反馈包含呼叫应用号码的注册成功响应消息，注册的角色属性信息包含：角色名称、角色的呼叫应用号码、角色的用户标识以及角色的用户状态；以及设置为从所述被呼叫角色的呼叫应用号码对应的角色下，选择一个用户状态为有效的用户标识作为被叫用户标识反馈给所述应用服务端装置。
  8. 如权利要求7所述的智能网(3)，其中，
    所述消息接收单元(31)还设置为接收所述应用服务端装置发送的来自所述客户端装置的角色管理业务消息，所述角色管理业务消息为角色注销业务消息、角色强制注销业务消息以及角色查询业务消息中的任意一种；
    所述智能网业务处理单元(32)还设置为对所述角色管理业务消息所请求的被管理角色进行管理处理，所述管理处理为角色注销处理、角色强制注销处理以及角色查询处理中的任意一种；并将处理后得到的角色管理响应消息发送给所述应用服务端装置。
  9. 如权利要求7或8所述的智能网(3)，其中，
    所述消息接收单元(31)还设置为接收所述应用服务端装置发送的来自所述客户端装置的角色订阅业务消息，所述角色订阅业务消息包括被订阅角色消息，所述被订阅角色消息包含被订阅角色名称、或呼叫应用号码、或被订阅角色名称和呼叫应用号码；
    所述智能网业务处理单元(32)还设置为根据所述角色订阅业务消息，在预设查询条件满足时向所述应用服务端装置发送包含所述被订阅角色对应用户标识的状态查询消息；以及设置为接收所述应用服务端装置反馈的查询结果，所述查询结果包括用户标识的用户名称查询结果、呼叫状态查询结果、通话统计查询结果以及所属人查询结果中的至少一种；以及设置为根据 所述查询结果生成角色订阅响应消息发送给所述应用服务端装置，所述角色订阅响应消息包含被订阅角色的用户标识、该用户标识的用户名称、该用户标识所属人、该用户标识的呼叫状态、该用户标识的用户状态、该用户标识的通话统计中的至少一种。
  10. 一种角色寻址业务实现方法，包括：
    客户端装置通过应用服务端装置向智能网发送角色注册业务消息(S01)，所述角色注册业务消息包括所述客户端装置待注册的角色名称以及用户标识；
    所述智能网根据所述角色注册业务消息对所述客户端装置进行角色注册(S02)，注册的角色属性信息包括：角色名称、角色的呼叫应用号码、角色的用户标识以及角色的用户状态；并通过所述应用服务端装置向所述客户端装置反馈包含呼叫应用号码的注册成功响应消息(S03)；
    所述客户端装置通过所述应用服务端装置向所述智能网发送包含被呼叫角色的呼叫应用号码的角色呼叫业务消息(S11)；
    所述智能网从所述被呼叫角色的呼叫应用号码对应的角色下，选择一个用户状态为有效的用户标识作为被叫用户标识反馈给所述应用服务端装置(S12)；
    所述应用服务端装置建立所述客户端装置与所述被叫用户标识对应的客户端装置之间的呼叫业务(S13)。
  11. 如权利要求10所述的角色寻址业务实现方法，其中，
    所述客户端装置、应用服务端装置和所述智能网之间基于会话初始协议进行通信。
  12. 如权利要求10或11所述的角色寻址业务实现方法，其中，
    所述角色属性信息还包括本角色所关联的角色信息和角色有效期中的至少一种。
  13. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现权利要求10-12中任一项所述的角色寻址业务实现方法。
PCT/CN2017/119368 2017-01-05 2017-12-28 一种角色寻址业务实现方法及系统 WO2018126980A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710008120.XA CN108282772A (zh) 2017-01-05 2017-01-05 一种角色寻址业务实现方法及系统
CN201710008120.X 2017-01-05

Publications (1)

Publication Number Publication Date
WO2018126980A1 true WO2018126980A1 (zh) 2018-07-12

Family

ID=62789191

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/119368 WO2018126980A1 (zh) 2017-01-05 2017-12-28 一种角色寻址业务实现方法及系统

Country Status (2)

Country Link
CN (1) CN108282772A (zh)
WO (1) WO2018126980A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112187863A (zh) * 2020-09-01 2021-01-05 远光软件股份有限公司 扩展组织角色的方法、装置、存储介质及电子设备
CN112333696A (zh) * 2020-09-22 2021-02-05 南京泰通科技股份有限公司 5g-r功能寻址方法
CN113450095A (zh) * 2020-03-24 2021-09-28 北京沃东天骏信息技术有限公司 标识配置的方法及装置
US11356459B2 (en) 2020-05-08 2022-06-07 Motorola Solutions, Inc. Method and console server for creating and managing dispatch role lists

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109362060A (zh) * 2018-11-21 2019-02-19 通号通信信息集团有限公司 一种适用于铁路无线宽带通信系统的功能寻址方法及系统
CN111866763B (zh) * 2019-04-26 2022-03-11 北京中兴高达通信技术有限公司 功能别称的处理、请求，管理方法及装置
CN112055354A (zh) * 2019-06-06 2020-12-08 中兴通讯股份有限公司 业务呼叫处理方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859647A (zh) * 2006-01-24 2006-11-08 华为技术有限公司 实现移动终端动态编组、编组注销的方法及系统
CN101483819A (zh) * 2008-12-24 2009-07-15 深圳市桑达无线通讯技术有限公司 一种铁路专用通信终端及其控制方法
CN101841777A (zh) * 2010-05-17 2010-09-22 中兴通讯股份有限公司 一种控制移动终端业务的方法和系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1596620A1 (en) * 2004-05-14 2005-11-16 Nortel Networks Limited System and method for non-unique functional number processing in telecommunication applications
JP5071158B2 (ja) * 2008-02-29 2012-11-14 沖電気工業株式会社 交換システム及びサーバ装置
CN101489204A (zh) * 2009-02-10 2009-07-22 北京交通大学 一种基于核心网的位置寻址解决不唯一车次号的方法
CN103857032B (zh) * 2014-01-20 2017-04-12 深圳市桑达无线通讯技术有限公司 向gsm‑r网络节点注册、查询或者注销多个功能号的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859647A (zh) * 2006-01-24 2006-11-08 华为技术有限公司 实现移动终端动态编组、编组注销的方法及系统
CN101483819A (zh) * 2008-12-24 2009-07-15 深圳市桑达无线通讯技术有限公司 一种铁路专用通信终端及其控制方法
CN101841777A (zh) * 2010-05-17 2010-09-22 中兴通讯股份有限公司 一种控制移动终端业务的方法和系统

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113450095A (zh) * 2020-03-24 2021-09-28 北京沃东天骏信息技术有限公司 标识配置的方法及装置
US11356459B2 (en) 2020-05-08 2022-06-07 Motorola Solutions, Inc. Method and console server for creating and managing dispatch role lists
CN112187863A (zh) * 2020-09-01 2021-01-05 远光软件股份有限公司 扩展组织角色的方法、装置、存储介质及电子设备
CN112187863B (zh) * 2020-09-01 2023-06-27 远光软件股份有限公司 扩展组织角色的方法、装置、存储介质及电子设备
CN112333696A (zh) * 2020-09-22 2021-02-05 南京泰通科技股份有限公司 5g-r功能寻址方法

Also Published As

Publication number Publication date
CN108282772A (zh) 2018-07-13

Similar Documents

Publication Publication Date Title
WO2018126980A1 (zh) 一种角色寻址业务实现方法及系统
US20240154827A1 (en) Capability Signaling in Wireless Communications
AU2012301417B2 (en) Method and apparatus for providing a group communications follow mode
EP3047696B1 (en) Device-to-device communication among wireless communication devices using group id and application id
CN107925666B (zh) 合并活动组呼叫
US20170257751A1 (en) Off-Network Wireless Mission Critical Session Initiation
US20090113487A1 (en) Method and Apparatus for Broadcasting/Multicasting Content from Mobile User Equipment over an MBMS Network
US12075320B2 (en) Method and apparatus for parameter configuration
CN102740297B (zh) 一种寻呼方法及寻呼装置、寻呼系统
EP3310108B1 (en) Method and apparatus for changing association relationship between mcptt user and mcptt group
CN106792627B (zh) 一种多设备连通通讯的实现方法及实现系统
WO2021109134A1 (zh) Mbms信息的获取、发送方法、终端设备及网元设备
KR101218949B1 (ko) Ｍｂｍｓ 베어러 설정 관리 방법 및 장치
US11653395B2 (en) Method for establishing a connection of a mobile terminal to a mobile radio communication network and radio access network component
CN116601917A (zh) 用于安全通信的方法和装置
US20050079858A1 (en) Method and apparatus for restricting media communication in a communication network
US10516987B2 (en) Discovery method and device
WO2019095261A1 (en) Methods and devices for group communication
CN108476384B (zh) 一种数据传输方法及相关装置
WO2021208059A1 (zh) 连接建立方法、装置、设备及存储介质
WO2004034655A1 (en) A method of establishing and deleting mbms service in sgsn and ggsn
WO2017163695A1 (ja) コアノード、加入者情報管理装置、通信システム、通信方法、及び、コンピュータ可読媒体
WO2023093271A1 (zh) 一种确定s-cscf的方法及装置
US20200195576A1 (en) Technique for Providing Content Via a Mobile Communications Network
CN116506810A (zh) 一种验证方法、通信装置及通信系统

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: 17890604

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17890604

Country of ref document: EP

Kind code of ref document: A1