WO2020063911A1 - 一种通信方法、装置及系统 - Google Patents

一种通信方法、装置及系统 Download PDF

Info

Publication number
WO2020063911A1
WO2020063911A1 PCT/CN2019/108702 CN2019108702W WO2020063911A1 WO 2020063911 A1 WO2020063911 A1 WO 2020063911A1 CN 2019108702 W CN2019108702 W CN 2019108702W WO 2020063911 A1 WO2020063911 A1 WO 2020063911A1
Authority
WO
WIPO (PCT)
Prior art keywords
processing entity
service
address information
entity
registration
Prior art date
Application number
PCT/CN2019/108702
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 WO2020063911A1 publication Critical patent/WO2020063911A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • 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/08—Network architectures or network communication protocols for network security for authentication of entities
    • 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/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a communication method, device, and system.
  • IP Multimedia Subsystem is a network system for providing multimedia services based on Internet Protocol (IP) networks.
  • IP Internet Protocol
  • IMS IP Multimedia Subsystem
  • terminal devices such as voice calls, Video calls, etc.
  • the serving call state control function (S-CSCF) entity in IMS is the core entity that provides multimedia services for the terminal device.
  • S-CSCF entity In the existing IMS communication mode, an S-CSCF entity generally only provides A type of service.
  • a terminal device registered to the IMS communicates with only one S-CSCF entity in the IMS registered.
  • the services of terminal equipment are no longer limited to basic voice calls, video calls, and other services, but rely on an S-CSCF entity in IMS. It can only provide a specific service, and cannot realize other services of the terminal device.
  • the existing IMS communication methods cannot meet the service expansion requirements of terminal equipment.
  • This application provides a communication method, device, and system, which are used to solve the problem that the IMS communication method in the prior art cannot meet the service expansion requirements of terminal equipment.
  • an embodiment of the present application provides a communication method.
  • the method includes: First, a registration processing entity receives a registration request from a terminal device through an access processing entity, and the registration request includes a service of the terminal device. Identification, and then the registration processing entity may authenticate the terminal device according to the registration request of the terminal device, and may further determine the address information of the service processing entity corresponding to the service identification according to the service identification of the terminal device, where The service processing entity may provide the terminal device with the service identified by the service identifier; after that, the registration processing entity sends to the access processing entity the address information and address of the service processing entity.
  • the registration response request for the service ID is described.
  • the registration processing entity can determine the address information of the service processing entity according to the service identifier, which can enable the terminal device to register when the terminal device needs service expansion.
  • the request carries the service identifier of the service that the terminal device needs to expand, and then the registration processing entity can determine the address information of the corresponding service processing entity, which can further meet the requirements of the terminal device service expansion.
  • the registration processing entity may determine the address information of the business processing entity according to the service identification, and the registration processing entity may determine the business processing based on the pre-stored service identification. Correspondence between the address information of the entity, the address information of the business processing entity is determined according to the service identifier, or the address information of the business processing entity may be determined by other equipment according to the service identifier, and other devices are used for inquiry processing Entity as an example:
  • the registration processing entity may first send a first request message to the query processing entity. After that, the registration processing entity receives a first response message from the query processing entity, where the first request message is used for Requesting address information of a business processing entity, the first request message includes the service identifier; the first response message includes address information of the business processing entity, and upon receiving the registration processing entity receiving the first After a response message, the address information of the service processing entity may be determined according to the first response message.
  • the registration processing entity can flexibly determine the address information of the business processing entity according to the service identifier, and the manner of determining the address information of the business processing entity is more diversified, which also makes the embodiments of the present application provide
  • the method can be applied to different application scenarios.
  • the registration processing entity may send a notification message to the business processing entity, where the notification message It is used to notify the service processing entity to obtain subscription information of the terminal device.
  • the registration processing entity can notify the service processing entity to obtain the contract information of the terminal device in advance, and ensure that when the terminal device subsequently needs the service processing entity to provide services, the service processing entity can further Provide services to the terminal device quickly and efficiently.
  • the registration processing entity may further notify the server to save the address information of the service processing entity and the service identifier. Specifically, the registration processing entity may send a first message to the server, where the first message includes a correspondence between the address information of the service processing entity and the service identifier.
  • the registration processing entity can save the correspondence between the address information of the business processing entity and the business identifier to the server, saving local storage space, and when the address of the business processing entity is needed Information, it may also be convenient to obtain address information of the service processing entity from the server.
  • an embodiment of the present application provides a communication method.
  • the method includes: first, an access processing entity may forward a registration request of the terminal device to a registration processing entity, and then may receive a registration request from the registration processing entity; A registration response message, where the registration response message includes address information of the service processing entity and the service identifier, and the service processing entity may provide the terminal device with the service identified by the service identifier; After the registration response message is received, the access processing entity may save the address information of the service processing entity and the correspondence between the service identifiers, and may also send the terminal device with the address of the service processing entity deleted. Information and the registration response message of the service ID.
  • the access processing entity can save the address information of the service processing entity and the correspondence between the service identifiers.
  • the access processing entity can save the service Processing the address information of the entity and the corresponding service identifier may enable service expansion of the terminal device.
  • the access processing entity receives a call request from the terminal device, where the call request includes the service identifier; after that, the access processing entity may store and save the service request according to the service identifier.
  • the access processing entity may process the service processing entity according to the address information of the business processing entity The entity sends the call request.
  • the access processing entity may forward the call request to the service processing entity according to the service identifier, so that the terminal device can communicate with the service.
  • the processing entity communicates, thereby ensuring that the terminal device can obtain service support.
  • an embodiment of the present application provides a communication method.
  • the method includes: first, an inquiry processing entity may receive a first request message from a registration processing entity, and the first request message is used to request a service processing entity;
  • the first request message includes the service identifier of the terminal device, and the service processing entity may provide the terminal device with the service identified by the service identifier; thereafter, the inquiry processing entity Determining, according to the service identifier, address information of a service processing entity corresponding to the service identifier; thereafter, the inquiry processing entity may send a first response message to the registration processing entity, where the first response message includes the Address information of the business processing entity.
  • the query processing entity may notify the registration processing entity of the address information of the business processing entity, which can make the terminal device
  • the query processing entity may determine the address information of the corresponding service processing entity afterwards, which may further meet the requirements of the terminal device service expansion.
  • the query processing entity receives a call request, and the call request includes the service identifier; after that, the query processing entity may determine the service identifier corresponding to the service identifier according to the service identifier. Address information of a business processing entity; the query processing entity sends the call request to the business processing entity according to the address information of the business processing entity.
  • the inquiry processing entity may forward the call request to the corresponding service processing entity according to the service identifier, so that the service processing entity provides corresponding services, thereby ensuring the Terminal equipment can get business support.
  • the query processing entity may locally store the service.
  • the identifier determines the correspondence between the address information of the service processing entity, and determines the address information of the service processing entity according to the service identifier.
  • the address information of the service processing entity may also be determined by other devices according to the service identifier.
  • the other devices are servers for example:
  • the query processing entity first sends a first query request to the server, where the first query request is used to request address information of the service processing entity, wherein the first query request includes the service identifier;
  • the query processing entity may receive a first query response from the server, and the query processing entity may determine the address information of the business processing entity according to the first query response.
  • the service processing entity can flexibly determine the address information of the service processing entity according to the service identifier.
  • the service processing entity can determine the address information of the service processing entity in different ways, and also expands Application scenarios.
  • an embodiment of the present application provides a communication method.
  • the method includes: first, a server may receive a first message from a registration processing entity, where the first message includes address information of the service processing entity and a terminal Correspondence between service identifiers of devices, the service processing entity may provide the terminal with the service entity identified by the service identifier; after that, the server saves the address information of the service processing entity and the service identifier Corresponding relationship.
  • the registration processing entity can save the correspondence between the address information of the business processing entity and the business identifier to the server, and the registration processing entity or other entity needs the address of the business processing entity Information, it may also be convenient to obtain address information of the service processing entity from the server.
  • the server may provide other entities with information of the service processing entity corresponding to the service identifier.
  • the address information is described below by taking another entity as an inquiry processing entity as an example: the server may receive a first query request from the inquiry processing entity, and the first query request includes the service identifier; after that, the server Determining the address information of the business processing entity according to the service identifier and the saved correspondence; after determining the address information of the business processing entity, the server sends a first query to the query processing entity In response, the first query response includes address information of the service processing entity.
  • the server can flexibly and conveniently provide address information of the business processing entity to other entities in a case where the address information of the business processing entity and the corresponding relationship of the service identifier are stored locally.
  • the service of the terminal device can be provided by the corresponding service processing entity, which can further ensure that the service of the terminal device can be effectively expanded.
  • an embodiment of the present application further provides a communication device, where the communication device is applied to a registration processing entity.
  • the device has the function of implementing the behavior in the method example of the first aspect described above.
  • the functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the device includes a receiving unit, a processing unit, and a sending unit. These units can perform the corresponding functions in the method example of the first aspect described above. For details, refer to the detailed description in the method example. To repeat.
  • an embodiment of the present application further provides a communication device, where the communication device is applied to an access processing entity.
  • the device has the function of implementing the behavior in the method example of the second aspect described above.
  • the functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the device includes a receiving unit, a sending unit, and a processing unit. These units can perform corresponding functions in the method example of the second aspect described above. For details, refer to the detailed description in the method example. To repeat.
  • an embodiment of the present application further provides a communication device, where the communication device is applied to an inquiry processing entity.
  • the device has the function of implementing the behavior in the method example of the third aspect described above.
  • the functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the device includes a receiving unit, a processing unit, and a sending unit. These units can perform the corresponding functions in the method example of the third aspect. For details, refer to the detailed description in the method example. To repeat.
  • an embodiment of the present application further provides a communication device, where the communication device is applied to a server.
  • the device has the function of implementing the behavior in the method example of the fourth aspect described above.
  • the functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the device includes a receiving unit and a processing unit, and may further include a sending unit, and these units may perform corresponding functions in the method example of the fourth aspect described above.
  • the structure of the device includes a receiving unit and a processing unit, and may further include a sending unit, and these units may perform corresponding functions in the method example of the fourth aspect described above.
  • an embodiment of the present application further provides a communication device, where the communication device is applied to a registration processing entity.
  • the structure of the communication device includes a processor and a memory, and the processor is configured to support the terminal to perform a corresponding function in the method of the first aspect.
  • the memory is coupled to the processor and stores program instructions and data necessary for the communication device.
  • the structure of the communication device further includes a communication interface for communicating with other devices.
  • an embodiment of the present application further provides a communication device, where the communication device is applied to an access processing entity.
  • the structure of the communication device includes a processor and a memory, and the processor is configured to support the terminal to execute a corresponding function in the method of the second aspect.
  • the memory is coupled to the processor and stores program instructions and data necessary for the communication device.
  • the structure of the communication device further includes a communication interface for communicating with other devices.
  • an embodiment of the present application further provides a communication device, where the communication device is applied to an inquiry processing entity.
  • the structure of the communication device includes a processor and a memory, and the processor is configured to support the terminal to perform a corresponding function in the method of the third aspect.
  • the memory is coupled to the processor and stores program instructions and data necessary for the communication device.
  • the structure of the communication device further includes a communication interface for communicating with other devices.
  • an embodiment of the present application further provides a communication device, where the communication device is applied to a server.
  • the structure of the communication device includes a processor and a memory, and the processor is configured to support the terminal to execute a corresponding function in the method of the fourth aspect.
  • the memory is coupled to the processor and stores program instructions and data necessary for the communication device.
  • the communication device further includes a transceiver in its structure for communicating with other devices.
  • an embodiment of the present application further provides a communication system.
  • a communication system For a beneficial effect, reference may be made to the description of each aspect above, and details are not described herein again.
  • the communication system registration processing entity and access processing entity are described.
  • the registration processing entity is configured to receive a registration request from a terminal device through an access processing entity, where the registration request includes a service identifier of the terminal device; and determine a service corresponding to the service identifier according to the service identifier of the terminal device. Address information of the processing entity; and sending a registration response request to the access processing entity, where the registration response request includes the address information of the service processing entity and the service identifier;
  • the access processing entity is configured to receive the registration response message after forwarding the registration request of the terminal device to the registration processing entity; and send the terminal device with the address information of the service processing entity and the The registration response message of the service identifier is described.
  • the communication system further includes an inquiry processing entity.
  • the registration processing entity may first send a first request message to the query processing entity, where the first request message is used to request a service Address information of a processing entity, wherein the first request message includes the service identifier; after that, the inquiry processing entity receives the first request message; and determines a corresponding service identifier corresponding to the service identifier according to the service identifier Address information of a business processing entity; thereafter, sending a first response message to the registration processing entity, where the first response message includes the address information of the business processing entity; and the registration processing entity may receive the first Response message.
  • the communication system further includes a server; the registration processing entity may send a first message to the server, and the first message includes address information of the service processing entity and the service identifier After that, the server receives the first message; and may save the correspondence between the address information of the service processing entity and the service identifier.
  • the registration processing entity may send a notification message to the service processing entity, and the notification message is used to notify the service processing entity to obtain the contract information of the terminal device.
  • the access processing entity may further receive a call request from the terminal device, where the call request includes the service identifier; after that, the access processing entity may according to the service identifier Determining address information of the service processing entity; and sending the call request to the service processing entity according to the address information of the service processing entity.
  • the query processing entity may further receive a call request, and the call request includes the service identifier; after that, the query processing entity may determine the service identifier according to the service identifier Address information of the corresponding business processing entity; and then sending the call request to the business processing entity according to the address information of the business processing entity.
  • the query processing entity may send a first query request to the server, where the first query request is used for requesting The address information of the service processing entity, wherein the first query request includes the service identifier.
  • the server is configured to receive the first query request; determine address information of the service processing entity according to the service identifier; and then send a first query response to the query processing entity, the first query
  • the response includes address information of the business processing entity.
  • the query processing entity may receive the first query response; and then send the call request to the service processing entity according to the first query response.
  • the present application also provides a computer-readable storage medium, where the computer-readable storage medium stores instructions, and when the computer-readable storage medium runs on the computer, causes the computer to execute the methods described in the above aspects.
  • the present application also provides a computer program product containing instructions that, when run on a computer, causes the computer to execute the methods described in the above aspects.
  • the present application further provides a computer chip, the chip is connected to a memory, and the chip is configured to read and execute a software program stored in the memory, and execute the methods described in the foregoing aspects.
  • FIG. 1 is a schematic diagram of an IMS architecture
  • FIG. 2 is a schematic architecture diagram of a network system provided by the present application.
  • FIG. 3 is a schematic architecture diagram of another network system provided by the present application.
  • 4 to 9 are schematic diagrams of a communication method provided by the present application.
  • 10 to 14 are schematic structural diagrams of a communication device provided by the present application.
  • This application provides a communication method, device, and system, which are used to solve the problem that the IMS communication method in the prior art cannot meet the service expansion requirements of a terminal device.
  • FIG. 1 is a schematic diagram of the IMS network framework, including: terminal equipment, proxy-call session control function (P-CSCF) entity, serving-call session control function (S-CSCF) An entity, a home subscriber server (HSS), and an application server (AS).
  • P-CSCF proxy-call session control function
  • S-CSCF serving-call session control function
  • HSS home subscriber server
  • AS application server
  • the terminal device is configured to generate a registration request and send the generated registration request to a P-CSCF entity in the IMS; and receive registration response information returned from the IMS system.
  • the P-CSCF entity is the first connection point between the access network and the IMS, and is the first contact point of the terminal device in the IMS.
  • the role of the P-CSCF entity in the IMS system is similar to the execution of proxy services. All information, whether from the terminal device or sent to the terminal device, must be forwarded by the P-CSCF entity.
  • the P-CSCF entity is responsible for verifying the request in the IMS, and forwards the verified request to the specified destination, and processes and forwards the response information.
  • the IMS of different networks may have the same P-CSCF entity.
  • the P-CSCF entity is configured to forward a registration request from a terminal device to the S-CSCF entity; and forward registration response information to the terminal device.
  • the S-CSCF entity is a control core of the IMS, and provides session control and registration for a terminal device.
  • the IMS business has involved areas such as autonomous driving, business meetings, and medical treatment.
  • S-CSCF entities used to support different services, such as S-CSCF entities that can provide services such as remote driving, group calling, and remote surgical monitoring.
  • the S-CSCF entity is used to receive the registration request of the terminal device forwarded by the P-CSCF entity; authenticate the terminal device; and after determining that the authentication is passed, obtain the terminal from the HSS through the CX interface of the Diameter protocol Device contract information; the S-CSCF entity is also used to connect to each application server based on the ISC interface, and the S-CSCF entity is also used to trigger the application server to perform operations and route the request message of the terminal device to the corresponding application server .
  • the HSS is a main data storage in the IMS that stores all data related to users and services.
  • the data stored in the HSS mainly includes user identity, contract information, access information, and so on.
  • the AS is located in a user's home network or a third-party location.
  • the third-party location refers to a network or an independent application server.
  • the main functions of the AS include: processing a request message sent from the S-CSCF entity; and sending a processed request message to the S-CSCF entity.
  • the IMS may further include an interrogating-call session control function (I-CSCF) entity, and the I-CSCF entity may connect the S-CSCF entity and the P-CSCF entity.
  • I-CSCF interrogating-call session control function
  • -A CSCF entity which is used to provide users with access to the home network; when a terminal device roams to other networks, it sends a message to the P-CSCF entity, and the P-CSCF entity can forward messages from the terminal device to all
  • the I-CSCF entity sends a message from a terminal device to the S-CSCF entity through the I-CSCF entity; specifically, the I-CSCF entity can query the terminal device for the corresponding response through the HSS in the IMS.
  • the S-CSCF entity's address information and then forward the message from the terminal device to the corresponding S-CSCF entity.
  • the terminal equipment in this application also known as user equipment (UE), can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as a ship, etc.); it can also be Deployed in the air (such as aircraft, balloons, satellites, etc.).
  • the terminal device may be a mobile phone, a tablet, a computer with a wireless transceiver function, a virtual reality (VR) device, an augmented reality (AR) device, or an industrial control device. ), Wireless devices in self-driving, wireless devices in remote medical, wireless devices in smart grid, wireless devices in transportation safety , Wireless devices in smart cities, wireless devices in smart homes, and so on.
  • the P-CSCF entity When the terminal device initiates a registration request to the IMS system, the P-CSCF entity will receive a registration request from the terminal device carrying the terminal device, the registration request including the identity of the terminal device, and the P-CSCF The entity forwards the registration request to the I-CSCF entity, the I-CSCF entity sends a user authorization request (UAR) to the HSS, and the UAR is used to request the first S-CSCF entity Address information, wherein the UAR carries the identity of the terminal device, and the first S-CSCF entity is an S-CSCF entity in the IMS that the terminal device needs to register, and is used to register the terminal device In the IMS, after receiving the UAR, the HSS sends a user authorization response (UAA) to the I-CSCF entity, and the UAA carries the identity of the first S-CSCF entity.
  • UAA user authorization response
  • the I-CSCF After receiving the UAA, the I-CSCF sends the registration request to the first S-CSCF entity according to the address information of the first S-CSCF entity, and the first S-CSCF entity according to the The registration request authenticates the terminal device. After the authentication is passed, a server assignment request (SAR) message is sent to the HSS.
  • SAR server assignment request
  • the HSS After receiving the SAR message, the HSS sends the SAR message to the first An S-CSCF entity feedbacks a SAA message, and the server assignment response (SAA) message includes subscription information of the terminal device, and the first S-CSCF entity obtains the SAA message after receiving the SAA message
  • the contract information of the terminal device, and then the first S-CSCF entity sends a 200OK message to the P-CSCF entity through the I-CSCF entity, and the 200OK message includes a service route of the terminal device ( service routing information, the service routing information is used to indicate the address information of the first S-CSCF entity, so that the P-CSCF entity, after receiving a call request carrying the terminal device, Service routing letter , The call request is forwarded to the first S-CSCF entity.
  • the P-CSCF entity After receiving the 200OK message, the P-CSCF entity deletes the service routing information in the 200OK message, and sends the 200OK message with the service routing information deleted to the terminal device. So far, the terminal device has registered with the IMS and established a connection with the IMS.
  • the P-CSCF entity locally stores only the address information of the first S-CSCF entity. If the terminal device needs to perform service expansion, it needs to communicate with other S-CSCF entities. The P-CSCF entity only stores the address information of the first S-CSCF entity locally and cannot send messages of the terminal device to other S-CSCF entities, making the terminal device unable to perform service expansion.
  • the IMS communication solution does not support service expansion.
  • an embodiment of the present application provides a communication method to solve a problem that an existing IMS communication method in the prior art cannot meet a service expansion requirement of a terminal device.
  • FIG. 2 is a schematic structural diagram of a network system applied in an embodiment of this application, including: an access processing entity and a registration processing entity.
  • the optional network system may further include a server, a service processing entity, and an inquiry. Processing entity.
  • the network system may further include a terminal device.
  • the number of service processing entities is not limited. That is, the terminal device may communicate with the registration processing entity, or may communicate with one or more The business processing entity communicates.
  • the terminal device may send a registration request to the registration processing entity, and may also receive a registration response message from the registration processing entity. After the registration is successful, the terminal device may actively initiate a call process to the registration processing entity. The access processing entity initiates a call request.
  • the access processing entity is the first point of contact between the terminal device and the network system.
  • the access processing entity may forward a registration request from the terminal device to the registration.
  • the processing entity may also receive a registration response message from the registration processing entity, and save the address information of the registration processing entity in the registration response message, and may also save the address information of the business processing entity and the service.
  • the corresponding relationship of the identifiers may also be sent to the terminal device to delete the registration information of the registration processing entity in the registration response message and the registration of the address information of the service processing entity corresponding to the terminal device service identifier. Reply message.
  • the access processing entity may receive a call request from the terminal device, and forward the call request to a corresponding service according to a service identifier carried in the call request.
  • the processing entity may also forward the call request to the registration processing entity.
  • the access processing entity may be a P-CSCF entity in the IMS, or may be another entity, which is not limited in the embodiment of the present application. Any method that can execute the access processing entity is applicable to Examples of this application.
  • the registration processing entity is an entity that provides a registration service for the terminal device in the network, and may receive a registration request from the terminal device, and may also authenticate the terminal device according to the registration request from the terminal device. After authentication, you can perform some or all of the following two operations:
  • the registration processing entity may determine address information of the service processing entity according to a service identifier of the terminal device, and notify the access processing entity of the address information of the service processing entity.
  • the registration processing entity may send a request message (corresponding to the first request message in the embodiment of the present application) for requesting the address information of the business processing entity to the inquiry processing entity, and may also The query processing entity obtains a response message (in the embodiment of the present application, corresponding to the first response message) carrying the address information of the service processing entity.
  • the registration processing entity further sends address information of the service processing entity and a service identifier of the terminal device to the server.
  • the registration processing entity may also receive a call request from the terminal device and execute an existing call flow.
  • the service processing entity is an entity in the network that can provide corresponding services for the terminal device, and different service processing entities can provide corresponding services for the terminal device.
  • the service processing entity It may correspond to the service identifier of the terminal device, and the corresponding service processing entity and the address information of the service processing entity may be determined through the service identifier of the terminal device.
  • the service processing entity may receive a notification message from the registration processing entity, and obtain subscription information of the terminal device from the server in advance. After receiving the call request of the terminal device forwarded by the access registration entity, the subscription information of the terminal device may also be obtained from the server; the service processing entity may also obtain the access of the terminal device.
  • Information, the manner in which the service processing entity obtains the access information of the terminal device is the same as the manner in which the contract information of the terminal device is obtained, and details are not described herein again.
  • the registration processing entity may also provide corresponding services for the terminal device, and the registration processing entity may also correspond to one or more service identities of the terminal device.
  • the query processing entity may provide an address query service of a service processing entity, and the query processing entity may query the address information of the service processing entity according to the service identifier of the terminal device, and The address information informs the registration processing entity.
  • the inquiry processing entity may also send a call request to the service processing entity after acquiring the address information of the service processing entity.
  • the query processing entity may be an I-CSCF entity in the IMS, or an entity capable of querying the address information of the service processing entity by other entities, such as an S-CSCF entity in the IMS,
  • the embodiments of the present application are not limited, and any method that can execute the query processing entity is applicable to the embodiments of the present application.
  • the registration processing entity or the service processing entity may be an S-CSCF entity in the IMS.
  • the registration processing entity is the first S-CSCF entity; the service processing The entity is a second S-CSCF entity.
  • the server is a memory for storing contract information and service-related data of the terminal device (for example, access information of the terminal device), and may further store the service corresponding to the service identifier of the terminal device. Address information of the processing entity, and address information of the registration processing entity.
  • the server may be an HSS.
  • FIG. 3 is a schematic diagram of another network system applicable to the embodiment of the present application, which includes a P-CSCF entity and a first S-CSCF entity.
  • the network system may further include a UE, an I-CSCF entity, HSS and a second S-CSCF entity, wherein the P-CSCF entity corresponds to the access processing entity shown in FIG. 2, and the first S-CSCF entity corresponds to the registration processing shown in FIG. 2 Entity, the second S-CSCF entity corresponds to the service processing entity shown in FIG. 2, the HSS corresponds to the server shown in FIG. 2, and functions of each entity shown in FIG. 3 are shown in FIG. The relevant descriptions shown in Figures 1 to 2 are not repeated here.
  • FIG. 3 although only one second S-CSCF entity is shown, the embodiment of the present application does not limit the number of the second S-CSCF entities, and only uses one second S-CSCF entity as an example for description.
  • the embodiments of the present application provide an IMS communication method, which involves three aspects, which are:
  • Registration process in the registration process, the registration processing entity determines the address information of the business processing entity corresponding to the service identification according to the service identification of the terminal device, and the registration processing entity may also feedback to the access processing entity
  • the registration response message, and the registration response message may carry address information of the service processing entity, and the access processing entity may save the address information of the service processing entity.
  • the access processing entity may save the correspondence between the service identifier and the address information of the service processing entity when saving the address information of the service processing entity. relationship.
  • the access processing entity can save not only the address information of the registration processing entity, but also the address information of the service processing entity corresponding to the service identifier, so that the terminal device can communicate with all
  • the registration processing entity is associated or may be associated with the service processing entity, which provides a possibility for service expansion of the terminal device and also ensures that the terminal device can perform service expansion in the future.
  • the terminal device may send a call request carrying the service ID to the access processing entity, and the access processing entity may be based on the stored service ID And the correspondence between the address information of the service processing entity, determining the address information of the service processing entity, and forwarding the call request to the service processing entity according to the address information of the service processing entity.
  • the access processing entity can forward the call request to the corresponding service processing entity based on the service identifier carried in the call request, so that the terminal device needs services During service, it can be connected with the business processing entity, and the business processing entity can provide business services to the terminal device, which can realize the service expansion of the terminal device.
  • the inquiry processing entity may determine the corresponding service identifier according to the service identifier. Address information of a service processing entity, and forwarding the call request to the service processing entity according to the address information of the service processing entity.
  • the inquiry processing entity can determine the address information of the service processing entity based on the service identifier carried in the call request, and then forward the call request to the corresponding service
  • the processing entity enables the terminal device to connect with the service processing entity and obtains other service services provided by the service processing entity. Further, it can ensure that the service of the terminal device can be effectively expanded.
  • the following uses the network framework shown in FIG. 3 as an example to introduce the three aspects involved in the communication method provided in the embodiment of the present application.
  • the embodiment of the present application can also be applied to the network system shown in FIG. 2. Because the principles are similar, the network system shown in FIG. 3 is used as an example for illustration.
  • FIG. 4 it is a communication method provided by the embodiment of the application.
  • the P-CSCF entity After receiving the registration request of the UE, the P-CSCF entity forwards the registration request of the UE to the first S-CSCF, that is, the first S-CSCF entity passes the P-CSCF The CSCF entity receives a registration request from the UE.
  • the first S-CSCF entity may authenticate the UE according to the registration request of the UE.
  • the registration request of the UE may include part or all of the following information:
  • the identifier of the UE, the authentication information, and the service identifier of the UE are identifiers of the UE, the authentication information, and the service identifier of the UE.
  • the identifier of the UE may be an IP multimedia private identity (IMPI) or other identifiers, which is not limited in the embodiment of the present application. Any information that can identify the UE can be used as the identifier of the UE. .
  • IP multimedia private identity IMPI
  • Any information that can identify the UE can be used as the identifier of the UE. .
  • the service identifier is information used to identify the service of the UE. Different services have different service identifiers.
  • the service identifier may be an IP multimedia subsystem communication service identifier (ICSI) or IP multimedia.
  • ICSI IP multimedia subsystem communication service identifier
  • IARI applications can also define new service identifiers.
  • the service identifiers of all the services of the UE can be carried, or the service identifiers of some services can be carried, such as If the services of the UE need to be activated and used during subsequent use of the UE, the service identities of all services of the UE may be carried in the registration request; if the services of the UE are only If some services need to be activated, the service identifiers of some services of the UE may be carried in the registration request, and the number of the service identifiers carried in the registration request may be set according to specific scenarios. Not limited.
  • the first S-CSCF entity determines, according to the service identifier, address information of the second S-CSCF entity corresponding to the service identifier.
  • the first S-CSCF entity may determine the address information of the second S-CSCF entity according to the service identifier.
  • the first S-CSCF entity may locally store the second S-CSCF entity in advance. -The address information of the CSCF entity and the corresponding service identifier, and the first S-CSCF entity may determine the address information of the second S-CSCF entity according to the locally saved information.
  • the first S-CSCF entity may directly send a request message for requesting the address information of the second S-CSCF entity to the server, and the request message sent to the server carries the service identifier.
  • the first S-CSCF entity may also determine address information of the second S-CSCF entity through other S-CSCF entities.
  • the first S-CSCF entity may also determine the address information of the second S-CSCF entity through the I-CSCF entity.
  • the specific process is as follows:
  • the first S-CSCF entity sends a first request message to the I-CSCF entity, and the first request message is used to request address information of a second S-CSCF entity, where the first request message
  • the service identifier is included.
  • the first S-CSCF entity passes the authentication to the UE, the first S-CSCF entity can complete registration for the UE, because the service of the UE may need to be removed from the first S-CSCF Provided by the second S-CSCF entity outside the entity, the first S-CSCF entity needs to determine a second S-CSCF entity corresponding to the service identifier.
  • the first S-CSCF entity may send the first request message to the I-CSCF entity to obtain the address of the second S-CSCF entity. information.
  • the service identifier needs to be carried in the first request message, and the number of the service identifiers carried in the first request message can be set according to a specific scenario, which is not limited in the embodiment of the present application.
  • the I-CSCF entity determines address information of the second S-CSCF entity according to the service identifier.
  • the I-CSCF entity may locally store address information of the S-CSCF entity and a service identifier of a service that each S-CSCF entity can provide.
  • the I-CSCF entity receives After the first request message, the address information of the S-CSCF entity stored locally and the service identifier of the service that each S-CSCF entity can provide can be traversed according to the service identifier, and the S-CSCF of the corresponding service will be able to be provided
  • the entity serves as the second S-CSCF entity.
  • the I-CSCF entity may choose one as the second S-CSCF entity, or all S-CSCF entities capable of providing corresponding services may be As the second S-CSCF entity, that is, there may be a plurality of the second S-CSCF entities.
  • the I-CSCF entity may send a response message to the first S-CSCF entity, informing the first S-CSCF entity that the second S- Address message of the CSCF entity.
  • the address information of the S-CSCF entity and the service identifier of the service that each S-CSCF entity can provide may also be stored on other devices, such as the HSS and the I-CSCF.
  • the entity may obtain the address information of the S-CSCF entity and the service identifier of the service provided by each S-CSCF entity from the other device, and then traverse according to the service identifier.
  • the address information of the S-CSCF entity and the service identifier of a service that each S-CSCF entity can provide, and the S-CSCF entity capable of providing a corresponding service is used as the second S-CSCF entity.
  • the I-CSCF entity may also send a query request carrying the service identifier to the other device to query an S-CSCF entity capable of providing a corresponding service.
  • the I-CSCF entity may send a first query request to the HSS, where the first query request carries the service identifier.
  • the HSS After receiving the first query request, the HSS determines an address message of the second S-CSCF entity according to the service identifier.
  • the HSS may select one as the second S-CSCF entity, or may assign all the corresponding S-CSCF entities to the service identifier.
  • the S-CSCF entities all serve as the second S-CSCF entity.
  • the HSS may send a first query response to the I-CSCF entity, and the first query response includes one or more of the
  • the address information of the second S-CSCF entity may also include the service identifier in the first query response, and there is a correspondence relationship between the address information of the second S-CSCF entity and the service identifier.
  • the HSS may send a query failure response message to the I-CSCF entity, informing the I-CSCF entity that the second entity is not found.
  • An address message of the S-CSCF entity, and thereafter, the I-CSCF entity notifies the first S-CSCF entity that the address message of the second S-CSCF entity is not found.
  • the first S-CSCF entity may further send a first message to the HSS, where the first message includes the second S-CSCF The corresponding relationship between the address information and the service identifier.
  • the server may save the correspondence between the address information of the second S-CSCF and the service identifier.
  • the first message may be a message in an existing registration process.
  • the first message may be a server allocation request SAR.
  • the server allocation request carries the address information and address of the second S-CSCF.
  • the service identifier; the first message may also be a newly defined message for sending the address information of the second S-CSCF and the service identifier to the server.
  • the first S-CSCF entity may interact with the HSS as described above, or may interact with the second S-CSCF entity.
  • the first S-CSCF entity When the first S-CSCF entity receives the first response message, the first S-CSCF entity learns the address information of the second S-CSCF entity, and the first S-CSCF entity may be based on The address information of the second S-CSCF entity performs information interaction with the second S-CSCF entity.
  • the first S-CSCF entity may send a notification message to the second S-CSCF entity according to the address information of the second S-CSCF entity, and the notification message is used to notify the second S-CSCF
  • the entity obtains the subscription information of the UE, for example, it may notify the second S-CSCF entity to obtain the subscription information of the UE from the HSS.
  • the second S-CSCF entity may send a server allocation request to the HSS to request subscription information of the UE.
  • the HSS may determine subscription information of the UE, and send a server allocation response message to the second S-CSCF entity, and the second The server allocation response message includes subscription information of the UE.
  • the second server allocation response message may further include access information of the UE.
  • the second S-CSCF entity may obtain the subscription information of the UE from the HSS in advance, so that when the second S-CSCF entity subsequently needs to provide business services to the UE, More efficient.
  • the first S-CSCF entity may send a registration response message to the P-CSCF entity, where the registration response message includes the second S-CSCF entity.
  • the registration response message includes the second S-CSCF entity.
  • the P-CSCF entity receives the registration response message of the first S-CSCF entity, and the P-CSCF entity stores the address information of the second S-CSCF and the corresponding relationship of the service identifier.
  • the registration response message may further include address information of the first S-CSCF entity, and may also include a service identifier corresponding to the first S-CSCF entity, and the P-CSCF entity is receiving the registration. After the response message, the address information of the first S-CSCF entity may also be stored.
  • the address information of the first S-CSCF entity may be used as the default address information of the S-CSCF entity; or the first The address information of an S-CSCF entity and the corresponding service identifier, that is, the correspondence between the address information of the first S-CSCF entity and the service identifier of the corresponding service is saved.
  • the P-CSCF entity when the P-CSCF entity saves the correspondence between the address information of the second S-CSCF entity and the service identifier, it may use the address information of the second S-CSCF and the The service identifier establishes a mapping, and when the UE needs the second S-CSCF entity to provide a service, the UE may determine the address information of the second S-CSCF according to the corresponding relationship, and then send the address information to the second S-CSCF.
  • the CSCF forwards information from the UE, such as a call request, a data request, and so on.
  • a communication method provided by an embodiment of the application includes:
  • the first S-CSCF entity authenticates the UE according to a registration request from the UE.
  • the first S-CSCF entity uses the address information of the first S-CSCF entity as the default S-CSCF entity address information, and the first S-CSCF entity according to the service carried in the registration request
  • the ID determines a service identification (ID) of a service of the UE that is not supported by the first S-CSCF entity (for convenience of description, a service of the service of the UE that is not supported by the first S-CSCF entity is The ID is referred to as the service ID of the UE).
  • the first S-CSCF entity sends a first request message to the I-CSCF entity, the first request message carries a service ID of the UE, and the first request message is used to request a service that can support a service.
  • Second S-CSCF address information The first S-CSCF entity sends a first request message to the I-CSCF entity, the first request message carries a service ID of the UE, and the first request message is used to request a service that can support a service.
  • Second S-CSCF address information Second S-CSCF address information.
  • the I-CSCF entity After the I-CSCF entity receives the first request message, the I-CSCF entity allocates the address information of the second S-CSCF entity to the first S- The CSCF entity sends the first response message, and the first response message carries address information of the second S-CSCF entity corresponding to the service ID of each UE.
  • the first S-CSCF entity After receiving the first response message, the first S-CSCF entity sends a SAR to the HSS, where the SAR carries the address information of the second S-CSCF and the corresponding service ID, and The access information of the UE.
  • the access information of the UE includes path information and contact information, where the path information is used to indicate address information of the P-CSCF entity, and the contact information is used to indicate that the P-CSCF Information of an entity routing to the UE, and access information of the UE is determined by the P-CSCF entity.
  • the HSS After receiving the SAR, the HSS stores the address information of the second S-CSCF and the corresponding service ID, stores the access information of the UE, and sends the information to the first S-CSCF entity.
  • SAA where the SAA includes subscription information of the UE.
  • the first S-CSCF entity sends a 200OK message to the P-CSCF entity, and the 200OK message carries multiple service routes, which include instructions for instructing the first S-CSCF entity
  • the service route of the address information further includes a service route for indicating the address information of the second S-CSCF entity.
  • the service for indicating the address information of the first S-CSCF entity may not include a service ID corresponding to the first S-CSCF entity, or may include a service corresponding to the first S-CSCF entity. ID; the service route used to indicate the address information of the second S-CSCF entity may further include a service ID corresponding to the second S-CSCF entity.
  • the first S-CSCF entity notifies the second S-CSCF entity to obtain related information of the UE, such as subscription information of the UE and access information of the UE, from the HSS.
  • the P-CSCF entity After receiving the 200 OK, the P-CSCF entity stores a service route indicating the address information of the first S-CSCF and a service route indicating the address information of the second S-CSCF.
  • the P-CSCF entity sends a 200 OK message to the UE with each service route deleted.
  • a communication method provided by an embodiment of the application includes:
  • the P-CSCF entity receives a call request from the UE, and the call request includes the service identifier.
  • the UE When the UE needs to obtain service support, such as the UE needs to make a voice call, the UE needs to implement remote driving, etc., the UE will send a call request to the P-CSCF entity.
  • the call request includes the service identifier, and may further include an identifier of the UE.
  • the P-CSCF entity determines the address information of the second S-CSCF entity according to the service identifier and the saved correspondence.
  • the P-CSCF entity stores the address information of the first S-CSCF entity and the address information of the second S-CSCF entity, both are stored in a manner corresponding to the service identifier, that is, That is, the P-CSCF entity stores the address information of the first S-CSCF entity and the identifier of the UE corresponding to the address information of the first S-CSCF entity, and the second S-CSCF entity The address information of the UE and the identifier of the UE corresponding to the address information of the second S-CSCF entity.
  • the P-CSCF entity may traverse the stored correspondence relationship according to the service identifier, and when the same service identifier is traversed, the corresponding address of the first S-CSCF entity may be determined Information or address information of the second S-CSCF entity; when the same service identifier is not traversed, the P-CSCF entity may send a call failure message to the UE.
  • the P-CSCF entity stores the address information of the first S-CSCF entity, it uses the address information of the first S-CSCF entity as the default address information of the S-CSCF entity, and may not store all When the service identifier corresponding to the address information of the first S-CSCF entity is stored; when the P-CSCF entity stores the correspondence between the address information of the second S-CSCF entity and the service identifier, the P-CSCF entity The stored service identifier may be traversed according to the service identifier. When the same service identifier is traversed, the address information of the corresponding second S-CSCF entity may be determined, and then step 603 is performed.
  • the P-CSCF entity selects the address information of the first S-CSCF entity, and sends the address information to the first S-CSCF entity according to the address information of the first S-CSCF entity; -The CSCF entity sends the call request.
  • the P-CSCF entity sends the call request to the second S-CSCF entity according to the address information of the second S-CSCF entity.
  • the second S-CSCF entity After receiving the call request, the second S-CSCF entity sends a server allocation request to the HSS after determining that the subscription information of the UE is not stored, and the server allocation request is used to request the UE's subscription information .
  • the second S-CSCF entity After receiving the call request, the second S-CSCF entity first determines whether the second S-CSCF entity has stored the subscription information of the UE; since during the registration process of the UE, if the first An S-CSCF entity notifies the second S-CSCF entity to obtain the subscription information of the UE from the HSS, and the second S-CSCF entity obtains the subscription information of the UE from the HSS in advance. If the second S-CSCF entity has stored the subscription information of the UE, the second S-CSCF entity continues to work according to the existing calling procedure; if the second S-CSCF entity does not store the UE's Subscription information, the second S-CSCF entity needs to obtain subscription information of the UE from the HSS.
  • the second S-CSCF entity sends a server allocation request to the HSS, where the server allocation request is used to request subscription information of the UE, and the server allocation request may also be used to request the UE's Access information.
  • the server allocation request may carry the identity of the UE.
  • the HSS After the HSS receives the server allocation request from the second S-CSCF entity, the HSS sends a server allocation response message to the second S-CSCF entity, and the server allocation response message includes the UE's Signing information.
  • the HSS may determine subscription information of the UE according to the identifier of the UE carried in the server allocation request, and then send the UE carrying the UE to the second S-CSCF entity.
  • the server assigns a response message to the subscription information.
  • the server allocation response message may further include access information of the UE.
  • the following uses the communication method shown in FIG. 6 in a specific scenario to further introduce the IMS communication method provided in the embodiment of the present application.
  • a communication method provided by an embodiment of the application includes:
  • the UE sends a call request to the P-CSCF entity, and the call request carries an identifier of the UE and a service ID of the UE.
  • the P-CSCF entity determines whether a service route including a service ID carrying the same UE is stored, and if it exists, the P-CSCF entity according to the second S-CSCF entity indicated in the service route And forward the call request to the second S-CSCF entity.
  • the P-CSCF entity determines that there is no service route including the same service ID of the UE. If it does not exist, the P-CSCF entity according to the first S-CSCF indicated in the default service route The address information of the entity forwards the call request to the first S-CSCF entity. After receiving the call request, the first S-CSCF entity continues to perform the calling process according to the existing calling process. .
  • the second S-CSCF entity After receiving the call request, the second S-CSCF entity sends a SAR to the HSS after determining that the subscription information of the UE is not stored, and the SAR is used to request to obtain the UE's Signing information.
  • the HSS sends an SAA to the second S-CSCF entity, and the SAA carries subscription information of the UE.
  • the second S-CSCF entity receives the SAA and continues to execute the calling process according to the existing calling process.
  • a communication method provided by an embodiment of the application includes:
  • the I-CSCF entity receives a call request, and the call request includes the service identifier.
  • the I-CSCF entity When other devices need to establish a connection with the UE through the IMS, the I-CSCF entity will receive the call request, that is, the call request in the called process, and the call request may be another network system Sent by a device in the device, for example, a device in a public switched telephone network (PSTN) can be sent to the I-CSCF entity through a media gateway controller (MGC); or it can be When a device in the IP network needs to call a device registered to the IMS, it can be sent to the I-CSCF entity through interconnection border control functions (IBCF); the device registered in the same IMS When the device makes an intra-network call, it can directly send a call request to the I-CSCF entity.
  • PSTN public switched telephone network
  • MSC media gateway controller
  • IBCF interconnection border control functions
  • the call request further includes an identity of the UE.
  • the I-CSCF entity determines, according to the service identifier, address information of a second S-CSCF entity corresponding to the service identifier.
  • the I-CSCF entity determines the address information of the second S-CSCF entity according to the service identifier, refer to S402.
  • the first S-CSCF entity determines the second S-CSCF entity through the I-CSCF entity.
  • the I-CSCF entity determines the related description of the address information of the second S-CSCF entity, and details are not described herein again.
  • the registration request may include service identifiers of all services that the UE needs to activate, and the The address information of the second S-CSCF entity is the address information of the second S-CSCF entity corresponding to each service identifier.
  • the service identifier in the call request may be a specific one of them.
  • One or more service identifiers, and the address information of the second S-CSCF entity that needs to be determined is the address of the second S-CSCF entity corresponding to each service identifier in the specific one or more service identifiers information.
  • the I-CSCF entity After determining the address information of the second S-CSCF entity, the I-CSCF entity sends the call request to the second S-CSCF entity according to the address information of the second S-CSCF entity.
  • a communication method provided by an embodiment of the application includes:
  • the I-CSCF entity receives a call request, and the call request carries a service ID of the UE.
  • the I-CSCF entity After receiving the call request, the I-CSCF entity sends a LIR to the HSS for querying address information of a second S-CSCF entity corresponding to the service ID of the UE, where the location A query request (location information request, LIR) carries the service ID of the UE.
  • location A query request location information request, LIR
  • the HSS After receiving the LIR, the HSS determines whether there is second S-CSCF entity address information corresponding to the UE's service ID according to the service ID of the UE, and if it exists, sends it to the I-CSCF entity Send a location query response (location info answer, LIA), where the LIA carries the second S-CSCF entity address information corresponding to the service ID of the UE. If it does not exist, the LIA carries address information related to the first S-CSCF entity.
  • location info answer LIA
  • S904A After the I-CSCF entity receives the LIA, if the LIA carries the second S-CSCF entity address information corresponding to the service ID of the UE, the I-CSCF entity sends the first S-CSCF entity to the first Two S-CSCF entities send the call request.
  • S904B If the LIA carries the address information of the first S-CSCF entity, the I-CSCF entity sends the call request to the first S-CSCF entity, and the first S-CSCF entity is receiving After the call request, the called process is continued according to the existing called process.
  • step S905 Same as step S703.
  • step S906 Same as step S704.
  • the second S-CSCF entity receives the SAA, and continues to execute the called process according to the existing called process.
  • an embodiment of the present application further provides a communication device for performing the method performed by the registration processing entity in the foregoing method embodiment.
  • the device includes a receiving unit 1001, a processing unit 1002, and a sending unit 1003;
  • the receiving unit 1001 is configured to receive a registration request from a terminal device through an access processing entity, where the registration request includes a service identifier of the terminal device;
  • the processing unit 1002 is configured to determine address information of a service processing entity corresponding to the service identifier according to the service identifier.
  • the sending unit 1003 is configured to send a registration response request to an access processing entity, where the registration response request includes address information of the service processing entity and the service identifier.
  • the processing unit 1002 may determine the address information of the business processing entity according to the service identifier based on the locally saved information.
  • Information where the locally stored information includes a correspondence between a service identifier and address information of a service processing entity.
  • the processing unit 1002 may also determine address information of the service processing entity by other methods. For example, when the processing unit 1002 determines the address information of the service processing entity according to the service identifier, the sending unit 1003 may first send a first request message to the query processing entity, and the first request message is Requesting the address information of a service processing entity, wherein the first request message includes the service identifier, after which the receiving unit 1001 may receive a first response message from the query processing entity, the first A response message includes address information of the business processing entity; the processing unit 1002 may determine the address information of the business processing entity according to the first response message.
  • the sending unit 1003 may first send a first request message to the query processing entity, and the first request message is Requesting the address information of a service processing entity, wherein the first request message includes the service identifier, after which the receiving unit 1001 may receive a first response message from the query processing entity, the first A response message includes address information of the business processing entity; the processing unit 1002 may determine the address information of the business processing entity according
  • the sending unit 1003 may further send a notification to the service processing entity.
  • a message the notification message is used to notify the service processing entity to obtain subscription information of the terminal device.
  • the sending unit 1003 may also send a first message to the server, where the first message Including the correspondence between the address information of the service processing entity and the service identifier.
  • the embodiment of the present application further provides a communication device for performing the method performed by the access processing entity in the foregoing method embodiment.
  • the device includes a sending unit 1101, a receiving unit 1102, and a processing unit 1103:
  • the sending unit 1101 is configured to forward a registration request of the terminal device to a registration processing entity.
  • the receiving unit 1102 is configured to receive a registration response message from the registration processing entity, where the registration response message includes address information of the service processing entity and the service identifier.
  • the processing unit 1103 is configured to store address information of the service processing entity and the service identifier.
  • the sending unit 1101 may also send to the terminal device a registration response message in which the address information of the service processing entity and the service identifier are deleted.
  • the receiving unit 1102 may further receive a call request from the terminal device, where the call request includes the service identifier; thereafter, since the processing unit 1103 The correspondence relationship may be saved before, and the processing unit 1103 may determine the address information of the service processing entity according to the service identifier of the terminal device in the call request and the correspondence relationship; after determining the service processing entity After the address information of the IP address, the sending unit 1101 may send the call request to the service processing entity according to the address information of the service processing entity.
  • the embodiment of the present application further provides a communication device for performing the method performed by the query processing entity in the foregoing method embodiment.
  • the device includes a receiving unit 1201, a processing unit 1202, and a sending unit 1203:
  • the receiving unit 1201 is configured to receive a first request message from a registration processing entity, where the first request message is used to request address information of a service processing entity, and the first request message includes the service identifier.
  • the processing unit 1202 is configured to determine address information of a service processing entity corresponding to the service identifier according to the service identifier.
  • the sending unit 1203 is configured to send a first response message to the registration processing entity, where the first response message includes address information of the service processing entity.
  • the receiving unit 1201 may further receive a call request, where the call request includes the service identifier; after that, the processing unit 1202 may receive the service identifier according to the service identifier. Determining address information of the service processing entity; the sending unit 1203 may send the call request to the service processing entity according to the address information of the service processing entity.
  • the processing unit 1202 needs to determine the address information of the service processing entity according to the service identifier, and the processing unit 1202 determines the service processing entity's address information according to the service identifier.
  • address information There are many methods for address information.
  • the processing unit 1202 may determine the address information of the service processing entity based on the service identifier based on the locally stored information.
  • the locally saved information includes the service identifier and the address of the service processing entity. Correspondence of information.
  • the processing unit 1202 may also determine address information of the service processing entity by other methods. For example, when the processing unit 1202 determines the address information of the service processing entity according to the service identifier of the terminal device, the sending unit 1203 may send a first query request to the server, where the first query request is used to request all The address information of the service processing entity, wherein the first query request includes the service identifier; thereafter, the receiving unit 1201 may receive a first query response from the server; and the processing unit 1202 may A query response determines address information of the business processing entity.
  • the embodiment of the present application further provides a communication device for performing the method executed by the server in the foregoing method embodiment.
  • the device includes a receiving unit 1301 and a processing unit 1302:
  • the receiving unit 1301 is configured to receive a first message from a registration processing entity, where the first message includes address information of the service processing entity and a correspondence between the service identifier.
  • the processing unit 1302 is configured to save a correspondence between the address information of the service processing entity and the service identifier.
  • the apparatus further includes a sending unit 1303.
  • the receiving unit 1301 may receive a first query request from an inquiry processing entity, where the first query request includes the service identifier; after that, the processing unit 1302 may perform the corresponding relationship according to the service identifier and the saved relationship. Determining the address information of the business processing entity; after determining the address information of the business processing entity, the sending unit 1303 may send a first query response to the query processing entity, where the first query response includes all Address information of the business processing entity.
  • the division of units in the embodiments of the present application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
  • the functional units in the embodiments of the present application may be integrated into one process. In the device, it may also exist alone physically, or two or more units may be integrated into one module.
  • the above integrated unit may be implemented in the form of hardware or in the form of software functional modules.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially a part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium. It includes several instructions to make a terminal device (which may be a personal computer, a mobile phone, or a network device) or a processor execute all or part of the steps of the method in each embodiment of the present application.
  • the aforementioned storage media include: U disks, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks or compact discs and other media that can store program codes .
  • the access processing entity, the registration processing entity, the server, and the inquiry processing entity may be presented in the form of dividing each functional module in an integrated manner.
  • the "module” herein may refer to a specific ASIC, a circuit, a processor and a memory executing one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions.
  • the access processing entity, the registration processing entity, the query processing entity, and the server may all adopt the form shown in FIG. 14.
  • the communication device 1400 shown in FIG. 14 includes at least one processor 1401, a memory 1402, and optionally, a communication interface 1403.
  • the memory 1402 may be a volatile memory, such as a random access memory; the memory may also be a non-volatile memory, such as a read-only memory, a flash memory, a hard disk drive (HDD), or a solid-state drive (solid-state drive, SSD), or memory 1402 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this.
  • the memory 1402 may be a combination of the aforementioned memories.
  • a specific connection medium between the processor 1401 and the memory 1402 is not limited in the embodiment of the present application.
  • the memory 1402 and the processor 1401 are connected by a bus 1404 in the figure.
  • the bus 1404 is indicated by a thick line in the figure.
  • the connection modes of other components are only for illustrative purposes and are not cited. Limited.
  • the bus 1404 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only a thick line is used in FIG. 14, but it does not mean that there is only one bus or one type of bus.
  • the processor 1401 may have a data transmitting and receiving function, and can communicate with other devices.
  • an independent data transmitting and receiving module such as a communication interface 1403, may be provided for transmitting and receiving data.
  • the processor 1401 is performing communication with other devices. During communication, data can be transmitted through the communication interface 1403.
  • the processor 1401 in FIG. 14 may call a computer to execute instructions stored in the memory 1402, so that the registration processing entity may execute any one of the foregoing method embodiments. Registers the methods executed by the processing entity.
  • the functions / implementation processes of the sending unit, the receiving unit, and the processing unit in FIG. 10 may be implemented by the processor 1401 in FIG. 14 calling a computer execution instruction stored in the memory 1402.
  • the function / implementation process of the processing unit in FIG. 7 may be implemented by the processor 1401 in FIG. 14 calling a computer execution instruction stored in the memory 1402
  • the function / implementation process of the sending unit and the receiving unit in FIG. 10 may be implemented by The communication interface 1403 in FIG. 14 is implemented.
  • the processor 1401 in FIG. 14 may call a computer stored in the memory 1402 to execute instructions, so that the access processing entity can execute any of the foregoing method embodiments. The method executed by the access processing entity.
  • the functions / implementation processes of the sending unit, the receiving unit, and the processing unit in FIG. 11 may be implemented by the processor 1401 in FIG. 14 calling a computer execution instruction stored in the memory 1402.
  • the function / implementation process of the processing unit in FIG. 6 may be implemented by the processor 1401 in FIG. 14 calling a computer execution instruction stored in the memory 1402
  • the function / implementation process of the sending unit and the receiving unit in FIG. 11 may be implemented by The communication interface 1403 in FIG. 14 is implemented.
  • the processor 1401 in FIG. 14 may call a computer stored in the memory 1402 to execute instructions, so that the inquiry processing entity may execute any one of the foregoing method embodiments.
  • the function / implementation process of the sending unit, the receiving unit, and the processing unit in FIG. 12 may be implemented by the processor 1401 in FIG. 14 calling a computer execution instruction stored in the memory 1402.
  • the function / implementation process of the processing unit in FIG. 6 may be implemented by the processor 1401 in FIG. 14 calling a computer execution instruction stored in the memory 1402
  • the function / implementation process of the sending unit and the receiving unit in FIG. 12 may be implemented by The communication interface 1403 in FIG. 14 is implemented.
  • the processor 1401 in FIG. 14 may call a computer stored in the memory 1402 to execute instructions, so that the server may execute the method performed by the server in any of the foregoing method embodiments. .
  • the function / implementation process of the receiving unit, the sending unit, and the processing unit in FIG. 13 may be implemented by the processor 1401 in FIG. 14 calling a computer execution instruction stored in the memory 1402.
  • the function / implementation process of the processing unit in FIG. 8 may be implemented by the processor 1401 in FIG. 14 calling a computer execution instruction stored in the memory 1402
  • the function / implementation process of the receiving unit and the sending unit in FIG. 13 may be It is implemented by the communication interface 1403 in FIG. 14.
  • the embodiment of the present application further provides a communication system for performing the method of any of the foregoing embodiments.
  • a communication system for performing the method of any of the foregoing embodiments.
  • the communication system includes a registration processing entity and an access processing entity.
  • the registration processing entity is configured to receive a registration request from a terminal device through an access processing entity, where the registration request includes a service identifier of the terminal device, and determine that the service identifier corresponds to the service identifier of the terminal device.
  • the address information of the service processing entity and sending a registration response request to the access processing entity, where the registration response request includes the address information of the business processing entity and the service identifier;
  • the access processing entity is configured to, after the registration processing entity forwards the registration request of the terminal device, receive the registration response message and save the correspondence between the address information of the business processing entity and the service identifier.
  • the communication system further includes an inquiry processing entity.
  • the registration processing entity may send a first request message to the query processing entity, where the first request message is used to request a service The address information of the processing entity, where the first request message includes the service identifier.
  • the inquiry processing entity receives the first request message; and may determine address information of a service processing entity corresponding to the service identifier according to the service identifier; and then sends a first response message to the registration processing entity.
  • the first response message includes address information of the service processing entity.
  • the registration processing entity receives the first response message, and after receiving the first response message, determines the address information of the service processing entity according to the first response message.
  • the communication system further includes a server.
  • the registration processing entity may notify the server to save the correspondence between the address information of the business processing entity and the service identifier.
  • the registration processing entity may send a first message to the server, where the first message includes a correspondence between the address information of the service processing entity and the service identifier; the server receives the first message And after receiving the first message, saving the correspondence between the address information of the service processing entity and the service identifier.
  • the registration processing entity may further send a notification message to the service processing entity, and the notification message is used to notify the service processing entity to obtain subscription information of the terminal device.
  • the access processing entity may receive a call request from the terminal device, where the call request includes the service identifier, and may determine the service identifier according to the service identifier and the saved correspondence relationship. The address information of the service processing entity; and then, sending the call request to the service processing entity according to the address information of the service processing entity.
  • the inquiry processing entity may further receive a call request, the call request includes the service identifier, and may determine address information of a service processing entity corresponding to the service identifier according to the service identifier; thereafter And sending the call request to the service processing entity according to the address information of the service processing entity.
  • the query processing entity may further send a first query request to the server, where the first query request is used to request address information of the service processing entity, wherein the first A query request includes the service identifier; after that, the server receives the first query request, determines address information of the service processing entity according to the service identifier, and then sends a first query response to the query processing entity.
  • the first query response includes address information of the service processing entity.
  • the query processing entity receives the first query response; the address information of the business processing entity may be determined according to the first query response, that is, the query processing entity may send the address information to the business processing entity The call request.
  • this application may be provided as a method, a system, or a computer program product. Therefore, this application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, this application may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to work in a particular manner such that the instructions stored in the computer-readable memory produce a manufactured article including an instruction device, the instructions
  • the device implements the functions specified in one or more flowcharts and / or one or more blocks of the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing device, so that a series of steps can be performed on the computer or other programmable device to produce a computer-implemented process, which can be executed on the computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种通信方法、装置及系统，用以解决现有技术中IMS通信方式，不能满足终端设备的业务扩展需求的问题。本申请中，接入处理实体可以向注册处理实体转发终端设备的注册请求；之后注册处理实体在接收到注册请求后，可以根据业务标识确定业务处理实体的地址信息，向接入处理实体发送注册应答消息；注册应答消息中包括业务处理实体的地址信息以及业务标识，接入处理实体接在接收到注册应答消息后，可以保存业务处理实体的地址信息以及业务标识的对应关系，终端设备需要扩展业务时，接入处理实体均可以保存业务处理实体的地址信息以及对应的业务标识，可以使得终端设备的业务扩展成为可能。

Description

一种通信方法、装置及系统
本申请要求于2018年9月30日提交中国国家知识产权局、申请号为201811163212.6，发明名称为“一种通信方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法、装置及系统。
背景技术
IP多媒体子系统(IP multimedia subsystem，IMS)是基于网络协议(internet protocol，IP)网络的一种用于提供多媒体业务的网络系统，通过IMS可以为终端设备提供多种多媒体业务，如语音通话、视频通话等。
IMS中的服务呼叫状态控制功能(serving call session control function，S-CSCF)实体是为所述终端设备提供多媒体服务的核心实体，在现有的IMS通信方式中，一个S-CSCF实体一般只提供一种类型的服务，通常，一个注册到IMS的终端设备只注册到的IMS中的一个S-CSCF实体通信。
目前，由于终端设备涉及的领域增多，终端设备的业务也需要进一步扩展，终端设备的业务已不再局限于基本的语音通话、视频通话等业务，而单单靠IMS中的一个S-CSCF实体，也只能提供特定的一种业务，并不能实现终端设备的其他业务。
综上，现有的IMS通信方式，不能满足终端设备的业务扩展需求。
发明内容
本申请提供一种通信方法、装置及系统，用以解决现有技术中IMS通信方式，不能满足终端设备的业务扩展需求的问题。
第一方面，本申请实施例提供了一种通信方法，所述方法包括：首先，注册处理实体通过接入处理实体接收来自终端设备的注册请求，所述注册请求中包括所述终端设备的业务标识，之后所述注册处理实体可以在根据所述终端设备的注册请求对所述终端设备的鉴权，还可以根据终端设备的业务标识确定所述业务标识对应的业务处理实体的地址信息，其中，所述业务处理实体可以为所述终端设备提供所述业务标识所标识的业务的实体；之后，所述注册处理实体再向接入处理实体发送携带有所述业务处理实体的地址信息和所述业务标识的注册应答请求。
通过上述方法，所述注册处理实体在所述终端设备的注册过程中，可以根据所述业务标识确定所述业务处理实体的地址信息，可以使得当所述终端设备在需要业务扩展时，在注册请求中携带所述终端设备需要扩展的业务的业务标识，之后所述注册处理实体就可以确定出对应的所述业务处理实体的地址信息，进而可以满足所述终端设备业务扩展的要求。
在一种可能的设计中，所述注册处理实体根据所述业务标识确定所述业务处理实体的地址信息的方式有许多，所述注册处理实体可以基于预存的所述业务标识确定所述业务处理实体的地址信息的对应关系，根据所述业务标识确定所述业务处理实体的地址信息，也可以通过其他设备根据所述业务标识确定所述业务处理实体的地址信息，以其他设备为问询处理实 体为例进行说明:
所述注册处理实体可以先向问询处理实体发送第一请求消息，之后，所述注册处理实体接收到来自所述问询处理实体的第一响应消息，其中，所述第一请求消息用于请求业务处理实体的地址信息，所述第一请求消息中包括所述业务标识；所述第一响应消息中包括所述业务处理实体的地址信息，在接收到所述注册处理实体接收所述第一响应消息之后，则可以根据所述第一响应消息确定所述业务处理实体的地址信息。
通过上述方法，可以使得所述注册处理实体灵活的根据所述业务标识确定所述业务处理实体的地址信息，确定所述业务处理实体的地址信息的方式更加多样化，也使得本申请实施例提供的方法能够应用于不同的应用场景。
在一种可能的设计中，所述注册处理实体在根据所述业务标识确定所述业务处理实体的地址信息之后，所述注册处理实体可以向所述业务处理实体发送通知消息，所述通知消息用于通知所述业务处理实体获取所述终端设备的签约信息。
通过上述方法，所述注册处理实体可以通知所述业务处理实体提前获取所述终端设备的签约信息，保证所述终端设备在后续需要所述业务处理实体提供业务时，所述业务处理实体可以更加快速、高效的为所述终端设备提供业务。
在一种可能的设计中，所述注册处理实体在根据所述业务标识确定所述业务处理实体的地址信息之后，还可以通知所述服务器保存所述业务处理实体的地址信息和所述业务标识。具体的，所述注册处理实体可以向服务器发送第一消息，所述第一消息包括所述业务处理实体的地址信息和所述业务标识的对应关系。
通过上述方法，所述注册处理实体可以将所述业务处理实体的地址信息和所述业务标识的对应关系保存至所述服务器，节省了本地的存储空间，且在需要所述业务处理实体的地址信息，也可以较为方便的从所述服务器中获取所述业务处理实体的地址信息。
第二方面，本申请实施例提供了一种通信方法，所述方法包括：首先，接入处理实体可以向注册处理实体转发所述终端设备的注册请求，之后可以接收来自所述注册处理实体的注册应答消息，所述注册应答消息中包括所述业务处理实体的地址信息以及所述业务标识，所述业务处理实体可以为所述终端设备提供所述业务标识所标识的业务的实体；在接收到所述注册应答消息后，所述接入处理实体可以保存所述业务处理实体的地址信息以及所述业务标识的对应关系；也可以向所述终端设备发送删除了所述业务处理实体的地址信息以及所述业务标识的注册应答消息。
通过上述方法，所述接入处理实体可以保存所述业务处理实体的地址信息以及所述业务标识的对应关系，所述终端设备需要扩展业务时，所述接入处理实体均可以保存所述业务处理实体的地址信息以及对应的所述业务标识，可以使得所述终端设备的业务扩展成为可能。
在一种可能的设计中，所述接入处理实体接收来自所述终端设备的呼叫请求，所述呼叫请求包括所述业务标识；之后，所述接入处理实体可以根据所述业务标识和保存的所述对应关系确定所述业务处理实体的地址信息；并在确定了所述业务处理实体的地址信息之后，所述接入处理实体可以根据所述业务处理实体的地址信息向所述业务处理实体发送所述呼叫请求。
通过上述方法，所述接入处理实体可以在接收到所述终端设备的呼叫请求后，根据所述业务标识向所述业务处理实体转发所述呼叫请求，使得所述终端设备可以与所述业务处理实体进行通信，进而保证所述终端设备可以获取业务支持。
第三方面，本申请实施例提供了一种通信方法，所述方法包括：首先，问询处理实体可以接收来自注册处理实体的第一请求消息，所述第一请求消息用于请求业务处理实体的地址信息，所述第一请求消息中包括终端设备的业务标识，所述业务处理实体可以为所述终端设备提供所述业务标识所标识的业务的实体；之后，所述问询处理实体再根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息；之后，所述问询处理实体则可以向所述注册处理实体发送第一响应消息，所述第一响应消息中包括所述业务处理实体的地址信息。
通过上述方法，所述问询处理实体在根据所述业务标识确定所述业务处理实体的地址信息后，可以告知所述注册处理实体所述业务处理实体的地址信息，可以使得当所述终端设备在需要业务扩展时，之后所述问询处理实体可以确定出对应的所述业务处理实体的地址信息，进而可以满足所述终端设备业务扩展的要求。
在一种可能的设计中，所述问询处理实体接收到呼叫请求，所述呼叫请求包括所述业务标识；之后，所述问询处理实体可以根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息；所述问询处理实体根据所述业务处理实体的地址信息向所述业务处理实体发送所述呼叫请求。
通过上述方法，所述问询处理实体可以在接收到呼叫请求后，根据所述业务标识向对应的业务处理实体转发所述呼叫请求，使得所述业务处理实体提供相应的业务，进而保证所述终端设备可以获取业务支持。
在一种可能的设计中，所述问询处理实体根据所述业务标识确定所述业务处理实体的地址信息的方式有许多种，例如所述问询处理实体可以在本地保存有的所述业务标识确定所述业务处理实体的地址信息的对应关系，根据所述业务标识确定所述业务处理实体的地址信息，也可以通过其他设备根据所述业务标识确定所述业务处理实体的地址信息，以其他设备为服务器为例进行说明：
所述问询处理实体先向所述服务器发送第一查询请求，所述第一查询请求用于请求所述业务处理实体的地址信息，其中，所述第一查询请求包括所述业务标识；之后，所述问询处理实体可以接收来自所述服务器的第一查询响应，所述问询处理实体可以根据所述第一查询响应确定所述业务处理实体的地址信息。
通过上述方法，可以使得所述业务处理实体灵活的根据所述业务标识确定所述业务处理实体的地址信息，所述业务处理实体可以采用不同的方式确定所述业务处理实体的地址信息，也扩展了应用场景。
第四方面，本申请实施例提供了一种通信方法，所述方法包括：首先，服务器可以接收来自注册处理实体的第一消息，所述第一消息包括所述业务处理实体的地址信息以及终端设备的业务标识的对应关系，所述业务处理实体可以为所述终端设备提供所述业务标识所标识的业务的实体；之后，所述服务器保存所述业务处理实体的地址信息和所述业务标识的对应关系。
通过上述方法，所述注册处理实体可以将所述业务处理实体的地址信息和所述业务标识的对应关系保存至所述服务器，在所述注册处理实体或者其他实体需要所述业务处理实体的地址信息，也可以较为方便的从所述服务器中获取所述业务处理实体的地址信息。
在一种可能的设计中，所述服务器在保存了所述业务处理实体的地址信息和所述业务标识之后，所述服务器可以为其他实体提供与所述业务标识对应的所述业务处理实体的地址信息，下面以其他实体为问询处理实体为例进行说明：所述服务器可以接收来自问询处理实体 的第一查询请求，所述第一查询请求包括所述业务标识；之后，所述服务器根据所述业务标识和已保存的所述对应关系确定所述业务处理实体的地址信息；在确定了所述业务处理实体的地址信息之后，所述服务器向所述问询处理实体发送第一查询响应，所述第一查询响应包括所述业务处理实体的地址信息。
通过上述方法，所述服务器在本地保存所述业务处理实体的地址信息和所述业务标识的对应关系的情况下，可以灵活的、方便的为其他实体提供所述业务处理实体的地址信息，所述终端设备的业务可以有对应的所述业务处理实体提供业务，进而可以保证所述终端设备的业务可有效扩展。
第五方面，本申请实施例还提供了一种通信装置，所述通信装置应用于注册处理实体，有益效果可以参见第一方面的描述此处不再赘述。该装置具有实现上述第一方面的方法实例中行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，所述装置的结构中包括接收单元、处理单元和发送单元，这些单元可以执行上述第一方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
第六方面，本申请实施例还提供了一种通信装置，所述通信装置应用于接入处理实体，有益效果可以参见第二方面的描述此处不再赘述。该装置具有实现上述第二方面的方法实例中行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，所述装置的结构中包括接收单元、发送单元以及处理单元，这些单元可以执行上述第二方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
第七方面，本申请实施例还提供了一种通信装置，所述通信装置应用于问询处理实体，有益效果可以参见第三方面的描述此处不再赘述。该装置具有实现上述第三方面的方法实例中行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，所述装置的结构中包括接收单元、处理单元和发送单元，这些单元可以执行上述第三方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
第八方面，本申请实施例还提供了一种通信装置，所述通信装置应用于服务器，有益效果可以参见第四方面的描述此处不再赘述。该装置具有实现上述第四方面的方法实例中行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，所述装置的结构中包括接收单元和处理单元，还可以包括发送单元，这些单元可以执行上述第四方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
第九方面，本申请实施例还提供了一种通信装置，所述通信装置应用于注册处理实体，有益效果可以参见第一方面的描述此处不再赘述。所述通信装置的结构中包括处理器和存储器，所述处理器被配置为支持所述终端执行上述第一方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。所述通信装置的结构中还包括通信接口，用于与其他设备进行通信。
第十方面，本申请实施例还提供了一种通信装置，所述通信装置应用于接入处理实体，有益效果可以参见第二方面的描述此处不再赘述。所述通信装置的结构中包括处理器和存储器，所述处理器被配置为支持所述终端执行上述第二方面方法中相应的功能。所述存储器与 所述处理器耦合，其保存所述通信装置必要的程序指令和数据。所述通信装置的结构中还包括通信接口，用于与其他设备进行通信。
第十一方面，本申请实施例还提供了一种通信装置，所述通信装置应用于问询处理实体，有益效果可以参见第三方面的描述此处不再赘述。所述通信装置的结构中包括处理器和存储器，所述处理器被配置为支持所述终端执行上述第三方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。所述通信装置的结构中还包括通信接口，用于与其他设备进行通信。
第十二方面，本申请实施例还提供了一种通信装置，所述通信装置应用于服务器，有益效果可以参见第四方面的描述此处不再赘述。所述通信装置的结构中包括处理器和存储器，所述处理器被配置为支持所述终端执行上述第四方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。所述通信装置的结构中还包括收发器，用于与其他设备进行通信。
第十二方面，本申请实施例还提供了一种通信系统，有益效果可以参见上个各个方面的描述此处不再赘述，所述通信系统注册处理实体和接入处理实体。
所述注册处理实体，用于通过接入处理实体接收来自终端设备的注册请求，所述注册请求中包括所述终端设备的业务标识；以及根据终端设备的业务标识确定所述业务标识对应的业务处理实体的地址信息；以及向所述接入处理实体发送注册应答请求，所述注册应答请求中包括所述业务处理实体的地址信息和所述业务标识；
所述接入处理实体，用于在向注册处理实体转发所述终端设备的注册请求之后，接收所述注册应答消息；以及向所述终端设备发送删除了所述业务处理实体的地址信息以及所述业务标识的注册应答消息。
在一种可能的设计中，所述通信系统还包括问询处理实体。
所述注册处理实体在根据终端设备的业务标识确定所述业务标识对应的业务处理实体的地址信息时，可以先向问询处理实体发送第一请求消息，所述第一请求消息用于请求业务处理实体的地址信息，其中，所述第一请求消息中包括所述业务标识；之后，所述问询处理实体接收所述第一请求消息；并根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息；之后，向所述注册处理实体发送第一响应消息，所述第一响应消息中包括所述业务处理实体的地址信息；所述注册处理实体则可以接收所述第一响应消息。
在一种可能的设计中，所述通信系统还包括服务器；所述注册处理实体可以向所述服务器发送第一消息，所述第一消息包括所述业务处理实体的地址信息和所述业务标识的对应关系；之后，所述服务器接收所述第一消息；并可以保存所述业务处理实体的地址信息和所述业务标识的对应关系。
在一种可能的设计中，所述注册处理实体可以向所述业务处理实体发送通知消息，所述通知消息用于通知所述业务处理实体获取所述终端设备的签约信息。
在一种可能的设计中，所述接入处理实体还可以接收来自所述终端设备的呼叫请求，所述呼叫请求包括所述业务标识；之后，所述接入处理实体可以根据所述业务标识确定所述业务处理实体的地址信息；并根据所述业务处理实体的地址信息向所述业务处理实体发送所述呼叫请求。
在一种可能的设计中，所述问询处理实体还可以接收到呼叫请求，所述呼叫请求包括所述业务标识；之后，所述问询处理实体可以根据所述业务标识确定所述业务标识对应的业务 处理实体的地址信息；再根据所述业务处理实体的地址信息向所述业务处理实体发送所述呼叫请求。
在一种可能的设计中，所述问询处理实体在根据终端设备的业务标识确定所述业务处理实体的地址信息时，可以向服务器发送第一查询请求，所述第一查询请求用于请求所述业务处理实体的地址信息，其中，所述第一查询请求包括所述业务标识。
所述服务器，用于接收所述第一查询请求；可以根据所述业务标识确定所述业务处理实体的地址信息；之后再向所述问询处理实体发送第一查询响应，所述第一查询响应包括所述业务处理实体的地址信息。所述问询处理实体则可以接收所述第一查询响应；之后根据所述第一查询响应向所述业务处理实体发送所述呼叫请求。
第十四方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第十五方面，本申请还提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第十六方面，本申请还提供一种计算机芯片，所述芯片与存储器相连，所述芯片用于读取并执行所述存储器中存储的软件程序，执行上述各方面所述的方法。
附图说明
图1为的一种IMS的架构示意图；
图2为本申请提供的一种网络系统的架构示意图；
图3为本申请提供的另一种网络系统的架构示意图；
图4～图9为本申请提供的一种通信方法示意图；
图10～14为本申请提供的一种通信装置的结构示意图。
具体实施方式
本申请提供了一种通信方法、装置及系统，用以解决现有技术中IMS通信方式不能满足终端设备的业务扩展需求的问题。
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。
图1为IMS的网络框架示意图，包括：终端设备、代理呼叫状态控制功能(proxy-call session control function，P-CSCF)实体、服务呼叫状态控制功能(serving-call session control function，S-CSCF)实体、归属地用户服务器(home subscriber server，HSS)、应用服务器(application server，AS)。
其中，所述终端设备：用于生成注册请求，并将生成的注册请求发送IMS中的P-CSCF实体；以及接收从IMS系统返回的注册应答信息。
所述P-CSCF实体：为接入网到IMS的最先连接点，是IMS中所述终端设备的第一个接触点，所述P-CSCF实体在IMS系统中的作用类似于执行代理服务，所有信息无论来自终端设备，或者是发送给终端设备，都必须通过所述P-CSCF实体转发。所述P-CSCF实体在IMS中负责验证请求，并将验证后的请求转发给指定的目标，并且处理和转发应答信息，不同网络的IMS中可以具有相同的所述P-CSCF实体。
具体的，所述P-CSCF实体用于将来自终端设备的注册请求转发给所述S-CSCF实体； 以及将注册应答信息转发给终端设备。
所述S-CSCF实体：为IMS的控制核心，为终端设备提供会话控制和注册。目前由于IMS业务的扩展，IMS业务已经涉及到自动驾驶、商务会议、以及医疗等领域。存在用于支持不同的业务的S-CSCF实体，如可以提供远程驾驶、组呼叫、远程手术监控等业务的S-CSCF实体。
所述S-CSCF实体用于接收所述P-CSCF实体转发的所述终端设备的注册请求；对终端设备进行鉴权；以及在确定鉴权通过后，通过Diameter协议的CX接口从HSS获取终端设备的签约信息；所述S-CSCF实体还用于基于ISC接口与各应用服务器相连，所述S-CSCF实体还用于触发应用服务器执行操作，将终端设备的请求消息路由到相应的应用服务器。
所述HSS：为IMS中存储有所有与用户和服务相关的数据的主要的数据存储器。存储在HSS中的数据主要包括用户身份、签约信息、接入信息等等。
所述AS：位于用户的归属网络或者第三方位置。其中第三方位置指一个网络或者一个独立的应用服务器。所述AS的主要功能有：处理从所述S-CSCF实体发来的请求消息；向所述S-CSCF实体发送处理后的请求消息。
尽管未示出，所述IMS中还可以包括问询呼叫会话控制功能(interrogating-call session control function，I-CSCF)实体，所述I-CSCF实体可以连接所述S-CSCF实体和所述P-CSCF实体，用于为用户提供到归属网络的入口；当终端设备漫游到其他网络时，向所述P-CSCF实体发送消息，所述P-CSCF实体可以将来自终端设备的消息转发给所述I-CSCF实体，通过所述I-CSCF实体将来自终端设备的消息发送给所述S-CSCF实体；具体的，所述I-CSCF实体可以通过IMS中的HSS为所述终端设备查询相应的S-CSCF实体的地址信息，之后再将来自所述终端设备的消息转发给相应的S-CSCF实体。
本申请中的终端设备，又可称之为用户设备(user equipment，UE)，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所述终端设备可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线设备、无人驾驶(self driving)中的无线设备、远程医疗(remote medical)中的无线设备、智能电网(smart grid)中的无线设备、运输安全(transportation safety)中的无线设备、智慧城市(smart city)中的无线设备、智慧家庭(smart home)中的无线设备等等。
基于如图1所示的网络框架，所述终端设备注册到IMS的过程如下：
当终端设备向IMS系统发起注册请求后，所述P-CSCF实体会接收到来自终端设备的携带有终端设备的注册请求，所述注册请求中包括所述终端设备的标识，所述P-CSCF实体将所述注册请求转发给所述I-CSCF实体，所述I-CSCF实体向所述HSS发送用户授权请求(user authorization request，UAR)，所述UAR用于请求第一S-CSCF实体的地址信息，其中，所述UAR中携带所述终端设备的标识，所述第一S-CSCF实体是所述终端设备需注册的IMS中的S-CSCF实体，用于为将所述终端设备注册到所述IMS中，所述HSS在接收到所述UAR后，向所述I-CSCF实体发送用户授权响应(user authorization answer，UAA),所述UAA中携带所述第一S-CSCF实体的地址信息。所述I-CSCF在接收到所述UAA，根据所述第一S-CSCF实体的地址信息向所述第一S-CSCF实体发送所述注册请求，所述第一S-CSCF实体根据所述注册请求对所述终端设备进行鉴权，在鉴权通过后，向所述HSS发送服务器分配 请求(server assignment request，SAR)消息，所述HSS在接收到所述SAR消息后，向所述第一S-CSCF实体反馈SAA消息，所述服务器分配应答(server assignment answer，SAA)消息中包括所述终端设备的签约信息，所述第一S-CSCF实体在接收到所述SAA消息后，获取所述终端设备的签约信息，之后所述第一S-CSCF实体通过所述I-CSCF实体，向所述P-CSCF实体发送200OK消息，所述200OK消息中包括所述终端设备的服务路由(service route)信息，所述服务路由信息用于指示所述第一S-CSCF实体的地址信息，以便所述P-CSCF实体在接收到携带所述终端设备的呼叫请求后，根据已保存所述服务路由信息，将所述呼叫请求转发给所述第一S-CSCF实体。所述P-CSCF实体接收到所述200OK消息后将删除所述200OK消息中的所述服务路由信息，将删除了服务路由信息的200OK消息发送给所述终端设备。至此，所述终端设备注册到了所述IMS，与所述IMS建立连接。
在上述注册过程中，所述P-CSCF实体在本地只存储所述第一S-CSCF实体的地址信息，若所述终端设备需要进行业务扩展，则需要与其他S-CSCF实体进行通信，由于所述P-CSCF实体在本地只存储所述第一S-CSCF实体的地址信息并不能将所述终端设备的消息发送给其他S-CSCF实体，使得所述终端设备无法进行业务扩展，现有的IMS通信方案并不支持业务扩展。
为此，本申请实施例提供了一种通信方法，用以解决现有技术中现有的IMS通信方式不能满足终端设备的业务扩展需求的问题。
图2所示为本申请实施例应用的一种网络系统的结构示意图，其中，包括：接入处理实体和注册处理实体，可选的所述网络系统还可以包括服务器、业务处理实体以及问询处理实体。所述网络系统还可以包括终端设备，在本申请实施例中并不限制业务处理实体的数量，也就是说，所述终端设备可以与所述注册处理实体通信，也可以与一个或多个所述业务处理实体通信。
需要理解的是，在本申请的描述中，“第一”、“第二”、“第三”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序；在本申请实施例中多个指两个或两个以上。
其中，所述终端设备可以向所述注册处理实体发送注册请求，还可以接收来自所述注册处理实体接收注册应答消息，所述终端设备在注册成功之后，可以主动地发起呼叫流程，向所述接入处理实体发起呼叫请求。
所述接入处理实体为终端设备与网络系统的第一个接触点，在所述终端设备的注册流程中，所述接入处理实体可以将来自所述终端设备的注册请求转发给所述注册处理实体，也可以接收来自所述注册处理实体的注册应答消息，并且保存所述注册应答消息中的所述注册处理实体的地址信息，还可以保存所述业务处理实体的地址信息以及所述业务标识的对应关系，还可以向所述终端设备发送删除了所述注册应答消息中的所述注册处理实体的地址信息以及与所述终端设备业务标识对应的所述业务处理实体的地址信息的注册应答消息。在所述终端设备的主叫流程中，所述接入处理实体可以接收来自所述终端设备的呼叫请求，并根据所述呼叫请求中携带的业务标识，将所述呼叫请求转发给对应的业务处理实体，也可以将所述呼叫请求转发给所述注册处理实体。
可选的，所述接入处理实体可以是IMS中的P-CSCF实体，也可以是其他实体，本申请实施例并不限定，凡是可以执行所述接入处理实体所执行的方法均适用于本申请实施例。
所述注册处理实体为网络中为所述终端设备提供注册服务的实体，可以接收来自所述终 端设备的注册请求，也可以根据来自所述终端设备的注册请求对所述终端设备进行鉴权，并在鉴权通过后可以执行如下两种操作的部分或全部：
第一、所述注册处理实体可以根据所述终端设备的业务标识确定所述业务处理实体的地址信息，并向所述接入处理实体通知所述业务处理实体的地址信息。
示例性的，所述注册处理实体可以向所述问询处理实体发送用于请求所述业务处理实体的地址信息的请求消息(在本申请实施例中，对应第一请求消息)，还可以从所述问询处理实体获取携带有所述业务处理实体的地址信息的响应消息(在本申请实施例中，对应第一响应消息)。
第二、所述注册处理实体还向所述服务器发送所述业务处理实体的地址信息和所述终端设备的业务标识。
除此之外，所述注册处理实体还可以接收来自所述终端设备的呼叫请求，执行现有的呼叫流程。
所述业务处理实体为网络中可以为所述终端设备提供相应业务的实体，不同的业务处理实体可以提供为所述终端设备提相应的业务，为了区分不同的业务处理实体，所述业务处理实体可以与所述终端设备的业务标识对应，通过所述终端设备的业务标识可以确定对应的业务处理实体，以及所述业务处理实体的地址信息。所述业务处理实体可以接收来自所述注册处理实体的通知消息，提前从所述服务器获取所述终端设备的签约信息。也可以在接收到所述接入注册实体转发的所述终端设备的呼叫请求后，从所述服务器获取所述终端设备的签约信息；所述业务处理实体也可以获取所述终端设备的接入信息，所述业务处理实体获取所述终端设备的接入信息的方式与获取所述终端设备的签约信息的方式相同，此处不再赘述。
需要说明的是，在本申请实施例中，所述注册处理实体也可以为所述终端设备提供相应的业务，所述注册处理实体也可以与所述终端设备的一个或多个业务标识对应。
所述问询处理实体，可以提供业务处理实体的地址查询服务，所述问询处理实体可以根据所述终端设备的业务标识查询所述业务处理实体的地址信息，并将所述业务处理实体的地址信息告知所述注册处理实体。在所述终端设备的被叫流程中，所述问询处理实体还可以在获取所述业务处理实体的地址信息后，将来自呼叫请求发送给所述业务处理实体。
可选的，所述问询处理实体可以是IMS中的I-CSCF实体，也可以是其他实体能够查询所述业务处理实体的地址信息的实体，如可以是IMS中的一个S-CSCF实体，本申请实施例并不限定，凡是可以执行所述问询处理实体所执行的方法均适用于本申请实施例。
所述注册处理实体或所述业务处理实体可以是IMS中的S-CSCF实体，为了区分两个不同的S-CSCF实体，如所述注册处理实体为第一S-CSCF实体；所述业务处理实体为第二S-CSCF实体。
所述服务器为用于存储所述终端设备的签约信息及服务相关数据的数据(如，所述终端设备的接入信息)存储器，还可以存储与所述终端设备的业务标识对应的所述业务处理实体的地址信息、所述注册处理实体的地址信息。示例性的，所述服务器可以是HSS。
如图3所示为本申请实施例适用的另一种网络系统的框架示意图，其中包括P-CSCF实体、第一S-CSCF实体，所述网络系统中还可以包括UE、I-CSCF实体、HSS以及第二S-CSCF实体，其中，所述P-CSCF实体对应如图2所示的所述接入处理实体，所述第一S-CSCF实体对应如图2所示的所述注册处理实体，所述第二S-CSCF实体对应如图2所示的所述业务处理实体，所述HSS对应于如图2所示的所述服务器，如图3所示各个实体的功能参见如 图1～2图所示中的相关说明此处不再赘述。
在图3中，尽管仅示出了一个第二S-CSCF实体，但本申请实施例并不限定第二S-CSCF实体的数目，仅是以一个第二S-CSCF实体为例进行说明。
本申请实施例提供IMS通信方法，涉及三方面的内容，分别为：
1、注册流程；在注册流程中，所述注册处理实体根据终端设备的业务标识确定所述业务标识对应的业务处理实体的地址信息，所述注册处理实体还可以向所述接入处理实体反馈的注册应答消息，还所述注册应答消息可以携带所述业务处理实体的地址信息，所述接入处理实体可以保存所述业务处理实体的地址信息。
其中，由于所述业务处理实体与所述业务标识对应，所述接入处理实体在保存所述业务处理实体的地址信息时，可以保存所述业务标识以及所述业务处理实体的地址信息的对应关系。
在注册流程中，所述接入处理实体不仅可以保存所述注册处理实体的地址信息，还可以保存与所述业务标识对应的所述业务处理实体的地址信息，使得所述终端设备可以与所述注册处理实体存在关联，也可以与所述业务处理实体存在关联，为所述终端设备的业务扩展提供了可能性，也保证了所述终端设备可以在后续可以进行业务扩展。
2、主叫流程；在主叫流程中，所述终端设备可以向所述接入处理实体发送携带有所述业务标识的呼叫请求，所述接入处理实体可以基于已存储的所述业务标识以及所述业务处理实体的地址信息的对应关系，确定所述业务处理实体的地址信息，并根据所述业务处理实体的地址信息向所述业务处理实体转发所述呼叫请求。
在主叫流程中，由于所述接入处理实体可以基于所述呼叫请求中携带的所述业务标识，将所述呼叫请求转发给对应的所述业务处理实体，使得所述终端设备在需要业务服务时，可以与所述业务处理实体连接，由所述业务处理实体为所述终端设提供业务服务，可以实现所述终端设备的业务扩展。
3、被叫流程；在被叫流程中，所述问询处理实体在接收携带有所述业务标识的呼叫请求后，所述问询处理实体可以根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息，并根据所述业务处理实体的地址信息向所述业务处理实体转发所述呼叫请求。
在被叫流程中，由于所述问询处理实体可以基于所述呼叫请求中携带的所述业务标识，确定所述业务处理实体的地址信息，之后将所述呼叫请求转发给对应的所述业务处理实体，使得所述终端设备可以与所述业务处理实体连接，获取所述业务处理实体提供其他业务服务，进一步的，能够保证所述终端设备的业务可以实现有效扩展。
下面以如图3所示的网络框架为例，对本申请实施例提供的通信方法涉及的三个方面分别进行介绍，事实上，本申请实施例也可应用于如图2所示的网络系统，由于原理相似，此处仅以图3所示的网络系统为例说明。
第一、注册流程。
如图4所示，为申请实施例提供的一种通信方法。
S401：所述P-CSCF实体在接到所述UE的注册请求后，向所述第一S-CSCF转发UE的注册请求，也就是说，所述第一S-CSCF实体通过所述P-CSCF实体接收来自UE的注册请求。
所述第一S-CSCF实体可以根据所述UE的注册请求对所述UE进行鉴权。
所述UE的注册请求中可以包括下列信息的部分或全部：
所述UE的标识、鉴权信息、所述UE的业务标识。
所述UE的标识可以是IP多媒体私有标识(IP multimedia private identity，IMPI)，也可以是其他标识，本申请实施例并不限定，凡是可以标识所述UE的信息均可以作为所述UE的标识。
所述业务标识为用于标识所述UE的业务的信息，不同的业务，业务标识也不同，业务标识可以是IP多媒体子系统通信服务标识(IMS communication service identifiers，ICSI)，也可以是IP多媒体子系统业务标识(identification of IMS applications，IARI)，也可以定义新的业务标识，在所述注册请求中，可以携带所述UE所有业务的业务标识，也可以至携带部分业务的业务标识，例如，若所述UE的业务在后续的所述UE的使用过程中均需要开通，并使用，则可以将所述UE所有业务的业务标识携带在所述注册请求中；若所述UE的业务只有部分业务需要开通，则可以将所述UE部分业务的业务标识携带在所述注册请求中，所述注册请求中携带的所述业务标识的个数可以根据具体场景进行设置，本申请实施例并不限定。
S402：所述第一S-CSCF实体根据所述业务标识确定所述业务标识对应的所述第二S-CSCF实体的地址信息。
所述第一S-CSCF实体根据所述业务标识确定所述第二S-CSCF实体的地址信息的方式有许多，例如，所述第一S-CSCF实体可以在本地预先存储所述第二S-CSCF实体的地址信息以及对应的业务标识，所述第一S-CSCF实体则可以根据本地保存的信息，确定所述第二S-CSCF实体的地址信息。
所述第一S-CSCF实体可以直接向所述服务器发送用于请求所述第二S-CSCF实体的地址信息的请求消息，且在向所述服务器发送的请求消息中携带所述业务标识。
所述第一S-CSCF实体也可以通过其他S-CSCF实体确定所述第二S-CSCF实体的地址信息。
所述第一S-CSCF实体也可以通过所述I-CSCF实体确定所述第二S-CSCF实体的地址信息，具体过程如下：
首先，所述第一S-CSCF实体向所述I-CSCF实体发送第一请求消息，所述第一请求消息用于请求第二S-CSCF实体的地址信息，其中，所述第一请求消息中包括所述业务标识。
若所述第一S-CSCF实体对所述UE鉴权通过，则所述第一S-CSCF实体可以为所述UE完成注册，由于所述UE的业务可能需要除所述第一S-CSCF实体外的所述第二S-CSCF实体提供，所述第一S-CSCF实体需要确定与所述业务标识对应的第二S-CSCF实体。
所述第一S-CSCF实体为了确定所述第二S-CSCF实体的地址信息，可以向所述I-CSCF实体发送所述第一请求消息，以获取所述第二S-CSCF实体的地址信息。
在所述第一请求消息中需要携带所述业务标识，所述第一请求消息中携带的所述业务标识的个数可以根据具体场景进行设置，本申请实施例并不限定。
然后，所述I-CSCF实体接收所述第一请求消息后，根据所述业务标识确定所述第二S-CSCF实体的地址信息。
作为一种可能的实施方式，所述I-CSCF实体中可以本地保存有S-CSCF实体的地址信息以及每个S-CSCF实体可提供的业务的业务标识，所述I-CSCF实体在接收到所述第一请求消息后，可以根据所述业务标识，遍历本地保存的S-CSCF实体的地址信息以及每个S-CSCF实体可提供的业务的业务标识，将能够提供相应业务的S-CSCF实体作为所述第二 S-CSCF实体。
若能够提供相应业务的S-CSCF实体的个数大于一个，则所述I-CSCF实体可以择一作为所述第二S-CSCF实体，也可以将所有能够提供相应业务的S-CSCF实体均作为所述第二S-CSCF实体，也就是说，可以存在多个所述第二S-CSCF实体。
若没有能够提供相应业务的S-CSCF实体，则所述I-CSCF实体可以向所述第一S-CSCF实体发送响应消息，告知所述第一S-CSCF实体未找到所述第二S-CSCF实体的地址消息。
作为另一种可能的实施方式，S-CSCF实体的地址信息以及每个S-CSCF实体可提供的业务的业务标识也可以存储在其他设备，如可以存储在所述HSS，所述I-CSCF实体在接收到所述第一请求消息后，可以从所述其他设备获取S-CSCF实体的地址信息以及每个S-CSCF实体可提供的业务的业务标识，之后再根据所述业务标识，遍历S-CSCF实体的地址信息以及每个S-CSCF实体可提供的业务的业务标识，将能够提供相应业务的S-CSCF实体作为所述第二S-CSCF实体。
可选的，所述I-CSCF实体也可以向所述其他设备发送携带有所述业务标识的查询请求，查询能够提供相应业务的S-CSCF实体。
所述I-CSCF实体可以向所述HSS发送第一查询请求，所述第一查询请求中携带所述业务标识。
所述HSS在接收到所述第一查询请求之后，根据所述业务标识确定所述第二S-CSCF实体的地址消息。
若所述HSS确定与所述业务标识对应的S-CSCF实体的个数大于一个，则所述HSS可以择一作为所述第二S-CSCF实体，也可以将所有与所述业务标识对应的S-CSCF实体均作为第二S-CSCF实体。
所述HSS在确定了所述第二S-CSCF实体的地址消息后，所述HSS可以向所述I-CSCF实体发送第一查询响应，所述第一查询响应中包括一个或多个所述第二S-CSCF实体的地址信息，所述第一查询响应中也可以包括所述业务标识，所述第二S-CSCF实体的地址信息和所述业务标识之间存在对应关系。
若所述HSS确定没有与所述业务标识对应的S-CSCF实体，则所述HSS可以向所述I-CSCF实体发送查询失败的响应消息，告知所述I-CSCF实体未找到所述第二S-CSCF实体的地址消息，之后，所述I-CSCF实体通知所述第一S-CSCF实体未找到所述第二S-CSCF实体的地址消息。
所述第一S-CSCF实体在接收到来自所述I-CSCF实体的第一响应消息后，还可以向所述HSS发送第一消息，所述第一消息中包括所述第二S-CSCF的地址信息和所述业务标识的对应关系。
所述服务器接收所述第一消息后，可以保存所述第二S-CSCF的地址信息和所述业务标识的对应关系。
所述第一消息可以是在现有注册流程中的消息，如所述第一消可以是服务器分配请求SAR，如在所述服务器分配请求中携带所述第二S-CSCF的地址信息和所述业务标识；所述第一消息也可以是新定义的用于向所述服务器发送所述第二S-CSCF的地址信息和所述业务标识的消息。
所述第一S-CSCF实体在接收所述第一响应消息后，可以如上述过程与所述HSS进行交互，也可以与所述第二S-CSCF实体进行交互。
当所述第一S-CSCF实体接收到所述第一响应消息，所述第一S-CSCF实体获知了所述第二S-CSCF实体的地址信息，所述第一S-CSCF实体可以基于所述第二S-CSCF实体的地址信息与所述第二S-CSCF实体进行信息交互。
例如，所述第一S-CSCF实体可以根据所述第二S-CSCF实体的地址信息向所述第二S-CSCF实体发送通知消息，所述通知消息用于通知所述第二S-CSCF实体获取所述UE的签约信息，例如可以通知所述第二S-CSCF实体从所述HSS获取所述UE的签约信息。
所述第二S-CSCF实体在接收所述通知消息后，可以向所述HSS发送服务器分配请求以请求所述UE的签约信息。
所述HSS在接收到来自所述第二S-CSCF实体的服务器分配请求后，可以确定所述UE的签约信息，并向所述第二S-CSCF实体发送服务器分配应答消息，所述第二服务器分配应答消息包括所述UE的签约信息。
可选的，所述第二服务器分配应答消息还可以包括所述UE的接入信息。
通过所述通知消息，所述第二S-CSCF实体可以提前从所述HSS获取所述UE的签约信息，以使得所述第二S-CSCF实体在后续需要为所述UE提供业务服务时，更加高效。
S403：所述第一S-CSCF实体在确定所述第二S-CSCF实体的地址信息后，可以向所述P-CSCF实体发送注册应答消息，所述注册应答消息中包括所述第二S-CSCF实体的地址信息以及所述业务标识。
S404：所述P-CSCF实体接收所述第一S-CSCF实体的注册应答消息，所述P-CSCF实体保存所述第二S-CSCF的地址信息以及所述业务标识的对应关系。
所述注册应答消息还可以包括所述第一S-CSCF实体的地址信息，也还可以包括与所述第一S-CSCF实体的对应的业务标识，所述P-CSCF实体在接收所述注册应答消息后，还可以保存所述第一S-CSCF实体的地址信息。
所述P-CSCF实体在保存所述第一S-CSCF实体的地址信息，可以将所述第一S-CSCF实体的地址信息作为默认的S-CSCF实体的地址信息；也可以保存所述第一S-CSCF实体的地址信息与对应的业务标识，也就是说，保存所述第一S-CSCF实体的地址信息与对应的业务的业务标识的对应关系。
在所述UE注册流程中，所述P-CSCF实体在保存所述第二S-CSCF实体的地址信息以及所述业务标识的对应关系时，可以在所述第二S-CSCF的地址信息与所述业务标识建立映射，在所述UE需要所述第二S-CSCF实体提供业务时，可以根据所述对应关系确定所述第二S-CSCF的地址信息，进而向所述第二S-CSCF转发来自所述UE的信息，如呼叫请求、数据请求等等。
下面以如图4所示的通信方法应用在具体场景，对本申请实施例提供的通信方法进行进一步介绍。
如图5所示，为申请实施例提供的一种通信方法，该方法包括：
S501：所述第一S-CSCF实体根据来自所述UE的注册请求对所述UE进行鉴权。
S502：所述第一S-CSCF实体将所述第一S-CSCF实体的地址信息作为默认的S-CSCF实体的地址信息，所述第一S-CSCF实体根据所述注册请求中携带的业务ID确定所述第一S-CSCF实体不支持的所述UE的业务的业务标识(identification，ID)(为方便说明，将所述第一S-CSCF实体不支持的所述UE的业务的业务ID简称为所述UE的业务ID)。
S503：所述第一S-CSCF实体向所述I-CSCF实体发送第一请求消息，所述第一请求消 息携带所述UE的业务ID，所述第一请求消息用于请求可以支持业务的第二S-CSCF地址信息。
S504：所述I-CSCF实体接收所述第一请求消息后，所述I-CSCF实体根据所述UE的业务ID分配所述第二S-CSCF实体的地址信息，向所述第一S-CSCF实体发送所述第一响应消息，所述第一响应消息携带与各个所述UE的业务ID对应的第二S-CSCF实体的地址信息。
S505：所述第一S-CSCF实体接收到所述第一响应消息之后，向所述HSS发送SAR，所述SAR中携带速所述第二S-CSCF的地址信息和对应的业务ID、以及所述UE的接入信息。
其中，所述UE的接入信息包括路径(path)信息和连接(contact)信息，其中，path信息用于指示所述P-CSCF实体的地址信息，contact信息用于指示从所述P-CSCF实体路由到所述UE的信息，所述UE的接入信息是由所述P-CSCF实体确定的。
S506：所述HSS在接收到所述SAR后，存储所述第二S-CSCF的地址信息和对应的业务ID，存储所述UE的接入信息后，向所述第一S-CSCF实体发送SAA，所述SAA中包括所述UE的签约信息。
S507：所述第一S-CSCF实体向所述P-CSCF实体发送200OK消息，所述200OK消息中携带多条服务路由(service route)，其中，包括用于指示所述第一S-CSCF实体的地址信息的service route，还包括用于指示所述第二S-CSCF实体的地址信息的service route。
用于指示所述第一S-CSCF实体的地址信息的service route中可以不包括与所述第一S-CSCF实体对应的业务ID，也可以包括与所述第一S-CSCF实体对应的业务ID；用于指示所述第二S-CSCF实体的地址信息的service route中还可以包括与所述第二S-CSCF实体对应的业务ID。
S508：所述第一S-CSCF实体通知所述第二S-CSCF实体从所述HSS获取所述UE的相关信息，如所述UE的签约信息、所述UE的接入信息等。
S509：所述P-CSCF实体接收所述200OK后，保存用于指示所述第一S-CSCF的地址信息的service route、用于指示所述第二S-CSCF的地址信息的service route。
S510：所述P-CSCF实体向所述UE发送删除了各个service route的200OK消息。
第二、主叫流程。
如图6所示，为申请实施例提供的一种通信方法，该方法包括：
S601：所述P-CSCF实体接收来自所述UE的呼叫请求，所述呼叫请求包括所述业务标识。
当所述UE需要获取业务支持时，如所述UE需要进行语音通话，所述UE需要实现远程驾驶等，所述UE均会向所述P-CSCF实体发送呼叫请求。
所述呼叫请求中包括所述业务标识，还可以包括所述UE的标识。
S602：所述P-CSCF实体根据所述业务标识以及保存的所述对应关系确定所述第二S-CSCF实体的地址信息。
若所述P-CSCF实体在存储所述第一S-CSCF实体的地址信息和所述第二S-CSCF实体的地址信息时，均是采用与所述业务标识对应的方式进行存储，也就是说，所述P-CSCF实体存储有所述第一S-CSCF实体的地址信息和所述第一S-CSCF实体的地址信息对应的所述 UE的标识、以及所述第二S-CSCF实体的地址信息和所述第二S-CSCF实体的地址信息对应的所述UE的标识。
所述P-CSCF实体可以根据所述业务标识，对已存储的所述对应关系进行遍历，当遍历到相同的所述业务标识时，可以确定出对应的所述第一S-CSCF实体的地址信息或所述第二S-CSCF实体的地址信息；当未遍历到相同的所述业务标识时，所述P-CSCF实体可以向所述UE发送呼叫失败的消息。
若所述P-CSCF实体在存储所述第一S-CSCF实体的地址信息时，将所述第一S-CSCF实体的地址信息作为默认的S-CSCF实体的地址信息，且可以不存储所述第一S-CSCF实体的地址信息对应的业务标识；所述P-CSCF实体存储了所述第二S-CSCF实体的地址信息与所述业务标识的对应关系时，所述P-CSCF实体可以根据所述业务标识，对已存储的所述业务标识进行遍历，当遍历到相同的所述业务标识时，可以确定出对应的所述第二S-CSCF实体的地址信息，之后执行步骤603；当未遍历到相同的所述业务标识时，所述P-CSCF实体选择所述第一S-CSCF实体的地址信息，根据所述第一S-CSCF实体的地址信息向所述第一S-CSCF实体发送所述呼叫请求。
S603：所述P-CSCF实体根据所述第二S-CSCF实体的地址信息向所述第二S-CSCF实体发送所述呼叫请求。
所述第二S-CSCF实体接收所述呼叫请求后，在确定未保存所述UE的签约信息后，向所述HSS发送服务器分配请求，所述服务器分配请求用于请求所述UE的签约信息。
所述第二S-CSCF实体在接收所述呼叫请求后，先确定所述第二S-CSCF实体是否已存储所述UE的签约信息；由于在所述UE的注册流程中，若所述第一S-CSCF实体通知所述第二S-CSCF实体从所述HSS获取所述UE的签约信息，所述第二S-CSCF实体会提前从所述HSS获取所述UE的签约信息，若所述第二S-CSCF实体已存储所述UE的签约信息，则所述第二S-CSCF实体按照现有的主叫流程继续工作；若所述第二S-CSCF实体未存储所述UE的签约信息，则所述第二S-CSCF实体需要从所述HSS获取所述UE的签约信息。
示例性的，所述第二S-CSCF实体向所述HSS发送服务器分配请求，所述服务器分配请求用于请求所述UE的签约信息，所述服务器分配请求还可以用于请求所述UE的接入信息。
所述服务器分配请求中可以携带所述UE的标识。
所述HSS接收来自所述第二S-CSCF实体的所述服务器分配请求后，所述HSS向所述第二S-CSCF实体发送服务器分配应答消息，所述服务器分配应答消息包括所述UE的签约信息。
所述HSS接收所述服务器分配请求后，可以根据所述服务器分配请求中携带的所述UE的标识确定所述UE的签约信息，之后向所述第二S-CSCF实体发送携带有所述UE的签约信息的服务器分配应答消息。
可选的，所述服务器分配应答消息中还可以包括所述UE的接入信息。
下面以如图6所示的通信方法应用在具体场景，对本申请实施例提供的IMS通信方法进行进一步介绍。
如图7所示，为申请实施例提供的一种通信方法，该方法包括：
S701：所述UE向所述P-CSCF实体发送呼叫请求，所述呼叫请求中携带所述UE的标识以及所述UE的业务ID。
S702A：所述P-CSCF实体确定是否存储有包括携带相同的所述UE的业务ID的service  route，若存在，则所述P-CSCF实体根据service route中指示的所述第二S-CSCF实体的地址信息，将所述呼叫请求转发给所述第二S-CSCF实体。
S702B：所述P-CSCF实体确定不存在包括相同的所述UE的业务ID的service route，若不存在，则所述P-CSCF实体根据默认的service route中指示的所述第一S-CSCF实体的地址信息将所述呼叫请求转发给所述第一S-CSCF实体，所述第一S-CSCF实体在接收到所述呼叫请求后，按照现有的主叫流程，继续执行主叫流程。
S703：所述第二S-CSCF实体在接到所述呼叫请求后，在确定未存储有所述UE的签约信息后，向所述HSS发送SAR，所述SAR用于请求获取所述UE的签约信息。
S704：所述HSS向所述第二S-CSCF实体发送SAA，所述SAA携带有所述UE的签约信息。
S705：所述第二S-CSCF实体接收到所述SAA，按照现有的主叫流程，继续执行主叫流程。
第三、被叫流程。
如图8所示，为申请实施例提供的一种通信方法，该方法包括：
S801：所述I-CSCF实体接收到呼叫请求，所述呼叫请求包括所述业务标识。
当其他设备需要通过所述IMS与所述UE建立连接时，所述I-CSCF实体会接收到所述呼叫请求，也就是在被叫流程中的呼叫请求，所述呼叫请求可以是其他网络系统中的设备发送的，如可以是公共交换电话网络(public switched telephone network，PSTN)中的设备可以通过媒体网关控制器(media gateway controller，MGC)发送给所述I-CSCF实体的；也可以是IP网络中的设备需要呼叫注册到所述IMS的设备时，可以通过互连边界控制功能(interconnection border control functions，IBCF)发送给所述I-CSCF实体的；注册到同一个所述IMS中的设备进行网内呼叫时，则可以直接向所述I-CSCF实体发送呼叫请求。
所述呼叫请求还包括所述UE的标识。
S802：所述I-CSCF实体根据所述业务标识确定所述业务标识对应的第二S-CSCF实体的地址信息。
所述I-CSCF实体根据所述业务标识确定所述第二S-CSCF实体的地址信息的方式可以参见S402中，所述第一S-CSCF实体通过所述I-CSCF实体确定所述第二S-CSCF实体的地址信息的方式中，所述I-CSCF实体确定所述第二S-CSCF实体的地址信息的相关描述，此处不再赘述。
区别在于，在注册流程中，所述注册请求中携带的所述业务标识的数目较多，例如，所述注册请求中会包括所述UE需要开通的所有业务的业务标识，需要确定的所述第二S-CSCF实体的地址信息，为每个业务标识对应的所述第二S-CSCF实体的地址信息；在所述注册请求中，所述呼叫请求中的所述业务标识可以是其中特定的一个或多个业务标识，需要确定的所述第二S-CSCF实体的地址信息，为特定的一个或多个业务标识中，每个业务标识对应的所述第二S-CSCF实体的地址信息。
S803：所述I-CSCF实体在确定所述第二S-CSCF实体的地址信息后，根据所述第二S-CSCF实体的地址信息向所述第二S-CSCF实体发送所述呼叫请求。
下面以如图8所示的通信方法应用在具体场景，对本申请实施例提供的通信方法进行进 一步介绍。
如图9所示，为申请实施例提供的一种通信方法，该方法包括：
S901：所述I-CSCF实体接收呼叫请求，所述呼叫请求中携带所述UE的业务ID。
S902：所述I-CSCF实体接收到所述呼叫请求后，向所述HSS发送LIR，用于查询与所述UE的业务ID对应的第二S-CSCF实体的地址信息，其中，所述位置查询请求(location info request，LIR)携带所述UE的业务ID。
S903：所述HSS接收到所述LIR后，根据所述UE的业务ID确定是否存在与所述UE的业务ID对应的第二S-CSCF实体地址信息，若存在，向所述I-CSCF实体发送位置查询响应(location info answer，LIA)，所述LIA携带与所述UE的业务ID对应的第二S-CSCF实体地址信息。若不存在，所述LIA携带与所述第一S-CSCF实体地址信息。
S904A：所述I-CSCF实体在接收到所述LIA后，若所述LIA携带与所述UE的业务ID对应的第二S-CSCF实体地址信息，则所述I-CSCF实体向所述第二S-CSCF实体发送所述呼叫请求。
S904B：若所述LIA携带所述第一S-CSCF实体地址信息，则所述I-CSCF实体向所述第一S-CSCF实体发送所述呼叫请求，所述第一S-CSCF实体在接收到所述呼叫请求后，按照现有的被叫流程，继续执行被叫流程。
S905：同步骤S703。
S906：同步骤S704。
S907：所述第二S-CSCF实体接收到所述SAA，按照现有的被叫流程，继续执行被叫流程。
基于与方法实施例同一发明构思，本申请实施例还提供了一种通信装置，用于执行上述方法实施例中注册处理实体执行的方法，相关特征可参见上述方法实施例，此处不再赘述，如图10所示，该装置包括接收单元1001，处理单元1002和发送单元1003；
所述接收单元1001，用于通过接入处理实体接收来自终端设备的注册请求，所述注册请求中包括所述终端设备的业务标识；
所述处理单元1002，用于根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息。
所述发送单元1003，用于向接入处理实体发送注册应答请求，所述注册应答请求中包括所述业务处理实体的地址信息和所述业务标识。
所述处理单元1002根据所述业务标识确定所述业务处理实体的地址信息的方法有许多，例如所述处理单元1002可以基于本地保存的信息，根据所述业务标识确定所述业务处理实体的地址信息，所述本地保存的信息包括业务标识与业务处理实体的地址信息的对应关系。
示例性的，所述处理单元1002还可以通过其他方法确定所述业务处理实体的地址信息。例如在所述处理单元1002根据所述业务标识确定所述业务处理实体的地址信息的情况下，所述发送单元1003可以先向问询处理实体发送第一请求消息，所述第一请求消息用于请求业务处理实体的地址信息，其中，所述第一请求消息中包括所述业务标识，之后，所述接收单元1001可以接收到来自所述问询处理实体的第一响应消息，所述第一响应消息中包括所述业务处理实体的地址信息；所述处理单元1002则可以根据所述第一响应消息确定所述业务处理实体的地址信息。
在一种可能的实施方式中，所述发送单元1003在所述处理单元1002根据所述业务标识 确定所述业务标识对应的业务处理实体的地址信息之后，还可以向所述业务处理实体发送通知消息，所述通知消息用于通知所述业务处理实体获取所述终端设备的签约信息。
在一种可能的实施方式中，所述发送单元1003在所述处理单元1002根据所述业务标识确定所述业务处理实体的地址信息之后，也可以向服务器发送第一消息，所述第一消息包括所述业务处理实体的地址信息和所述业务标识的对应关系。
基于与方法实施例同一发明构思，本申请实施例还提供了一种通信装置，用于执行上述方法实施例中接入处理实体执行的方法，相关特征可参见上述方法实施例，此处不再赘述，如图11所示，该装置包括发送单元1101，接收单元1102和处理单元1103：
所述发送单元1101，用于向注册处理实体转发所述终端设备的注册请求。
所述接收单元1102，用于接收来自所述注册处理实体的注册应答消息，所述注册应答消息中包括所述业务处理实体的地址信息以及所述业务标识。
所述处理单元1103，用于保存所述业务处理实体的地址信息以及所述业务标识。
可选的，所述发送单元1101还可以向所述终端设备发送删除了所述业务处理实体的地址信息以及所述业务标识的注册应答消息。
在一种可能的实施方式中，在主叫流程中，所述接收单元1102还可以接收来自所述终端设备的呼叫请求，所述呼叫请求包括所述业务标识；之后，由于所述处理单元1103可以在之前保存所述对应关系，所述处理单元1103可以根据所述呼叫请求中的终端设备的业务标识和所述对应关系确定所述业务处理实体的地址信息；在确定了所述业务处理实体的地址信息之后，所述发送单元1101可以根据所述业务处理实体的地址信息向所述业务处理实体发送所述呼叫请求。
基于与方法实施例同一发明构思，本申请实施例还提供了一种通信装置，用于执行上述方法实施例中问询处理实体执行的方法，相关特征可参见上述方法实施例，此处不再赘述，如图12所示，该装置包括接收单元1201、处理单元1202和发送单元1203：
所述接收单元1201，用于接收来自注册处理实体的第一请求消息，所述第一请求消息用于请求业务处理实体的地址信息，其中所述第一请求消息中包括所述业务标识。
所述处理单元1202，用于根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息。
所述发送单元1203，用于向所述注册处理实体发送第一响应消息，所述第一响应消息中包括所述业务处理实体的地址信息。
在一种可能的实施方式中，在被叫流程中，所述接收单元1201还可以接收到呼叫请求，所述呼叫请求包括所述业务标识；之后，所述处理单元1202可以根据所述业务标识确定所述业务处理实体的地址信息；所述发送单元1203可以根据所述业务处理实体的地址信息向所述业务处理实体发送所述呼叫请求。
无论在注册流程还是被叫流程中，所述处理单元1202都需要根据所述业务标识确定所述业务处理实体的地址信息，而所述处理单元1202根据所述业务标识确定所述业务处理实体的地址信息的方法有许多，例如所述处理单元1202可以基于本地保存的信息，根据所述业务标识确定所述业务处理实体的地址信息，所述本地保存的信息包括业务标识与业务处理实体的地址信息的对应关系。
示例性的，所述处理单元1202还可以通过其他方法确定所述业务处理实体的地址信息。例如在所述处理单元1202根据终端设备的业务标识确定所述业务处理实体的地址信息的情 况下，所述发送单元1203可以向服务器发送第一查询请求，所述第一查询请求用于请求所述业务处理实体的地址信息，其中，所述第一查询请求包括所述业务标识；之后所述接收单元1201可以接收来自所述服务器的第一查询响应；所述处理单元1202可以根据所述第一查询响应确定所述业务处理实体的地址信息。
基于与方法实施例同一发明构思，本申请实施例还提供了一种通信装置，用于执行上述方法实施例中服务器执行的方法，相关特征可参见上述方法实施例，此处不再赘述，如图13所示，该装置包括接收单元1301和处理单元1302：
所述接收单元1301，用于接收来自注册处理实体的第一消息，所述第一消息包括所述业务处理实体的地址信息以及所述业务标识的对应关系。
所述处理单元1302，用于保存所述业务处理实体的地址信息和所述业务标识的对应关系。
在一种可能的实施方式中，所述装置还包括发送单元1303。
所述接收单元1301可以接收来自问询处理实体的第一查询请求，所述第一查询请求包括所述业务标识；之后，所述处理单元1302可以根据所述业务标识和保存的所述对应关系确定所述业务处理实体的地址信息；在确定了所述业务处理实体的地址信息后，所述发送单元1303可以向所述问询处理实体发送第一查询响应，所述第一查询响应包括所述业务处理实体的地址信息。
本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能单元可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个模块中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
该集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台终端设备(可以是个人计算机，手机，或者网络设备等)或处理器(processor)执行本申请各个实施例该方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
在本申请实施例中，所述接入处理实体、所述注册处理实体、所述服务器以及所述问询处理实体均可以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
在一个简单的实施例中，本领域的技术人员可以想到所述接入处理实体、所述注册处理实体、所述问询处理实体和所述服务器均可采用图14所示的形式。
如图14所示的通信装置1400，包括至少一个处理器1401、存储器1402，可选的，还可以包括通信接口1403。
存储器1402可以是易失性存储器，例如随机存取存储器；存储器也可以是非易失性存储器，例如只读存储器，快闪存储器，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)、或者存储器1402是能够用于携带或存储具有指令或数据结构形式的期望的程 序代码并能够由计算机存取的任何其他介质，但不限于此。存储器1402可以是上述存储器的组合。
本申请实施例中不限定上述处理器1401以及存储器1402之间的具体连接介质。本申请实施例在图中以存储器1402和处理器1401之间通过总线1404连接，总线1404在图中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。该总线1404可以分为地址总线、数据总线、控制总线等。为便于表示，图14中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
处理器1401可以具有数据收发功能，能够与其他设备进行通信，在如图14装置中，也可以设置独立的数据收发模块，例如通信接口1403，用于收发数据；处理器1401在与其他设备进行通信时，可以通过通信接口1403进行数据传输。
当所述注册处理实体采用图14所示的形式时，图14中的处理器1401可以通过调用存储器1402中存储的计算机执行指令，使得所述注册处理实体可以执行上述任一方法实施例中的注册处理实体执行的方法。
具体的，图10中的发送单元、接收单元和处理单元的功能/实现过程均可以通过图14中的处理器1401调用存储器1402中存储的计算机执行指令来实现。或者，图7中的处理单元的功能/实现过程可以通过图14中的处理器1401调用存储器1402中存储的计算机执行指令来实现，图10中的发送单元和接收单元的功能/实现过程可以通过图14中的通信接口1403来实现。
当接入处理实体采用图14所示的形式时，图14中的处理器1401可以通过调用存储器1402中存储的计算机执行指令，使得所述接入处理实体可以执行上述任一方法实施例中的接入处理实体执行的方法。
具体的，图11中的发送单元、接收单元和处理单元的功能/实现过程均可以通过图14中的处理器1401调用存储器1402中存储的计算机执行指令来实现。或者，图6中的处理单元的功能/实现过程可以通过图14中的处理器1401调用存储器1402中存储的计算机执行指令来实现，图11中的发送单元和接收单元的功能/实现过程可以通过图14中的通信接口1403来实现。
当所述问询处理实体采用图14所示的形式时，图14中的处理器1401可以通过调用存储器1402中存储的计算机执行指令，使得所述问询处理实体可以执行上述任一方法实施例中的问询处理实体执行的方法。
具体的，图12中的发送单元、接收单元和处理单元的功能/实现过程均可以通过图14中的处理器1401调用存储器1402中存储的计算机执行指令来实现。或者，图6中的处理单元的功能/实现过程可以通过图14中的处理器1401调用存储器1402中存储的计算机执行指令来实现，图12中的发送单元和接收单元的功能/实现过程可以通过图14中的通信接口1403来实现。
当所述服务器采用图14所示的形式时，图14中的处理器1401可以通过调用存储器1402中存储的计算机执行指令，使得所述服务器可以执行上述任一方法实施例中的服务器执行的方法。
具体的，图13中的接收单元、发送单元和处理单元的功能/实现过程均可以通过图14中的处理器1401调用存储器1402中存储的计算机执行指令来实现。或者，图8中的处理单 元的功能/实现过程可以通过图14中的处理器1401调用存储器1402中存储的计算机执行指令来实现，图13中的接收单元和发送单元和的功能/实现过程可以通过图14中的通信接口1403来实现。
基于与方法实施例同一发明构思，本申请实施例还提供了一种通信系统，用于执行上述任一实施例的方法，相关特征可参见上述方法实施例，此处不再赘述。
本申请实施例提供的一种通信系统的结构示意图可参见图2，具体的，所述通信系统包括注册处理实体和接入处理实体。
其中，所述注册处理实体，用于通过接入处理实体接收来自终端设备的注册请求，所述注册请求中包括所述终端设备的业务标识；以及根据终端设备的业务标识确定所述业务标识对应的业务处理实体的地址信息；以及向所述接入处理实体发送注册应答请求，所述注册应答请求中包括所述业务处理实体的地址信息和所述业务标识；
所述接入处理实体，用于所述注册处理实体转发终端设备的注册请求之后，接收所述注册应答消息以及保存所述业务处理实体的地址信息以及所述业务标识的对应关系。
在一种可能的实施方式中，所述通信系统还包括问询处理实体。
所述注册处理实体在根据终端设备的业务标识确定所述业务处理实体的地址信息时，所述注册处理实体可以向问询处理实体发送第一请求消息，所述第一请求消息用于请求业务处理实体的地址信息，其中，所述第一请求消息中包括所述业务标识。
所述问询处理实体接收所述第一请求消息；并可以根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息；之后再向所述注册处理实体发送第一响应消息，所述第一响应消息中包括所述业务处理实体的地址信息。
所述注册处理实体接收所述第一响应消息，在接收所述第一响应消息之后，根据所述第一响应消息确定所述业务处理实体的地址信息。
可选的，所述通信系统还包括服务器。所述注册处理实体可以通知所述服务器保存所述业务处理实体的地址信息和所述业务标识的对应关系。
具体的，所述注册处理实体可以向所述服务器发送第一消息，所述第一消息包括所述业务处理实体的地址信息和所述业务标识的对应关系；所述服务器接收所述第一消息；并在接收到所述第一消息后，保存所述业务处理实体的地址信息和所述业务标识的对应关系。
一种可能的实施方法中，所述注册处理实体还可以向所述业务处理实体发送通知消息，所述通知消息用于通知所述业务处理实体获取所述终端设备的签约信息。
在主叫流程中，所述接入处理实体可以接收来自所述终端设备的呼叫请求，所述呼叫请求包括所述业务标识；并可以根据所述业务标识和保存的所述对应关系确定所述业务处理实体的地址信息；之后，再根据所述业务处理实体的地址信息向所述业务处理实体发送所述呼叫请求。
在被叫流程中，所述问询处理实体还可以接收呼叫请求，所述呼叫请求包括所述业务标识；并可以根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息；之后再根据所述业务处理实体的地址信息向所述业务处理实体发送所述呼叫请求。
在一种可能的实施方法中，所述问询处理实体还可以向所述服务器发送第一查询请求，所述第一查询请求用于请求所述业务处理实体的地址信息，其中，所述第一查询请求包括所述业务标识；之后所述服务器接收所述第一查询请求，根据所述业务标识确定所述业务处理实体的地址信息；之后，向所述问询处理实体发送第一查询响应，所述第一查询响应包括所 述业务处理实体的地址信息。所述问询处理实体接收所述第一查询响应；可以根据所述第一查询响应确定所述业务处理实体的地址信息，也就是说可以根据所述第一查询响应向所述业务处理实体发送所述呼叫请求。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (29)

  1. 一种通信方法，其特征在于，所述方法包括：
    注册处理实体通过接入处理实体接收来自终端设备的注册请求，所述注册请求中包括所述终端设备的业务标识；
    所述注册处理实体根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息；
    所述注册处理实体向所述接入处理实体发送注册应答请求，所述注册应答请求中包括所述业务处理实体的地址信息和所述业务标识。
  2. 如权利要求1所述的方法，其特征在于，所述注册处理实体根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息，包括：
    所述注册处理实体向问询处理实体发送第一请求消息，所述第一请求消息用于请求业务处理实体的地址信息，其中，所述第一请求消息中包括所述业务标识；
    所述注册处理实体接收到来自所述问询处理实体的第一响应消息，所述第一响应消息中包括所述业务处理实体的地址信息。
  3. 如权利要求1所述的方法，其特征在于，所述注册处理实体根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息之后，还包括：
    所述注册处理实体向所述业务处理实体发送通知消息，所述通知消息用于通知所述业务处理实体获取所述终端设备的签约信息。
  4. 如权利要求1所述的方法，其特征在于，所述注册处理实体根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息之后，还包括：
    所述注册处理实体向服务器发送第一消息，所述第一消息包括所述业务处理实体的地址信息和所述业务标识的对应关系。
  5. 一种通信方法，其特征在于，所述方法包括：
    接入处理实体在向注册处理实体转发终端设备的注册请求之后，接收来自所述注册处理实体的注册应答消息；其中，所述注册请求中包括所述终端设备的业务标识；所述注册应答消息中包括所述业务处理实体的地址信息以及所述业务标识；
    所述接入处理实体保存所述业务处理实体的地址信息以及所述业务标识的对应关系。
  6. 如权利要求5所述的方法，其特征在于，所述方法还包括：
    所述接入处理实体接收来自所述终端设备的呼叫请求，所述呼叫请求包括所述业务标识；
    所述接入处理实体根据所述呼叫请求中包括的业务标识以及保存的所述对应关系，确定所述业务处理实体的地址信息；
    所述接入处理实体根据所述业务处理实体的地址信息向所述业务处理实体发送所述呼叫请求。
  7. 一种通信方法，其特征在于，所述方法包括：
    问询处理实体接收来自注册处理实体的第一请求消息，所述第一请求消息用于请求业务处理实体的地址信息，其中所述第一请求消息中包括终端设备的业务标识；
    所述问询处理实体根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息；
    所述问询处理实体向所述注册处理实体发送第一响应消息，所述第一响应消息中包括所 述业务处理实体的地址信息。
  8. 如权利要求7所述的方法，其特征在于，所述方法还包括：
    所述问询处理实体接收到呼叫请求，所述呼叫请求包括所述业务标识；
    所述问询处理实体根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息；
    所述问询处理实体根据所述业务处理实体的地址信息向所述业务处理实体发送所述呼叫请求。
  9. 如权利要求7或8所述的方法，其特征在于，所述问询处理实体根据所述业务标识确定所述业务处理实体的地址信息，包括：
    所述问询处理实体向服务器发送第一查询请求，所述第一查询请求用于请求业务处理实体的地址信息，其中，所述第一查询请求包括所述业务标识；
    所述问询处理实体接收来自所述服务器的第一查询响应，根据所述第一查询响应确定所述业务处理实体的地址信息。
  10. 一种通信装置，其特征在于，所述装置包括接收单元、处理单元和发送单元；
    所述接收单元，用于通过接入处理实体接收来自终端设备的注册请求，所述注册请求中包括所述终端设备的业务标识；
    所述处理单元，用于根据终端设备的业务标识确定所述业务标识对应的业务处理实体的地址信息；
    所述发送单元，用于向所述接入处理实体发送注册应答请求，所述注册应答请求中包括所述业务处理实体的地址信息和所述业务标识。
  11. 如权利要求10所述的装置，其特征在于，在所述处理单元根据终端设备的业务标识确定所述业务处理实体的地址信息时，所述发送单元，还用于向问询处理实体发送第一请求消息，所述第一请求消息用于请求业务处理实体的地址信息，其中，所述第一请求消息中包括所述业务标识；
    所述接收单元，用于接收到来自所述问询处理实体的第一响应消息，所述第一响应消息中包括所述业务处理实体的地址信息。
  12. 如权利要求10所述的装置，其特征在于，所述发送单元在所述处理单元根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息之后，还用于：
    向所述业务处理实体发送通知消息，所述通知消息用于通知所述业务处理实体获取所述终端设备的签约信息。
  13. 如权利要求10所述的装置，其特征在于，所述发送单元在所述处理单元根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息之后，还用于：
    向服务器发送第一消息，所述第一消息包括所述业务处理实体的地址信息和所述终端设备的业务标识的对应关系。
  14. 一种通信装置，其特征在于，所述装置包括发送单元，接收单元和处理单元：
    所述发送单元，用于向注册处理实体转发所述终端设备的注册请求，其中，所述注册请求中包括所述终端设备的业务标识；
    所述接收单元，用于接收来自所述注册处理实体的注册应答消息；所述注册应答消息中包括所述业务处理实体的地址信息以及所述业务标识；
    所述处理单元，用于保存所述业务处理实体的地址信息以及所述业务标识的对应关系。
  15. 如权利要求14所述的装置，其特征在于，
    所述接收单元，还用于接收来自所述终端设备的呼叫请求，所述呼叫请求包括所述业务标识；
    所述处理单元，还用于根据所述呼叫请求中包括的业务标识以及保存的所述对应关系，确定所述业务处理实体的地址信息；
    所述发送单元，还用于根据所述业务处理实体的地址信息向所述业务处理实体发送所述呼叫请求。
  16. 一种通信装置，其特征在于，所述装置包括接收单元、处理单元和发送单元：
    所述接收单元，用于接收来自注册处理实体的第一请求消息，所述第一请求消息用于请求业务处理实体的地址信息，其中所述第一请求消息中包括所述终端设备的业务标识；
    所述处理单元，用于根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息；
    所述发送单元，用于向所述注册处理实体发送第一响应消息，所述第一响应消息中包括所述业务处理实体的地址信息。
  17. 如权利要求16所述的装置，其特征在于，
    所述接收单元，还用于接收到呼叫请求，所述呼叫请求包括所述业务标识；
    所述处理单元，还用于根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息；
    所述发送单元，还用于根据所述业务处理实体的地址信息向所述业务处理实体发送所述呼叫请求。
  18. 如权利要求16或17所述的装置，其特征在于，在所述处理单元根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息时，所述发送单元，用于向服务器发送第一查询请求，所述第一查询请求用于请求所述业务处理实体的地址信息，其中，所述第一查询请求包括所述业务标识；
    所述接收单元，用于接收来自所述服务器的第一查询响应；
    所述处理单元，用于根据所述第一查询响应确定所述业务处理实体的地址信息。
  19. 一种通信系统，其特征在于，所述通信系统包括注册处理实体和接入处理实体；
    所述注册处理实体，用于通过接入处理实体接收来自终端设备的注册请求，所述注册请求中包括所述终端设备的业务标识；以及根据终端设备的业务标识确定所述业务标识对应的业务处理实体的地址信息；以及向所述接入处理实体发送注册应答请求，所述注册应答请求中包括所述业务处理实体的地址信息和所述业务标识；
    所述接入处理实体，用于在向所述注册处理实体转发终端设备的注册请求之后，接收所述注册应答消息以及保存所述业务处理实体的地址信息以及所述业务标识的对应关系。
  20. 如权利要求19所述的通信系统，其特征在于，所述通信系统还包括问询处理实体；
    所述注册处理实体，具体用于向所述问询处理实体发送第一请求消息，所述第一请求消息用于请求业务处理实体的地址信息，其中，所述第一请求消息中包括所述业务标识；
    所述问询处理实体，用于接收所述第一请求消息；以及所述业务标识确定所述业务标识对应的业务处理实体的地址信息；以及向所述注册处理实体发送第一响应消息，所述第一响应消息中包括所述业务处理实体的地址信息；
    所述注册处理实体，具体用于接收所述第一响应消息。
  21. 如权利要求19或20所述的通信系统，其特征在于，所述注册处理实体，还用于向所述业务处理实体发送通知消息，所述通知消息用于通知所述业务处理实体获取所述终端设备的签约信息。
  22. 如权利要求19～21任一所述的通信系统，其特征在于，所述接入处理实体，还用于接收来自所述终端设备的呼叫请求，所述呼叫请求包括所述业务标识；以及根据所述呼叫请求中包括的业务标识以及保存的所述对应关系，确定所述业务处理实体的地址信息；以及根据所述业务处理实体的地址信息向所述业务处理实体发送所述呼叫请求。
  23. 如权利要求20～22任一所述的通信系统，其特征在于，所述问询处理实体，还用于接收到呼叫请求，所述呼叫请求包括所述业务标识；以及根据所述业务标识确定所述业务标识对应的业务处理实体的地址信息；以及根据所述业务处理实体的地址信息向所述业务处理实体发送所述呼叫请求。
  24. 一种通信装置，其特征在于，所述装置包括处理器和存储器；所述存储器用于存储计算机执行指令，当所述装置运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述装置执行如权利要求1-4任一项所述的通信方法。
  25. 一种通信装置，其特征在于，包括：处理器和存储器；其中，所述存储器用于存储计算机执行指令，当所述服务管理网元运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述装置执行如权利要求5或6所述的通信方法。
  26. 一种通信装置，其特征在于，包括：处理器和存储器；其中，所述存储器用于存储计算机执行指令，当所述服务管理网元运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述装置执行如权利要求7-9任一所述的通信方法。
  27. 一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求1-4任一项所述的所述的通信方法。
  28. 一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求5或6所述的所述的通信方法。
  29. 一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求7-9任一所述的通信方法。
