CN110971583B - Communication method, device and system - Google Patents

Communication method, device and system Download PDF

Info

Publication number
CN110971583B
CN110971583B CN201811163212.6A CN201811163212A CN110971583B CN 110971583 B CN110971583 B CN 110971583B CN 201811163212 A CN201811163212 A CN 201811163212A CN 110971583 B CN110971583 B CN 110971583B
Authority
CN
China
Prior art keywords
processing entity
service
address information
entity
registration
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201811163212.6A
Other languages
Chinese (zh)
Other versions
CN110971583A (en
Inventor
汪红星
练仑
王敬举
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201811163212.6A priority Critical patent/CN110971583B/en
Priority to PCT/CN2019/108702 priority patent/WO2020063911A1/en
Publication of CN110971583A publication Critical patent/CN110971583A/en
Application granted granted Critical
Publication of CN110971583B publication Critical patent/CN110971583B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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

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)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

A communication method, a device and a system are used for solving the problem that the IMS communication mode in the prior art cannot meet the service expansion requirement of terminal equipment. In the application, the access processing entity can forward the registration request of the terminal equipment to the registration processing entity; then after receiving the registration request, the registration processing entity can determine the address information of the service processing entity according to the service identifier and send a registration response message to the access processing entity; the registration response message comprises address information and a service identifier of the service processing entity, the access processing entity can store the corresponding relation between the address information and the service identifier of the service processing entity after receiving the registration response message, and the access processing entity can store the address information and the corresponding service identifier of the service processing entity when the terminal equipment needs to expand the service, so that the service expansion of the terminal equipment becomes possible.

Description

Communication method, device and system
Technical Field
The present application relates to the field of communications technologies, and in particular, to a communication method, apparatus, and system.
Background
An IP Multimedia Subsystem (IMS) is a network system for providing multimedia services based on an Internet Protocol (IP) network, and can provide various multimedia services, such as voice call, video call, and the like, for a terminal device through the IMS.
In the existing IMS communication scheme, one S-CSCF entity generally provides only one type of service, and generally, a terminal device registered to the IMS only communicates with one S-CSCF entity in the IMS.
At present, as the fields related to terminal equipment are increased, the services of the terminal equipment also need to be further expanded, the services of the terminal equipment are not limited to basic services such as voice call, video call and the like any more, but only one S-CSCF entity in the IMS can provide a specific service, and other services of the terminal equipment cannot be realized.
In summary, the existing IMS communication method cannot meet the service expansion requirement of the terminal device.
Disclosure of Invention
The application provides a communication method, a communication device and a communication system, which are used for solving the problem that the service expansion requirement of terminal equipment cannot be met by an IMS communication mode in the prior art.
In a first aspect, an embodiment of the present application provides a communication method, where the method includes: firstly, a registration processing entity receives a registration request from a terminal device through an access processing entity, wherein the registration request comprises a service identifier of the terminal device, and then the registration processing entity can authenticate the terminal device according to the registration request of the terminal device and can also determine address information of the service processing entity corresponding to the service identifier according to the service identifier of the terminal device, wherein the service processing entity can provide an entity of a service identified by the service identifier for the terminal device; and then, the registration processing entity sends a registration response request carrying the address information of the service processing entity and the service identifier to an access processing entity.
By the method, the registration processing entity can determine the address information of the service processing entity according to the service identifier in the registration process of the terminal device, so that when the terminal device needs service extension, the service identifier of the service which needs to be extended by the terminal device is carried in a registration request, and then the registration processing entity can determine the corresponding address information of the service processing entity, thereby meeting the requirement of service extension of the terminal device.
In a possible design, there are many ways for the registration processing entity to determine the address information of the service processing entity according to the service identifier, the registration processing entity may determine the corresponding relationship of the address information of the service processing entity based on the pre-stored service identifier, determine the address information of the service processing entity according to the service identifier, and also determine the address information of the service processing entity according to the service identifier by using other devices, taking other devices as query processing entities for example:
the registration processing entity may first send a first request message to an inquiry processing entity, and then, the registration processing entity receives a first response message from the inquiry 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 first response message includes address information of the service processing entity, and after receiving the first response message received by the registration processing entity, the address information of the service processing entity may be determined according to the first response message.
By the method, the registration processing entity can flexibly determine the address information of the service processing entity according to the service identifier, the mode of determining the address information of the service processing entity is more diversified, and the method provided by the embodiment of the application can be applied to different application scenes.
In a possible design, after the registration processing entity determines the address information of the service processing entity according to the service identifier, the registration processing entity may send a notification message to the service processing entity, where the notification message is used to notify the service processing entity to obtain subscription information of the terminal device.
By the method, the registration processing entity can inform the service processing entity to acquire the subscription information of the terminal equipment in advance, and the service processing entity can provide services for the terminal equipment more quickly and efficiently when the terminal equipment needs to provide services for the service processing entity subsequently.
In a possible design, after determining the address information of the service processing entity according to the service identifier, the registration processing entity may further notify the server to store the address information of the service processing entity and the service identifier. Specifically, the registration processing entity may send a first message to a server, where the first message includes a correspondence between address information of the service processing entity and the service identifier.
By the method, the registration processing entity can store the corresponding relation between the address information of the service processing entity and the service identifier to the server, so that the local storage space is saved, and the address information of the service processing entity can be conveniently acquired from the server when the address information of the service processing entity is needed.
In a second aspect, an embodiment of the present application provides a communication method, where the method includes: firstly, an access processing entity may forward a registration request of the terminal device to a registration processing entity, and then may 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, and the service processing entity may provide an entity of a service identified by the service identifier for the terminal device; after receiving the registration response message, the access processing entity may store the address information of the service processing entity and the corresponding relationship of the service identifier; or sending a registration response message deleting the address information of the service processing entity and the service identifier to the terminal device.
By the method, the access processing entity can store the address information of the service processing entity and the corresponding relation of the service identification, and when the terminal equipment needs to expand the service, the access processing entity can store the address information of the service processing entity and the corresponding service identification, so that the service expansion of the terminal equipment becomes possible.
In one possible design, the access processing entity receives a call request from the terminal device, where the call request includes the service identifier; then, the access processing entity can determine the address information of the service processing entity according to the service identifier and the stored corresponding relation; and after determining the address information of the service processing entity, the access processing entity may send the call request to the service processing entity according to the address information of the service processing entity.
By the method, the access processing entity can forward the call request to the service processing entity according to the service identifier after receiving the call request of the terminal equipment, so that the terminal equipment can communicate with the service processing entity, and the terminal equipment can be ensured to obtain service support.
In a third aspect, an embodiment of the present application provides a communication method, where the method includes: first, an inquiry processing entity may 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, the first request message includes a service identifier of a terminal device, and the service processing entity may provide, for the terminal device, an entity of a service identified by the service identifier; then, the inquiring processing entity determines the address information of the service processing entity corresponding to the service identifier according to the service identifier; then, the querying processing entity may send a first response message to the registration processing entity, where the first response message includes address information of the service processing entity.
By the method, the inquiry processing entity can inform the registration processing entity of the address information of the business processing entity after determining the address information of the business processing entity according to the business identifier, so that when the terminal equipment needs business expansion, the inquiry processing entity can determine the corresponding address information of the business processing entity, and further can meet the requirement of the business expansion of the terminal equipment.
In one possible design, the query processing entity receives a call request, where the call request includes the service identifier; then, the query processing entity may determine, according to the service identifier, address information of a service processing entity corresponding to the service identifier; and the inquiry processing entity sends the call request to the service processing entity according to the address information of the service processing entity.
By the method, the query processing entity can forward the call request to the corresponding service processing entity according to the service identifier after receiving the call request, so that the service processing entity provides corresponding service, and the terminal equipment can be ensured to obtain service support.
In a possible design, there are many ways for the query processing entity to determine the address information of the service processing entity according to the service identifier, for example, the query processing entity may determine a corresponding relationship of the address information of the service processing entity according to the service identifier stored locally, determine the address information of the service processing entity according to the service identifier, or determine the address information of the service processing entity according to the service identifier by using other devices, and take other devices as a server for example:
the query processing entity firstly sends a first query request to the server, wherein the first query request is used for requesting address information of the service processing entity, and the first query request comprises the service identifier; thereafter, the query processing entity may receive a first query response from the server, and the query processing entity may determine address information of the business processing entity according to the first query response.
By the method, the service processing entity can flexibly determine the address information of the service processing entity according to the service identification, the service processing entity can determine the address information of the service processing entity in different modes, and the application scene is expanded.
In a fourth aspect, an embodiment of the present application provides a communication method, where the method includes: firstly, 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 correspondence between service identifiers of terminal devices, and the service processing entity may provide, for the terminal devices, an entity of a service identified by the service identifier; and then, the server stores the corresponding relation between the address information of the service processing entity and the service identification.
By the method, the registration processing entity can store the corresponding relation between the address information of the service processing entity and the service identifier to the server, and the address information of the service processing entity can be acquired from the server conveniently when the registration processing entity or other entities need the address information of the service processing entity.
In a possible design, after the server stores the address information of the service processing entity and the service identifier, the server may provide the address information of the service processing entity corresponding to the service identifier for other entities, and the following description takes other entities as query processing entities as an example: the server may receive a first query request from a query processing entity, the first query request including the service identification; then, the server determines the address information of the service processing entity according to the service identification and the stored corresponding relation; after determining the address information of the business processing entity, the server sends a first query response to the query processing entity, wherein the first query response comprises the address information of the business processing entity.
By the method, the server can flexibly and conveniently provide the address information of the service processing entity for other entities under the condition of locally storing the corresponding relation between the address information of the service processing entity and the service identification, and the service of the terminal equipment can have the service provided by the corresponding service processing entity, so that the service of the terminal equipment can be effectively expanded.
In a fifth aspect, an embodiment of the present application further provides a communication apparatus, where the communication apparatus is applied to a registration processing entity, and for beneficial effects, reference may be made to the description of the first aspect and details are not repeated here. The apparatus has the functionality to implement the actions in the method instance of the first aspect described above. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. In a possible design, the structure of the apparatus includes a receiving unit, a processing unit, and a sending unit, and these units may perform corresponding functions in the method example of the first aspect, for which specific reference is made to the detailed description in the method example, and details are not repeated here.
In a sixth aspect, an embodiment of the present application further provides a communication apparatus, where the communication apparatus is applied to an access processing entity, and for beneficial effects, reference may be made to the description of the second aspect and details are not repeated here. The apparatus has the functionality to implement the actions in the method instance of the second aspect described above. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. In a possible design, the structure of the apparatus includes a receiving unit, a sending unit, and a processing unit, and these units may perform corresponding functions in the method example of the second aspect, for specific reference, detailed description in the method example is given, and details are not repeated here.
In a seventh aspect, an embodiment of the present application further provides a communication apparatus, where the communication apparatus is applied to a query processing entity, and for beneficial effects, reference may be made to the description of the third aspect and details are not repeated here. The apparatus has the function of implementing the actions in the method instance of the third aspect described above. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. In a possible design, the structure of the apparatus includes a receiving unit, a processing unit, and a sending unit, and these units may perform corresponding functions in the method example of the third aspect, for specific reference, detailed description in the method example is given, and details are not repeated here.
In an eighth aspect, an embodiment of the present application further provides a communication apparatus, where the communication apparatus is applied to a server, and for beneficial effects, reference may be made to the description of the fourth aspect and details are not repeated here. The apparatus has the functionality to implement the actions in the method instance of the fourth aspect described above. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. In a possible design, the structure of the apparatus 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, for specific reference, detailed description in the method example is given, and details are not repeated here.
In a ninth aspect, an embodiment of the present application further provides a communication apparatus, where the communication apparatus is applied to a registration processing entity, and for beneficial effects, reference may be made to the description of the first aspect and details are not repeated here. The communication device has a structure including a processor and a memory, and the processor is configured to support the terminal to execute corresponding functions in the method of the first aspect. The memory is coupled to the processor and retains program instructions and data necessary for the communication device. The structure of the communication device also comprises a communication interface used for communicating with other equipment.
In a tenth aspect, an embodiment of the present application further provides a communication apparatus, where the communication apparatus is applied to an access processing entity, and for beneficial effects, reference may be made to the description of the second aspect and details are not repeated here. The communication device has a structure including a processor and a memory, and the processor is configured to support the terminal to execute the corresponding functions in the method of the second aspect. The memory is coupled to the processor and retains program instructions and data necessary for the communication device. The structure of the communication device also comprises a communication interface used for communicating with other equipment.
In an eleventh aspect, an embodiment of the present application further provides a communication apparatus, where the communication apparatus is applied to a query processing entity, and for beneficial effects, reference may be made to the description of the third aspect, which is not described herein again. The communication device has a structure including a processor and a memory, and the processor is configured to support the terminal to execute corresponding functions in the method of the third aspect. The memory is coupled to the processor and retains program instructions and data necessary for the communication device. The structure of the communication device also comprises a communication interface used for communicating with other equipment.
In a twelfth aspect, an embodiment of the present application further provides a communication apparatus, where the communication apparatus is applied to a server, and for beneficial effects, reference may be made to the description of the fourth aspect and details are not repeated here. The communication device has a structure including a processor and a memory, and the processor is configured to support the terminal to execute the corresponding functions in the method of the fourth aspect. The memory is coupled to the processor and retains program instructions and data necessary for the communication device. The structure of the communication device also comprises a transceiver used for communicating with other equipment.
In a thirteenth aspect, an embodiment of the present application further provides a communication system, which is not described herein again with reference to the description of the above aspects, and the communication system registers a processing entity and an access processing entity.
The registration processing entity is used for receiving a registration request from a terminal device through an access processing entity, wherein the registration request comprises a service identifier of the terminal device; determining address information of a service processing entity corresponding to the service identifier according to the service identifier of the terminal equipment; sending a registration response request to the access processing entity, wherein the registration response request comprises the address information of the service processing entity and the service identifier;
the access processing entity is used for receiving the registration response message after forwarding the registration request of the terminal equipment to the registration processing entity; and sending a registration response message deleting the address information of the service processing entity and the service identifier to the terminal equipment.
In one possible design, the communication system further includes a query processing entity.
When determining the address information of the service processing entity corresponding to the service identifier according to the service identifier of the terminal device, the registration processing entity may first send a first request message to an inquiry processing entity, where the first request message is used to request the address information of the service processing entity, and the first request message includes the service identifier; thereafter, the querying processing entity receives the first request message; determining the address information of the service processing entity corresponding to the service identifier according to the service identifier; then, sending a first response message to the registration processing entity, wherein the first response message comprises the address information of the service processing entity; the registration processing entity may then receive the first response message.
In one possible design, the communication system further includes a server; the registration processing entity may send a first message to the server, where the first message includes a correspondence between address information of the service processing entity and the service identifier; then, the server receives the first message; and the corresponding relation between the address information of the service processing entity and the service identification can be stored.
In a possible design, the registration processing entity may send a notification message to the service processing entity, where the notification message is used to notify the service processing entity to obtain subscription information of the terminal device.
In one possible design, the access processing entity may further receive a call request from the terminal device, where the call request includes the service identifier; then, the access processing entity may determine address information of the service processing entity according to the service identifier; and sending the call request to the service processing entity according to the address information of the service processing entity.
In one possible design, the query processing entity may further receive a call request, where the call request includes the service identifier; then, the query processing entity may determine, according to the service identifier, address information of a service processing entity corresponding to the service identifier; and then the call request is sent to the service processing entity according to the address information of the service processing entity.
In one possible design, when determining the address information of the service processing entity according to the service identifier of the terminal device, the query processing entity may send a first query request to a server, where the first query request is used to request the address information of the service processing entity, and the first query request includes the service identifier.
The server is used for receiving the first query request; the address information of the service processing entity can be determined according to the service identification; and then sending a first query response to the query processing entity, wherein the first query response comprises the address information of the service processing entity. The query processing entity may then receive the first query response; and then sending the call request to the service processing entity according to the first query response.
In a fourteenth aspect, the present application also provides a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to perform the method of the above-described aspects.
In a fifteenth aspect, the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the above aspects.
In a sixteenth aspect, the present application further provides a computer chip, where the computer chip is connected to a memory, and the computer chip is configured to read and execute a software program stored in the memory, and execute the method in the above aspects.
Drawings
FIG. 1 is a schematic diagram of an IMS architecture;
fig. 2 is a schematic architecture diagram of a network system provided in the present application;
FIG. 3 is a schematic diagram of another network system architecture provided in the present application;
fig. 4 to 9 are schematic diagrams of a communication method provided in the present application;
fig. 10 to 14 are schematic structural diagrams of a communication device according to the present application.
Detailed Description
The application provides a communication method, a communication device and a communication system, which are used for solving the problem that an IMS communication mode in the prior art cannot meet the service expansion requirement of terminal equipment.
In order to make the objects, technical solutions and advantages of the present application more clear, the present application will be further described in detail with reference to the accompanying drawings.
Fig. 1 is a schematic diagram of a network framework of an IMS, including: a terminal device, a proxy-call session control function (P-CSCF) entity, a serving-call session control function (S-CSCF) entity, a Home Subscriber Server (HSS), and an Application Server (AS).
Wherein the terminal device: the system comprises a P-CSCF entity and a gateway controller, wherein the P-CSCF entity is used for generating a registration request and sending the generated registration request to the IMS; and receiving registration reply information returned from the IMS system.
The P-CSCF entity: the first point of attachment from the access network to the IMS is the first point of contact of the terminal device in the IMS, the P-CSCF entity functions in the IMS system similarly to performing proxy services, and all information, whether coming 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 validating requests in the IMS, forwarding validated requests to a specified destination, and processing and forwarding reply information, and the IMS of different networks may have the same P-CSCF entity.
Specifically, the P-CSCF entity is configured to forward a registration request from a terminal device to the S-CSCF entity; and forwarding the registration response information to the terminal equipment.
The S-CSCF entity: and the method provides session control and registration for the terminal equipment for the control core of the IMS. At present, due to the expansion of IMS services, the IMS services have been related to the fields of autopilot, business conference, and medical treatment. There are S-CSCF entities for supporting different services, such as those that can provide services for remote driving, group calling, remote surgical monitoring, etc.
The S-CSCF entity is used for receiving the registration request of the terminal equipment forwarded by the P-CSCF entity; authenticating the terminal equipment; after the authentication is determined to pass, acquiring the subscription information of the terminal equipment from the HSS through a CX interface of a Diameter protocol; and the S-CSCF entity is also used for connecting with each application server based on the ISC interface, and triggering the application servers to execute operation, and routing the request message of the terminal equipment to the corresponding application servers.
The HSS is used for: is the main data storage in the IMS that stores all user and service related data. The data stored in the HSS mainly includes user identity, subscription information, access information, and the like.
The AS: at the user's home network or third party location. Where a third party location refers to a network or a separate application server. The main functions of the AS are: processing a request message sent from the S-CSCF entity; and sending the processed request message to the S-CSCF entity.
Although not shown, an interrogating-call session control function (I-CSCF) entity may also be included in the IMS, which may connect the S-CSCF entity and the P-CSCF entity for providing a user with an entry to a home network; when terminal equipment roams to other networks, a message is sent to the P-CSCF entity, the P-CSCF entity can forward the message from the terminal equipment to the I-CSCF entity, and the message from the terminal equipment is sent to the S-CSCF entity through the I-CSCF entity; specifically, the I-CSCF entity may query, via the HSS in the IMS, the terminal device for address information of a corresponding S-CSCF entity, and then forward the message from the terminal device to the corresponding S-CSCF entity.
The terminal device in the present application, which may also be referred to as a User Equipment (UE), may be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.). The terminal device may be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiving function, a Virtual Reality (VR) device, an Augmented Reality (AR) device, a wireless device in industrial control (industrial control), a wireless device in self driving (self driving), a wireless device in remote medical (remote medical), a wireless device in smart grid (smart grid), a wireless device in transportation safety (transportation safety), a wireless device in smart city (smart city), a wireless device in smart home (smart home), and so on.
Based on the network framework shown in fig. 1, the process of registering the terminal device to the IMS is as follows:
after a terminal device initiates a registration request to an IMS system, a P-CSCF entity receives a registration request carrying the terminal device from the terminal device, where the registration request includes an identifier of the terminal device, the P-CSCF entity forwards the registration request to an I-CSCF entity, the I-CSCF entity sends a User Authorization Request (UAR) to an HSS, the UAR is configured to request address information of a first S-CSCF entity, where the UAR carries the identifier of the terminal device, the first S-CSCF entity is an S-CSCF entity in the IMS where the terminal device needs to be registered, and is configured to register the terminal device in the IMS, and the HSS sends a user authorization response (user authorization answer), UAA) carrying address information of the first S-CSCF entity. The I-CSCF sends the register request to the first S-CSCF entity according to the address information of the first S-CSCF entity after receiving the UAA, the first S-CSCF entity authenticates the terminal equipment according to the register request, after the authentication is passed, a Server Allocation Request (SAR) message is sent to the HSS, the HSS feeds back an SAA message to the first S-CSCF entity after receiving the SAR message, the Server Allocation Answer (SAA) message comprises the subscription information of the terminal equipment, the first S-CSCF entity obtains the subscription information of the terminal equipment after receiving the SAA message, and then the first S-CSCF entity sends a 200OK message to the P-CSCF entity through the I-CSCF entity, the 200OK message includes service route (service route) information of the terminal device, where the service route information is used to indicate address information of the first S-CSCF entity, so that the P-CSCF entity forwards a call request carrying the terminal device to the first S-CSCF entity according to the stored service route information after receiving the call request. And 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 deleted service routing information to the terminal equipment. So far, the terminal device registers to the IMS, and establishes a connection with the IMS.
In the above registration process, the P-CSCF entity locally stores only the address information of the first S-CSCF entity, and if the terminal device needs to perform service extension, it needs to communicate with other S-CSCF entities, because the P-CSCF entity locally stores only the address information of the first S-CSCF entity and cannot send the message of the terminal device to other S-CSCF entities, the terminal device cannot perform service extension, and the existing IMS communication scheme does not support service extension.
Therefore, the embodiment of the present application provides a communication method, so as to solve the problem that the existing IMS communication method in the prior art cannot meet the service expansion requirement of the terminal device.
Fig. 2 is a schematic structural diagram of a network system applied in the embodiment of the present application, where the network system includes: the network system comprises an access processing entity and a registration processing entity, and optionally, the network system further comprises a server, a service processing entity and a query processing entity. The network system may further include a terminal device, and in this embodiment, the number of service processing entities is not limited, that is, the terminal device may communicate with the registration processing entity, and may also communicate with one or more service processing entities.
It is to be understood that the terms "first," "second," "third," and the like in the description of the present application are used for descriptive purposes only and not for purposes of indicating or implying relative importance, nor order; in the embodiments of the present application, a plurality means two or more.
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, and after the terminal device succeeds in registration, the terminal device may actively initiate a call flow and initiate a call request to the access processing entity.
The access processing entity is a first contact point between a terminal device and a network system, and in a registration process of the terminal device, the access processing entity may forward a registration request from the terminal device to the registration processing entity, may also receive a registration response message from the registration processing entity, and store address information of the registration processing entity in the registration response message, may also store address information of the service processing entity and a corresponding relationship of the service identifier, and may also send, to the terminal device, a registration response message in which the address information of the registration processing entity in the registration response message and the address information of the service processing entity corresponding to the service identifier of the terminal device are deleted. In the calling process of the terminal device, the access processing entity may receive a call request from the terminal device, and forward the call request to a corresponding service processing entity according to a service identifier carried in the call request, or forward the call request to the registration processing entity.
Optionally, 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, and all methods that can be executed by the access processing entity are applicable to the embodiment of the present application.
The registration processing entity is an entity providing registration service for the terminal device in a network, and may receive a registration request from the terminal device, or authenticate the terminal device according to the registration request from the terminal device, and may perform part or all of the following two operations after the authentication is passed:
first, the registration processing entity may determine address information of the service processing entity according to the service identifier of the terminal device, and notify the access processing entity of the address information of the service processing entity.
For example, the registration processing entity may send a request message (in this embodiment, corresponding to the first request message) for requesting the address information of the service processing entity to the query processing entity, and may further obtain a response message (in this embodiment, corresponding to the first response message) carrying the address information of the service processing entity from the query processing entity.
Secondly, the register processing entity also sends the address information of the service processing entity and the service identification of the terminal equipment to the server.
Besides, the registration processing entity can also receive a call request from the terminal equipment and execute the existing call flow.
The service processing entity is an entity capable of providing corresponding services for the terminal device in a network, different service processing entities are capable of providing corresponding services for the terminal device, in order to distinguish the different service processing entities, the service processing entity may correspond to a service identifier of the terminal device, and the corresponding service processing entity and address information of the service processing entity may be determined by the service identifier of the terminal device. The service processing entity may receive the notification message from the registration processing entity, and obtain the subscription information of the terminal device from the server in advance. Or after receiving the call request of the terminal device forwarded by the access registration entity, obtaining subscription information of the terminal device from the server; the service processing entity may also obtain the access information of the terminal device, and the manner of obtaining the access information of the terminal device by the service processing entity is the same as the manner of obtaining the subscription information of the terminal device, which is not described herein again.
It should be noted that, in this embodiment of the present application, 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 identifiers 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 address information of the service processing entity according to the service identifier of the terminal device and notify the address information of the service processing entity to the registration processing entity. In the called flow of the terminal device, the query processing entity may further send a call request to the service processing entity after acquiring the address information of the service processing entity.
Optionally, the query processing entity may be an I-CSCF entity in the IMS, or may be an entity that can query the address information of the service processing entity by other entities, for example, the query processing entity may be an S-CSCF entity in the IMS.
The registration processing entity or the service processing entity may be an S-CSCF entity in the IMS, in order to distinguish two different S-CSCF entities, for example, the registration processing entity is a first S-CSCF entity; and the service processing entity is a second S-CSCF entity.
The server is a data (for example, access information of the terminal device) storage for storing subscription information and service-related data of the terminal device, and may further store address information of the service processing entity and address information of the registration processing entity corresponding to the service identifier of the terminal device. Illustratively, the server may be a HSS.
Fig. 3 is a schematic diagram of a framework of another network system applicable to the embodiment of the present application, where the network system includes a P-CSCF entity and a first S-CSCF entity, and the network system may further include a UE, an I-CSCF entity, an HSS and a second S-CSCF entity, where the P-CSCF entity corresponds to the access processing entity shown in fig. 2, the first S-CSCF entity corresponds to the registration processing entity shown in fig. 2, the second S-CSCF entity corresponds to the service processing entity shown in fig. 2, and the HSS corresponds to the server shown in fig. 2, and the functions of the entities shown in fig. 3 are not described herein again with reference to the relevant descriptions shown in fig. 1 to 2.
In fig. 3, although only one second S-CSCF entity is shown, the number of the second S-CSCF entities is not limited in the embodiments of the present application, and only one second S-CSCF entity is taken as an example for explanation.
The embodiment of the application provides an IMS communication method, which relates to the three aspects and respectively comprises the following steps:
1. registering process; in the registration process, the registration processing entity determines address information of a service processing entity corresponding to the service identifier according to the service identifier of the terminal device, the registration processing entity may further send a registration response message to the access processing entity, the registration response message may carry the address information of the service processing entity, and the access processing entity may store the address information of the service processing entity.
The access processing entity can store the corresponding relation between the service identifier and the address information of the service processing entity when storing the address information of the service processing entity because the service processing entity corresponds to the service identifier.
In the registration process, the access processing entity may store not only address information of the registration processing entity, but also address information of the service processing entity corresponding to the service identifier, so that the terminal device may be associated with the registration processing entity and also associated with the service processing entity, thereby providing possibility for service expansion of the terminal device and ensuring that the terminal device may perform service expansion subsequently.
2. Calling process; in the calling process, the terminal device may send a call request carrying the service identifier to the access processing entity, and the access processing entity may determine address information of the service processing entity based on a correspondence between the stored service identifier and the address information of the service processing entity, and forward the call request to the service processing entity according to the address information of the service processing entity.
In the calling process, the access processing entity may 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 may be connected to the service processing entity when needing a service, and the service processing entity provides the service for the terminal device, thereby implementing service expansion of the terminal device.
3. A called process; in the called process, after the query processing entity receives the call request carrying the service identifier, the query processing entity may determine, according to the service identifier, address information of a service processing entity corresponding to the service identifier, and forward the call request to the service processing entity according to the address information of the service processing entity.
In the called process, the query processing entity may determine 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 processing entity, so that the terminal device may be connected to the service processing entity to obtain other service provided by the service processing entity, and further, it may be ensured that the service of the terminal device may be effectively expanded.
In fact, the embodiment of the present application can also be applied to the network system shown in fig. 2, and because the principle is similar, only the network system shown in fig. 3 is taken as an example here for explanation.
First, a registration process.
Fig. 4 shows a communication method provided in the embodiments of the present application.
S401: 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 receives the registration request from the UE through the P-CSCF entity.
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 identity of the UE, authentication information and the service identity of the UE.
The identity of the UE may be an IP Multimedia Private Identity (IMPI), or may be other identities, which is not limited in this embodiment of the application, and all information that may identify the UE may be used as the identity of the UE.
The service identifier is information for identifying a service of the UE, and different services and service identifiers are also different, where the service identifier may be an IP multimedia subsystem communication service identifier (ICSI), an IP multimedia subsystem service identifier (identity of IMS applications, IARI), or a new service identifier may be defined, and in the registration request, the service identifier of all services of the UE may be carried, or the service identifier of a part of services may be carried, for example, if the service of the UE needs to be activated and used in a subsequent use process of the UE, the service identifier of all services of the UE may be carried in the registration request; if only part of the services of the UE need to be opened, the service identifiers of the part of the 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 a specific scenario, which is not limited in the embodiment of the present application.
S402: and the first S-CSCF entity determines the address information of the second S-CSCF entity corresponding to the service identifier according to the service identifier.
There are many ways for the first S-CSCF entity to determine the address information of the second S-CSCF entity according to the service identifier, for example, the first S-CSCF entity may locally pre-store the address information of the second S-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 locally stored information.
The first S-CSCF entity may directly send a request message for requesting 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 can also determine the 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, and the specific process is as follows:
first, the first S-CSCF entity sends a first request message to the I-CSCF entity, where the first request message is used to request address information of a second S-CSCF entity, and the first request message includes the service identifier.
If the first S-CSCF entity authenticates the UE, the first S-CSCF entity may complete registration for the UE, and since the service of the UE may need to be provided by the second S-CSCF entity other than the first S-CSCF entity, the first S-CSCF entity needs to determine the 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 acquire the address information of the second S-CSCF entity in order to determine the address information of the second S-CSCF entity.
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 may be set according to a specific scenario, which is not limited in the embodiment of the present application.
And then, after receiving the first request message, the I-CSCF entity determines the address information of the second S-CSCF entity according to the service identifier.
As a possible implementation manner, the I-CSCF entity may locally store address information of the S-CSCF entity and a service identifier of a service that can be provided by each S-CSCF entity, and after receiving the first request message, the I-CSCF entity may traverse the locally stored address information of the S-CSCF entity and the service identifier of the service that can be provided by each S-CSCF entity according to the service identifier, and use the S-CSCF entity that can provide the corresponding service as the second S-CSCF entity.
If the number of the S-CSCF entities capable of providing the corresponding service is greater than one, the I-CSCF entity may select one of the S-CSCF entities as the second S-CSCF entity, or all the S-CSCF entities capable of providing the corresponding service may be used as the second S-CSCF entity, that is, a plurality of second S-CSCF entities may exist.
If there is no S-CSCF entity capable of providing the corresponding service, the I-CSCF entity may send a response message to the first S-CSCF entity, informing that the first S-CSCF entity does not find the address message of the second S-CSCF entity.
As another possible implementation, the address information of the S-CSCF entity and the service identifier of the service that can be provided by each S-CSCF entity may also be stored in other devices, for example, may be stored in the HSS, after the I-CSCF entity receives the first request message, the I-CSCF entity may obtain the address information of the S-CSCF entity and the service identifier of the service that can be provided by each S-CSCF entity from the other devices, and then traverse the address information of the S-CSCF entity and the service identifier of the service that can be provided by each S-CSCF entity according to the service identifier, and use the S-CSCF entity that can provide the corresponding service as the second S-CSCF entity.
Optionally, the I-CSCF entity may also send an inquiry request carrying the service identifier to the other device, and inquire 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.
And after receiving the first query request, the HSS determines the address message of the second S-CSCF entity according to the service identifier.
If the HSS determines that the number of the S-CSCF entities corresponding to the service identifier is more than one, the HSS can select one S-CSCF entity as the second S-CSCF entity, and can also select all the S-CSCF entities corresponding to the service identifier as the second S-CSCF entities.
After determining the address message of the second S-CSCF entity, the HSS may send a first query response to the I-CSCF entity, where the first query response includes address information of one or more second S-CSCF entities, the first query response may also include the service identifier, and a correspondence exists between the address information of the second S-CSCF entity and the service identifier.
If the HSS determines that there is no S-CSCF entity corresponding to the service identifier, the HSS may send a response message indicating that the query is failed to the I-CSCF entity, and notify that the I-CSCF entity does not find the address message of the second S-CSCF entity, and then notify, by the I-CSCF entity, that the first S-CSCF entity does not find the address message of the second S-CSCF entity.
The first S-CSCF entity may further send a first message to the HSS after receiving a first response message from the I-CSCF entity, where the first message includes a correspondence between address information of the second S-CSCF and the service identifier.
After receiving the first message, the server may store 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 procedure, for example, the first message may be a server allocation request SAR, and for example, the server allocation request SAR carries address information of the second S-CSCF and 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 identity to the server.
After receiving the first response message, the first S-CSCF entity may interact with the HSS in the above procedure, or interact with the second 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 perform information interaction with the second S-CSCF entity based on the address information of the second S-CSCF entity.
For example, 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, where the notification message is used to notify the second S-CSCF entity to acquire the subscription information of the UE, for example, may notify the second S-CSCF entity to acquire the subscription information of the UE from the HSS.
The second S-CSCF entity, after receiving the notification message, may send a server allocation request to the HSS to request subscription information of the UE.
After receiving the server allocation request from the second S-CSCF entity, the HSS may determine subscription information of the UE, and send a server allocation response message to the second S-CSCF entity, where the second server allocation response message includes the subscription information of the UE.
Optionally, the second server allocation response message may further include access information of the UE.
Through the notification message, the second S-CSCF entity may obtain the subscription information of the UE from the HSS in advance, so that the second S-CSCF entity is more efficient when it needs to provide a service for the UE subsequently.
S403: after determining the address information of the second S-CSCF entity, the first S-CSCF entity may send a registration response message to the P-CSCF entity, where the registration response message includes the address information of the second S-CSCF entity and the service identifier.
S404: and the P-CSCF entity receives a 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 relation of the service identification.
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 may further store the address information of the first S-CSCF entity after receiving the registration response message.
The P-CSCF entity saves the address information of the first S-CSCF entity, and may use the address information of the first S-CSCF entity as the address information of the default S-CSCF entity; the address information of the first S-CSCF entity and the corresponding service identifier may also be stored, that is, the corresponding relationship between the address information of the first S-CSCF entity and the service identifier of the corresponding service is stored.
In the UE registration process, when the P-CSCF entity stores the address information of the second S-CSCF entity and the corresponding relationship between the service identifiers, a mapping may be established between the address information of the second S-CSCF entity and the service identifiers, and when the UE needs to provide services by the second S-CSCF entity, the P-CSCF entity may determine the address information of the second S-CSCF according to the corresponding relationship, and further forward information from the UE, such as a call request, a data request, and the like, to the second S-CSCF.
The communication method provided by the embodiment of the present application is further described below with the application of the communication method shown in fig. 4 to a specific scenario.
As shown in fig. 5, a communication method provided for an application embodiment includes:
s501: and the first S-CSCF entity authenticates the UE according to the registration request from the UE.
S502: the first S-CSCF entity uses the address information of the first S-CSCF entity as the address information of a default S-CSCF entity, and the first S-CSCF entity determines, according to the service ID carried in the registration request, a service Identification (ID) of the service of the UE that is not supported by the first S-CSCF entity (for convenience of description, the service ID of the service of the UE that is not supported by the first S-CSCF entity is simply referred to as the service ID of the UE).
S503: the first S-CSCF entity sends a first request message to the I-CSCF entity, the first request message carries the service ID of the UE, and the first request message is used for requesting second S-CSCF address information capable of supporting services.
S504: after the I-CSCF entity receives the first request message, the I-CSCF entity allocates address information of the second S-CSCF entity according to the service ID of the UE and sends the first response message to the first S-CSCF entity, wherein the first response message carries the address information of the second S-CSCF entity corresponding to the service ID of each UE.
S505: and after receiving the first response message, the first S-CSCF entity sends an SAR to the HSS, wherein the SAR carries the address information of the second S-CSCF, the corresponding service ID and the access information of the UE.
The access information of the UE comprises path (path) information and connection (contact) information, wherein the path information is used for indicating the address information of the P-CSCF entity, the contact information is used for indicating the information routed from the P-CSCF entity to the UE, and the access information of the UE is determined by the P-CSCF entity.
S506: and after receiving the SAR, the HSS stores the address information of the second S-CSCF and the corresponding service ID, and after storing the access information of the UE, the HSS sends SAA to the first S-CSCF entity, wherein the SAA comprises subscription information of the UE.
S507: the first S-CSCF entity sends a 200OK message to the P-CSCF entity, wherein the 200OK message carries a plurality of service routes (service routes), and the service routes comprise the service route used for indicating the address information of the first S-CSCF entity and the service route used for indicating the address information of the second S-CSCF entity.
The service route used for indicating the address information of the first S-CSCF entity may not include the service ID corresponding to the first S-CSCF entity, or may include the service ID corresponding to the first S-CSCF entity; the service route for indicating the address information of the second S-CSCF entity may further include a service ID corresponding to the second S-CSCF entity.
S508: and the first S-CSCF entity informs the second S-CSCF entity to acquire the related information of the UE from the HSS, such as subscription information of the UE, access information of the UE and the like.
S509: and after receiving the 200OK, the P-CSCF entity stores the service route used for indicating the address information of the first S-CSCF and the service route used for indicating the address information of the second S-CSCF.
S510: and the P-CSCF entity sends 200OK information deleting each service route to the UE.
Second, calling process.
As shown in fig. 6, a communication method provided for an application embodiment includes:
s601: and the P-CSCF entity receives a call request from the UE, wherein the call request comprises the service identification.
When the UE needs to obtain service support, if the UE needs to perform voice call, the UE needs to implement remote driving, and the like, the UE sends a call request to the P-CSCF entity.
The call request includes the service identifier and may further include an identifier of the UE.
S602: and the P-CSCF entity determines the address information of the second S-CSCF entity according to the service identification and the stored corresponding relation.
If 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 the P-CSCF entity and the second S-CSCF entity are stored in a manner corresponding to the service identifier, 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 address information of the second S-CSCF entity 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 according to the service identifier, and may determine address information of the corresponding first S-CSCF entity or address information of the second S-CSCF entity when the same service identifier is traversed; when the same service identifier is not traversed, the P-CSCF entity may send a call failure message to the UE.
If the P-CSCF entity stores the address information of the first S-CSCF entity, the address information of the first S-CSCF entity is used as the address information of the default S-CSCF entity, and a service identifier corresponding to the address information of the first S-CSCF entity can not be 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 may traverse the stored service identifier according to the service identifier, and when the same service identifier is traversed, may determine the address information of the corresponding second S-CSCF entity, and then perform step 603; and when the same service identifier is not traversed, the P-CSCF entity selects the address information of the first S-CSCF entity and sends the call request to the first S-CSCF entity according to the address information of the first S-CSCF entity.
S603: and 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.
And after receiving the call request and determining that the subscription information of the UE is not stored, the second S-CSCF entity sends a server allocation request to the HSS, wherein the server allocation request is used for requesting the subscription information of the UE.
After receiving the call request, the second S-CSCF entity determines whether the second S-CSCF entity stores subscription information of the UE; in the registration process of the UE, if the first S-CSCF entity notifies the second S-CSCF entity to acquire the subscription information of the UE from the HSS, the second S-CSCF entity may acquire the subscription information of the UE from the HSS in advance, and if the second S-CSCF entity stores the subscription information of the UE, the second S-CSCF entity continues to operate according to the existing calling process; and if the second S-CSCF entity does not store the subscription information of the UE, the second S-CSCF entity needs to acquire the subscription information of the UE from the HSS.
For example, 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 access information of the UE.
The server allocation request may carry an identifier of the UE.
And after receiving the server allocation request from the second S-CSCF entity, the HSS sends a server allocation response message to the second S-CSCF entity, wherein the server allocation response message comprises subscription information of the UE.
After receiving the server allocation request, the HSS may determine subscription information of the UE according to the UE identifier carried in the server allocation request, and then send a server allocation response message carrying the subscription information of the UE to the second S-CSCF entity.
Optionally, the server allocation response message may further include access information of the UE.
In the following, the IMS communication method provided in the embodiment of the present application is further described in a specific scenario where the communication method shown in fig. 6 is applied.
As shown in fig. 7, a communication method provided for an application embodiment includes:
s701: and the UE sends a call request to the P-CSCF entity, wherein the call request carries the identification of the UE and the service ID of the UE.
S702A: and the P-CSCF entity determines whether service route carrying the same service ID of the UE is stored, and if so, the P-CSCF entity forwards the call request to the second S-CSCF entity according to the address information of the second S-CSCF entity indicated in the service route.
S702B: and the P-CSCF entity determines that service route comprising the same service ID of the UE does not exist, if the service route does not exist, the P-CSCF entity forwards the call request to the first S-CSCF entity according to the address information of the first S-CSCF entity indicated in the default service route, and the first S-CSCF entity continues to execute the calling process according to the existing calling process after receiving the call request.
S703: and after receiving the call request and determining that the subscription information of the UE is not stored, the second S-CSCF entity sends an SAR to the HSS, wherein the SAR is used for requesting to acquire the subscription information of the UE.
S704: and the HSS sends SAA to the second S-CSCF entity, wherein the SAA carries subscription information of the UE.
S705: and the second S-CSCF entity receives the SAA and continues to execute the calling process according to the existing calling process.
And thirdly, called process.
As shown in fig. 8, a communication method provided for an application embodiment includes:
s801: and the I-CSCF entity receives a call request, wherein the call request comprises the service identification.
When other devices need to establish a connection with the UE through the IMS, the I-CSCF entity receives the call request, that is, the call request in the called flow, where the call request may be sent by a device in another network system, for example, a device in a Public Switched Telephone Network (PSTN) may send the call request to the I-CSCF entity through a Media Gateway Controller (MGC); or when a device in the IP network needs to call a device registered to the IMS, the device may send the call to the I-CSCF entity through an Interconnection Border Control Function (IBCF); when the device registered in the same IMS carries out in-network calling, the device can directly send a calling request to the I-CSCF entity.
The call request also includes an identity of the UE.
S802: and the I-CSCF entity determines the address information of a second S-CSCF entity corresponding to the service identifier according to the service identifier.
The mode of determining, by the I-CSCF entity, the address information of the second S-CSCF entity according to the service identifier may be referred to in S402, and in the mode of determining, by the first S-CSCF entity, the address information of the second S-CSCF entity through the I-CSCF entity, the I-CSCF entity determines a description related to the address information of the second S-CSCF entity, which is not described herein again.
The difference is that in the registration process, the number of the service identifiers carried in the registration request is large, for example, the registration request includes the service identifiers of all services that the UE needs to open, the address information of the second S-CSCF entity that needs to be determined, and the address information of the second S-CSCF entity corresponding to each service identifier; in the registration request, the service identifier in the call request may be one or more specific service identifiers, the address information of the second S-CSCF entity that needs to be determined, and the address information of the second S-CSCF entity corresponding to each service identifier in the one or more specific service identifiers.
S803: and 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.
The communication method provided in the embodiment of the present application is further described below with the application of the communication method shown in fig. 8 to a specific scenario.
As shown in fig. 9, a communication method provided for an application embodiment includes:
s901: and the I-CSCF entity receives a call request, wherein the call request carries the service ID of the UE.
S902: and after receiving the call request, the I-CSCF entity sends an LIR to the HSS, where the LIR is used to query address information of a second S-CSCF entity corresponding to the service ID of the UE, and the Location Information Request (LIR) carries the service ID of the UE.
S903: and after receiving the LIR, the HSS determines whether second S-CSCF entity address information corresponding to the service ID of the UE exists or not according to the service ID of the UE, and if so, sends a Location Information Answer (LIA) to the I-CSCF entity, wherein the LIA carries the second S-CSCF entity address information corresponding to the service ID of the UE. And if the LIA does not exist, the LIA carries the address information of the first S-CSCF entity.
S904A: and after receiving the LIA, the I-CSCF entity sends the call request to a second S-CSCF entity if the LIA carries second S-CSCF entity address information corresponding to the service ID of the UE.
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 continues to execute the called flow according to the existing called flow after receiving the call request.
S905: step S703 is synchronized.
S906: the synchronization step S704.
S907: and the second S-CSCF entity receives the SAA and continues to execute the called flow according to the existing called flow.
Based on the same inventive concept as the method embodiment, an embodiment of the present application further provides a communication apparatus, configured to execute the method performed by the registration processing entity in the method embodiment, where related features may refer to the method embodiment and are not described herein again, and as shown in fig. 10, the apparatus includes a receiving unit 1001, a processing unit 1002, and a sending unit 1003;
the receiving unit 1001 is configured to receive, through an access processing entity, a registration request from a terminal device, where the registration request includes a service identifier of the terminal device;
the processing unit 1002 is configured to determine, according to the service identifier, address information of a service processing entity corresponding 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 the address information of the service processing entity and the service identifier.
There are many ways for the processing unit 1002 to determine the address information of the service processing entity according to the service identifier, for example, the processing unit 1002 may determine the address information of the service processing entity according to the service identifier based on locally stored information, where the locally stored information includes a correspondence between the service identifier and the address information of the service processing entity.
For example, the processing unit 1002 may also determine the address information of the service processing entity by other methods. For example, in a case that 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 a query processing entity, where the first request message is used to request the address information of the service processing entity, where the first request message includes the service identifier, and then the receiving unit 1001 may receive a first response message from the query processing entity, where the first response message includes the address information of the service processing entity; the processing unit 1002 may determine address information of the service processing entity according to the first response message.
In a possible implementation manner, after the processing unit 1002 determines the address information of the service processing entity corresponding to the service identifier according to the service identifier, the sending unit 1003 may further send a notification message to the service processing entity, where the notification message is used to notify the service processing entity to obtain the subscription information of the terminal device.
In a possible implementation manner, after the processing unit 1002 determines the address information of the service processing entity according to the service identifier, the sending unit 1003 may also send a first message to a server, where the first message includes the address information of the service processing entity and the corresponding relationship of the service identifier.
Based on the same inventive concept as the method embodiment, an embodiment of the present application further provides a communication apparatus for executing a method executed by an access processing entity in the method embodiment, and related features may refer to the method embodiment, which is not described herein again, and as shown in fig. 11, the apparatus 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 the address information of the service processing entity and the service identifier.
The processing unit 1103 is configured to store the address information of the service processing entity and the service identifier.
Optionally, the sending unit 1101 may further send a registration response message to the terminal device, where the address information of the service processing entity and the service identifier are deleted.
In a possible implementation manner, in the calling flow, the receiving unit 1102 may further receive a call request from the terminal device, where the call request includes the service identifier; then, since the processing unit 1103 may store the corresponding relationship before, 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 corresponding relationship; after determining the address information of the service processing entity, the sending unit 1101 may send the call request to the service processing entity according to the address information of the service processing entity.
Based on the same inventive concept as the method embodiment, an embodiment of the present application further provides a communication apparatus, configured to execute the method executed by the query processing entity in the method embodiment, where related features may refer to the method embodiment described above, and are not described herein again, as shown in fig. 12, the apparatus 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, according to the service identifier, address information of a service processing entity corresponding 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.
In a possible implementation manner, in a called procedure, the receiving unit 1201 may further receive a call request, where the call request includes the service identifier; then, the processing unit 1202 may determine address information of the service processing entity according to the service identifier; the sending unit 1203 may send the call request to the service processing entity according to the address information of the service processing entity.
In both the registration process and the called process, the processing unit 1202 needs to determine the address information of the service processing entity according to the service identifier, and there are many methods for the processing unit 1202 to determine the address information of the service processing entity according to the service identifier, for example, the processing unit 1202 may determine the address information of the service processing entity according to the service identifier based on locally stored information, where the locally stored information includes a corresponding relationship between the service identifier and the address information of the service processing entity.
For example, the processing unit 1202 may also determine the address information of the service processing entity by other methods. For example, in a case that the processing unit 1202 determines the address information of the service processing entity according to a service identifier of a terminal device, the sending unit 1203 may send a first query request to a server, where the first query request is used to request the address information of the service processing entity, where the first query request includes the service identifier; the receiving unit 1201 may then receive a first query response from the server; the processing unit 1202 may determine address information of the service processing entity according to the first query response.
Based on the same inventive concept as the method embodiment, an embodiment of the present application further provides a communication apparatus for executing the method executed by the server in the method embodiment, and related features may refer to the method embodiment, which is not described herein again, and as shown in fig. 13, the apparatus 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 corresponding relationship between the service identifiers.
The processing unit 1302 is configured to store a corresponding relationship between the address information of the service processing entity and the service identifier.
In a possible implementation, the apparatus further includes a sending unit 1303.
The receiving unit 1301 may receive a first query request from a query processing entity, where the first query request includes the service identifier; then, the processing unit 1302 may determine address information of the service processing entity according to the service identifier and the stored corresponding relationship; after determining the address information of the service processing entity, the sending unit 1303 may send a first query response to the query processing entity, where the first query response includes the address information of the service processing entity.
The division of the units in the embodiments of the present application is schematic, and only one logic function division is used, and there may be another division manner in actual implementation, and in addition, each functional unit in each embodiment of the present application may be integrated in one processor, may also exist alone physically, or may also be integrated in one module by two or more units. The integrated unit can be realized in a form of hardware or a form of a software functional module.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a terminal device (which may be a personal computer, a mobile phone, or a network device) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
In the embodiment of the present application, the access processing entity, the registration processing entity, the server, and the query processing entity may all be presented in a form of dividing each functional module in an integrated manner. A "module" herein may refer to a particular ASIC, a circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other device that provides the described functionality.
In a simple embodiment, it will be appreciated by those skilled in the art that the access processing entity, the registration processing entity, the query processing entity and the server may all take the form shown in fig. 14.
The communications device 1400 shown in fig. 14 includes at least one processor 1401, a memory 1402, and optionally a communications interface 1403.
Memory 1402 may be a volatile memory, such as a random access memory; the memory may also be a non-volatile memory such as, but not limited to, a read-only memory, a flash memory, a Hard Disk Drive (HDD) or solid-state drive (SSD), or the 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 that can be accessed by a computer. Memory 1402 may be a combination of the above.
The embodiment of the present application does not limit the specific connection medium between the processor 1401 and the memory 1402. In the embodiment of the present application, the memory 1402 and the processor 1401 are connected by the bus 1404, the bus 1404 is shown by a thick line in the figure, and the connection manner between other components is merely illustrative and is not limited. The bus 1404 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 14, but this is not intended to represent only one bus or type of bus.
The processor 1401 may have a data transceiving function, and may be capable of communicating with other devices, and in the apparatus shown in fig. 14, a separate data transceiving module, such as the communication interface 1403, may be provided for transceiving data; the processor 1401 can perform data transmission through the communication interface 1403 when communicating with other devices.
When the registration processing entity takes the form shown in fig. 14, the processor 1401 in fig. 14 may execute the instructions by calling a computer stored in the memory 1402, so that the registration processing entity may execute the method performed by the registration processing entity in any of the above-described method embodiments.
Specifically, the functions/implementation processes of the sending unit, the receiving unit and the processing unit in fig. 10 can be implemented by the processor 1401 in fig. 14 calling a computer executing instruction stored in the memory 1402. Alternatively, the functions/implementation procedures of the processing unit in fig. 7 may be implemented by the processor 1401 in fig. 14 calling a computer executing instruction stored in the memory 1402, and the functions/implementation procedures of the transmitting unit and the receiving unit in fig. 10 may be implemented by the communication interface 1403 in fig. 14.
When the access processing entity takes the form shown in fig. 14, the processor 1401 in fig. 14 may execute the instructions by calling a computer stored in the memory 1402, so that the access processing entity may execute the method performed by the access processing entity in any of the above-described method embodiments.
Specifically, the functions/implementation processes of the sending unit, the receiving unit and the processing unit in fig. 11 can be implemented by the processor 1401 in fig. 14 calling a computer executing instruction stored in the memory 1402. Alternatively, the functions/implementation procedures of the processing unit in fig. 6 may be implemented by the processor 1401 in fig. 14 calling a computer executing instruction stored in the memory 1402, and the functions/implementation procedures of the transmitting unit and the receiving unit in fig. 11 may be implemented by the communication interface 1403 in fig. 14.
When the query processing entity takes the form shown in fig. 14, the processor 1401 in fig. 14 may execute the instructions by calling a computer stored in the memory 1402, so that the query processing entity may execute the method performed by the query processing entity in any of the above-described method embodiments.
Specifically, the functions/implementation processes of the sending unit, the receiving unit and the processing unit in fig. 12 can be implemented by the processor 1401 in fig. 14 calling a computer executing instruction stored in the memory 1402. Alternatively, the functions/implementation procedures of the processing unit in fig. 6 may be implemented by the processor 1401 in fig. 14 calling a computer executing instruction stored in the memory 1402, and the functions/implementation procedures of the transmitting unit and the receiving unit in fig. 12 may be implemented by the communication interface 1403 in fig. 14.
When the server takes the form shown in fig. 14, the processor 1401 in fig. 14 may execute the instructions by calling a computer stored in the memory 1402, so that the server may execute the method performed by the server in any of the above-described method embodiments.
Specifically, the functions/implementation processes of the receiving unit, the sending unit and the processing unit in fig. 13 can be implemented by the processor 1401 in fig. 14 calling a computer executing instruction stored in the memory 1402. Alternatively, the functions/implementation procedures of the processing unit in fig. 8 may be implemented by the processor 1401 in fig. 14 calling a computer executing instruction stored in the memory 1402, and the functions/implementation procedures of the receiving unit and the transmitting unit in fig. 13 may be implemented by the communication interface 1403 in fig. 14.
Based on the same inventive concept as the method embodiment, the embodiment of the present application further provides a communication system for executing the method of any of the above embodiments, and related features may refer to the above method embodiment, which is not described herein again.
Referring to fig. 2, a schematic structural diagram of a communication system provided in an embodiment of the present application is specifically shown, where the communication system includes a registration processing entity and an access processing entity.
The registration processing entity is configured to receive, by an access processing entity, a registration request from a terminal device, where the registration request includes a service identifier of the terminal device; determining address information of a service processing entity corresponding to the service identifier according to the service identifier of the terminal equipment; sending a registration response request to the access processing entity, wherein the registration response request comprises the address information of the service processing entity and the service identifier;
the access processing entity is configured to receive the registration response message and store the address information of the service processing entity and the corresponding relationship between the service identifiers after the registration processing entity forwards the registration request of the terminal device.
In one possible embodiment, the communication system further comprises a query processing entity.
When the registration processing entity determines the address information of the service processing entity according to the service identifier of the terminal device, the registration processing entity may send a first request message to an inquiry processing entity, where the first request message is used to request the address information of the service processing entity, and the first request message includes the service identifier.
The query processing entity receiving the first request message; determining the address information of the service processing entity corresponding to the service identifier according to the service identifier; and then sending a first response message to the registration processing entity, wherein the first response message comprises the address information of the service processing entity.
And 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.
Optionally, the communication system further includes a server. The registration processing entity may notify the server to store the correspondence between 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 address information of the service processing entity and the service identifier; the server receives the first message; and after receiving the first message, storing the corresponding relationship between the address information of the service processing entity and the service identifier.
In a possible implementation method, the registration processing entity may further send a notification message to the service processing entity, where the notification message is used to notify the service processing entity to obtain subscription information of the terminal device.
In a calling flow, the access processing entity may receive a call request from the terminal device, where the call request includes the service identifier; and can confirm the address information of the said business processing entity according to said business label and said corresponding relation preserved; and then, the call request is sent to the service processing entity according to the address information of the service processing entity.
In the called flow, the query processing entity may further receive a call request, where the call request includes the service identifier; determining the address information of the service processing entity corresponding to the service identifier according to the service identifier; and then sending the call request to the service processing entity according to the address information of the service processing entity.
In a possible implementation method, 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, and the first query request includes the service identifier; then the server receives the first query request, and determines the address information of the service processing entity according to the service identification; and then sending a first query response to the query processing entity, wherein the first query response comprises the address information of the service processing entity. The query processing entity receiving the first query response; the address information of the service processing entity may be determined from the first query response, that is, the call request may be sent to the service processing entity according to the first query response.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims (23)