PCT/CN2019/108702 2018-09-30 2019-09-27 一种通信方法、装置及系统 WO2020063911A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811163212.6A CN110971583B (zh) 2018-09-30 2018-09-30 一种通信方法、装置及系统
CN201811163212.6 2018-09-30

Publications (1)

Publication Number Publication Date
WO2020063911A1 true WO2020063911A1 (zh) 2020-04-02

Family

ID=69951082

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/108702 WO2020063911A1 (zh) 2018-09-30 2019-09-27 一种通信方法、装置及系统

Country Status (2)

Country Link
CN (1) CN110971583B (zh)
WO (1) WO2020063911A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111683264A (zh) * 2020-06-16 2020-09-18 中国联合网络通信集团有限公司 视频点播方法、网络设备和终端
CN113765735A (zh) * 2021-04-19 2021-12-07 北京沃东天骏信息技术有限公司 应用测试方法、装置、设备及存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114710470A (zh) * 2020-12-16 2022-07-05 华为技术有限公司 一种通信系统、方法及装置
CN116170416A (zh) * 2021-11-25 2023-05-26 华为技术有限公司 一种确定s-cscf的方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101242406A (zh) * 2007-02-08 2008-08-13 华为技术有限公司 紧急业务呼叫的发送方法、装置及网络系统
US20080305811A1 (en) * 2007-06-11 2008-12-11 Yigang Cai Storing access network information for an ims user in a subscriber profile
US20150093996A1 (en) * 2013-09-27 2015-04-02 Broadcom Corporation Method and Apparatus for Heterogeneous Small Cells Self-Organization in LTE Networks Based on Internet Protocol Multimedia Subsystems

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100493011C (zh) * 2005-08-16 2009-05-27 华为技术有限公司 一种接入ip多媒体子系统的方法
US9787726B2 (en) * 2015-01-30 2017-10-10 Blackberry Limited Control of accesses for IMS services
US9451421B1 (en) * 2015-06-30 2016-09-20 Blackberry Limited Method and system to authenticate multiple IMS identities
CN105429988B (zh) * 2015-11-30 2018-08-24 东莞酷派软件技术有限公司 基于多业务的ims注册方法和ims注册系统
CN106941669B (zh) * 2017-02-28 2020-01-31 华为技术有限公司 无线通信方法和p-cscf设备
CN107070950B (zh) * 2017-05-24 2021-04-20 深圳市万普拉斯科技有限公司 Ims注册控制的方法、装置和计算机可读存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101242406A (zh) * 2007-02-08 2008-08-13 华为技术有限公司 紧急业务呼叫的发送方法、装置及网络系统
US20080305811A1 (en) * 2007-06-11 2008-12-11 Yigang Cai Storing access network information for an ims user in a subscriber profile
US20150093996A1 (en) * 2013-09-27 2015-04-02 Broadcom Corporation Method and Apparatus for Heterogeneous Small Cells Self-Organization in LTE Networks Based on Internet Protocol Multimedia Subsystems

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Conclusion on IMS Support for RLOS for Key issues IMS#1, IMS#2, IMS#3", SA WG2 MEETING #128BIS S 2-188921, 24 August 2018 (2018-08-24), XP051537700 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111683264A (zh) * 2020-06-16 2020-09-18 中国联合网络通信集团有限公司 视频点播方法、网络设备和终端
CN111683264B (zh) * 2020-06-16 2022-11-04 中国联合网络通信集团有限公司 视频点播方法、网络设备和终端
CN113765735A (zh) * 2021-04-19 2021-12-07 北京沃东天骏信息技术有限公司 应用测试方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN110971583A (zh) 2020-04-07
CN110971583B (zh) 2021-04-09