1. A method of communication, the method comprising:
a registration processing entity receives a registration request from a terminal device through an access processing entity, wherein the registration request comprises a service identifier of the terminal device;
the register processing entity determines the address information of the service processing entity corresponding to the service identification according to the service identification;
and the registration processing entity sends a registration response request to the access processing entity, wherein the registration response request comprises the address information of the service processing entity and the service identifier.
2. The method of claim 1, wherein the determining, by the registration processing entity according to the service identifier, address information of a service processing entity corresponding to the service identifier comprises:
the registration processing entity sends a first request message to an inquiry processing entity, wherein the first request message is used for requesting address information of a service processing entity, and the first request message comprises the service identifier;
and the registration processing entity receives a first response message from the inquiry processing entity, wherein the first response message comprises the address information of the service processing entity.
3. The method of claim 1, wherein after the registration processing entity determines, according to the service identifier, address information of a service processing entity corresponding to the service identifier, the method further comprises:
and the registration processing entity sends a notification message to the service processing entity, wherein the notification message is used for notifying the service processing entity to acquire the subscription information of the terminal equipment.
4. The method of claim 1, wherein after the registration processing entity determines, according to the service identifier, address information of a service processing entity corresponding to the service identifier, the method further comprises:
and the registration processing entity sends a first message to a server, wherein the first message comprises the address information of the service processing entity and the corresponding relation of the service identification.
5. A method of communication, the method comprising:
the access processing entity receives a registration response message from the registration processing entity after forwarding a registration request of the terminal equipment to the registration processing entity; wherein, the registration request includes the service identifier of the terminal device; the registration response message comprises address information of a service processing entity and the service identification;
and the access processing entity stores a corresponding relation, wherein the corresponding relation is the corresponding relation between the address information of the service processing entity and the service identification.
6. The method of claim 5, wherein the method further comprises:
the access processing entity receives a call request from the terminal equipment, wherein the call request comprises the service identifier;
the access processing entity determines the address information of the service processing entity according to the service identification included in the call request and the stored corresponding relation;
and the access processing entity sends the call request to the service processing entity according to the address information of the service processing entity.
7. A method of communication, the method comprising:
an inquiry processing entity receives a first request message from a registration processing entity, wherein the first request message is used for requesting address information of a service processing entity, and the first request message comprises a service identifier of terminal equipment;
the inquiring processing entity determines the address information of the service processing entity corresponding to the service identification according to the service identification;
and the inquiry processing entity sends a first response message to the registration processing entity, wherein the first response message comprises the address information of the service processing entity.
8. The method of claim 7, wherein the method further comprises:
the query processing entity receives a call request, wherein the call request comprises the service identifier;
the inquiring processing entity determines the address information of the service processing entity corresponding to the service identification according to the service identification;
and the inquiry processing entity sends the call request to the service processing entity according to the address information of the service processing entity.
9. The method of claim 7 or 8, wherein the query processing entity determining address information of the service processing entity according to the service identifier comprises:
the query processing entity sends a first query request to a server, wherein the first query request is used for requesting address information of a service processing entity, and the first query request comprises the service identifier;
and the query processing entity receives a first query response from the server and determines the address information of the service processing entity according to the first query response.
10. A communication apparatus, characterized in that the apparatus comprises a receiving unit, a processing unit and a transmitting unit;
the receiving unit is configured to receive, through an access processing entity, a registration request from a terminal device, where the registration request includes a service identifier of the terminal device;
the processing unit is used for determining the address information of the service processing entity corresponding to the service identifier according to the service identifier of the terminal equipment;
the sending unit is configured to send 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.
11. The apparatus of claim 10, wherein when the processing unit determines the address information of the service processing entity according to a service identifier of a terminal device, the sending unit is further configured to send a first request message to a query processing entity, where the first request message is used to request the address information of the service processing entity, and the service identifier is included in the first request message;
the receiving unit is configured to receive a first response message from the query processing entity, where the first response message includes address information of the service processing entity.
12. The apparatus of claim 10, wherein the sending unit, after the processing unit determines, according to the service identifier, address information of a service processing entity corresponding to the service identifier, is further configured to:
and sending a notification message to the service processing entity, wherein the notification message is used for notifying the service processing entity to acquire the subscription information of the terminal equipment.
13. The apparatus of claim 10, wherein the sending unit, after the processing unit determines, according to the service identifier, address information of a service processing entity corresponding to the service identifier, is further configured to:
and sending a first message to a server, wherein the first message comprises the corresponding relation between the address information of the service processing entity and the service identifier of the terminal equipment.
14. A communication apparatus, characterized in that the apparatus comprises a transmitting unit, a receiving unit and a processing unit:
the sending unit is configured to forward a registration request of a terminal device to a registration processing entity, where the registration request includes a service identifier of the terminal device;
the receiving unit is used for receiving a registration response message from the registration processing entity; the registration response message comprises the address information of the service processing entity and the service identification;
and the processing unit is used for storing a corresponding relationship, wherein the corresponding relationship is the corresponding relationship between the address information of the service processing entity and the service identifier.
15. The apparatus of claim 14,
the receiving unit is further configured to receive a call request from the terminal device, where the call request includes the service identifier;
the processing unit is further configured to determine address information of the service processing entity according to the service identifier included in the call request and the stored corresponding relationship;
the sending unit is further configured to send the call request to the service processing entity according to the address information of the service processing entity.
16. A communication apparatus, characterized in that the apparatus comprises a receiving unit, a processing unit and a transmitting unit:
the receiving unit 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 a service identifier of a terminal device;
the processing unit is used for determining the address information of the service processing entity corresponding to the service identifier according to the service identifier;
the sending unit 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.
17. The apparatus of claim 16,
the receiving unit is further configured to receive a call request, where the call request includes the service identifier;
the processing unit is further configured to determine, according to the service identifier, address information of a service processing entity corresponding to the service identifier;
the sending unit is further configured to send the call request to the service processing entity according to the address information of the service processing entity.
18. The apparatus according to claim 16 or 17, wherein when the processing unit determines, according to the service identifier, address information of a service processing entity corresponding to the service identifier, the sending unit is configured to send a first query request to a server, where the first query request is used to request the address information of the service processing entity, and the first query request includes the service identifier;
the receiving unit is used for receiving a first query response from the server;
and the processing unit is used for determining the address information of the service processing entity according to the first query response.
19. A communication system, characterized in that the communication system comprises a registration processing entity and an access processing entity;
the registration processing entity is used for receiving a registration request from a terminal device through an access processing entity, wherein the registration request comprises a service identifier of the terminal device; determining address information of a service processing entity corresponding to the service identifier according to the service identifier of the terminal equipment; sending a registration response message to the access processing entity, wherein the registration response message comprises the address information of the service processing entity and the service identifier;
the access processing entity is configured to receive the registration response message and store a corresponding relationship after forwarding the registration request of the terminal device to the registration processing entity, where the corresponding relationship is a corresponding relationship between the address information of the service processing entity and the service identifier.
20. The communication system of claim 19, wherein the communication system further comprises a query processing entity;
the registration processing entity is specifically configured to send a first request message to the query 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 query processing entity is used for receiving the first request message; the service identification determines the address information of the service processing entity corresponding to the service identification; sending a first response message to the registration processing entity, wherein the first response message comprises the address information of the service processing entity;
the registration processing entity is specifically configured to receive the first response message.
21. The communication system according to claim 19 or 20, wherein the registration processing entity is further configured to send a notification message to the service processing entity, where the notification message is used to notify the service processing entity to obtain the subscription information of the terminal device.
22. The communication system according to any of claims 19 to 20, wherein the access processing entity is further configured to receive a call request from the terminal device, wherein the call request includes the service identifier; and according to the service identification included in the call request and the stored corresponding relation, determining the 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.
23. The communication system of claim 20, wherein the query processing entity is further configured to receive a call request, the call request including the service identification; determining the address information of the service processing entity corresponding to the service identifier according to the service identifier; and sending the call request to the service processing entity according to the address information of the service processing entity.
CN201811163212.6A 2018-09-30 2018-09-30 Communication method, device and system Active CN110971583B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201811163212.6A CN110971583B (en) 2018-09-30 2018-09-30 Communication method, device and system
PCT/CN2019/108702 WO2020063911A1 (en) 2018-09-30 2019-09-27 Communication method, apparatus and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811163212.6A CN110971583B (en) 2018-09-30 2018-09-30 Communication method, device and system

Publications (2)

Publication Number Publication Date
CN110971583A CN110971583A (en) 2020-04-07
CN110971583B true CN110971583B (en) 2021-04-09

Family

ID=69951082

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811163212.6A Active CN110971583B (en) 2018-09-30 2018-09-30 Communication method, device and system

Country Status (2)

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

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111683264B (en) * 2020-06-16 2022-11-04 中国联合网络通信集团有限公司 Video-on-demand method, network equipment and terminal
CN114710470A (en) * 2020-12-16 2022-07-05 华为技术有限公司 Communication system, method and device
CN113765735A (en) * 2021-04-19 2021-12-07 北京沃东天骏信息技术有限公司 Application testing method, device, equipment and storage medium
CN116170416A (en) * 2021-11-25 2023-05-26 华为技术有限公司 Method and device for determining S-CSCF

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1917457A (en) * 2005-08-16 2007-02-21 华为技术有限公司 Method for connecting to IP multimedia sub system
CN105429988A (en) * 2015-11-30 2016-03-23 东莞酷派软件技术有限公司 IMS (Internet Protocol Multimedia Subsystem) registration method and IMS registration system based on multiple services
WO2017000071A1 (en) * 2015-06-30 2017-01-05 Blackberry Limited Method and system to authenticate multiple ims identities
CN106941669A (en) * 2017-02-28 2017-07-11 华为技术有限公司 Wireless communications method and P CSCF equipment
CN107070950A (en) * 2017-05-24 2017-08-18 深圳市万普拉斯科技有限公司 Method, device and the computer-readable recording medium of IMS registration control
CN107431711A (en) * 2015-01-30 2017-12-01 黑莓有限公司 The Access Control of IMS service

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101242406A (en) * 2007-02-08 2008-08-13 华为技术有限公司 Transmission method, device and network system for emergent service call
US8265090B2 (en) * 2007-06-11 2012-09-11 Alcatel Lucent Storing access network information for an IMS user in a subscriber profile
US9788216B2 (en) * 2013-09-27 2017-10-10 Avago Technologies General Ip (Singapore) Pte. Ltd. Method and apparatus for heterogeneous small cells self-organization in LTE networks based on internet protocol multimedia subsystems

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1917457A (en) * 2005-08-16 2007-02-21 华为技术有限公司 Method for connecting to IP multimedia sub system
CN107431711A (en) * 2015-01-30 2017-12-01 黑莓有限公司 The Access Control of IMS service
WO2017000071A1 (en) * 2015-06-30 2017-01-05 Blackberry Limited Method and system to authenticate multiple ims identities
CN105429988A (en) * 2015-11-30 2016-03-23 东莞酷派软件技术有限公司 IMS (Internet Protocol Multimedia Subsystem) registration method and IMS registration system based on multiple services
CN106941669A (en) * 2017-02-28 2017-07-11 华为技术有限公司 Wireless communications method and P CSCF equipment
CN107070950A (en) * 2017-05-24 2017-08-18 深圳市万普拉斯科技有限公司 Method, device and the computer-readable recording medium of IMS registration control