Similar Documents

Publication Publication Date Title
WO2020063911A1 (zh) 一种通信方法、装置及系统
US8213935B2 (en) Creating a globally unique identifier of a subscriber device
US7916685B2 (en) Methods, systems, and computer program products for supporting database access in an internet protocol multimedia subsystem (IMS) network environment
US11431774B2 (en) Method, user equipment and application server for adding media stream of multimedia session
WO2020001609A1 (zh) 一种网络的注册方法、装置及系统
WO2017036227A1 (zh) 一种实现终端被叫业务恢复的方法及装置
US20100189248A1 (en) Implementing Method and System for UE Redirection Service of Sharing Pui
WO2009024076A1 (fr) Procédé pour configurer un service et entité pour stocker une configuration de service
US8966091B2 (en) Method of distinguishing a plurality of UEs sharing one PUID and a device thereof
US20090252157A1 (en) Method of setting up a call in an internet protocol multimedia subsystem network
CN101026870A (zh) 一种实现被叫服务的方法和系统
EP3471379B1 (en) Method and apparatuses for multi-identity service based on registration of shared identities
CN104168190A (zh) 一种呼叫路由方法及装置
WO2009046660A1 (fr) Procédé, système et dispositif pour établir la relation de commande de l'association
CN105830412B (zh) 会话发起处理
WO2016050032A1 (zh) 用户注册处理方法、装置及系统
CN110191516A (zh) 一种通话建立方法及系统
KR101360151B1 (ko) Ｇｒｕｕ 사용 가입자 간의 ｉｍｓ망에서의 ｓｉｐ 메시지 전송 방법 및 그 장치
WO2016050033A1 (zh) 终呼处理方法、装置及系统
KR101022165B1 (ko) 능력 정보에 기반한 세션 관리 방법
WO2011134157A1 (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: 19867880

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

Country of ref document: EP

Kind code of ref document: A1