Also Published As

Publication number Publication date
CN110971583A (en) 2020-04-07
WO2020063911A1 (en) 2020-04-02

Similar Documents

Publication Publication Date Title
CN110971583B (en) Communication method, device and system
US8811988B2 (en) Dynamically creating a globally unique identified of a subscriber device based on an identified of an aggregation device and identification information of the subscriber device for circuit-switched and packet-switched communication systems
US20220038514A1 (en) Method, User Equipment and Application Server for Adding Media Stream of Multimedia Session
CN102177698B (en) Correlating communication sessions
CN110661753B (en) Network registration method, device and system
US8422405B2 (en) Mobile switching center platform having interfaces with functionalities defined by an architecture that provides packet-switched multimedia subscriber services
CN105307144B (en) A kind of register method, method of calling, application server and network domain arrangement
EP2315409A1 (en) Realizing method, system and apparatus of register mechanism in ip multimedia subsystem
US9699220B2 (en) System and method to provide combinational services to anonymous callers
JP2009542106A (en) How to notify network applications of client registration in a roaming network
CN106941669B (en) Wireless communication method and P-CSCF (proxy Call Session control function) equipment
CN107666657B (en) Core network element, multimedia call routing method and system
EP3471379B1 (en) Method and apparatuses for multi-identity service based on registration of shared identities
US20130060954A1 (en) Enabling set up of a connection from a non-registered ue in ims
RU2454031C2 (en) Method, system and device for establishing association-control relations
US20150319588A1 (en) Method and device for sms processing through ims network
CN102612827B (en) There is for Route Selection method and the node of the calling of the service that the first and second networks provide
CN103200383A (en) Method, device and system capable of achieving high-definition videophone services
CN106714136B (en) Data synchronization method, HLR, MMTEL AS and system
EP4070523B1 (en) Interworking between a stand-alone non-public network (npn) and an internet protocol multimedia subsystem (ims)
CN113055874A (en) Method, platform, system and medium for realizing multi-number service of cross-network operator
CN107888547B (en) Method and device for realizing international roaming incoming call blocking service and application server
CN105830412A (en) Session initiation handling
CN108616829B (en) Method for domain selection, service centralization and continuity application server and system
CN102739499B (en) A kind of method for routing of signaling message, Apparatus and system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant