WO2024032213A1 - 通信方法、装置和系统 - Google Patents

通信方法、装置和系统 Download PDF

Info

Publication number
WO2024032213A1
WO2024032213A1 PCT/CN2023/103765 CN2023103765W WO2024032213A1 WO 2024032213 A1 WO2024032213 A1 WO 2024032213A1 CN 2023103765 W CN2023103765 W CN 2023103765W WO 2024032213 A1 WO2024032213 A1 WO 2024032213A1
Authority
WO
WIPO (PCT)
Prior art keywords
media
network element
endpoint
umf
information
Prior art date
Application number
PCT/CN2023/103765
Other languages
English (en)
French (fr)
Inventor
柳亮亮
黄锴
朱登云
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024032213A1 publication Critical patent/WO2024032213A1/zh

Links

Classifications

    • 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/80—Responding to QoS

Definitions

  • IP Internet Protocol
  • IMS multimedia subsystem
  • the media plane network element in IMS can provide a variety of control plane network elements with The media plane services associated with the call service, such as access services, resource services (such as voice conferencing), etc., enable the network to provide rich media streaming services to terminal devices in the call service.
  • the media plane network elements used to provide access services can be called access media plane network elements
  • the media plane network elements used to provide resource services can be called resource media plane network elements.
  • a media plane network element may be both an access media plane network element and a resource media plane network element.
  • the application server (AS) as a control plane network element needs to distinguish between the resource type media plane network element currently assigned to the AS and the one previously assigned to the AS.
  • the relationship between access media plane network elements is handled differently; for example, the AS decides whether to request the resource media plane network element based on whether the resource media plane network element and the access media plane network element are the same network element. Meta-allocates new media endpoints.
  • Such a mechanism requires the AS to support different processing processes, which increases the processing complexity of the AS and reduces the processing efficiency of the AS.
  • the embodiment of the present application provides a communication method in order to simplify the operation of the AS in the process of providing media streaming services.
  • a first aspect provides a communication method, which can be executed by a communication device.
  • the communication device can be a communication device or a communication device capable of supporting the communication device to implement functions required by the method, such as a chip system.
  • the communication device is a media plane network element, or a chip provided in the media plane network element, or other components used to implement the functions of the media plane network element.
  • the following description takes the communication device as a media plane network element as an example.
  • the method includes: a media plane network element receives request information from an application server, the request information is used to request the media plane network element to allocate a media endpoint for providing resource-based services, and the request information includes a request for providing access The information of the first media endpoint of the class service; the media plane network element sends the information of the second media endpoint to the application server, and the second media endpoint is the media plane network element according to whether the first media endpoint is Belonging to the media plane network element determined.
  • the above technical solution allows the AS to unconditionally request the resource-type media plane network element to allocate media endpoints. That is to say, the AS does not need to determine whether the resource-type media plane network element is consistent with the previous allocation. Whether the access media plane network element of the AS is the same media plane network element determines whether to request the resource media plane network element to allocate a new media endpoint, thereby reducing the processing complexity of the AS and improving the processing of the AS. efficiency.
  • the AS when the AS requests the resource-type media plane network element to allocate a media endpoint for providing resource-type services (referred to as a resource-type media endpoint), the AS can provide the first media endpoint for providing access-type services ( (referred to as access media endpoint) information, enables the resource media plane network element to decide what kind of second media endpoint to allocate based on whether the first media endpoint is a media endpoint on the resource media plane network element, in disguised form
  • the task of determining whether the resource media plane network element and the access media plane network element are the same network element is transferred to the media plane network element, thereby improving the processing efficiency of the AS.
  • the AS is a device provided by a third party, and the media plane network element is provided by the operator. By increasing the processing complexity of the media plane network element, the processing complexity of the AS is reduced and its processing efficiency is improved. Can improve the use satisfaction of third parties (such as operators' customers) degree and therefore is an acceptable practice.
  • the first media endpoint belongs to the media plane network element, the local address of the second media endpoint and the local address of the first media endpoint The address is the same.
  • the first media endpoint belonging to the media plane network element can also be understood as the first media endpoint being a media endpoint on the media plane network element.
  • the media plane network element is based on The network element that the first media endpoint belongs to the media plane determines not to allocate a new media endpoint, and uses the mirrored media endpoint of the first media endpoint as the second media endpoint, where the mirrored image of the first media endpoint
  • the media endpoint is the allocated first media endpoint for the media plane network element, that is to say, the media plane network element uses the first media endpoint on the media plane network element as the second media endpoint.
  • the first media endpoint does not belong to the media plane network element, and the local address of the second media endpoint and the local address of the first media endpoint are The end addresses are different. If the local address of the second media endpoint is different from the local address of the first media endpoint, it can be understood that the second media endpoint and the first media endpoint are media endpoints on different media plane network elements.
  • the fact that the first media endpoint does not belong to the media plane network element can also be understood to mean that the first media endpoint is not a media endpoint on the media plane network element.
  • the media plane network element is based on The first media endpoint does not belong to the media plane network element and determines to allocate a new media endpoint as the second media endpoint.
  • the local address of the first media endpoint is used to indicate the IP address and port of the first media endpoint in the connection between the first media endpoint and other endpoints
  • the local address of the second media endpoint is The address is used to indicate the IP address and port of the second media endpoint in the connection between the second media endpoint and other endpoints.
  • the media plane network element determines that the first media endpoint is the media endpoint on the media plane network element, the local address of the second media endpoint assigned by the media plane network element and the local address of the first media endpoint The end addresses are the same; when the media plane network element determines that the first media endpoint is not a media endpoint on the media plane network element, the local address of the second media endpoint determined by the media plane network element is the same as the local address of the first media endpoint. The addresses are not the same.
  • the information of the first media endpoint includes an identifier of the media plane network element to which the first media endpoint belongs and an identifier of the first media endpoint; or , the information of the first media endpoint includes an identifier of the first media endpoint, and the identifier of the first media endpoint includes an identifier of the media plane network element to which the first media endpoint belongs.
  • the media plane network element determines whether the first media endpoint is a media endpoint on the media plane network element based on the information of the first media endpoint. , including: the first media plane network element determines whether the media plane network element to which the first media endpoint belongs is based on the identifier of the media plane network element to which the first media endpoint belongs and the identifier of the first media endpoint. The media plane network element.
  • the information of the first media endpoint may include two parts of information: the identity of the media plane network element to which the first media endpoint belongs and the identity of the first media endpoint, so as to facilitate receiving the first media endpoint.
  • the media plane network element of the information accurately determines whether the first media endpoint is a media endpoint on the media plane network element based on the information of the first media endpoint.
  • the method further includes: the media plane network element receiving instruction information from the application server, the instruction information being used to instruct execution of the resource type service,
  • the indication information includes the information of the second media endpoint; the media plane network element performs the resource service according to the indication information.
  • the request information further includes a remote address, and the remote address is used to indicate the address of a media endpoint that establishes a connection with the second media endpoint.
  • the media plane network element when the local address of the second media endpoint is different from the remote address, the media plane network element passes through the second media endpoint. Provide the resource type service; when the local address of the second media endpoint is the same as the remote address, the media plane network element provides the resource type service through the third media endpoint, and the third media endpoint provides the resource type service.
  • the media endpoint is determined by the media plane network element based on the information of the second media endpoint.
  • the third media endpoint is an endpoint on the media plane network element related to the second media endpoint, and the association between different media endpoints on a certain media plane network element is known to the media plane network element.
  • the media plane network element can determine to perform the resource type service based on the received instruction information, and can determine the media plane network element based on whether the local address of the second media endpoint is the same as the remote address included in the request information.
  • Media endpoints that execute resource services on YuanShang support providing resource services through different media endpoints, improving the flexibility of the solution.
  • the media plane network element is a unified media plane function UMF network element.
  • a communication method is provided, which method can be executed by a communication device.
  • the communication device can be a communication device or a communication device capable of supporting the communication device to implement the functions required by the method, such as a chip system.
  • the communication device is an application server, or a chip provided in the application server, or other components used to implement the functions of the application server.
  • the following description takes the communication device as an application server as an example.
  • the method includes: an application server receives information from a media plane network element of a service discovery function network element; the application server sends request information to the media plane network element, and the request information is used to request allocation of the media plane network element A media endpoint used to provide resource-based services.
  • the request information includes information about a first media endpoint used to provide access-based services; the application server receives information from a second media endpoint of the media plane network element. , the second media endpoint is determined by the media plane network element based on whether the first media endpoint belongs to the media plane network element.
  • the request information further includes a remote address, and the remote address is used to indicate the address of a media endpoint that establishes a connection with the second media endpoint.
  • the remote address of the second media endpoint is used to indicate the IP address and port of the other endpoint in the connection between the second media endpoint and other endpoints.
  • the first media endpoint belongs to the media plane network element, the local address of the second media endpoint and the local address of the first media endpoint The address is the same.
  • the first media endpoint does not belong to the media plane network element, and the local address of the second media endpoint and the local address of the first media endpoint are The end addresses are different.
  • the information of the first media endpoint includes an identifier of the media plane network element to which the first media endpoint belongs and an identifier of the first media endpoint.
  • the method further includes: the application server sending indication information to the media plane network element, the indication information being used to instruct execution of the resource type service .
  • a communication device which is used to perform the method provided in the first aspect.
  • the device includes a transceiver module and a processing module;
  • the transceiver module is configured to receive request information from an application server.
  • the request information is used to request the media plane network element to allocate a media endpoint for providing resource-based services.
  • the request information includes a media endpoint for providing access-type services. Information about the first media endpoint of the service;
  • the transceiver module is also configured to send information about a second media endpoint to the application server.
  • the second media endpoint is determined by the media plane network element based on whether the first media endpoint belongs to the media plane network element. .
  • the first media endpoint belongs to the media plane network element, the local address of the second media endpoint and the local address of the first media endpoint The address is the same.
  • the processing module is further configured to determine not to allocate a new media endpoint according to the fact that the first media endpoint belongs to the media plane network element, so as to use the third aspect.
  • a mirror media endpoint of one media endpoint serves as the second media endpoint.
  • the first media endpoint does not belong to the media plane network element, and the local address of the second media endpoint and the local address of the first media endpoint are The end addresses are different.
  • the processing module is further configured to determine and allocate a new media endpoint as the second media endpoint based on the fact that the first media endpoint does not belong to the media plane network element. Media endpoint.
  • the information of the first media endpoint includes an identifier of the media plane network element to which the first media endpoint belongs and an identifier of the first media endpoint.
  • the processing module determines whether the first media endpoint is a media endpoint on the media plane network element according to the information of the first media endpoint, including : The processing module determines whether the media plane network element to which the first media endpoint belongs is the communication device based on the identity of the media plane network element to which the first media endpoint belongs and the identity of the first media endpoint.
  • the transceiver module is further configured to receive instruction information from the application server, where the instruction information is used to instruct execution of the resource-based service.
  • the instruction information The information of the second media endpoint is included; the processing module is further configured to execute the resource service according to the instruction information.
  • the request information further includes a remote address, and the remote address is used to indicate the address of a media endpoint that establishes a connection with the second media endpoint.
  • the media plane network element when the local address of the second media endpoint is different from the remote address, the media plane network element passes through the second media endpoint. Provide the resource type service; when the local address of the second media endpoint is the same as the remote address, the media plane network element provides the resource type service through the third media endpoint, and the third media endpoint provides the resource type service.
  • the media endpoint is determined by the media plane network element based on the information of the second media endpoint.
  • a fourth aspect provides a communication device, which is used to perform the method provided in the first aspect.
  • the device includes a transceiver module and a processing module;
  • the transceiver module is used to receive information from the media plane network element of the service discovery function network element; the transceiver module is also used to send request information to the media plane network element, and the request information is used to request the media.
  • the plane network element allocates media endpoints used to provide resource-type services, and the request information includes information about the first media endpoint used to provide access-type services; the transceiver module is also used to receive messages from the media plane network element.
  • the information of the second media endpoint is determined by the media plane network element based on whether the first media endpoint belongs to the media plane network element.
  • the request information further includes a remote address, and the remote address is used to indicate the address of a media endpoint that establishes a connection with the second media endpoint.
  • the first media endpoint belongs to the media plane network element, the local address of the second media endpoint and the local address of the first media endpoint The address is the same.
  • the first media endpoint does not belong to the media plane network element, and the local address of the second media endpoint and the local address of the first media endpoint are The end addresses are different.
  • the information of the first media endpoint includes an identifier of the media plane network element to which the first media endpoint belongs and an identifier of the first media endpoint.
  • the transceiver module is further configured to send indication information to the media plane network element, where the indication information is used to instruct execution of the resource-based service.
  • inventions of the present application provide a communication device, which has the function of implementing the behavior in the method embodiment of the first aspect or the second aspect.
  • the beneficial effects can be found in the first aspect to the second aspect. Description will not be repeated here.
  • the communication device may be a media plane network element in the first aspect, or the communication device may be a device capable of implementing the method provided in the first aspect, such as a chip or a chip system.
  • the communication device may be an application server in the second aspect, or the communication device may be a device capable of implementing the method provided in the second aspect, such as a chip or a chip system.
  • the communication device includes corresponding means or modules for performing the method of the first aspect or the second aspect.
  • the communication device includes a processing unit (sometimes also called a processing module or processor) and/or a transceiver unit (sometimes also called a transceiver module or transceiver).
  • a processing unit sometimes also called a processing module or processor
  • a transceiver unit sometimes also called a transceiver module or transceiver.
  • inventions of the present application provide a communication device.
  • the communication device may be the communication device in the first aspect or the second aspect in the above-mentioned embodiments, or the communication device provided in the first aspect or the second aspect.
  • the communication device includes a communication interface and a processor, and optionally, a memory. Wherein, the memory is used to store computer programs, and the processor is coupled to the memory and the communication interface.
  • the processor reads the computer program or instructions
  • the communication device executes the instructions executed by the media plane network element or the application server in the above method embodiment. method of execution.
  • embodiments of the present application provide a communication device, which includes an input-output interface and a logic circuit. Input and output interfaces are used to input and/or output information.
  • the logic circuit is used to perform the method described in the first aspect or the second aspect.
  • embodiments of the present application provide a chip system, which includes a processor and may also include a memory and/or a communication interface for implementing the method described in the first or second aspect.
  • the chip system further includes a memory for storing a computer program.
  • the chip system can be composed of chips or include chips and other discrete devices.
  • inventions of the present application provide a communication system.
  • the communication system includes a media plane network element and an application server, wherein the media plane network element is used to perform the tasks performed by the first control plane network element in the first aspect.
  • the execution method is used by the application server to execute the method executed by the network function storage network element in the second aspect.
  • the present application provides a computer-readable storage medium that stores a computer program. When the computer program is run, the method in the first or second aspect is implemented.
  • a computer program product includes: computer program code.
  • the computer program product includes: computer program code.
  • Figure 1 is a schematic diagram of a network architecture of a communication system provided by an embodiment of the present application.
  • FIG. 2 Shown in (a) of Figure 2 is a schematic flow chart of the process of receiving a call request and returning a 180 message;
  • Figure 2(b) shows a process for playing a special ringback tone
  • Figure 2(c) shows another process of playing a special ringback tone
  • Figure 3 is a schematic diagram of establishing a connection of a media transmission channel provided by an embodiment of the present application.
  • Figure 4 (a) is another schematic diagram of establishing a connection of a media transmission channel provided by an embodiment of the present application.
  • Figure 4(b) is another schematic diagram of establishing a connection of a media transmission channel provided by an embodiment of the present application.
  • Figure 5 is a schematic flow chart of a communication method provided by an embodiment of the present application.
  • Figure 6 is a schematic flow chart for providing resource services provided by an embodiment of the present application.
  • Figure 7 is another schematic flow chart for providing resource services provided by an embodiment of the present application.
  • Figure 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 9 is another schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the technical solutions of the embodiments of this application can be applied to various communication systems, such as: fifth generation (5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency Frequency division duplex (FDD) system, LTE time division duplex (TDD), etc.
  • the technical solution provided by this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
  • the technical solutions of the embodiments of this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, and machine-to-machine (M2M) communication.
  • D2D device-to-device
  • V2X vehicle-to-everything
  • M2M machine-to-machine
  • M2M machine-to-machine
  • M2M machine-to-machine
  • M2M machine-to-machine
  • M2M machine-to-machine
  • M2M machine-to-
  • IMS In order to meet the needs of multimedia communications, the 3GPP organization introduced IMS on the basis of the original packet bearer network. IMS can not only provide users with traditional voice services, but also provide users with rich multimedia experiences.
  • the distinguishing feature of IMS is the use of session initiation. Protocol (Session Initiation Protoco1, SIP)) system, communication and access have nothing to do, can have a variety of media business control functions and bearer capacity separation, call and session separation, application and service separation, business and network separation, as well as mobile network and English Internet service integration and other capabilities, the proposal of IMS conforms to the trend of communication network integration and development.
  • Protocol Session Initiation Protoco1, SIP
  • the embodiments of this application mainly provide a communication method based on IMS.
  • the IMS architecture may include a network function storage network element, at least one control plane network element, at least one media plane network element and at least one terminal device.
  • the network function storage network element is the network repository function (NRF) network element
  • the control plane network element is the Proxy Call Session Control Function (P-CSCF) network element
  • the media plane network element The UMF network element is used as an example for explanation.
  • Other network elements that can realize the functions of network function storage network elements, control plane network elements, and media plane network elements are also within the scope of protection of this application.
  • a UMF network element in the embodiment of the present application may be a converged UMF network element or a non-converged UMF network element.
  • FIG. 1 is a schematic diagram of an IMS architecture.
  • the IMS architecture may include but is not limited to the following network elements (also called functional network elements, functional entities, nodes, devices, etc.):
  • UE User terminal
  • P-CSCF P-CSCF network element
  • UMF UMF network element
  • AS AS_O and AS_T shown in Figure 1
  • NRF NRF network elements
  • UMF UMF
  • P-CSCF P-CSCF
  • NRF NRF
  • UE can include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems with wireless communication functions, as well as various forms of terminals and mobile stations (MS) , terminal or soft terminal, etc. For example, water meters, electricity meters, sensors, etc.
  • MS mobile stations
  • the user equipment in the embodiment of the present application may refer to an access terminal, a user unit, a user station, a mobile station, a mobile station, a relay station, a remote station, a remote terminal, a mobile device, a user terminal (user terminal), and a terminal device.
  • terminal equipment wireless communications equipment, user agent or user device.
  • the user equipment may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a device with wireless communications Functional handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, user equipment in 5G networks or users in future evolved public land mobile communications networks (PLMN) Equipment or user equipment in future Internet of Vehicles, etc., the embodiments of this application are not limited to this.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • PLMN public land mobile communications networks
  • a wearable device may also be called a wearable smart device, which is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, Gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories.
  • Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • Broadly defined wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones. Use, such as various types of smart bracelets, smart jewelry, etc. for physical sign monitoring.
  • the user equipment can also be user equipment in the Internet of Things (IoT) system.
  • IoT Internet of Things
  • IoT is an important part of the future development of information technology. Its main technical feature is to transfer items through communication technology. Connect with the network to realize an intelligent network of human-computer interconnection and physical-object interconnection.
  • IOT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrowband (NB) technology.
  • NB narrowband
  • the user equipment may also include sensors, whose main functions include collecting data (part of the user equipment), receiving control information and downlink data of the access network equipment, and sending electromagnetic waves to transmit uplink to the access network equipment. data.
  • the device used to realize the function of the user equipment may be the user equipment, or may be a device capable of supporting the user equipment to realize the function, for example, a chip system or a combined device or component that can realize the function of the user equipment.
  • the device can be installed in the user equipment.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the technical solution provided by the embodiments of the present application is described by taking the device for realizing the functions of the user equipment as user equipment as an example.
  • P-CSCF Call control function network element, which is a functional entity within the IMS network and the core of the entire IMS network. It is mainly responsible for processing signaling control during multimedia call sessions.
  • the call control function network element can be a (serving-call session control function, CSCF) network element.
  • CSCF serving-call session control function
  • the application service network element may still be a CSCF network element, or may have other names, which are not limited by the embodiments of this application.
  • CSCF network elements can be further divided into serving-call session control function (SCSCF) network elements, interrogating-call session control function (ICSCF) network elements, and agent-call session elements according to their functions.
  • SCSCF serving-call session control function
  • ICSCF interrogating-call session control function
  • agent-call session elements according to their functions.
  • Control function proxy-call session control function, PCSCF
  • CSCF CSCF
  • SCSCF SCSCF
  • ICSCF ICSCF
  • ICSCF ICSCF
  • SCSCF is the service processing node of the IMS network, responsible for the IMS network registration of terminal devices and related media service processing.
  • the PCSCF is located in the visited network and is an edge network node of the IMS network. It can also be the entry node for users to access the IMS network.
  • the role of PCSCF in the IMS network is similar to executing proxy services. Whether it is information from the terminal device or information sent to the terminal device, it must be forwarded through the P-CSCF.
  • the PCSCF may be responsible for the forwarding of SIP signaling between the SIP user and the home network.
  • ICSCF is located in the home network and is the unified entry point of the home network.
  • ICSCF can connect SCSCF and PCSCF to provide the terminal device with an entrance to the home network.
  • PCSCF can forward messages from the terminal device to ICSCF, and ICSCF forwards messages from the terminal to the PCSCF.
  • Device messages are sent to SCSCF.
  • the ICSCF may be responsible for allocating SCSCFs serving users or querying SCSCFs serving users.
  • ICSCF/SCSCF is connected to the PCSCF in the local network through the Mw interface.
  • PCSCF Compared with the media plane network elements that provide media services, PCSCF, SCSCF, and ICSCF are all control plane network elements. From a functional perspective, it can be considered that PCSCF is an access control plane network element, and ICSCF is an interoperability control plane access network element. It can be understood that PCSCF, SCSCF, and ICSCF can be independently configured in different entities or integrated in the same entity. Hereinafter, for ease of understanding and explanation, PCSCF, SCSCF, and ICSCF are collectively referred to as CSCF.
  • the media plane network element can be connected to the call control function network element through the media gateway control network element.
  • the media gateway control network element can be understood as a gateway that enables communication between IMS users and client users. Call control signaling from client users all points to the media gateway control network element.
  • the media gateway control network element is mainly responsible for carrying out the integrated services digital network (ISDN) user part or carrying irrelevant call control and session initialization protocols (session). initiation protocol (SIP) protocol and forward the session to IMS.
  • ISDN integrated services digital network
  • SIP initiation protocol
  • the media gateway control network element may be a media gateway control function (MGCF) network element.
  • the application service network element may still be the MGCF, or may have other names, which are not limited by the embodiments of this application.
  • MGCF is connected to the P-CSCF/I-CSCF network element/S-CSCF network element in the local network.
  • the media plane network element can also be connected to the call control function network element through the interconnection boundary point control network element.
  • the interconnection boundary point control network element is the boundary functional entity of the control plane between two operator networks.
  • the interconnection border point control network element may be an interconnection border control function (IBCF) network element.
  • IBCF network elements/TrGW are deployed between different IMS core networks or between IMS core networks and other IP networks, and IP relays are used to connect the networks. IBCF is connected to PCSCF/ICSCF/SCSCF in this network.
  • the signaling plane of IBCF is connected to other networks through Ici interface.
  • the media plane (TrGW) of IBCF network element is connected to other networks through Izi interface.
  • Each operator can select an interworking node based on the nature of the calling user. For example, when the calling user is an IMS user, the interworking method is adopted through the IBCF network element/TrGW.
  • the multimedia system entrance network element can be proxy CSCF (Proxy-CSCF, P-CSCF), or have other names.
  • proxy CSCF Proxy-CSCF, P-CSCF
  • the P-CSCF forwards the SIP transaction proxy from the visited access network to the S-CSCF of its home network (according to the information recorded during registration).
  • P-CSCF is responsible for IP bearer (may also be at other granularities, such as sessions, data flows, etc.) resource authentication, network address translation (Network Address Translation, NAT) and QoS management functions of the IMS local access network, for IMS provides end-to-end service guarantee.
  • IP bearer may also be at other granularities, such as sessions, data flows, etc.
  • resource authentication may also be at other granularities, such as sessions, data flows, etc.
  • network address translation Network Address Translation, NAT
  • QoS management functions of the IMS local access network for IMS provides end-to-end service guarantee.
  • the multimedia system entrance network element can still be P-CSCF, or have other names, which is not limited by this application.
  • Media plane network element also called media plane functional network element, it refers to the functional network element that can provide media plane services.
  • Media plane network elements can use their own media capabilities to provide media streaming services for terminal devices.
  • a media plane network element exposes its media capabilities to other network entities (such as a control plane network element) through SBI, other network entities can indirectly provide media streaming services for terminal devices.
  • media plane network elements may include media processing network elements on the access side, media processing network elements on the center side, media processing network elements on the interworking side, and so on.
  • the media processing network element on the access side can implement functions such as user media access proxy and forwarding, NAT traversal, and audio codec conversion.
  • the media processing network element on the access side includes an IMS access gateway (IMS Access gateway, IMS-AGW).
  • IMS Access gateway IMS-AGW
  • the media processing network element on the interoperability side can realize media interoperability between IMS and other networks.
  • the media processing network element on the interoperability side may include a transition gateway (TrGW), which is used to implement interoperability between IMS and other IP network media planes.
  • the media processing network element on the interoperability side may include an IP multimedia gateway (IM-MGW), which can realize interoperability between the IMS network and other non-IP network media planes.
  • IM-MGW IP multimedia gateway
  • the media processing network element on the center side can provide media resources for media plane services, such as audio playback resources, call collection resources, voice conference resources, DC resources, XRM resources, etc.
  • the media processing network element on the center side may include a multimedia resource function processor (MRFP).
  • MRFP multimedia resource function processor
  • the deployment of MRFP to the center side is taken as an example.
  • MRFP can also be deployed on the access side.
  • the media on the access side Processing network elements may also include MRFP.
  • the media plane network element may be a physical network element or a logical network element (or virtual network element).
  • media plane network elements can be divided into converged media plane network elements and non-converged media plane network elements.
  • the former refers to media plane network elements that can provide multiple media plane services, such as providing access at the same time.
  • the latter refers to network elements that provide a single media plane service. For example, media plane services that only provide access services.
  • the media plane network element may be a unified media plane network element specified in the 3GPP standard or a unified media plane function (unified media function, UMF) network element.
  • UMF unified media function
  • Each UMF can register its own network function service (NFS) information to the NRF network element.
  • NFS network function service
  • the media services provided by different UMFs may be different or the same.
  • UMF_1, UMF_2 and UMF_3 are three UMFs.
  • the media plane services that UMF_1 can provide include conference services and speech recognition services; the media plane services that UMF_2 can provide include network address translation services, audio playback services, and media processing services; the media plane services that UMF_3 can provide include network addresses. Translation services and audio playback services.
  • each UMF also registers its own identification information on the NRF network element.
  • NRF can save information of each UMF. It can be understood that the NRF can store the NFS information of the UMF in correspondence with the identification information of the UMF, so that the NRF can clarify the services that each UMF can provide. It can be understood that in addition to NFS information and identification information, UMF information may also include other information. The embodiments of this application focus on the media services that each UMF can provide, so other information about the UMF is not introduced.
  • UMF can provide media streaming services for UE_O and can also provide media streaming services for UE_T.
  • UE_O and UE_T and network elements such as UMF, NRF, PCSCF_O, PCSCF_T in the network interact with each other, so that the necessary media transmission channel (or connection) between UMF and UE_O and/or UE_T is established. So that UMF provides media streaming services to UE_O and/or UE_T.
  • the media endpoint of a UMF interconnecting with the UE and the media endpoints of the UMF interconnecting with other UMFs are connected by default.
  • the media endpoint connected to the UE receives the information and forwards it to the media endpoints connected to the UMF and other UMFs by default.
  • the media endpoint connected to the UE receives the information and can broadcast the information.
  • the media endpoint connected to other UMFs receives information and forwards it to the media endpoint connected to the UMF and UE by default.
  • media endpoints connected to other UMFs receive information and can broadcast the information.
  • NRF Network storage function network element, which can be used to collect specific information of network entities, such as the services that network entities can provide, identification information of network implementation, etc.
  • network storage function network elements can collect information such as services provided by media plane network elements.
  • the network function storage network element can be the network repository function (NRF) network element defined by the 3GPP standard specification.
  • NRF network repository function
  • the network function storage network element may still be an NRF, or may have other names, which are not limited by the embodiments of this application.
  • AS Application service network element, which can be used to obtain information about the initial access media plane network element, and can also request the media plane network element to provide media plane services.
  • the application service network element can be an (application server, AS) network element.
  • AS application server
  • application service network elements may still be ASs, or may have other names, which are not limited by the embodiments of this application.
  • AS is the uppermost application layer device in the IMS system.
  • AS and CSCF interact through the standard SIP protocol, and then Realize the triggering and execution of various network services and provide various business logic control functions.
  • the AS is divided into the calling side AS (denoted as AS_O) and the called side AS (denoted as AS_T);
  • the PCSCF network element is divided into the calling side PCSCF (denoted as PCSCF_O) and the called side PCSCF network element (denoted as PCSCF_O).
  • PCSCF_T the terminal equipment is divided into the calling side terminal equipment (denoted as UE_O) and the called side terminal equipment (denoted as UE_T).
  • UMF can be connected with NRF, PCSCF_O, PCSCF_T, UE_O and UE_T.
  • NRF can be connected with PCSCF_O and PCSCF_T.
  • UE_O can be connected to PCSCF_O
  • UE_T can be connected to PCSCF_T
  • AS_O can be connected to AS_T and PCSCF_O
  • AS_T can be connected to AS_O and PCSCF_T.
  • the interfaces between each network element in Figure 1 can refer to the existing interface protocol definitions and will not be described again here.
  • Figure 1 is only an example.
  • the IMS network applicable to the embodiments of this application is not limited to only including the network elements shown in Figure 1, but may also include other devices not shown in Figure 1, such as SCSCF, etc., which will not be listed here.
  • the distribution form of each network element in Figure 1 is only exemplary, and the embodiment of the present application does not limit the distribution form of each network element.
  • the above network element can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (for example, a cloud platform).
  • Media plane service also called media service, it refers to network services provided to network entities (such as control plane network elements) based on service-based interface (SBI).
  • the implementation of the network service or the process of providing the network service includes providing media-related services, such as media streaming services and media processing services, to the terminal equipment in the call service (calling terminal equipment and/or called terminal equipment) etc., for example, the color ringback service oriented to the terminal equipment of the call service initiator, the color ringback service oriented to the terminal equipment of the call service receiver, etc.
  • media plane services can be divided into three categories: one is resource services, the other is access services, and the third is interoperability services, which are introduced as follows.
  • Resource services can also be called media application services or media resource services.
  • Resource services can also be understood as services that require the provision of media resources, such as call collection (referring to receiving numbers input by terminal devices, such as menu numbers, etc.) services, audio playback (pointing to terminal devices to play audio content) services, and voice conferencing services, video conferencing services, data channel (DC) services, extended reality management (extended reality management, XRM) services, etc.
  • the implementation of resource services or the process of providing resource services includes providing resource media streaming services, such as ring back tone services, to terminal devices in the call service.
  • Access services are mainly services that help terminal equipment in call services realize NAT traversal of media streams. Accordingly, the implementation of access services or the process of providing access services includes providing access media streaming services, such as NAT traversal services, to terminal devices in call services.
  • Interoperability services mainly help terminal equipment in the call service realize network address conversion of media streams, for example, conversion of IPv4 addresses and IPv6 addresses, so that the terminal equipment can communicate with the peer network in the call service. Accordingly, the realization of interoperability services or the process of providing interoperability services includes providing interoperability media streaming services, such as address translation services, to terminal devices in call services.
  • the network-side equipment referred to in the embodiments of this application is a general term for the core network, gateway, access network equipment, etc. that are responsible for processing media plane services.
  • the specific devices included on the network side will be explained with examples below and will not be introduced in detail here.
  • Converged UMF and non-converged UMF An independent UMF can be the normalized result of multiple media plane network elements, which is called converged UMF. Relatively speaking, if a UMF is not the normalized result of multiple media plane network elements, then the UMF is a non-converged UMF. Alternatively, it can also be understood that converged UMF can provide multiple types of media plane services, and non-converged UMF can provide one type of media plane services.
  • Media resources refers to the computer resources used to provide resource services in MRFP.
  • the media processing network element on the center side provides resources used to provide resource services.
  • media resources may include audio playback resources, call collection resources, voice conference resources, video streaming resources, DC service resources, XRM service resources, etc.
  • Media capability refers to the ability to provide media plane services, or the ability to provide media resources required for media plane services, indicating whether the media plane network element can provide media resources.
  • the media plane network element has the ability to access media, which can also be understood as the media plane network element can realize the user's media access function.
  • the media plane network element has the ability to interoperate with the IP network. It can also be understood that the media plane network element can realize the interoperability between the IMS network and the media plane of other IP networks.
  • Media processing (operation) including media service processing (operation), media access processing (operation) and media interoperability processing (operation).
  • Media business processing (operation) mainly refers to the audio playback, call collection, voice conferencing, DC, and XRM provided by the media processing network element on the center side. Processing involved in other functions.
  • Media access processing (operation) mainly includes access processing provided by the media processing network element on the access side
  • media interoperability processing (operation) mainly includes interoperability processing provided by the media processing network element on the interworking side.
  • Media endpoint It is a logical entity located in the media gateway, such as the media plane network element, and can send/receive media streams and/or control streams.
  • media endpoints can be characterized by IP ports or asynchronous transfer mode (ATM) ports.
  • IP port includes the IP address and port number.
  • ATM asynchronous transfer mode
  • media plane network elements provide services (such as the above-mentioned access services, resource services, etc.) through media endpoints.
  • the media plane network element needs to establish a media transmission channel between the media endpoint on the media plane network element (i.e., the local end) and the media endpoint (i.e., the opposite end) on other network element entities (or UE). Therefore, , the media endpoint can be understood as one end of the media transmission channel.
  • the information of the media endpoint will include five-tuple information: such as the local address (local IP address and port number), the peer address (the peer IP address and port number). ) and the agreement.
  • Session description protocol It is designed to describe multimedia sessions. It is mainly used to describe session announcements, session invitations or other forms of multimedia session initialization. In order to initialize a multimedia session, participants need to be provided with media information, transmission addresses, etc. SDP provides a standard form for describing this information.
  • T_caller_UE@UMF_O refers to the media endpoint T_caller_UE in UMF_O.
  • T_caller_NW@UMF_O refers to the media endpoint T_caller_NW in UMF_O
  • T_called_UE@UMF_T refers to the media endpoint T_called_UE in UMF_T
  • T_called_NW@UMF_T refers to the media endpoint T_called_NW in UMF_T
  • T_called_media@UMF_T_Res refers to is the media endpoint T_called_media in UMF_T_Res.
  • UMF_T in Figure 2 refers to the UMF that provides access services in the embodiment of this application.
  • UMF_T_Res refers to the network element that provides special ringback tone service in the embodiment of this application.
  • the sound playback service is one of the resource-type services described in the embodiment of this application.
  • the service for UE_T to access the network is an access-type service.
  • the thin lines mark the signaling, and the thick lines mark the media streams.
  • the resource service provided by IMS is a special ringback tone service.
  • This special ringback tone service is used when the called terminal equipment wants to play different ringback tones for a specific calling terminal equipment.
  • the special ringback tone service needs to be triggered on the AS_T on the called terminal equipment side.
  • the called AS_T plays a special ringback tone for the caller, including the process of receiving the call request and returning the 180 message, and the process of playing the special ringback tone.
  • the process of playing the special ringback tone includes two possibilities.
  • the process of playing the special ringback tone is different based on whether the UMF that provides the access service and the UMF that provides the special ringback tone are the same UMF.
  • the following describes the process of the call request initiated by the caller and the 180 message returned by the called party with reference to Figure 2(a); the UMF that provides access services and the UMF that provides special ringback tone is introduced with reference to Figure 2(b).
  • the process of playing a special ringback tone is introduced. process.
  • Figure 2 (a) shows a schematic flow chart of the process of receiving a call request and returning a 180 message, including the following steps:
  • Each UMF initiates service registration with the NRF.
  • the UMF may send a registration request to the NRF, and the registration request may include UMF information.
  • the registration request may include UMF information.
  • the UMF information may include information on services that the UMF can provide.
  • UMF information also includes information used to identify UMF, such as UMF ID or IP address. It can be understood that the NFS information of the UMF has a corresponding relationship with the identification information of the UMF, so that the NRF can clarify the services that each UMF can provide based on the identification information of the UMF.
  • UMF_O can initiate service registration to NRF
  • UMF_T and UMF_T_Res can also initiate registration requests to NRF.
  • UE_O sends a call request to PCSCF_O.
  • PCSCF_O receives the call request sent by UE_O.
  • the call request is an invitation message in the call process.
  • the call request may include information about UE_O and UE_T information and session description protocol (session description portocol, SDP) information related to the call request.
  • SDP session description portocol
  • SDP is for UE_O.
  • SDP information included in the call request is recorded as SDP_UE_O.
  • SDP_UE_O may include media information of UE_O, such as media type (audio, time frequency, etc.), media format (H264 video, etc.), transmission address and port, and so on.
  • PCSCF_O initiates service discovery to the NRF.
  • the service discovery request is used to request information about the UMF that provides access services for UE_O.
  • PCSCF_O sends a service discovery request to NRF.
  • NRF receives the service discovery request sent by PCSCF_O.
  • the service discovery request can be used to request a UMF that can provide access services. It is understandable that information about multiple UMFs is registered on the NRF. Different UMFs may have different capabilities, provide different media resources, and may provide different media streaming services.
  • NRF can query the capabilities of each UMF to determine the media streaming services that each UMF can provide.
  • the NRF can obtain the stored capability information of each UMF, and the capability information can indicate the media services that the UMF can provide, so that the NRF determines the UMF that can provide access services based on the capability information of each UMF. Taking (a) of Figure 2 as an example, the NRF determines that the UMF that can provide access class services for UE_O is UMF_O.
  • NRF After NRF determines UMF_O, it can provide UMF_O information to PCSCF_O. For example, NRF sends a service discovery response to PCSCF_O, and the service discovery response includes UMF_O information, such as UMF_O identification information, IP address, etc.
  • PCSCF_O sends an allocation endpoint request to UMF_O.
  • UMF_O receives the allocation endpoint request sent by PCSCF_O.
  • This allocation endpoint request can be used to request the allocation of a media endpoint to UMF_O, or to request to obtain UMF_O's media endpoint information, such as the IP address and port of UMF_O's media endpoint, so that UE_O can access the network based on the media endpoint allocated by UMF_O.
  • the allocation endpoint request may include the SDP information in the first call request, namely SDP_UE_O.
  • UMF_O can determine the media endpoint (which can be recorded as T_caller_UE) to interface with UE_O based on SDP_UE_O, and determine the media endpoint (which can be recorded as T_caller_NW) to interface with other UMFs (UMF_T is used as an example in this embodiment).
  • UMF_O sends an allocation endpoint response to PCSCF_O.
  • PCSCF_O receives the allocation endpoint response sent by UMF_O.
  • the allocated endpoint response may include media endpoint information allocated by UMF_O.
  • UMF_O may be assigned two media endpoints, T_caller_UE and T_caller_NW.
  • T_caller_NW is the media endpoint on UMF_O connected to UMF_T.
  • the allocation endpoint response may include information of T_caller_UE and information of T_caller_NW.
  • the allocation response endpoint includes information of T_caller_UE@UMF_O and information of T_caller_NW@UMF_O.
  • T_caller_UE information may include the IP address and port number of T_caller_UE.
  • the information of T_caller_NW may include the IP address and port number of T_caller_NW.
  • PCSCF_O sends the invite message
  • PCFCS_T receives the invite message
  • the information element T_caller_UE may indicate the information of T_caller_UE
  • the information element T_caller_NW may indicate the information of T_caller_NW
  • the information element UMF_ori may indicate the information of UMF_O.
  • PCSCF_O forwards the invite message to PCSCF_T. It can be understood that PCSCF_O forwards the invite message to PCSCF_T through multiple network elements. These multiple network elements include network elements on the O side and network elements on the T side. When the O-side network element forwards the invite message to the T-side network element, the local-media in the invite message is deleted.
  • UE_T can also access the network through requests, that is, UE_T sends a request to the control plane network element on the T side, and PCSCF_T receives the request from UE_T and requests the NRF to provide access services for UE_T.
  • UMF may determine that the UMF capable of providing access class services for UE_T is UMF_T.
  • PCSCF_O and PCSCF_T can also request UMF_T to allocate media endpoints.
  • PCSCF_T sends a service discovery request to NRF.
  • NRF receives the service discovery request sent by PCSCF_T.
  • the service discovery request is used to obtain information about UMF with required access capabilities.
  • NRF sends a service discovery response to PCSCF_T.
  • PCSCF_T receives the service discovery response sent by NRF.
  • the service discovery response indicates the UMF with the required access capability.
  • the service discovery response includes UMF_T information.
  • PCSCF_T sends an allocation endpoint request to UMF_T.
  • UMF_T receives the allocation endpoint sent by PCSCF_T. ask.
  • the allocation endpoint request may include information about T_caller_NW@UMF_O, such as the IP address of T_caller_NW.
  • the allocation endpoint request may include SDP information including information of T_caller_NW@UMF_O.
  • UMF_T sends an allocation endpoint response to PCSCF_T.
  • PCSCF_T receives the allocation endpoint response sent by UMF_T.
  • the allocated endpoint response may include media endpoint information allocated by the UMF_T.
  • UMF_T may be assigned two media endpoints, T_called_UE and T_called_NW.
  • T_called_UE is the media endpoint on UMF_T that interfaces with UE_T
  • T_called_NW is the media endpoint on UMF_T that interfaces with other UMFs (the embodiment of this application takes UMF_O as an example).
  • the allocation endpoint response includes T_called_UE@UMF_T information and T_called_NW@UMF_T information.
  • the information of T_called_UE@UMF_T includes the IP address and port number of T_called_UE.
  • the information of T_called_NW@UMF_T includes the IP address and port number of T_called_NW.
  • PCSCF_T sends an invite message to UE_T.
  • UE_T receives the invite message sent by PCSCF_T.
  • PCSCF_T After receiving the invite message sent by AS_T, PCSCF_T can modify the IP address in the SDP information included in the invite message to the IP address of T_called_UE of UMF_T, and then forward it to UE_T. That is, the invite message sent by PCSCF_T to UE_T includes the information of T_called_UE@UMF_T, for example, the IP address and port number of T_called_UE.
  • UE_T establishes a connection with T_called_UE of UMF_T.
  • UE_T When UE_T receives the invite message, it can determine that the endpoint on UMF_T that interfaces with UE_T is T_called_UE based on the SDP information in the invite message, thereby establishing a connection with the T_called_UE of UMF_T.
  • UE_T sends a 180 message to PCSCF_T.
  • PCSCF_T receives the 180 message sent by UE_T.
  • the 180 message includes the information of T_called_UE@UMF_T.
  • AS_T receives call signaling.
  • This call signaling is associated with the call service between UE_O and UE_T. It can be understood that the access control plane network element or the interworking control plane network element sends the call signaling to the AS_T when triggered by the call signaling of the UE_T.
  • the call signaling may be a 180 message in the call process.
  • the call signaling includes media plane network element information used to provide media plane services for the call service and media endpoint information of the media plane network element, such as the IP address and port number of the media endpoint.
  • media plane network element information used to provide media plane services for the call service
  • media endpoint information of the media plane network element such as the IP address and port number of the media endpoint.
  • the information element T_called_UE may indicate the information of T_called_UE
  • the information element T_called_NW may indicate the information of T_called_UE
  • the information element UMF_ori may indicate the information of UMF_T.
  • PCSCF_T forwards the 180 message after constructing local-media, that is, call signaling. It can be seen that the call signaling carries the T_called_UE information of UMF_T and the T_called_NW information of UMF_T.
  • the call signaling received by AS_T may be the call signaling forwarded by PCSCF_T and SCSCF.
  • the call signaling received by AS_T may be a signaling received by AS_T.
  • the signaling includes information about T_called_NW@UMF_T, information about T_called_UE@UMF_T, information about UMF_T, and information about T_caller_UE@UMF_O.
  • AS_T can also receive call signaling by AS_T receiving multiple pieces of signaling.
  • AS_T can receive two pieces of signaling respectively, one of which includes the information of T_called_NW@UMF_T, the information of T_called_UE@UMF_T and the information of UMF_T, and the other signaling Includes T_caller_UE@UMF_O information. It can also be understood that the information of T_caller_NW@UMF_O and the information of UMF_T can be carried in one signaling or in different signaling.
  • AS_T may choose to provide a special ringback tone service for the UMF with special ringback tone capability.
  • the UMF that provides access services and the UMF that provides special ringback tones are one UMF, as shown in Figure 2 (b).
  • Figure 2 (b) shows a UMF that plays special
  • the ringback tone process includes the following steps:
  • AS_T sends request message #1 to NRF.
  • NRF receives request message #1 sent by AS_T.
  • AS_T determines that it needs to play audio to UE_O based on the information in the call signaling, for example, the identification of UE_O or UE_T (the reason is, for example: the user of UE_T has subscribed to the "voice broadcast" proliferation service , that is, the ring back tone service), and then determines that a UMF capable of playing sounds to UE_O is needed; for this purpose, AS_T can send request message #1 to the NRF to request a UMF capable of providing sound playing services.
  • UMF_T is UMF_1 in Figure 1.
  • the media plane services that UMF_1 can provide include conference services and speech recognition services, but cannot support audio playback services. If the audio playback service is provided for UE_O through UMF_T by default, the audio playback service will fail.
  • AS_T may send a request message #1 to the NRF. The request message #1 is used to request a media plane network element that can support the audio playback service required by AS_T.
  • request message #1 may be a service discovery request message.
  • UMF_T can also provide audio playback services
  • UMF_T can be preferred to provide audio playback services. This is because when UE_T is accessing the network, UMF_T has already allocated media endpoints, namely T_called_UE and T_called_NW. Therefore, the media transmission channel between UMF_T and UE_O can be established through T_called_NW without triggering the process of requesting to allocate media endpoints again, thus reducing the delay in providing audio playback services. Therefore, when UMF_T can provide audio playback services, NRF can give priority to UMF_T to provide audio playback services to minimize the delay.
  • AS_T may provide UMF_T information to NRF to instruct NRF to give priority to UMF_T.
  • request message #1 also includes preferred network element information indicating the initially selected UMF.
  • the initially selected UMF is UMF_T.
  • the preferred network element information may include the ID or IP address of UMF_T. It should be understood that the call signaling received by AS_T includes information of UMF_T, and is thus provided to the NRF through request message #1.
  • the preferred network element information includes information about UMF_T. It can also be understood that the preferred network element information implicitly indicates that UMF_T is used as the target UMF when both UMF_T and UMF_T_Res can provide audio playback services. That is, the target UMF and UMF_T may be the same network element, or the target UMF and UMF_T may be different network elements. (b) of Figure 2 takes the target UMF as UMF_T as an example.
  • Request message #1 includes network element requirement information, which may indicate required media plane service information, such as audio playback service information.
  • the information on the sound playback service may include a value indicating that a UMF that is capable of providing the sound playback service is required, to indicate that a UMF that can provide the sound playback service is required.
  • the network element requirement information may also indicate required media plane network element information.
  • NRF can select an appropriate media plane network element (called a target media plane network element) for the playback service based on the network element demand information, for example, UMF_T in (b) of Figure 2.
  • the request message #1 may be an HTTP request message.
  • the HTTP request message can be:
  • PreferredUMF indicates that the initially selected UMF is the preferred UMF.
  • its value can be the information of the initially selected UMF (such as UMF_T in this example), for example, the value is "UMF-beijing-haidian1 ”, indicating the initial access UMF carried from the aforementioned 180 message.
  • RequiredUMF indicates a UMF that needs to provide resource services. For example, the value is "playtone”, which indicates that a UMF with the ability to "play tone to the calling UE" is required.
  • NRF sends response message #1 to AS_T.
  • AS_T receives response message #1 sent by NRF.
  • the NRF determines a target UMF that can provide audio playback services from multiple UMFs based on the preferred network element information and network element demand information, that is, UMF_T. After determining the target UMF, the NRF sends response message #1 to AS_T.
  • the response message #1 may indicate the target UMF.
  • the NRF may obtain the stored NFS information of each UMF to determine the UMF that can provide the audio playback service based on the NFS information of each UMF.
  • NRF can obtain the capability information of UMF_T first based on the preferred network element information, and thereby determine whether UMF_T can provide audio playback services based on the capability information of UMF_T. If UMF_T can provide audio playback services, then NRF determines UMF_T as the target UMF, that is, the target UMF and UMF_T are the same network element.
  • (b) of Figure 2 mainly considers the target UMF and UMF_T is the case of the same network element.
  • the response message #1 may include UMF_T information, such as the ID or IP address of the UMF_T; or the response message #1 may also include a feedback indication. If response message #1 includes a feedback indication, for AS_T, the target UMF may be UMF_T by default.
  • response message #1 may be an HTTP response message.
  • the HTTP response message could be:
  • the field “nfInstances” represents the information of UMF (that is, UMF_T) that meets the requirements of the playback service.
  • “nfInstanceId” is a field belonging to the field “nfInstances”, which represents an ID that uniquely identifies UMF. For example, the value is "UMF-beijing-haidian1" (consistent with the specified value in request message #1).
  • AS_T determines that the target UMF and UMF_T are the same network element.
  • AS_T can determine based on the information included in the received response message #1 that the target UMF that provides resource-type services and the UMF_T that provides access-type services are the same network element.
  • AS_T sends a 180 message to AS_O.
  • AS_O receives the 180 message sent by AS_T.
  • AS_T receives response message #1 and can construct SDP information, that is, assign the IP address in the SDP information to the IP address of UMF_T's T_called_NW, assign the port in the SDP information to the port number of UMF_T's T_called_NW, and then send the SDP information to AS_O. 180 messages.
  • AS_T can pass the IP address of T_called_NW to AS_O through the 180 message.
  • AS_T can send a 180 message carrying the IP address of T_called_NW to SCSCF_T, and SCSCF_T forwards the 180 message carrying the IP address of T_called_NW to SCSCF_O.
  • SCSCF_O forwards the 180 message carrying the IP address of T_called_NW to AS_O.
  • AS_O sends a 180 message to PCSCF_O.
  • PCSCF_O receives the 180 message sent by AS_O.
  • the 180 message carries the same content as the 180 message of S419, that is, the 180 message also includes the T_called_NW information of UMF_T.
  • PCSCF_O indicates to UMF_O that the T_caller_NW of UMF_O is connected to the T_called_NW of UMF_T.
  • PCSCF_O sends the 18x message to UE_O.
  • UE_O receives the 18x message sent by PCSCF_O.
  • PCSCF_O can replace the IP address in the SDP information included in the 180 message received from AS_O with the IP address of T_caller_UE, generate a new 18x message, and then forward it to UE_O.
  • an 18x message may be a 183 message.
  • the T_caller_NW of UMF_O establishes a connection with the T_called_NW of UMF_T.
  • T_caller_NW when T_caller_NW is connected to T_called_NW, the channel connection between UMF_O and UMF_T can be realized, thereby realizing the channel connection between UE_O and UMF_T.
  • T_caller_UE of UMF_O establishes a connection with UE_O.
  • PRACK request message/200 message is exchanged between UE_O and UE_T.
  • the PRACK request message/200 message is carried through two signalings, one signaling carries the PRACK request message, and the other signaling carries the 200 message.
  • the 200 message can be considered as the response message of the PRACK request message.
  • UE_O receives the 18x message from PCSCF_O and can send the PRACK request message/200 message to PCSCF_O, and PCSCF_O sends the PRACK request message/200 message to AS_O.
  • AS_O receives the PRACK request message/200 message and sends the PRACK request message or 200 message to AS_T.
  • AS_T receives the PRACK request message/or 200 message and can determine that the T_caller_NW of UMF_O and the T_called_NW of UMF_T have established a connection.
  • AS_T instructs UMF_T to play audio to UE_O.
  • AS_T responds to determining that the T_caller_NW of UMF_O and the T_called_NW of UMF_T have established a connection, Instruction information may be sent to UMF_T, and the instruction information may instruct UMF_T to provide a sound playback service. It may also be understood that the instruction information may instruct UMF_T to start sound playback.
  • the indication information may include information of T_called_NW of UMF_T to instruct T_called_NW to play an announcement to UE_O.
  • UMF_T sends the audio stream to UE_O.
  • UMF_T After receiving the indication information, UMF_T sends the audio stream to UE_O.
  • FIG. 3 is a schematic diagram showing the establishment of a media transmission channel connection.
  • UMF_O is a UMF that can provide both access-type media streaming services for UE_O and resource-type media streaming services for UE_T and/or UE_O.
  • UMF_T is a UMF that can provide both access-type media streaming services for UE_T and resource-type media streaming services for UE_O/UE_T. It can also be understood that the UMF capable of providing resource-type media streaming services for UE_T is the UMF initially selected by UE_T to provide access-type media streaming services.
  • the UMF capable of providing resource-type media streaming services for UE_O is the UMF initially selected to provide access-type media streaming services for UE_O.
  • UMF_T since UE_T is joining the call session, UMF_T has already allocated a media endpoint to interface with UE_T (denoted as T_called_UE) and a media endpoint to interface with other UMFs (denoted as T_called_NW). Therefore, PCSCF_T does not need to trigger the process of requesting the allocation of endpoints to UMF_T. In the same way, PCSCF_O does not need to trigger the process of requesting endpoint allocation to UMF_O.
  • the UMF that provides the access service and the UMF that provides the special ringback tone are not one UMF, as shown in Figure 2(c).
  • the UMF shown in Figure 2(c) is another UMF.
  • a process for playing a special ringback tone including the following steps:
  • AS_T sends request message #2 to NRF.
  • NRF receives request message #2 sent by AS_T.
  • the request message #2 is the same as the request message #1 shown in the above-mentioned S215a, and will not be described again here.
  • the difference between the process shown in (c) of FIG. 2 and the process shown in (b) of FIG. 2 is that the target UMF is UMF_T_Res as an example.
  • NRF sends response message #2 to AS_T.
  • AS_T receives response message #2 sent by NRF.
  • the NRF determines the target UMF that can provide audio playback services from multiple UMFs based on the preferred network element information and network element demand information, that is, UMF_T_Res. After determining the target UMF, the NRF sends response message #2 to AS_T. The response message #2 may indicate the target UMF.
  • the NRF may obtain the stored NFS information of each UMF to determine the UMF that can provide the audio playback service based on the NFS information of each UMF.
  • NRF can obtain the capability information of UMF_T first based on the preferred network element information, and thereby determine whether UMF_T can provide audio playback services based on the capability information of UMF_T. If UMF_T can provide audio playback services, then NRF determines UMF_T as the target UMF, that is, the target UMF and UMF_T are the same network element. On the contrary, if the UMF_T cannot provide the audio playback service, then the NRF obtains the stored capability information of other UMFs, thereby selecting a UMF that can provide the audio playback service.
  • the NRF can select a UMF that can provide audio playback services as the target UMF.
  • the target UMF and UMF_T are not the same network element.
  • NRF preferably considers UMF_T, which can minimize the delay of the playback service on the premise of reducing the failure of the playback service.
  • NRF can obtain the capability information of UMF_1 and determine that UMF_1 cannot provide audio playback services. Subsequently, NRF can obtain the capability information of UMF_2 and the capability information of UMF_3, and then determine that the services that UMF_2 can provide include network address translation services, audio playback services, and media processing services, and the services that UMF_3 can provide include network address translation services and audio playback services. .
  • the network function storage network element can determine UMF_2 or UMF_3 as the target UMF, that is, UME_T_Res.
  • response message #2 may be an HTTP response message.
  • the HTTP response message could be:
  • the field “nfInstances” represents the information of UMF (that is, UMF_T_Res) that meets the requirements of the playback service.
  • “nfInstanceId” is a field belonging to the field “nfInstances”, which represents an ID that uniquely identifies UMF. For example, the value is "UMF-beijing-haidian2" (which is inconsistent with the specified value in request message #2).
  • AS_T determines that the target UMF and UMF_T are not the same network element.
  • AS_T may determine based on the information included in the received response message #2 that the target UMF providing resource-type services and the UMF_T providing access-type services are not the same network element.
  • AS_T sends request message #3 to UMF_T_Res.
  • UMF_T_Res receives request message #3 sent by AS_T.
  • This request message #3 may be used to request an allocation of a media endpoint (eg, called a target media endpoint) to UMF_T_Res.
  • the target media endpoint is T_called_media.
  • the request message #3 is used to request a target media endpoint that provides a playback service, or is used to request target media endpoint information.
  • the target media endpoint information may include the IP address and port number used by UMF_T_Res to provide audio playback services. It can be understood that the embodiment of the present application does not limit the specific name of request message #3.
  • request message #3 may also be called an allocation endpoint request message.
  • the request message #3 may include media endpoint information for UMF_O to interface with the T-side UMF.
  • the media endpoint information that connects UMF_O to the T-side UMF is the T_caller_NW information of UMF_O.
  • request message #3 may include SDP information including the IP address and port number of UMF_O's T_caller_NW.
  • UMF_T_Res receives request message #3 and can allocate the target media endpoint, such as T_called_media. Similar to request message #2, request message #3 is also an HTTP message.
  • UMF_T_Res sends response message #3 to AS_T.
  • AS_T receives response message #3 sent by UMF_T_Res.
  • This response message #3 may also be called a service discovery response message.
  • Response message #3 may indicate that UMF_T_Res is the target media endpoint allocated to provide the playback service, that is, T_called_media.
  • response message #3 may include information of T_called_media of UMF_T_Res, such as the IP address and port number of T_called_media.
  • AS_T learns the T_called_media information of UMF_T_Res and can forward the T_called_media information to PCSCF_O. For example, AS_T can forward the information of T_called_media to AS_O, and AS_O then forwards the information of T_called_media to PCSCF_O.
  • AS_T sends a 180 message to AS_O, and accordingly, AS_O receives the 180 message sent by AS_T.
  • AS_T receives response message #3 and can construct SDP information, that is, assign the IP address in the SDP information to the IP address of T_called_media of UMF_T_Res, assign the port in the SDP information to the port number of T_called_media of UMF_T_Res, and then send the SDP information to AS_O. 180 messages.
  • AS_T can pass the IP address of T_called_media to AS_O through the 180 message.
  • AS_T can send a 180 message carrying the IP address of T_called_media to SCSCF_T, and SCSCF_T forwards the 180 message carrying the IP address of T_called_media to SCSCF_O.
  • SCSCF_O forwards the 180 message carrying the IP address of T_called_media to AS_O.
  • AS_O sends a 180 message to PCSCF_O.
  • PCSCF_O receives the 180 message sent by AS_O.
  • the 180 message carries the same content as the 180 message of S220a, that is, the 180 message also includes the T_called_media information of UMF_T_Res.
  • PCSCF_O indicates to UMF_O that the T_caller_NW of UMF_O is connected to the T_called_media of UMF_T_Res.
  • PCSCF_O sends the 18x message to UE_O.
  • UE_O receives the 18x message sent by PCSCF_O.
  • PCSCF_O can replace the IP address in the SDP information included in the 180 message received from AS_O with the IP address of T_caller_UE, generate a new 18x message, and then forward it to UE_O.
  • an 18x message may be a 183 message.
  • T_caller_NW of UMF_O establishes a connection with T_called_media of UMF_T_Res.
  • T_caller_UE of UMF_O establishes a connection with UE_O.
  • AS_T receives the PRACK request message/or 200 message and can determine that the T_caller_NW of UMF_O and the T_called_media of UMF_T_Res have established a connection.
  • AS_T instructs UMF_T_Res to play audio to UE_O.
  • AS_T may send indication information to UMF_T_Res.
  • the indication information may instruct UMF_T_Res to provide a playback service. It may also be understood that the indication information may instruct UMF_T_Res to start playback. sound.
  • the indication information may include T_called_media information of UMF_T_Res to instruct T_called_media to play audio to UE_O.
  • UMF_T_Res sends the audio stream to UE_O.
  • UMF_T_Res After receiving the indication information, UMF_T_Res sends the audio stream to UE_O.
  • FIG. 4(a) is another schematic diagram showing the establishment of a media transmission channel connection.
  • (a) of FIG. 4 is another schematic diagram showing the establishment of a media transmission channel connection.
  • Figure 4 takes UMF_O, UMF_T, UMF_T_Res, UE_O, and UE_T as an example.
  • the control plane network element on the O side (that is, the calling side) can request the UMF to provide media streaming services for UE_O and/or UE_T.
  • UE_T can request the network side to provide media streaming services through the control plane network element on the T side (that is, the called side).
  • UMF_O is a UMF that can provide access-type media streaming services for UE_O and can also provide resource-type media streaming services for UE_T and/or UE_O.
  • UMF_T is the UMF initially selected by the T-side control plane network element (such as PCSCF_T) for the T-side when UE_T joins the call session, and can provide access media streaming services for UE_O and/or UE_T.
  • UMF_T_Res is a UMF capable of providing resource-based media streaming services for UE_O and/or UE_T.
  • the initially selected UMF can also be understood as the UMF selected by the side where the PCSCF network element is located when the PCSCF network element applies for a media endpoint for the first time during a call session.
  • UMF_T When UE_T joins the call session, UMF_T will allocate media endpoints to interface with UE_T (recorded as T_called_UE) and media endpoints to interface with other UMFs (recorded as T_called_NW). Similarly, when UE_O joins a call session, UMF_O will allocate a media endpoint (recorded as T_caller_UE) connected to UE_O and a media endpoint connected to other UMFs (recorded as T_caller_NW). And during the above access process, UE_T will connect with T_called_UE, and UE_O will connect with T_caller_UE. Therefore, when T_called_NW and T_caller_NW establish a connection, the connection of the media transmission channel between UE_O and UE_T can be realized.
  • PCSCF_T when UMF_T_Res is able to provide media streaming services for UE_T, since the initially selected UMF is UMF_T, PCSCF_T does not know the media endpoint on UMF_T_Res. In this case, PCSCF_T requests to obtain the media endpoint on UMF_T_Res to realize the connection of the media transmission channel between UMF_T_Res and UE_O and/or UE_T. For example, PCSCF_T can request allocation of media endpoints from UMF_T_Res, UMF_T_Res can allocate media endpoints T_called_media, and UMF_T_Res provides media streaming services through T_called_media. When T_called_media is connected to T_caller_NW, it can provide media streaming services for UE_O.
  • UMF_T cannot provide resource-based media streaming services.
  • PCSCF_O can request the allocation of media endpoints from UMF_O_Res, and UMF_O_Res can allocate media endpoints T_caller_media.
  • UMF_O_Res is provided through T_caller_media.
  • T_caller_media is connected to T_called_NW, it can provide media streaming services for UE_T.
  • the media transmission channel is shown in (b) of Figure 4.
  • Figure 4 (b) is another schematic diagram showing the establishment of a media transmission channel connection. For details, refer to the description of Figure 4 (a). The difference lies in the main Resource services are provided by UMF_O_Res on the calling side, which will not be described here.
  • step S217a needs to be executed to determine that the received UMF information is UMF_T information, and after step S217a is executed, there is no need to request the allocation of a new media endpoint, and steps S218a to S224a are directly executed to establish the connection between the media endpoints. Connect, and perform S225a to instruct the media endpoint on UMF_T to perform the service.
  • step S217b determines that the received UMF information is not UMF_T information but UMF_T_Res information, and request UMF_T_Res to allocate a media endpoint by executing step S218b, and then execute steps S220b to S226b to establish the media connection between endpoints, and perform S227b to instruct the media endpoint on UMF_T_Res to perform the service.
  • this application provides a communication method in order to simplify the operation of the AS and improve the AS processing efficiency in the process of providing resource services.
  • for indicating may include direct indicating and indirect indicating.
  • indication information When describing that certain indication information is used to indicate A, it may include that the indication information directly indicates A or indirectly indicates A, but it does not mean that the indication information must carry A.
  • the information indicated by the indication information is called information to be indicated.
  • the information to be indicated can be directly indicated, such as the information to be indicated itself or the information to be indicated. Index indicating information, etc.
  • the information to be indicated may also be indirectly indicated by indicating other information, where there is an association relationship between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while other parts of the information to be indicated are known or agreed in advance.
  • Instructions for specific information can also be achieved with the help of a pre-agreed (for example, protocol stipulated) arrangement order of each piece of information, thereby reducing the instruction overhead to a certain extent.
  • the common parts of each piece of information can also be identified and indicated in a unified manner to reduce the instruction overhead caused by indicating the same information individually.
  • the “save” involved in the embodiments of this application may refer to saving in one or more memories.
  • the one or more memories may be provided separately, or may be integrated in an encoder or decoder, processor, or communication device.
  • the one or more memories may also be partially provided separately and partially integrated in the decoder, processor, or communication device.
  • the type of memory can be any form of storage medium, and this application is not limited thereto.
  • the "protocol” involved in the embodiments of this application may refer to a standard protocol in the communication field.
  • it may include the NR protocol and related protocols applied in future communication systems. This application does not limit this.
  • Figure 5 is a schematic flow chart of a communication method provided by an embodiment of the present application, including the following steps:
  • the media plane network element that provides access services for the first terminal and the second terminal can be determined.
  • the first terminal is the calling terminal and the second terminal is the called terminal; or the first terminal is the called terminal and the second terminal is the calling terminal.
  • the process of determining the media plane network element that provides access services for the first terminal and the second terminal can refer to the process shown in (a) of Figure 2 above.
  • the media endpoint that provides access services can follow the process shown in Figure 2(a).
  • the identifiers shown in (a) of 2 (such as T_caller_UE, T_caller_NW, T_called_UE and T_called_NW) will not be described again here.
  • the first terminal is the calling terminal (such as UE_O shown in Figure 2(a)), and the second terminal is the called terminal (such as UE_T shown in Figure 2(a)) Describe as an example. It should be understood that when the first terminal is UE_T and the second terminal is UE_O, the steps performed by UE_O in the following embodiments can be replaced by UE_T, and the steps performed by UE_T can be replaced by UE_O, which will not be repeated. illustrate.
  • the media plane network elements determined to provide access services for UE_O and UE_T include: the UMF determined to provide access services for UE_O (for example, as shown in (a) of Figure 2 (shown as UMF_O), and determine to provide access class service UMF (such as UMF_T shown in (a) of Figure 2) for UE_T.
  • the embodiment mainly involves how the application server selects the media plane network element that provides the resource type service after receiving the call signaling, and how to implement the resource type service.
  • the following description takes the called-side application server (for example, AS_T) selecting a UMF (for example, UMF_T/UMF_T_Res) that provides resource services as an example.
  • UMF for example, UMF_T/UMF_T_Res
  • AS_O the calling-side application server
  • UMF eg, UMF_O/O_Res
  • the steps performed by the called side application server are replaced by those performed by the calling side application server, and the steps performed by the media plane network element that provides resource class services on the called side are replaced by those performed by the media plane network element that provides resource class services.
  • the media plane network element of the service can be executed and will not be explained again.
  • the method flow shown in Figure 5 also includes:
  • the application server sends request message #1 to NRF.
  • NRF receives request message #1 sent by the application server.
  • step S215a Refer to the description of step S215a above, which will not be described again here.
  • the application server is an application server corresponding to the second terminal (eg, AS_T shown in Figure 5).
  • NRF sends the media plane network element information to AS_T.
  • AS_T receives the media plane network element information sent by NRF.
  • the media plane network element information sent by the NRF to AS_T may be UMF_T information (for example, refer to the information included in the response message #1 in the above step S216a), or may be UMF_T_Res information (for example, Refer to the information included in the response message #2 in step S216b above).
  • the media plane network element indicated by the media plane network element information is denoted as UMF_T/UMF_T_Res in the following.
  • the information of the media plane network element may be the identification (ID) of UMF_T/UMF_T_Res, or other information that can be used to identify UMF_T/UMF_T_Res, which is not limited in this application.
  • AS_T after AS_T receives the above-mentioned media plane network element information, it does not need to determine whether the UMF_T/UMF_T_Res indicated by the media plane network element information and the UMF_T that provides access services are the same UMF. It is understood that in this embodiment, AS_T does not know whether it is a converged scene or a non-converged scene, and directly requests UMF_T/UMF_T_Res to allocate media endpoints for providing resource services.
  • the method flow shown in Figure 5 also includes:
  • AS_T sends request information to UMF_T/UMF_T_Res.
  • UMF_T/UMF_T_Res receives the request information from AS_T.
  • AS_T does not need to determine the relationship between the media plane network element indicated by the received media plane network element information and the UMF_T that has been determined to provide access services, and directly initiates a media endpoint allocation request.
  • AS_T the operation process is simplified and the processing efficiency is improved.
  • fusion scenarios and non-fusion scenarios are no longer distinguished, and different scenarios are based on the same processing flow.
  • the UMF_T/UMF_T_Res is a UMF that provides resource services (for example, UMF_T shown in (b) of Figure 2 or UMF_T_Res shown in (c) of Figure 2).
  • This request information is used to request UMF_T/UMF_T_Res to allocate media endpoints used to provide resource-based services. It can also be understood that the request information is used to request the target media endpoint that provides the playback service, or that the request information is used to request the target media endpoint information.
  • the target media endpoint information may include the IP address and port number used by UMF_T/UMF_T_Res to provide audio playback services. Among them, the IP address and port number used by UMF_T/UMF_T_Res to provide the playback service can be understood as the IP address and port number included in the local address of the second media endpoint.
  • the embodiment of the present application does not limit the specific name of the request information.
  • the request information may also be called an allocation endpoint request message.
  • the request information may include the IP address connected to the second media endpoint on UMF_T/UMF_T_Res.
  • the request information includes a remote address, which can be understood as the address of the media endpoint that establishes a connection with the second media endpoint, and can be called the remote address of the second media endpoint.
  • the remote address included in the request information is the remote IP address and remote port information (eg, port number).
  • the request information includes media endpoint information for UMF_O to interface with the T-side UMF.
  • the media endpoint information connecting UMF_O to T-side UMF is the information of T_caller_NW of UMF_O.
  • the request information may include SDP information, and the SDP information includes the IP address of T_caller_NW of UMF_O.
  • the SDP information includes the IP address and port number of UMF_O's T_caller_NW.
  • the request information includes media endpoint information for UMF_T to interface with the T-side UMF.
  • the media endpoint information connecting UMF_T to T-side UMF is the T_called_NW information of UMF_T.
  • the request information may include SDP information, and the SDP information includes the IP address of the T_called_NW of the UMF_T.
  • the SDP information includes the IP address and port number of T_called_NW of UMF_T.
  • the above request information includes the IP address and port number of T_caller_NW, or the IP address and port number of T_called_NW.
  • the protection of this application The scope does not constitute any limitation.
  • the media endpoint information connected to the T-side UMF included in the request information can also be the information of other media endpoints, and no examples will be given here.
  • the request information also includes information about the first media endpoint, and the information about the first media endpoint includes information about the media endpoint used to provide access-type services.
  • the request information also includes information about T_called_NW, where T_called_NW is the media endpoint determined in step S501.
  • the information of T_called_NW may include the identifier of the UMF to which T_called_NW belongs (eg, UMF-beijing-haidian1) and the identifier of the T_called_NW (eg, T-2).
  • the request information is HTTP information.
  • the HTTP message could be:
  • imsRCIR represents the NFS that provides the Reserve and (or) Configure IMS Resource function
  • the field related_termination_UMF represents the information of the first media endpoint, which contains two parts: the first part is the UMF information to which it belongs, and the second part is the media endpoint identification.
  • the remote address 10.10.10.10:8888 can be understood as the IP address of T_caller_NW.
  • UMF_T/UMF_T_Res When UMF_T/UMF_T_Res receives the request information, it can determine whether the first media endpoint is a media endpoint on UMF_T/UMF_T_Res based on the information of the first media endpoint included in the request information.
  • the process shown in Figure 5 also includes:
  • UMF_T/UMF_T_Res determines whether the first media endpoint is a media endpoint on UMF_T/UMF_T_Res based on the information of the first media endpoint.
  • AS_T does not need to determine the relationship between the media plane network element indicated by the received media plane network element information and the UMF_T that has been determined to provide access services, and directly initiates the request information, and by
  • the request information carries the information of the first media endpoint, and the UMF_T/UMF_T_Res that receives the request information determines whether the UMF_T/UMF_T_Res is a UMF that can provide access services and resource services, or a UMF that provides resource services.
  • UMF_T/UMF_T_Res determines whether the first media endpoint is a media endpoint on UMF_T/UMF_T_Res according to the information of the first media endpoint, and obtains a determination result.
  • the determination result includes: the first media endpoint is a media endpoint on UMF_T/UMF_T_Res or The first media endpoint is not a media endpoint on UMF_T/UMF_T_Res.
  • the information of the first media endpoint includes UMF information to which the first media endpoint belongs and the identification of the first media endpoint.
  • the information of the first media endpoint includes an identifier of the first media endpoint, and the identifier of the first media endpoint includes UMF information to which the first media endpoint belongs.
  • UMF_T/UMF_T_Res can determine whether the first media endpoint is based on the UMF information to which the first media endpoint belongs. Media endpoint on UMF_T/UMF_T_Res.
  • UMF_T/UMF_T_Res determines that the UMF to which the first media endpoint belongs is UMF_T/UMF_T_Res based on the UMF information to which the first media endpoint belongs. Further, UMF_T/UMF_T_Res determines that the first media endpoint is UMF_T/UMF_T_Res based on the identifier of the first media endpoint. assigned endpoint.
  • UMF_T/UMF_T_Res determines the first media endpoint as the media endpoint on UMF_T/UMF_T_Res. It can be understood that the above judgment result is: the first media endpoint is a media endpoint on UMF_T/UMF_T_Res (or the first media endpoint belongs to UMF_T/UMF_T_Res).
  • the UMF_T/UMF_T_Res allocated with the second media endpoint for providing resource-based services is allocated with the media endpoint used for providing access-based services. That is to say, UMF_T/UMF_T_Res can provide access-based services.
  • the service can also provide resource services, which can be understood as the integration scenario mentioned above, that is, UMF_T/UMF_T_Res and UMF_T are the same UMF.
  • UMF_T/UMF_T_Res may not need to allocate a new media endpoint, but use the allocated first media endpoint as a resource for provisioning The second media endpoint of the class service.
  • the local address of the second media endpoint is the same as the local address of the first media endpoint, and the remote address of the second media endpoint and the remote address of the first media endpoint may be the same or different. It can be understood that the second media endpoint is determined by UMF_T/UMF_T_Res according to whether the first media endpoint belongs to the media plane network element.
  • the local address and the remote address are for a single media endpoint.
  • the local address refers to its own IP address and port in the quintuple
  • the remote address refers to the IP address and port in the quintuple.
  • the end address refers to the other party's IP address and port in the five-tuple.
  • the second media endpoint may be called a mirror media endpoint of the first media endpoint.
  • the first media endpoint is T_called_NW
  • the second media endpoint is T_called_NW’.
  • the first media endpoint and the second media endpoint are identified by different identification information. That is to say, even if UMF_T/UMF_T_Res does not allocate a new media endpoint, for the application server that applies to allocate the second media endpoint It does get information about a new media endpoint.
  • UMF_T/UMF_T_Res determines that the first media endpoint is not the media endpoint on UMF_T/UMF_T_Res.
  • the UMF_T/UMF_T_Res allocated to the second media endpoint for providing resource-based services is not allocated a media endpoint for providing access-based services. That is to say, UMF_T/UMF_T_Res cannot provide access services.
  • the entry service also provides resource services, which can be understood as the non-fusion scenario mentioned above, that is, UMF_T/UMF_T_Res and UMF_T are not the same UMF.
  • UMF_T/UMF_T_Res determines that the first media endpoint is not the media endpoint on UMF_T/UMF_T_Res
  • UMF_T/UMF_T_Res allocates a new media endpoint, similar to the allocation T_called_media shown in (c) of Figure 2 above .
  • the local address of the second media endpoint is different from the local address of the first media endpoint.
  • UMF_T/UMF_T_Res allocates the second media endpoint
  • the information of UMF_T/UMF_T_Res is recorded in the local memory. For example, as shown in Table 2 below:
  • the first media endpoint is the media endpoint on UMF_T/UMF_T_Res
  • the second media endpoint is the mirror media endpoint of the first media endpoint
  • UMF_T/UMF_T_Res is the UMF_T shown above.
  • the first media endpoint is not the media endpoint on UMF_T/UMF_T_Res.
  • UMF_T/UMF_T_Res is the UMF_T_Res shown above.
  • UMF_T/UMF_T_Res sends the information of the second media endpoint to the application server.
  • the method flow shown in Figure 5 also includes:
  • UMF_T/UMF_T_Res sends the information of the second media endpoint to AS_T.
  • AS_T receives the information of the second media endpoint from UMF_T/UMF_T_Res.
  • the information of the second media endpoint may be the IP address and port number of the second media endpoint.
  • the information of the second media endpoint is sent to AS_T through an HTTP response message.
  • the HTTP response message could be:
  • the field termination_id represents the unique identification of the second media endpoint.
  • the value T-2-Mir indicates that it is the mirror media endpoint of the first media endpoint T-2, or can be identified by other identification information. In this embodiment, it is not Make restrictions.
  • the local address of the second media endpoint is 9.9.9.9:9999, which is the same as the local address of T_called_NW.
  • steps S520 to S540 describe in detail how to select the media plane network element that provides resource-type services, and the process of allocating the second media endpoint for providing resource-type services to the media plane network element that provides resource-type services.
  • the resource class service can be implemented.
  • the process of providing resource services in this embodiment includes the following two methods:
  • UMF_T/UMF_T_Res provides resource services to UE_O
  • the second media endpoint on UMF_T/UMF_T_Res provides resource services.
  • Figure 6 is a schematic flow chart for providing resource services provided by an embodiment of the present application, including the following steps:
  • AS_T sends a 180 message to AS_O.
  • AS_O receives the 180 message sent by AS_T.
  • AS_T After AS_T receives the information of the second media endpoint, it can construct the SDP information, that is, assign the IP address in the SDP information to the IP address of the second media endpoint of UMF_T/UMF_T_Res, and assign the port in the SDP information to the second IP address of UMF_T/UMF_T_Res.
  • the port number of the media endpoint and then sends a 180 message including SDP information to AS_O. It can be understood that AS_T can pass the IP address of the second media endpoint to AS_O through the 180 message.
  • AS_T may send a 180 message carrying the IP address of the second media endpoint to SCSCF_T, and SCSCF_T forwards the 180 message carrying the IP address of the second media endpoint to SCSCF_O.
  • SCSCF_O forwards the 180 message carrying the IP address of the second media endpoint to AS_O.
  • AS_O sends a 180 message to PCSCF_O.
  • PCSCF_O receives the 180 message sent by AS_O.
  • the 180 message carries the same content as the 180 message of S602, that is, the 180 message also includes the information of the second media endpoint.
  • PCSCF_O indicates to UMF_O that the T_caller_NW of UMF_O is connected to the second media endpoint of UMF_T/UMF_T_Res.
  • PCSCF_O sends the 18x message to UE_O.
  • UE_O receives the 18x message sent by PCSCF_O.
  • PCSCF_O can replace the IP address in the SDP information included in the 180 message received from AS_O with the IP address of T_caller_UE, generate a new 18x message, and then forward it to UE_O.
  • an 18x message may be a 183 message.
  • the T_caller_NW of UMF_O establishes a connection with the second media endpoint of UMF_T/UMF_T_Res.
  • T_caller_UE of UMF_O establishes a connection with UE_O.
  • PRACK request message/200 message is exchanged between UE_O and UE_T.
  • AS_T receives the PRACK request message/or 200 message and can determine that the T_caller_NW of UMF_O and the second media endpoint of UMF_T/UMF_T_Res have established a connection.
  • AS_T sends indication information to UMF_T/UMF_T_Res.
  • UMF_T/UMF_T_Res receives indication information from AS_T.
  • AS_T may send indication information to UMF_T/UMF_T_Res, and the indication information may instruct UMF_T/UMF_T_Res to provide resource services.
  • the indication information may include information of the second media endpoint of UMF_T/UMF_T_Res to indicate that the second media endpoint is used to provide resource-based services.
  • UMF_T/UMF_T_Res determines that the local address and the remote address of the second media endpoint are different.
  • UMF_T/UMF_T_Res determines that the local address and the remote address of the second media endpoint are different.
  • UMF_T/UMF_T_Res provides resource services to UE_O.
  • UMF_T/UMF_T_Res is UMF_T as mentioned above, and the second media endpoint is T_called_NW as mentioned above, then UMF_T/UMF_T_Res provides the media stream corresponding to the resource class service to UE_O
  • the transmission path is shown in Figure 3.
  • UMF_T/UMF_T_Res is the UMF_T_Res mentioned above, and the second media endpoint is T_called_media mentioned above, then UMF_T/UMF_T_Res provides the media corresponding to the resource class service to UE_O
  • the streaming transmission path is shown in (a) of Figure 4 .
  • UMF_T/UMF_T_Res provides resource services to UE_T
  • the third media endpoint on UMF_T/UMF_T_Res provides resource services.
  • Figure 7 is another schematic flow chart for providing resource services provided by an embodiment of the present application, including the following steps:
  • AS_T sends an ACK message to PCSCF_T.
  • PCSCF_T receives the ACK message sent by AS_T.
  • the ACK message is a response message of the 200 message.
  • AS_T After AS_T receives the information of the second media endpoint, it can construct the SDP information, that is, assign the IP address in the SDP information to the IP address of the second media endpoint of UMF_T/UMF_T_Res, assign the port in the SDP information to the port number of the second media endpoint of UMF_T/UMF_T_Res, and then send the SDP information to PCSCF_T.
  • SDP information that is, assign the IP address in the SDP information to the IP address of the second media endpoint of UMF_T/UMF_T_Res, assign the port in the SDP information to the port number of the second media endpoint of UMF_T/UMF_T_Res, and then send the SDP information to PCSCF_T.
  • ACK message It can be understood that AS_T can transfer the IP address of the second media endpoint to PCSCF_T through the ACK message.
  • PCSCF_T indicates to UMF_T that the T_called_NW of UMF_T is connected to the second media endpoint of UMF_T/UMF_T_Res.
  • PCSCF_T sends an ACK message to UE_T.
  • UE_T receives the ACK message sent by PCSCF_T.
  • PCSCF_T can replace the IP address in the SDP information included in the ACK message received from AS_T with the IP address of T_called_UE, generate a new ACK message, and then forward it to UE_T.
  • AS_T sends indication information to UMF_T/UMF_T_Res.
  • UMF_T/UMF_T_Res receives indication information from AS_T.
  • the indication information may include information of the second media endpoint of UMF_T/UMF_T_Res to indicate that the second media endpoint is used to provide resource-based services.
  • UMF_T/UMF_T_Res determines that the local address and the remote address of the second media endpoint are the same.
  • UMF_T/UMF_T_Res determines that the local address and the remote address of the second media endpoint are the same.
  • UMF_T/UMF_T_Res provides the resource type service through the third media endpoint.
  • the third media endpoint is the media endpoint configured on UMF_T/UMF_T_Res that corresponds to the second media endpoint.
  • UMF_T/UMF_T_Res may determine the third media endpoint according to the information of the second media endpoint included in the indication information.
  • the above-mentioned UMF_T/UMF_T_Res is a UMF_T that provides access services
  • the above-mentioned second media endpoint is the mirror endpoint of T_called_NW shown above (for example, the local address of the second media endpoint is the same as the T_called_NW Same)
  • the third media endpoint is T_called_UE as shown above.
  • the corresponding relationship between T_called_NW and T_called_UE is stored in UMF_T/UMF_T_Res.
  • UMF_T/UMF_T_Res can determine T_called_UE based on the corresponding relationship and the information of T_called_NW.
  • UMF_T/UMF_T_Res determines that the local address and remote address of the second media endpoint are the same, where the remote address of the second media endpoint can be carried by the request information.
  • the IP address and The port number is obtained. It is stipulated in the embodiment of this application that when the local address of the second media endpoint allocated by UMF_T/UMF_T_Res is the same as the remote address, the third media corresponding to the second media endpoint configured on UMF_T/UMF_T_Res The endpoint provides the resource class service.
  • UMF_T/UMF_T_Res provides resource services to UE_T.
  • the application server carries information about the first media endpoint for providing access-type services in the request information requesting allocation of the second media endpoint for providing resource-type services, so as to facilitate the allocation of the second media endpoint.
  • the media plane network element of the two media endpoints determines whether the first media endpoint is a media endpoint on the media plane network element based on the information of the first media endpoint, and the media plane network element can allocate the second media endpoint according to the judgment result, where the first The media endpoint is the media endpoint on the media plane network element. It can be understood that the media plane network element that can provide resource services and the media plane network element that can provide access services are the same media plane network element, which corresponds to the determination of providing resources in the convergence scenario.
  • the media endpoint on the media plane network element can be understood as the media plane network element that can provide resource-type services and the media plane network element of access-type services are not the same.
  • Media plane network elements correspond to media plane network elements that are determined to provide resource services in non-converged scenarios. That is to say, in the above technical solution, the application server does not need to determine different processing methods based on whether the media plane network element that provides access services and the media plane network element that provides resource services are the same media plane network element.
  • the media plane network element of the media endpoint can be determined, thereby simplifying the processing difficulty of the application server and improving the processing efficiency of the application server.
  • devices in the existing network architecture are mainly used as examples for illustrative explanations (such as media network element, application server, etc.), it should be understood that the embodiment of the present application does not limit the specific form of the equipment. For example, devices that can achieve the same functions in the future are applicable to the embodiments of this application.
  • the methods and operations implemented by the media plane network element can also be implemented by components available for the media plane network element; the methods and operations implemented by the application server can also be implemented by components available for the media plane network element.
  • Application server component implementation
  • the communication method provided by the embodiment of the present application is described in detail with reference to FIGS. 5 to 7 .
  • the above communication methods are mainly introduced from the perspective of interaction between media plane network elements and application servers. It can be understood that, in order to implement the above functions, the media plane network elements and application servers include hardware structures and/or software modules corresponding to each function.
  • Embodiments of the present application can divide the transmitting end device or the receiving end device into functional modules according to the above method examples.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. middle.
  • the above integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods. The following is an example of dividing each functional module according to each function.
  • FIG. 8 is a schematic block diagram of a communication device 800 provided by an embodiment of the present application.
  • the communication device 800 may include a processing module 810 and a transceiver module 820.
  • a storage unit may also be included, which may be used to store instructions (code or programs) and/or data.
  • the processing module 810 and the transceiver module 820 can be coupled with the storage unit.
  • the processing module 810 can read the instructions (code or program) and/or data in the storage unit to implement the corresponding method.
  • Each of the above modules can be set up independently or partially or fully integrated.
  • the communication device 800 can correspondingly implement the behaviors and functions of the media plane network element in the above method embodiments.
  • the communication device 800 can be a media plane network element, or can be a component applied in the media plane network element (for example, a chip or a circuit), or it may be a chip or chipset in the media plane network element, or a part of the chip used to perform related method functions.
  • the communication device 800 implements the method performed by the media plane network element (eg, UMF_T/UMF_T_Res) in the embodiment of at least one of the figures in FIG. 5 to FIG. 7 .
  • the transceiver module 820 is used to perform the above-mentioned operations related to UMF_T/UMF_T_Res receiving and sending messages, for example: used to receive request information from the application server, the request information is used to request the allocation of the media plane network element for providing resource services.
  • the request information includes information about a first media endpoint used to provide access services; and is also used to send information about a second media endpoint to the application server, where the second media endpoint is the
  • the media plane network element is determined based on whether the first media endpoint belongs to the media plane network element.
  • the processing module 810 is used to perform operations of the above-mentioned UMF_T/UMF_T_Res except receiving and sending messages.
  • the first media endpoint belongs to the media plane network element, and the local address of the second media endpoint is the same as the local address of the first media endpoint.
  • the processing module 810 determines not to allocate a new media endpoint according to the fact that the first media endpoint belongs to the media plane network element, and uses the mirrored media endpoint of the first media endpoint as the Secondary media endpoint.
  • the first media endpoint does not belong to the media plane network element, and the local address of the second media endpoint is different from the local address of the first media endpoint.
  • the processing module 810 determines to allocate a new media endpoint as the second media endpoint based on the fact that the first media endpoint does not belong to the media plane network element.
  • the information about the first media endpoint includes the identity of the media plane network element to which the first media endpoint belongs and the identity of the first media endpoint.
  • the transceiver module 820 is also configured to receive instruction information from the application server.
  • the instruction information is used to instruct execution of the resource type service.
  • the instruction information includes the second media. Endpoint information; the processing module 810 is also configured to execute the resource service according to the instruction information.
  • the communication device 800 can correspondingly implement the behaviors and functions of the application server (such as AS_T) in the above method embodiments.
  • the communication device 800 can be an application server or a component applied in the application server. (such as a chip or circuit), or it can be a chip or a chipset in a network function storage network element or a part of the chip used to perform related method functions.
  • the communication device 800 implements the methods performed by AS_T in the embodiments in FIGS. 5 to 7 .
  • the transceiver module 820 is used to perform the above-mentioned operations related to AS_T receiving and sending messages, for example: used to receive information from the media plane network element of the service discovery function network element; the transceiver module is also used to send messages to the media plane network element.
  • Request information the request information includes information about the first media endpoint, the information about the first media endpoint includes information about a media endpoint used to provide access services, and the request information is used to request the media
  • the plane network element allocates media endpoints for providing resource-based services; the transceiver module is also used to receive information from the second media endpoint of the media plane network element.
  • the processing module 810 is used to perform operations of the above-mentioned AS_T except receiving and sending messages.
  • the request information also includes a remote address, where the remote address is used to indicate the address of a media endpoint that establishes a connection with the second media endpoint.
  • the first media endpoint belongs to the media plane network element, and the local address of the second media endpoint is the same as the local address of the first media endpoint.
  • the first media endpoint does not belong to the media plane network element, and the local address of the second media endpoint is different from the local address of the first media endpoint.
  • the information about the first media endpoint includes the identity of the media plane network element to which the first media endpoint belongs and the identity of the first media endpoint.
  • the transceiver module 820 is also configured to send indication information to the media plane network element, where the indication information is used to instruct execution of the resource type service.
  • processing module 810 in the embodiment of the present application can be implemented by a processor or processor-related circuit components
  • transceiver module 820 can be implemented by a transceiver or transceiver-related circuit components or a communication interface.
  • FIG 9 is a schematic block diagram of a communication device 900 provided by an embodiment of the present application.
  • the communication device 900 may be a terminal device and can implement the functions of the media plane network element in the method provided by the embodiments of the present application.
  • the communication device 900 may also be a device that can support media plane network elements to implement corresponding functions in the methods provided in the embodiments of the present application, where the communication device 900 may be a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the communication device 900 may also be an application server and can implement the functions of the application server in the method provided by the embodiments of the present application.
  • the communication device 900 may also be a device that can support the application server to implement the corresponding functions in the method provided by the embodiment of the present application, wherein the communication device 900 may be a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices. For specific functions, please refer to the description in the above method embodiment.
  • the communication device 900 includes one or more processors 920, which can be used to implement or support the communication device 900 to implement the functions of the media plane network element in the method provided by the embodiment of the present application. For details, please refer to the detailed description in the method example and will not be repeated here.
  • One or more processors 920 may also be used to implement or support the communication device 900 in implementing the function of the application server in the method provided by the embodiment of the present application. For details, please refer to the detailed description in the method example and will not be repeated here.
  • the processor 920 can also be called a processing unit or processing module, and can implement certain control functions.
  • the processor 920 may be a general-purpose processor or a special-purpose processor, or the like.
  • central processing unit may be used to control the communication device 900, execute software programs and/or process data.
  • Different processors may be independent devices, or may be integrated in one or more processors, for example, integrated on one or more application specific integrated circuits.
  • one or more memories 930 are included in the communication device 900 for storing program instructions and/or data.
  • Memory 930 and processor 920 are coupled.
  • the coupling in the embodiment of this application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information interaction between devices, units or modules.
  • Processor 920 may cooperate with memory 930.
  • the processor 920 may execute program instructions and/or data stored in the memory 930, so that the communication device 900 implements the corresponding method. At least one of the at least one memory may be included in processor 920 .
  • the communication device 900 may also include a communication interface 910 using any transceiver-like device for communicating with other devices or communication networks, such as radio access network (RAN), wireless local area networks (WLAN) ), wired access network and other communications.
  • the communication interface 910 is used to communicate with other devices through a transmission medium, so that the device used in the communication device 900 can communicate with other devices.
  • the communication device 900 is a media plane network element
  • the other equipment is an application service server; or, when the communication device is an application server, the other equipment is a media plane network element.
  • Processor 920 may utilize communication interface 910 to send and receive data.
  • the communication interface 910 may specifically be a transceiver.
  • the embodiment of the present application does not limit the specific connection medium between the communication interface 910, the processor 920 and the memory 930.
  • the memory 930, the processor 920 and the communication interface 910 are connected through a bus 940 in Figure 9.
  • the bus is represented by a thick line in Figure 9.
  • the connection between other components is only schematically explained. , is not limited.
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one thick line is used in Figure 9, but it does not mean that there is only one bus or one type of bus.
  • the processor 920 may be a general processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, which can be implemented Or execute the disclosed methods, steps and logical block diagrams in the embodiments of this application.
  • a general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware processor for execution, or can be executed by a combination of hardware and software modules in the processor.
  • Memory 930 may be ROM or other types of static storage devices that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, or it may be electrically erasable programmable read-only memory (electrically erasable programmable).
  • read-only memory EEPROM
  • compact disc read-only memory CD-ROM
  • optical disc storage including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.
  • the memory may exist independently and be connected to the processor through the communication bus 940. Memory can also be integrated with the processor.
  • the memory 930 is used to store computer execution instructions for executing the solution of the present application, and is controlled by the processor 920 for execution.
  • the processor 920 is configured to execute computer execution instructions stored in the memory 930, thereby implementing the communication method provided by the above embodiments of the present application.
  • the computer-executed instructions in the embodiments of the present application may also be called application codes, which are not specifically limited in the embodiments of the present application.
  • the communication device in the above embodiments may be a media plane network element (or application server) or a circuit, or may be a chip applied in the media plane network element (or application server) or other devices with the above media
  • the processing module may be a processor, such as a central processing unit (CPU).
  • the processing module may be a processor of a chip system.
  • the transceiver module or communication interface may be the input/output interface or interface circuit of the chip system.
  • the interface circuit may be a code/data read and write interface circuit.
  • the interface circuit can be used to receive code instructions (code instructions are stored in the memory and can be read directly from the memory, or can also be read from the memory through other devices) and transmitted to the processor; the processor can be used to run all The code instructions are used to execute the methods in the above method embodiments.
  • the interface circuit may also be a signal transmission interface circuit between the communication processor and the transceiver.
  • the device may include a transceiver unit and a processing unit.
  • the transceiver unit may be an input-output circuit and/or a communication interface;
  • the processing unit may be an integrated processor or microprocessor or an integrated circuit.
  • An embodiment of the present application also provides a communication system.
  • the communication system includes at least one media plane network element and at least one application server.
  • the communication system includes a media plane network element and an application server used to implement the relevant functions of any one or more of the above-mentioned figures 5 to 7, as well as a control plane network element.
  • the relevant descriptions in the above method embodiments which will not be described again here.
  • An embodiment of the present application also provides a computer-readable storage medium that includes instructions that, when run on a computer, cause the computer to execute the method performed by one or more of the media plane network elements in any one or more of Figures 5 to 7. Or, when it is run on the computer, the computer is caused to execute the method executed by the application server in any of the figures in Figures 5 to 7 .
  • An embodiment of the present application also provides a computer program product, which includes instructions that, when run on a computer, cause the computer to execute the method executed by one or more of the media plane network elements in any one or more of Figures 5 to 7. Or, when it is run on a computer, the computer is caused to execute the method executed by the application server in any one or more of Figures 5 to 7 .
  • Embodiments of the present application provide a chip system.
  • the chip system includes a processor and may also include a memory, which is used to implement the function of the media plane network element in the foregoing method; or is used to implement the function of the application server in the foregoing method.
  • the chip system can be composed of chips or include chips and other discrete devices.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种通信方法、装置和系统。该方法包括：媒体面网元接收来自应用服务器的请求该媒体面网元分配用于提供资源类服务的媒体端点的请求信息，该请求信息包括用于提供接入类服务的第一媒体端点的信息；媒体面网元向应用服务器发送用于提供资源类服务的第二媒体端点的信息，该第二媒体端点是媒体面网元根据第一媒体端点是否属于该媒体面网元确定的。通过在请求信息中携带第一媒体端点的信息，以便于媒体面网元根据第一媒体端点是否属于该媒体面网元确定并发送第二媒体端点的信息，应用服务器无需判断分配端点的媒体面网元与设置有第一媒体端点的媒体面网元是否为同一个媒体面网元，简化了应用服务器的操作。

Description

通信方法、装置和系统
本申请要求于2022年8月11日提交中国专利局、申请号为202210961956.2、申请名称为“通信方法、装置和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及互联网协议(internet protocol，IP)多媒体子系统(IP multimedia subsystem，IMS)通信技术领域，尤其涉及一种通信方法、装置和系统。
背景技术
为了满足多媒体通信的需求，第三代合作伙伴计划(3rd generation partnership project，3GPP)组织在原有分组承载网的基础上引入了IMS，IMS中媒体面网元可以向控制面网元提供多种与呼叫业务关联的媒体面服务，例如，接入类服务、资源类服务(例如语音会议)等，从而使网络侧向呼叫业务中的终端设备提供丰富的媒体流传输服务。其中，用于提供接入类服务的媒体面网元可称为接入类媒体面网元，用于提供资源类服务的媒体面网元可称为资源类媒体面网元。在实际应用中，一个媒体面网元可能既是接入类媒体面网元，又是资源类媒体面网元。
因此，在提供与呼叫业务关联的媒体面服务的流程中，作为控制面网元的应用服务器(application server，AS)需要甄别当前分配给该AS的资源类媒体面网元与先前分配给该AS的接入类媒体面网元的关系做不同的处理；例如，AS要根据资源类媒体面网元与接入类媒体面网元是否为同一个网元而决定是否请求该资源类媒体面网元分配新的媒体端点。这样的机制需要AS支持不同的处理流程，加大了AS的处理复杂度，降低了AS的处理效率。
如何在为AS提供媒体面网元功能的过程中，降低AS的处理复杂度，提高AS的处理效率，成为亟待解决的问题。
发明内容
本申请实施例提供一种通信方法，以期在提供媒体流传输服务的流程中简化AS的操作。
第一方面，提供了一种通信方法，该方法可由通信装置执行，通信装置可以是通信设备或能够支持通信设备实现该方法所需的功能的通信装置，例如芯片系统。示例性地，所述通信装置为媒体面网元，或者为设置在媒体面网元中的芯片，或者为用于实现媒体面网元的功能的其他部件。下面以所述通信设备是媒体面网元为例进行描述。
该方法包括：媒体面网元接收来自应用服务器的请求信息，所述请求信息用于请求所述媒体面网元分配用于提供资源类服务的媒体端点，所述请求信息包括用于提供接入类服务的第一媒体端点的信息；所述媒体面网元向所述应用服务器发送第二媒体端点的信息，所述第二媒体端点是所述媒体面网元根据所述第一媒体端点是否属于所述媒体面网元确定的。
针对分配给应用服务器AS的资源类媒体面网元，上述技术方案使得AS可以无条件请求该资源类媒体面网元分配媒体端点，也就是说，AS无需判断该资源类媒体面网元与先前分配给该AS的接入类媒体面网元是否为同一个媒体面网元而决定是否请求该资源类媒体面网元分配新的媒体端点，从而降低了AS的处理复杂度，提高了AS的处理效率。而之所以能够如此，是因为AS在请求资源类媒体面网元分配用于提供资源类服务的媒体端点(简称资源类媒体端点)时可以提供用于提供接入类服务的第一媒体端点(简称接入类媒体端点)的信息，使该资源类媒体面网元能够根据第一媒体端点是否为该资源类媒体面网元上的媒体端点而决定分配什么样的第二媒体端点，变相地将判断资源类媒体面网元与接入类媒体面网元是否为同一个网元的任务转移到媒体面网元，从而提高了AS的处理效率。在一种可能的情况下，AS为第三方提供的设备，而媒体面网元为运营商提供的，通过增加媒体面网元的处理复杂度来降低AS的处理复杂度、提高其处理效率，可以提高第三方(如运营商的客户)的使用满意 度，因此是可以接受的做法。
结合第一方面，在第一方面的某些实现方式中，所述第一媒体端点属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址相同。
具体地，所述第一媒体端点属于所述媒体面网元还可以理解为所述第一媒体端点为所述媒体面网元上的媒体端点，在该情况下：所述媒体面网元根据所述第一媒体端点属于所述媒体面网元确定不分配新的媒体端点，以所述第一媒体端点的镜像媒体端点作为所述第二媒体端点，其中，所述第一媒体端点的镜像媒体端点对于所述媒体面网元来说就是已分配的第一媒体端点，也就是说所述媒体面网元将所述媒体面网元上的第一媒体端点作为所述第二媒体端点。
结合第一方面，在第一方面的某些实现方式中，所述第一媒体端点不属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址不同。所述第二媒体端点的本端地址和所述第一媒体端点的本端地址不同，可以理解为所述第二媒体端点和所述第一媒体端点为不同媒体面网元上的媒体端点。
具体地，所述第一媒体端点不属于所述媒体面网元还可以理解为所述第一媒体端点不为所述媒体面网元上的媒体端点，在该情况下：媒体面网元根据所述第一媒体端点不属于所述媒体面网元确定分配新的媒体端点作为所述第二媒体端点。
其中，所述第一媒体端点的本端地址用于指示所述第一媒体端点与其他端点之间的连接中所述第一媒体端点的IP地址和端口，所述第二媒体端点的本端地址用于指示所述第二媒体端点与其他端点之间的连接中所述第二媒体端点的IP地址和端口。
基于上述的技术方案，在媒体面网元确定第一媒体端点为媒体面网元上的媒体端点的情况下，媒体面网元分配的第二媒体端点的本端地址和第一媒体端点的本端地址相同；在媒体面网元确定第一媒体端点不为媒体面网元上的媒体端点的情况下，媒体面网元确定的第二媒体端点的本端地址和第一媒体端点的本端地址不相同。
结合第一方面，在第一方面的某些实现方式中，所述第一媒体端点的信息包括所述第一媒体端点所属的媒体面网元的标识和所述第一媒体端点的标识；或者，所述第一媒体端点的信息包括所述第一媒体端点的标识，该所述第一媒体端点的标识包括所述第一媒体端点所属的媒体面网元的标识。
结合第一方面，在第一方面的某些实现方式中，所述媒体面网元根据所述第一媒体端点的信息判断所述第一媒体端点是否为所述媒体面网元上的媒体端点，包括：所述第一媒体面网元根据所述第一媒体端点所属的媒体面网元的标识和所述第一媒体端点的标识判断所述第一媒体端点所属的媒体面网元是否为所述媒体面网元。
基于上述的技术方案，第一媒体端点的信息可以包括两个部分的信息：第一媒体端点所属的媒体面网元的标识和所述第一媒体端点的标识，以便于接收到第一媒体端点的信息的媒体面网元根据第一媒体端点的信息准确地确定该第一媒体端点是否为媒体面网元上的媒体端点。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：所述媒体面网元接收来自应用服务器的指示信息，所述指示信息用于指示执行所述资源类服务，所述指示信息中包括所述第二媒体端点的信息；所述媒体面网元根据所述指示信息执行所述资源类服务。
结合第一方面，在第一方面的某些实现方式中，所述请求信息中还包括远端地址，所述远端地址用于指示与所述第二媒体端点建立连接的媒体端点的地址。
结合第一方面，在第一方面的某些实现方式中，所述第二媒体端点的本端地址与所述远端地址不同的情况下，所述媒体面网元通过所述第二媒体端点提供所述资源类服务；所述第二媒体端点的本端地址与所述远端地址相同的情况下，所述媒体面网元通过第三媒体端点提供所述资源类服务，所述第三媒体端点是所述媒体面网元根据所述第二媒体端点的信息确定的。其中，所述第三媒体端点是所述媒体面网元上与所述第二媒体端点相关的端点，某个媒体面网元上不同媒体端点之间的关联关系媒体面网元已知。
基于上述的技术方案，媒体面网元可以基于接收到的指示信息确定执行资源类服务，并且可以根据第二媒体端点的本端地址和请求信息中包括的远端地址是否相同，确定媒体面网元上执行资源类服务的媒体端点，支持通过不同媒体端点提供资源类服务，提高方案的灵活性。
结合第一方面，在第一方面的某些实现方式中，所述媒体面网元为统一媒体面功能UMF网元。
第二方面，提供了一种通信方法，该方法可由通信装置执行，通信装置可以是通信设备或能够支持通信设备实现该方法所需的功能的通信装置，例如芯片系统。示例性地，所述通信装置为应用服务器，或者为设置在应用服务器中的芯片，或者为用于实现应用服务器的功能的其他部件。下面以所述通信设备是应用服务器为例进行描述。
该方法包括：应用服务器接收来自服务发现功能网元的媒体面网元的信息；所述应用服务器向所述媒体面网元发送请求信息，所述请求信息用于请求所述媒体面网元分配用于提供资源类服务的媒体端点，所述请求信息中包括用于提供接入类服务的第一媒体端点的信息；所述应用服务器接收来自所述媒体面网元的第二媒体端点的信息，所述第二媒体端点是所述媒体面网元根据所述第一媒体端点是否属于所述媒体面网元确定的。
结合第二方面，在第二方面的某些实现方式中，所述请求信息中还包括远端地址，所述远端地址用于指示与所述第二媒体端点建立连接的媒体端点的地址。
其中，所述第二媒体端点的远端地址用于指示所述第二媒体端点与其他端点之间的连接中所述其他端点的IP地址和端口。
结合第二方面，在第二方面的某些实现方式中，所述第一媒体端点属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址相同。
结合第二方面，在第二方面的某些实现方式中，所述第一媒体端点不属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址不同。
结合第二方面，在第二方面的某些实现方式中，所述第一媒体端点的信息包括所述第一媒体端点所属的媒体面网元的标识和所述第一媒体端点的标识。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：所述应用服务器向所述媒体面网元发送指示信息，所述指示信息用于指示执行所述资源类服务。
关于第二方面以及第二方面的各个可能的实施方式所带来的技术效果，可以参考对第一方面以及第一方面的各个可能的实施方式的技术效果的介绍。
第三方面，提供了一种通信装置，该装置用于执行上述第一方面提供的方法。该装置包括收发模块和处理模块；
所述收发模块，用于接收来自应用服务器的请求信息，所述请求信息用于请求所述媒体面网元分配用于提供资源类服务的媒体端点，所述请求信息包括用于提供接入类服务的第一媒体端点的信息；
所述收发模块还用于向所述应用服务器发送第二媒体端点的信息，所述第二媒体端点是所述媒体面网元根据所述第一媒体端点是否属于所述媒体面网元确定的。
结合第三方面，在第三方面的某些实现方式中，所述第一媒体端点属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址相同。
结合第三方面，在第三方面的某些实现方式中，所述处理模块，还用于根据所述第一媒体端点属于所述媒体面网元确定不分配新的媒体端点，以所述第一媒体端点的镜像媒体端点作为所述第二媒体端点。
结合第三方面，在第三方面的某些实现方式中，所述第一媒体端点不属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址不同。
结合第三方面，在第三方面的某些实现方式中，所述处理模块，还用于根据所述第一媒体端点不属于所述媒体面网元确定分配新的媒体端点作为所述第二媒体端点。
结合第三方面，在第三方面的某些实现方式中，所述第一媒体端点的信息包括所述第一媒体端点所属的媒体面网元的标识和所述第一媒体端点的标识。
结合第三方面，在第三方面的某些实现方式中，所述处理模块根据所述第一媒体端点的信息判断所述第一媒体端点是否为所述媒体面网元上的媒体端点，包括：所述处理模块根据所述第一媒体端点所属的媒体面网元的标识和所述第一媒体端点的标识确定所述第一媒体端点所属的媒体面网元是否为所述通信装置。
结合第三方面，在第三方面的某些实现方式中，所述收发模块还用于接收来自应用服务器的指示信息，所述指示信息用于指示执行所述资源类服务，所述指示信息中包括所述第二媒体端点的信息；所述处理模块，还用于根据所述指示信息执行所述资源类服务。
结合第三方面，在第三方面的某些实现方式中，所述请求信息中还包括远端地址，所述远端地址用于指示与所述第二媒体端点建立连接的媒体端点的地址。
结合第三方面，在第三方面的某些实现方式中，所述第二媒体端点的本端地址与所述远端地址不同的情况下，所述媒体面网元通过所述第二媒体端点提供所述资源类服务；所述第二媒体端点的本端地址与所述远端地址相同的情况下，所述媒体面网元通过第三媒体端点提供所述资源类服务，所述第三媒体端点是所述媒体面网元根据所述第二媒体端点的信息确定的。
第四方面，提供了一种通信装置，该装置用于执行上述第一方面提供的方法。该装置包括收发模块和处理模块；
所述收发模块，用于接收来自服务发现功能网元的媒体面网元的信息；所述收发模块还用于向所述媒体面网元发送请求信息，所述请求信息用于请求所述媒体面网元分配用于提供资源类服务的媒体端点，所述请求信息中包括用于提供接入类服务的第一媒体端点的信息；所述收发模块还用于接收来自所述媒体面网元的第二媒体端点的信息，所述第二媒体端点是所述媒体面网元根据所述第一媒体端点是否属于所述媒体面网元确定的。
结合第四方面，在第四方面的某些实现方式中，所述请求信息中还包括远端地址，所述远端地址用于指示与所述第二媒体端点建立连接的媒体端点的地址。
结合第四方面，在第四方面的某些实现方式中，所述第一媒体端点属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址相同。
结合第四方面，在第四方面的某些实现方式中，所述第一媒体端点不属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址不同。
结合第四方面，在第四方面的某些实现方式中，所述第一媒体端点的信息包括所述第一媒体端点所属的媒体面网元的标识和所述第一媒体端点的标识。
结合第四方面，在第四方面的某些实现方式中，所述收发模块还用于向所述媒体面网元发送指示信息，所述指示信息用于指示执行所述资源类服务。
第五方面，本申请实施例提供了一种通信装置，所述通信装置具有实现上述第一方面或第二方面的方法实施例中行为的功能，有益效果可以参见第一方面至第二方面的描述，此处不再赘述。该通信装置可以是第一方面中的媒体面网元，或者该通信装置可以是能够实现第一方面提供的方法的装置，例如芯片或芯片系统。或者，该通信装置可以是第二方面中的应用服务器，或者该通信装置可以是能够实现第二方面提供的方法的装置，例如芯片或芯片系统。
在一个可能的设计中，该通信装置包括用于执行第一方面或第二方面的方法的相应手段(means)或模块。例如，所述通信装置：包括处理单元(有时也称为处理模块或处理器)和/或收发单元(有时也称为收发模块或收发器)。这些单元(模块)可以执行上述第一方面或第二方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
第六方面，本申请实施例提供一种通信装置，该通信装置可以为上述实施例中第一方面或第二方面中的通信装置，或者为设置在第一方面或第二方面中的通信装置中的芯片或芯片系统。该通信装置包括通信接口以及处理器，可选的，还包括存储器。其中，该存储器用于存储计算机程序，处理器与存储器、通信接口耦合，当处理器读取所述计算机程序或指令时，使通信装置执行上述方法实施例中由媒体面网元或应用服务器所执行的方法。
第七方面，本申请实施例提供了一种通信装置，该通信装置包括输入输出接口和逻辑电路。输入输出接口用于输入和/或输出信息。逻辑电路用于执行第一方面或第二方面所述的方法。
第八方面，本申请实施例提供了一种芯片系统，该芯片系统包括处理器，还可以包括存储器和/或通信接口，用于实现第一方面或第二方面中所述的方法。在一种可能的实现方式中，所述芯片系统还包括存储器，用于保存计算机程序。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第九方面，本申请实施例提供了一种通信系统，所述通信系统包括媒体面网元和应用服务器，其中，媒体面网元用于执行上述第一方面中由第一控制面网元所执行的方法，应用服务器用于执行上述第二方面中由网络功能存储网元所执行的方法。
第十方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，当该计算机程序被运行时，实现上述第一方面或第二方面中的方法。
第十一方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被运行时，使得上述第一方面或第二方面中的方法被执行。
上述第三方面至第十一方面及其实现方式的有益效果可以参考对第一方面至第二方面及其实现方式的有益效果的描述。
附图说明
图1为本申请实施例提供的通信系统的一种网络架构示意图；
图2的(a)所示的为接收呼叫请求并返回180消息的流程的示意性流程图；
图2的(b)所示的为一种播放特殊回铃音的流程；
图2的(c)所示的为另一种播放特殊回铃音的流程；
图3为本申请实施例提供的建立媒体传输通道的连接的一种示意图；
图4的(a)为本申请实施例提供的建立媒体传输通道的连接的另一种示意图；
图4的(b)为本申请实施例提供的建立媒体传输通道的连接的又一种示意图；
图5是本申请实施例提供的一种通信方法的示意性流程图；
图6是本申请实施例提供的一种提供资源类服务的示意性流程图；
图7是本申请实施例提供的另一种提供资源类服务的示意性流程图；
图8为本申请实施例提供的通信装置的一种结构示意图；
图9为本申请实施例提供的通信装置的另一种结构示意图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：第五代(5th generation，5G)系统或新无线(new radio，NR)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)等。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统。本申请实施例的技术方案还可以应用于设备到设备(device to device，D2D)通信，车辆外联(vehicle-to-everything，V2X)通信，机器到机器(machine to machine，M2M)通信，机器类型通信(machine type communication，MTC)，以及物联网(internet of things，IoT)通信系统或者其他通信系统。
为了满足多媒体通信的需求，3GPP组织在原有分组承载网的基础上引入了IMS，IMS不仅能向用户提供传统语音业务，也能向用户提供丰富的多媒体体验，IMS的显著特点是采用了会话发起协议(Session Initiation Protoco1，SIP))体系，通讯与接入无关，可以具备多种媒体业务控制功能与承载能力分离，呼叫与会话分离，应用与服务分离，业务与网络分离，以及移动网与英特网业务融合等多种能力，IMS的提出顺应了通讯网融合发展的趋势。
本申请实施例主要提供基于IMS的一种通信方法。为便于本领域技术人员理解本申请实施例提供的技术方案，首先结合图1简单介绍IMS体系结构中的和本申请相关的网元实体以及网元之间的连接。IMS架构可包括网络功能存储网元，至少一个控制面网元、至少一个媒体面网元和至少一个终端设备。图1以网络功能存储网元是网络存储功能(network repository function，NRF)网元、控制面网元是代理呼叫会话控制功能(Proxy Call Session Control Function，P-CSCF)网元、媒体面网元是UMF网元为例进行说明。其他能够实现网络功能存储网元的功能的网元、控制面网元的功能的网元、媒体面网元的功能的网元也在本申请的保护范围之内。
可以理解的是，本申请实施例中的一个UMF网元可以是融合UMF网元，也可以是非融合UMF网元。
图1是一种IMS架构的示意图，该IMS架构可以包括但不限于以下网元(或者称为功能网元、功能实体、节点、设备等)：
用户终端(user terminal，UE)(如图1中所示的UE_O和UE_T)、P-CSCF网元(如图1中所示的P-CSCF_O和P-CSCF_T)、UMF网元(如图1中所示的UMF_1、UMF_2和UMF_3)、AS(如图1中所示的AS_O和AS_T)以及NRF网元。
进一步地，将UMF网元简称为UMF，P-CSCF网元简称为P-CSCF，NRF网元简称为NRF。即本申请后续所描述的UMF均可替换为UMF网元，P-CSCF均可替换为P-CSCF网元，NRF均可替换为NRF网元。
下面对图1中示出的各网元进行简单介绍：
1、UE：可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的终端、移动台(mobile station，MS)、终端(terminal)或软终端等等。例如，水表、电表、传感器等。
示例性地，本申请实施例中的用户设备可以指接入终端、用户单元、用户站、移动站、移动台、中继站、远方站、远程终端、移动设备、用户终端(user terminal)、终端设备(terminal equipment)、无线通信设备、用户代理或用户装置。用户设备还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的用户设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的用户设备或者未来车联网中的用户设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，用户设备还可以是物联网(internet of Things，IoT)系统中的用户设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。在本申请实施例中，IOT技术可以通过例如窄带(narrow band，NB)技术，做到海量连接，深度覆盖，终端省电。
此外，在本申请实施例中，用户设备还可以包括传感器，主要功能包括收集数据(部分用户设备)、接收接入网设备的控制信息与下行数据，并发送电磁波，向接入网设备传输上行数据。
本申请实施例中，用于实现用户设备的功能的装置可以是用户设备，也可以是能够支持用户设备实现该功能的装置，例如，芯片系统或可实现用户设备功能的组合器件、部件，该装置可以被安装在用户设备中。
本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。本申请实施例提供的技术方案中，以用于实现用户设备的功能的装置是用户设备为例，描述本申请实施例提供的技术方案。
2、P-CSCF：呼叫控制功能网元，是IMS网络内部的功能实体，是整个IMS网络的核心，主要负责处理多媒体呼叫会话过程中的信令控制。在5G通信系统中，呼叫控制功能网元可以是(serving-call session control function，CSCF)网元。在未来的通信系统(如6G通信系统)中，应用服务网元可以仍是CSCF网元，或者也可以具有其它名称，本申请实施例并不限定。
CSCF网元根据功能进一步可分为服务-呼叫控制功能(serving-call session control function，SCSCF)网元、查询-呼叫会话控制功能(interrogating-call session control function，ICSCF)网元、代理-呼叫会话控制功能(proxy-call session control function，PCSCF)网元等。
进一步地，将CSCF网元简称为CSCF，SCSCF网元简称为SCSCF，ICSCF网元简称为ICSCF，ICSCF网元简称为ICSCF。
其中，SCSCF是IMS网络的业务处理节点，负责终端设备的IMS网络注册以及相关的媒体服务处理。PCSCF位于拜访网络，为IMS网络的边缘网络节点，也可以因为是用户接入IMS网络的入口节点。PCSCF在IMS网络中的作用类似于执行代理服务，无论是来自终端设备的信息或者发送给终端设备的信息，均需通过P-CSCF转发。例如，PCSCF可负责SIP用户与归属网络之间SIP信令的转发。 ICSCF位于归属网络，是归属网络的统一入口点。ICSCF可以连接SCSCF和PCSCF，用于为终端设备提供到归属网络的入口，当终端设备漫游到其他网络时，向PCSCF发送消息，PCSCF可以将来自终端设备的消息转发给ICSCF，通过ICSCF将来自终端设备的消息发送给SCSCF。ICSCF可负责分配为用户服务的SCSCF或查询为用户服务的SCSCF。另外，ICSCF/SCSCF通过Mw接口和本网内的PCSCF连接。
相较于提供媒体服务的媒体面网元来说，PCSCF、SCSCF、ICSCF都属于控制面网元。从功能上来说，可认为，PCSCF是接入类控制面网元，ICSCF是互通类控制面接入网元。可以理解的是，PCSCF、SCSCF、ICSCF可以独立配置于不同实体，也可以集成于同一实体。以下，为了便于理解和说明，PCSCF、SCSCF、ICSCF统称为CSCF。
媒体面网元可通过媒体网关控制网元与呼叫控制功能网元连接。媒体网关控制网元可以理解为是使IMS用户和客户端用户之间可以进行通信的网关。来自客户端用户的呼叫控制信令都指向媒体网关控制网元，媒体网关控制网元主要负责进行综合业务数字网(integrated services digital network，ISDN)用户部分或承载无关呼叫控制与会话初始协议(session initiation protocol，SIP)协议之间的协议转换，并且将会话转发给IMS。在5G通信系统中，媒体网关控制网元可以是媒体网关控制功能(media gateway control function，MGCF)网元。在未来的通信系统(如6G通信系统)中，应用服务网元可以仍是MGCF，或者也可以具有其它名称，本申请实施例并不限定。MGCF和本网内的P-CSCF/I-CSCF网元/S-CSCF网元连接。
媒体面网元也可以通过互联边界点控制网元与呼叫控制功能网元连接。互联边界点控制网元是两个运营商网络之间控制平面的边界功能实体。在5G通信系统中，互联边界点控制网元可以是互联边界点控制功能(interconnection border control functions，IBCF)网元。在本申请实施例中，在未来的通信系统(如6G通信系统)中，应用服务网元可以仍是IBCF网元，或者也可以具有其它名称，本申请实施例并不限定。IBCF网元/TrGW部署在不同IMS核心网络之间或者IMS核心网络与其他IP网络之间，网间采用IP中继连接。IBCF和本网内的PCSCF/ICSCF/SCSCF连接，IBCF的信令面通过Ici接口与其他网络连接，IBCF网元的媒体面(TrGW)通过Izi接口与其他网络连接。各运营商可根据主叫用户性质选择互通节点。例如，当主叫用户为IMS用户时，采用通过IBCF网元/TrGW进行互通的方式。
为多媒体系统入口网元，是终端设备接入IMS的接入点，用于完成用户注册、服务质量控制和安全管理等。比如，在5G中，多媒体系统入口网元可以是代理CSCF(Proxy-CSCF，P-CSCF)，或有其它的名称。P-CSCF作为SIP代理功能，将来自拜访的接入网络的SIP事务代理转接到其归属网络的S-CSCF(根据注册时记录的信息)。
具体地，P-CSCF负责进行IMS本地接入网的IP承载(也可能是别的粒度，比如会话、数据流等)资源认证，网络地址转换(Network Address Translation，NAT)和QoS管理功能，为IMS提供端到端的业务保障。
在未来通信，比如第6代(6th generation，6G)网络中，多媒体系统入口网元仍可以是P-CSCF，或有其它的名称，本申请不做限定。
3、媒体面(media plane)网元：也称为媒体面功能网元，指能够提供媒体面服务的功能网元。媒体面网元可以使用自身的媒体能力，为终端设备提供媒体流传输服务。媒体面网元将自身的媒体能力通过SBI暴露给使其他网络实体(例如控制面网元)，则可使其他网络实体间接地为终端设备提供媒体流传输服务。举例来说，媒体面网元可包括接入侧的媒体处理网元、中心侧的媒体处理网元，以及互通侧的媒体处理网元，等等。其中，接入侧的媒体处理网元可实现用户媒体接入代理与转发、NAT穿越，以及音频编解码转换等功能。例如，接入侧的媒体处理网元包括IMS接入网关(IMS Access gateway，IMS-AGW)。互通侧的媒体处理网元可实现IMS与其他网络的媒体互通。例如，互通侧的媒体处理网元可包括转换网关(transition gateway，TrGW)，用于实现IMS与其他IP网络媒体面的互通。又例如，互通侧的媒体处理网元可包括IP多媒体网关(IP multimedia media gateway，IM-MGW)，可实现IMS网络和其他非IP网络媒体面的互通。中心侧的媒体处理网元可为媒体面服务提供媒体资源，例如放音资源、收号资源、语音会议资源、DC资源、XRM资源等。例如，中心侧的媒体处理网元可包括多媒体资源功能处理器(multimedia resource function processor，MRFP)。可以理解的是，此处以MRFP部署到中心侧为例。在一些实施例中，MRFP也可以部署在接入侧。换句话说，接入侧的媒体 处理网元也可能包括MRFP。可以理解的是，媒体面网元可以是物理网元也可以是逻辑网元(或虚拟网元)。
根据所能提供的媒体面服务的种类，媒体面网元可以分为融合媒体面网元和非融合媒体面网元，前者指能提供多种媒体面服务的媒体面网元，例如同时提供接入类服务和资源类服务的媒体面网元，后者指提供单一媒体面服务的网元，例如，仅提供接入类服务的媒体面服务。
在本申请实施例中，媒体面网元可以是3GPP标准规范的统一媒体面网元或者统一媒体面功能(unified media function，UMF)网元。可以理解的是，本申请实施例对媒体面网元的具体名称不作限制，如无特殊说明，媒体面网元均以UMF网元为例。也就是说下文中的UMF可以替换为媒体面网元。
各个UMF可将自身的网络功能服务(network function service，NFS)信息注册到NRF网元上。不同的UMF能够提供的媒体面服务可能不同，也可能相同。
如图1所示，UMF_1、UMF_2和UMF_3为3个UMF。示例性地，UMF_1能够提供的媒体面服务包括会议服务和语音识别服务；UMF_2能够提供的媒体面服务包括网络地址翻译服务、放音服务和媒体处理服务；UMF_3能够提供的媒体面服务包括网络地址翻译服务和放音服务。相应的，各个UMF还将自身的标识信息注册到NRF网元上。
例如，UMF_1、UMF_2和UMF_3在NRF中注册的信息如下表1所示：
表1
NRF可保存各个UMF的信息。可以理解的是，NRF可以将UMF的NFS信息与UMF的标识信息对应存储，从而NRF可以明确各个UMF能够提供的服务。可以理解的是，UMF的信息除了包括NFS信息和标识信息，还可以包括其他的信息。本申请实施例关注的是各个UMF能够提供的媒体服务，因此对于UMF的其他信息不作介绍。
UMF可为UE_O提供媒体流传输服务，也可以为UE_T提供媒体流传输服务。在呼叫业务过程中，UE_O和UE_T以及网络中的UMF、NRF、PCSCF_O、PCSCF_T等网元之间进行交互，使得UMF与UE_O和/或UE_T之间必要的媒体传输通道(或者连接)得到建立，以便UMF向UE_O和/或UE_T提供媒体流传输服务。本申请实施例中，一个UMF与UE对接的媒体端点，和该UMF与其他UMF对接的媒体端点默认是连通的。也可以理解为，对于一个UMF来说，与UE对接的媒体端点接收到信息，默认转发给该UMF与其他UMF对接的媒体端点。例如，与UE对接的媒体端点接收到信息，可广播该信息。同理，对于一个UMF来说，与其他UMF对接的媒体端点接收到信息，默认转发给该UMF与UE对接的媒体端点。例如，与其他UMF对接的媒体端点接收到信息，可广播该信息。
4、NRF：网络存储功能网元，可用于收集网络实体的具体信息，例如网络实体所能提供的服务、网络实现的标识信息等。例如，网络存储功能网元可以收集媒体面网元所能提供的服务等信息。在5G通信系统中，网络功能存储网元可以是3GPP标准规范定义的网络存储功能(network repository function，NRF)网元。在未来的通信系统(如6G通信系统)中，网络功能存储网元可以仍是NRF，或者也可以具有其它名称，本申请实施例并不限定。
5、AS：应用服务网元，可用于获取初始接入的媒体面网元的信息，也可以请求媒体面网元提供媒体面服务。在5G通信系统中，应用服务网元可以是(application server，AS)网元。在未来的通信系统(如6G通信系统)中，应用服务网元可以仍是AS，或者也可以具有其它名称，本申请实施例并不限定。
AS是IMS系统中位于最上层的应用层设备。AS与CSCF之间通过标准SIP协议进行交互，进而 实现各种网络业务的触发和执行，提供各种业务逻辑控制功能。
在图1中，AS分为主叫侧AS(记为AS_O)和被叫侧AS(记为AS_T)；PCSCF网元分为主叫侧PCSCF(记为PCSCF_O)和被叫侧PCSCF网元(记为PCSCF_T)；终端设备分为主叫侧终端设备(记为UE_O)和被叫侧终端设备(记为UE_T)。UMF可与NRF、PCSCF_O、PCSCF_T、UE_O和UE_T连接。NRF可与PCSCF_O和PCSCF_T连接。UE_O可与PCSCF_O连接，UE_T可与PCSCF_T连接。AS_O可与AS_T、PCSCF_O连接。AS_T可与AS_O、PCSCF_T连接。图1中各个网元之间的接口可参考现有接口协议定义，此处不再赘述。
可以理解的是，图1仅是举例示意。本申请实施例适用的IMS网络不限于仅包含图1中所示的网元，还可以包含其它未在图1中表示的设备，例如，SCSCF等，此处不再一一列举。且图1中各个网元的分布形式只是示例性的，本申请实施例并不限定各个网元的分布形式。
可以理解的是，上述网元既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
为了便于理解本申请实施例的技术方案，在介绍本申请实施例的方案之前，首先对本申请实施例可能涉及到的一些术语或概念进行简单描述。
首先对本申请实施例中的部分用语进行解释说明。
1、媒体面服务：也称为媒体服务，指基于服务化接口(service based interface，SBI)向网络实体(例如控制面网元)提供的网络服务。该网络服务的实现或者提供该网络服务的过程，包括向呼叫业务中的终端设备(主叫终端设备和/或被叫终端设备)提供与媒体有关的服务，如媒体流传输服务、媒体处理服务等，例如，面向呼叫业务发起方的终端设备的彩铃服务、面向呼叫业务接收方的终端设备的彩振服务等。示例性地，媒体面服务可以分为三类，一类是资源类服务，一类是接入类服务，还有一类是互通类服务，分别介绍如下。
资源类服务，也可以称为媒体应用类服务或者媒体资源类服务。资源类服务，也可以理解为，是需要提供媒体资源的服务，例如收号(指接收终端设备输入的号码，如菜单号码等)服务、放音(指向终端设备播放音频内容)服务、语音会议服务、视频会议服务、数据信道(data channel，DC)服务、扩展现实管理(extended reality manage，XRM)服务等。相应地，资源类服务的实现或者提供资源类服务的过程，包括向呼叫业务中的终端设备提供资源类媒体流传输服务，如彩铃服务。
接入类服务，主要是帮助呼叫业务中的终端设备实现媒体流的NAT穿越的服务。相应地，接入类服务的实现或者提供接入类服务的过程，包括向呼叫业务中的终端设备提供接入类媒体流传输服务，如，NAT穿越服务。
互通类服务，主要是帮助呼叫业务中的终端设备实现媒体流的网络地址转换，例如，IPv4地址和IPv6地址的转换，以便该终端设备与呼叫业务中的对端网络互通媒体流。相应地，互通类服务的实现或者提供互通类服务的过程，包括向呼叫业务中的终端设备提供互通类媒体流传输服务，如地址转换服务。
本申请实施例所指的网络侧设备为负责处理媒体面服务的核心网、网关、接入网设备等的统称。网络侧设备具体包括哪些设备将在下文中举例说明，此处暂不详细介绍。
2、融合UMF和非融合UMF：一个独立的UMF可以是多个媒体面网元归一化所得，称为融合UMF。相对来说，如果一个UMF不是多个媒体面网元归一化所得，那么该UMF为非融合UMF。或者，也可以理解，融合UMF能够提供多种类型的媒体面服务，非融合UMF提供一类媒体面服务。
3、媒体资源：指MRFP中提供资源类服务使用的计算机资源，例如，中心侧的媒体处理网元提供资源类服务使用的资源。举例来说，媒体资源可包括放音资源、收号资源、语音会议资源、视频流资源、DC服务资源、XRM服务资源等。
4、媒体能力：指能够提供媒体面服务的能力，或者提供媒体面服务所需媒体资源的能力，表示媒体面网元是否能够提供媒体资源。例如，媒体面网元具有接入媒体的能力，也可以理解为，媒体面网元能够实现用户媒体接入的功能。又例如，媒体面网元具有与IP网络互通的能力，也可以理解为，媒体面网元能够实现IMS网络与其他IP网络媒体面的互通。
5、媒体处理(操作)：包括媒体业务处理(操作)、媒体接入处理(操作)和媒体互通处理(操作)。媒体业务处理(操作)主要指中心侧的媒体处理网元提供的放音、收号、语音会议、DC、XRM 等功能涉及的处理。媒体接入处理(操作)主要包括接入侧的媒体处理网元提供的接入处理，媒体互通处理(操作)主要包括互通侧的媒体处理网元提供的互通处理等。
6、媒体端点：是位于媒体网关，例如媒体面网元中的一个逻辑实体，可以发送/接收媒体流和/或控制流。
例如，媒体端点可以通过IP端口或异步传输模式(asynchronous transfer mode，ATM)端口来表征。IP端口包括IP地址和端口号，具体可参考H248协议的相关内容。
具体地，媒体面网元通过媒体端点提供服务(如上述的接入类服务、资源类服务等)。媒体面网元为提供服务，需要在该媒体面网元上的媒体端点(即本端)与其他网元实体(或UE)上的媒体端点(即对端)之间建立媒体传输通道，因此，媒体端点可以理解为是媒体传输通道的一端，媒体端点的信息会包含五元组信息：如，本端地址(本端IP地址和端口号)、对端地址(对端IP地址和端口号)以及协议。
7、会话描述协议(session description protocol，SDP)：是为了描述多媒体会话而设计的，主要用来描述会话通告、会话邀请或者其他形式的多媒体会话初始化。为了初始化多媒体会话，需要对参与者提供媒体信息、传输地址等。SDP为了描述这些信息提供了一个标准的形式。
上文主要介绍了本申请实施例适用的场景以及涉及的基本概念，为了便于理解，下面结合图2至图4简单介绍IMS架构中如何选择提供接入类服务的UMF和接入类服务资源类服务的UMF。
示例性地，以基本呼叫中被叫AS为主叫播放特殊回铃音的场景为例说明IMS架构下实现媒体业务的流程，该通信方法以应用于图1所示的架构为例。图2中(图，图2的(a)至图2的(c))，T_caller_UE@UMF_O，指的是UMF_O中的媒体端点T_caller_UE。同理，T_caller_NW@UMF_O，指的是UMF_O中的媒体端点T_caller_NW，T_called_UE@UMF_T，指的是UMF_T中的媒体端点T_called_UE；T_called_NW@UMF_T，指的是UMF_T中的媒体端点T_called_NW；T_called_media@UMF_T_Res，指的是UMF_T_Res中的媒体端点T_called_media。图2中的UMF_T指本申请实施例中的提供接入类服务的UMF。UMF_T_Res指本申请实施例中的提供特殊回铃音服务的网元。图2所示实施例中，放音服务为本申请实施例中所述的资源类服务的一种，相应的，UE_T接入网络的服务为接入类服务。在图2中细线标识交互的是信令，粗线标识交互的是媒体流。
该示例中IMS提供的资源类服务为特殊回铃音业务，该特殊回铃音业务为被叫终端设备希望对特定的主叫终端设备播放不一样的回铃音，为了实现该特殊回铃音业务，需要在被叫终端设备侧的AS_T上触发该特殊回铃音业务。
应理解，对于其他的资源类服务处理流程与图2所示的该特殊回铃音业务流程相同，将被叫AS_T为主叫播放特殊回铃音替换为相应的媒体业务即可，不再一一举例说明。
具体地，被叫AS_T为主叫播放特殊回铃音包括接收呼叫请求并返回180消息的流程，以及播放特殊回铃音的流程。其中，播放特殊回铃音的流程包括两种可能，如，基于提供接入服务的UMF和提供特殊回铃音的UMF是否为一个UMF，针对不同的播放特殊回铃音的流程。
为了便于描述，下面结合图2的(a)介绍主叫发起呼叫请求以及被叫返回180消息的流程；结合图2的(b)介绍提供接入服务的UMF和提供特殊回铃音的UMF为一个UMF的情况下的播放特殊回铃音的流程；结合图2的(c)介绍提供接入服务的UMF和提供特殊回铃音的UMF不为一个UMF的情况下的播放特殊回铃音的流程。
图2的(a)所示的为接收呼叫请求并返回180消息的流程的示意性流程图，包括以下步骤：
S201、各UMF向NRF发起服务注册。
UMF可向NRF发送注册请求，该注册请求可包括UMF的信息。NRF从注册请求获取UMF的信息之后，可存储UMF的信息。UMF的信息可包括UMF能够提供的服务的信息。UMF的信息也包括用于标识UMF的信息，例如UMF的ID或IP地址等。可以理解的是，UMF的NFS信息与UMF的标识信息具有对应关系，从而NRF可以根据UMF的标识信息明确各个UMF能够提供的服务。如图2的(a)所示，UMF_O可以向NRF发起服务注册，UMF_T和UMF_T_Res也可以向NRF发起注册请求。
S202、UE_O向PCSCF_O发送呼叫请求，相应的，PCSCF_O接收UE_O发送的呼叫请求。
示例性地，呼叫请求为呼叫流程中的邀请(invite)消息。该呼叫请求可包括UE_O的信息和UE_T 的信息以及与呼叫请求相关的会话描述协议(session description portocol，SDP)信息。可以理解的是，SDP是针对UE_O而言的，为方便描述，呼叫请求包括的SDP信息记为SDP_UE_O。可以理解的是，SDP_UE_O可包括UE_O的媒体信息，例如，媒体类型(音频、时频等)、媒体格式(H264视频等)、传输地址和端口，等等。
S203、PCSCF_O向NRF发起服务发现，该服务发现请求用于请求为UE_O提供接入类服务的UMF的信息。
例如，PCSCF_O向NRF发送服务发现请求，相应的，NRF接收PCSCF_O发送的服务发现请求，该服务发现请求可用于请求能够提供接入类服务的UMF。可以理解的是，NRF上注册有多个UMF的信息，不同的UMF具有的能力可能不同，所能够提供的媒体资源也不同，能够提供媒体流传输服务也可能不同。NRF接收PCSCF_O发送的服务发现请求之后，可查询各个UMF的能力，以确定各个UMF能够提供的媒体流传输服务。具体的，NRF可以获取所存储的各个UMF的能力信息，该能力信息可指示UMF所能提供的媒体服务，从而NRF根据各个UMF的能力信息确定能够提供接入类服务的UMF。以图2的(a)为例，NRF确定能够为UE_O提供接入类服务的UMF为UMF_O。
NRF确定UMF_O之后，可向PCSCF_O提供UMF_O的信息。例如，NRF向PCSCF_O发送服务发现响应，该服务发现响应包括UMF_O的信息，例如，UMF_O的标识信息、IP地址等。
S204、PCSCF_O向UMF_O发送分配端点请求，相应的，UMF_O接收PCSCF_O发送的分配端点请求。
该分配端点请求可用于向UMF_O请求分配媒体端点，或者请求获取UMF_O的媒体端点信息，例如，UMF_O的媒体端点的IP地址和端口等，从而使得UE_O基于UMF_O分配的媒体端点接入网络。
该分配端点请求可包括第一呼叫请求中的SDP信息，即SDP_UE_O。UMF_O可根据SDP_UE_O确定与UE_O对接的媒体端点(可记为T_caller_UE)，确定与其他UMF(本申请实施例以UMF_T为例)对接的媒体端点(记为T_caller_NW)。
S205、UMF_O向PCSCF_O发送分配端点响应，相应的，PCSCF_O接收UMF_O发送的分配端点响应。
该分配端点响应可包括UMF_O所分配的媒体端点信息。例如，UMF_O可分配两个媒体端点，即T_caller_UE和T_caller_NW。其中，T_caller_NW为UMF_O上与UMF_T对接的媒体端点。分配端点响应可包括T_caller_UE的信息和T_caller_NW的信息。如图2的(a)所示，分配响应端点包括T_caller_UE@UMF_O的信息和T_caller_NW@UMF_O的信息。T_caller_UE信息可包括T_caller_UE的IP地址和端口号。T_caller_NW的信息可包括T_caller_NW的IP地址和端口号。
S206、PCSCF_O发送invite消息，PCFCS_T接收invite消息。
PCSCF_O可将所接收的SDP信息中的IP地址修改为T_caller_NW的IP地址(记为IP_er_NW)，并构造本地媒体信息(记为local-media)的头域，例如，local-media：T_caller_UE＝“UMF-beijing-haidian2\T-1”；T_caller_NW＝“UMF-beijing-haidian2\T-2”，UMF_ori＝“UMF-beijing-haidian2”。可以理解的是，信元T_caller_UE可指示T_caller_UE的信息，信元T_caller_NW可指示T_caller_NW的信息，信元UMF_ori指示UMF_O的信息。
之后，PCSCF_O向PCSCF_T转发该invite消息。可以理解的是，PCSCF_O通过多个网元向PCSCF_T转发invite消息。这多个网元包括O侧的网元和T侧的网元。O侧网元向T侧网元转发invite消息时，删除invite消息中的local-media。
可以理解的是，类似UE_O，UE_T也可以通过请求接入网络，即UE_T向T侧的控制面网元发送请求，PCSCF_T接收到来自UE_T的请求，向NRF请求能够为UE_T提供接入类服务的UMF。NRF可确定能够为UE_T提供接入类服务的UMF为UMF_T。后续，类似，PCSCF_O，PCSCF_T也可以请求UMF_T分配媒体端点。
S207、PCSCF_T向NRF发送服务发现请求，相应的，NRF接收PCSCF_T发送的服务发现请求，该服务发现请求用于获取所需接入能力的UMF的信息。
S208、NRF向PCSCF_T发送服务发现响应，相应的，PCSCF_T接收NRF发送的服务发现响应，该服务发现响应指示具有所需接入能力的UMF。例如，该服务发现响应包括UMF_T的信息。
S209、PCSCF_T向UMF_T发送分配端点请求，相应的，UMF_T接收PCSCF_T发送的分配端点 请求。
该分配端点请求可包括T_caller_NW@UMF_O的信息，例如T_caller_NW的IP地址。该分配端点请求可以包括SDP信息，该SDP信息包括T_caller_NW@UMF_O的信息。
S210、UMF_T向PCSCF_T发送分配端点响应，相应的，PCSCF_T接收UMF_T发送的分配端点响应。
该分配端点响应可包括UMF_T所分配的媒体端点信息。例如，UMF_T可分配两个媒体端点，即T_called_UE和T_called_NW。其中，T_called_UE为UMF_T上与UE_T对接的媒体端点，T_called_NW为UMF_T上与其他UMF(本申请实施例以UMF_O为例)对接的媒体端点。分配端点响应包括T_called_UE@UMF_T的信息和T_called_NW@UMF_T的信息。T_called_UE@UMF_T的信息包括T_called_UE的IP地址和端口号。T_called_NW@UMF_T的信息包括T_called_NW的IP地址和端口号。
S211、PCSCF_T向UE_T发送invite消息，相应的，UE_T接收PCSCF_T发送的invite消息。
PCSCF_T接收到AS_T发送的invite消息，可将该invite消息包括的SDP信息中的IP地址修改为UMF_T的T_called_UE的IP地址，再转发给UE_T。即PCSCF_T发送给UE_T的invite消息包括T_called_UE@UMF_T的信息，例如，T_called_UE的IP地址和端口号。
S212、UE_T与UMF_T的T_called_UE与建立连接。
UE_T接收到invite消息，可根据invite消息中的SDP信息确定UMF_T上与UE_T对接的端点为T_called_UE，从而与UMF_T的T_called_UE与建立连接。
S213、UE_T向PCSCF_T发送180消息，相应的，PCSCF_T接收UE_T发送的180消息。该180消息包括T_called_UE@UMF_T的信息。
S214、AS_T接收呼叫信令。
该呼叫信令与UE_O与UE_T之间的呼叫业务相关联。可以理解的是，接入类控制面网元或互通类控制面网元在UE_T的呼叫信令的触发下，向AS_T发送呼叫信令。该呼叫信令可为呼叫流程中的180消息。
该呼叫信令包括用于为呼叫业务提供媒体面服务的媒体面网元信息和媒体面网元的媒体端点信息，例如媒体端点的IP地址和端口号。例如，PCSCF_T接收180消息之后，可构造local-media的头域，例如，local-media：T_called_UE＝“UMF-beijing-haidian1\T-1”；T_called_NW＝“UMF-beijing-haidian1\T-2”，UMF_ori＝“UMF-beijing-haidian1”。可以理解的是，信元T_called_UE可指示T_called_UE的信息，信元T_called_NW可指示T_called_UE的信息，信元UMF_ori指示UMF_T的信息。之后，PCSCF_T转发构造local-media之后的180消息，即呼叫信令。由此可知，呼叫信令携带了UMF_T的T_called_UE的信息，以及UMF_T的T_called_NW的信息。
可以理解的是，AS_T接收的呼叫信令，可以是PCSCF_T和SCSCF转发的呼叫信令。AS_T接收呼叫信令可以是AS_T接收一条信令，例如，该信令包括T_called_NW@UMF_T的信息、T_called_UE@UMF_T的信息和UMF_T的信息以及T_caller_UE@UMF_O的信息。AS_T接收呼叫信令也可以是AS_T接收多条信令，例如，AS_T分别接收两条信令，其中一条信令包括T_called_NW@UMF_T的信息、T_called_UE@UMF_T的信息和UMF_T的信息，另一条信令包括T_caller_UE@UMF_O的信息。也可以理解为，T_caller_NW@UMF_O的信息和UMF_T的信息可承载于一条信令，也可以承载于不同的信令。
具体地，图2的(a)所示的流程结束之后，AS_T可以选择为具有特殊回铃音能力的UMF提供特殊回铃音服务。
作为一种可能的实现方式，提供接入服务的UMF和提供特殊回铃音的UMF为一个UMF，如图2的(b)所示，图2的(b)所示的为一种播放特殊回铃音的流程，包括以下步骤：
S215a、AS_T向NRF发送请求消息#1，相应的，NRF接收AS_T发送的请求消息#1。
示例性地，AS_T接收呼叫信令之后，基于呼叫信令中的信息，例如，UE_O或者UE_T的标识，确定需要向UE_O放音(其原因例如：UE_T的用户已经订购了“放音”增殖服务，即彩铃服务)，进而确定需要一个能够向UE_O放音的UMF；为此，AS_T可向NRF发送请求消息#1，以请求获取能够提供放音服务的UMF。这是因为如果仍然使用为UE_T初始选择的UMF_T为UE_O或UE_T提供放音服务，由于UMT_T自身能力的限制，可能无法提供放音服务。即，默认使用UMF_T提供放音服务， 可能会造成放音服务的失败。举例来说，UMF_T为图1中的UMF_1，该UMF_1能够提供的媒体面服务包括会议服务和语音识别服务，不能支持放音服务。如果默认通过UMF_T为UE_O提供放音服务，那么放音服务会失败。具体的，AS_T可向NRF发送请求消息#1，该请求消息#1用于请求能够支持AS_T需要的放音服务的媒体面网元。
可以理解的是，本申请实施例对请求消息#1的具体名称不作限制。例如，请求消息#1可以是服务发现请求消息。
可以理解的是，如果UMF_T也能够提供放音服务，那么可优先选择UMF_T提供放音服务。这是因为UE_T在接入网络过程中，UMF_T已经分配了媒体端点，即T_called_UE和T_called_NW。因此，通过T_called_NW就可以建立UMF_T与UE_O之间的媒体传输通道，无需再次触发请求分配媒体端点的流程，从而可以降低提供放音服务的时延。因此，在UMF_T能够提供放音服务的情况下，NRF可优先选择UMF_T提供放音服务，以尽量降低时延。
可选地，为了使得NRF优先考虑以UMF_T作为提供放音服务的目标UMF，AS_T可向NRF提供UMF_T的信息，以指示NRF优先考虑UMF_T。例如，请求消息#1还包括优选网元信息，该优选网元信息指示初始选择的UMF。例如初始选择的UMF为UMF_T，例如，优选网元信息可包括UMF_T的ID或者IP地址。应理解，AS_T所接收的呼叫信令包括UMF_T的信息，从而通过请求消息#1提供给NRF。
优选网元信息包括UMF_T的信息，也可以理解为，优选网元信息隐含指示在UMF_T和UMF_T_Res都能够提供放音服务的情况下，以UMF_T作为目标UMF。即，目标UMF和UMF_T可以是同一个网元，或者，目标UMF和UMF_T也可以是不同的网元。图2的(b)以目标UMF为UMF_T为例。
请求消息#1包括网元需求信息，该网元需求信息可以指示所需要的媒体面服务的信息，例如放音服务的信息。该放音服务的信息可包括指示需要具备放音服务的UMF的取值，以表示需要能够提供放音服务的UMF。可选地，该网元需求信息也可以指示所需要的媒体面网元的信息。NRF可根据网元需求信息为放音服务选择合适的媒体面网元(称为目标媒体面网元)，例如，图2的(b)的UMF_T。具体的，该请求消息#1可为HTTP请求消息。作为一示例，HTTP请求消息可为：
其中，“PreferedUMF”指示以初始选择的UMF为优先选择的UMF，示例性地，其值可以是初始选择的UMF(如本例中的UMF_T)的信息，例如取值为“UMF-beijing-haidian1”，表示从前述180消息携带过来的初始接入UMF。“RequiredUMF”表示需要提供资源类服务的UMF，例如，取值为“playtone”，表示需要具备“向主叫UE放音”能力的UMF。
S216a、NRF向AS_T发送响应消息#1，相应的，AS_T接收NRF发送的响应消息#1。
NRF根据优选网元信息和网元需求信息从多个UMF中确定能够提供放音服务的目标UMF，即UMF_T。NRF确定目标UMF之后，向AS_T发送响应消息#1，该响应消息#1可指示目标UMF。
例如，NRF可获取所存储的各个UMF的NFS信息，以根据各个UMF的NFS信息确定能够提供的放音服务的UMF。首先，NRF根据优选网元信息，可优先获取UMF_T的能力信息，从而根据UMF_T的能力信息确定UMF_T是否能够提供放音服务。如果UMF_T能够提供放音服务，那么NRF将UMF_T确定为目标UMF，也就是，目标UMF和UMF_T是同一个网元。图2的(b)主要考虑目标UMF和 UMF_T是同一个网元的情况。
如果目标媒体面和UMF_T是同一个网元，该响应消息#1可包括UMF_T的信息，例如UMF_T的ID或IP地址；或者，该响应消息#1也可以包括一个反馈指示。如果响应消息#1包括反馈指示，对于AS_T来说，可默认目标UMF为UMF_T。
其中，响应消息#1可为HTTP响应消息。作为一个示例，该HTTP响应消息可为：
其中，字段"nfInstances"表示满足放音服务要求的UMF(即UMF_T)的信息。"nfInstanceId"为属于字段"nfInstances"的一个字段，表示唯一标识UMF的ID，例如取值为“UMF-beijing-haidian1”(与请求消息#1中的指定值一致)。
S217a，AS_T确定目标UMF和UMF_T是同一个网元。
图2的(b)所示的情况下，AS_T可以根据接收到的响应消息#1中包括的信息确定提供资源类服务的目标UMF和提供接入类服务的UMF_T是同一个网元。
S218a，AS_T向AS_O发送180消息，相应的，AS_O接收AS_T发送的180消息。
AS_T接收响应消息#1，可构造SDP信息，即将SDP信息中的IP地址赋值为UMF_T的T_called_NW的IP地址，将SDP信息中的端口赋值为UMF_T的T_called_NW的端口号，再向AS_O发送包括SDP信息的180消息。
可以理解为，AS_T可通过180消息向AS_O传递T_called_NW的IP地址。例如，AS_T可向SCSCF_T发送携带T_called_NW的IP地址的180消息，SCSCF_T向SCSCF_O转发携带T_called_NW的IP地址的180消息。SCSCF_O向AS_O转发携带T_called_NW的IP地址的180消息。
S219a、AS_O向PCSCF_O发送180消息，相应的，PCSCF_O接收AS_O发送的180消息。
该180消息与S419的180消息携带的内容相同，即该180消息也包括UMF_T的T_called_NW的信息。
S220a、PCSCF_O向UMF_O指示UMF_O的T_caller_NW与UMF_T的T_called_NW连接。
S221a、PCSCF_O向UE_O发送18x消息，相应的，UE_O接收PCSCF_O发送的18x消息。
PCSCF_O可将从AS_O接收的180消息包括的SDP信息中的IP地址替换为T_caller_UE的IP地址，生成新的18x消息，再转发给UE_O。例如，18x消息可以是183消息。
S222a、UMF_O的T_caller_NW与UMF_T的T_called_NW建立连接。
可以理解的是，当T_caller_NW与T_called_NW连接，可实现UMF_O与UMF_T之间的通道连接，从而实现UE_O与UMF_T之间的通道连接。
S223a、UMF_O的T_caller_UE与UE_O建立连接。
S224a、UE_O和UE_T之间交互PRACK请求消息/200消息。
PRACK请求消息/200消息通过两条信令承载，一条信令承载PRACK请求消息，另一条信令承载200消息。200消息可认为是PRACK请求消息的响应消息。通过在UE_O和UE_T之间交互PRACK请求消息/200消息，可指示UMF_O的T_caller_NW与UMF_Ts的T_called_NW已经建立连接。UE_O从PCSCF_O接收到18x消息，可向PCSCF_O发送PRACK请求消息/200消息，由PCSCF_O将PRACK请求消息/200消息发送AS_O。AS_O接收到PRACK请求消息/200消息，向AS_T发送PRACK请求消息或200消息。AS_T接收PRACK请求消息/或200消息，可确定UMF_O的T_caller_NW与UMF_T的T_called_NW已经建立连接。
S225a、AS_T指示UMF_T向UE_O放音。
示例性地，AS_T响应于确定UMF_O的T_caller_NW与UMF_T的T_called_NW已经建立连接， 可向UMF_T发送指示信息，该指示信息可指示UMF_T提供放音服务，也可以理解为，该指示信息可指示UMF_T开始放音。该指示信息可包括UMF_T的T_called_NW的信息，以指示T_called_NW向UE_O放音。
S226a、UMF_T向UE_O发送音频流。
UMF_T接收指示信息之后，向UE_O发送音频流。
示例性地，图2的(b)所示的情况下，媒体传输通道如图3所示，图3是示出了建立媒体传输通道连接的一种示意图。图3中，UMF_O为既能够为UE_O提供接入类媒体流传输服务，又能够为UE_T和/或UE_O提供资源类媒体流传输服务的UMF。UMF_T为既能够为UE_T提供接入类媒体流传输服务，又能够为UE_O/UE_T提供资源类媒体流传输服务的UMF。也可以理解为，能够为UE_T提供资源类媒体流传输服务的UMF是为UE_T初始选择的提供接入类媒体流传输服务的UMF。能够为UE_O提供资源类媒体流传输服务的UMF是为UE_O初始选择的提供接入类媒体流传输服务的UMF。这种情况下，由于UE_T在加入呼叫会话过程中，UMF_T已经分配了与UE_T对接的媒体端点(记为T_called_UE)和与其他UMF对接的媒体端点(记为T_called_NW)。因此，PCSCF_T无需向UMF_T触发请求分配端点的流程。同理，PCSCF_O也无需向UMF_O触发请求分配端点的流程。
作为另一种可能的实现方式，提供接入服务的UMF和提供特殊回铃音的UMF不为一个UMF，如图2的(c)所示，图2的(c)所示的为另一种播放特殊回铃音的流程，包括以下步骤：
S215b、AS_T向NRF发送请求消息#2，相应的，NRF接收AS_T发送的请求消息#2。
具体地，请求消息#2与上述的S215a中所示的请求消息#1相同，这里不再赘述。图2的(c)所示的流程与图2的(b)所示的流程不同点在于，以目标UMF为UMF_T_Res为例。
S216b、NRF向AS_T发送响应消息#2，相应的，AS_T接收NRF发送的响应消息#2。
NRF根据优选网元信息和网元需求信息从多个UMF中确定能够提供放音服务的目标UMF，即UMF_T_Res。NRF确定目标UMF之后，向AS_T发送响应消息#2，该响应消息#2可指示目标UMF。
例如，NRF可获取所存储的各个UMF的NFS信息，以根据各个UMF的NFS信息确定能够提供的放音服务的UMF。首先，NRF根据优选网元信息，可优先获取UMF_T的能力信息，从而根据UMF_T的能力信息确定UMF_T是否能够提供放音服务。如果UMF_T能够提供放音服务，那么NRF将UMF_T确定为目标UMF，也就是，目标UMF和UMF_T是同一个网元。相反，如果UMF_T不能提供放音服务，那么NRF获取所存储的其他UMF的能力信息，从而选择出能够提供放音服务的UMF。即NRF可选择一个能够提供放音服务的UMF作为目标UMF。这种情况下，目标UMF与UMF_T不是同一个网元。NRF优选考虑UMF_T，在减少放音服务失败的前提下，可尽量降低放音服务的时延。
假设UMF_T为图1中的UMF1，NRF可获取UMF_1的能力信息，确定UMF_1无法提供放音服务。后续，NRF可获取UMF_2的能力信息和UMF_3的能力信息，进而确定UMF_2能够提供的服务包括网络地址翻译服务、放音服务和媒体处理服务，UMF_3能够提供的服务包括网络地址翻译服务和放音服务。网络功能存储网元可确定UMF_2或UMF_3作为目标UMF，即UME_T_Res。
其中，响应消息#2可为HTTP响应消息。作为一个示例，该HTTP响应消息可为：
其中，字段"nfInstances"表示满足放音服务要求的UMF(即UMF_T_Res)的信息。"nfInstanceId"为属于字段"nfInstances"的一个字段，表示唯一标识UMF的ID，例如取值为“UMF-beijing-haidian2”(与请求消息#2中的指定值不一致)。
S217b，AS_T确定目标UMF和UMF_T不是同一个网元。
图2的(c)所示的情况下，AS_T可以根据接收到的响应消息#2中包括的信息确定提供资源类服务的目标UMF和提供接入类服务的UMF_T不是同一个网元。
S218b、AS_T向UMF_T_Res发送请求消息#3，相应的，UMF_T_Res接收AS_T发送的请求消息#3。
该请求消息#3可用于向UMF_T_Res请求分配媒体端点(例如称为目标媒体端点)。该目标媒体端点为T_called_media。也可以理解为，请求消息#3用于请求提供放音服务的目标媒体端点，或者用于请求目标媒体端点信息。目标媒体端点信息可包括UMF_T_Res提供放音服务所用的IP地址和端口号。可以理解的是，本申请实施例对请求消息#3的具体名称不作限制，例如，请求消息#3也可以称为分配端点请求消息。
该请求消息#3可包括UMF_O与T侧UMF对接的媒体端点信息。为方便描述，将UMF_O与T侧UMF对接的媒体端点信息为UMF_O的T_caller_NW的信息。例如，请求消息#3可包括SDP信息，该SDP信息包括UMF_O的T_caller_NW的IP地址和端口号。UMF_T_Res接收到请求消息#3，可分配目标媒体端点，例如T_called_media。与请求消息#2类似，请求消息#3也为HTTP信息。
S219b、UMF_T_Res向AS_T发送响应消息#3，相应的，AS_T接收UMF_T_Res发送的响应消息#3。该响应消息#3也可以称为服务发现响应消息。
响应消息#3可指示UMF_T_Res为提供放音服务分配的目标媒体端点，即T_called_media。例如，响应消息#3可包括UMF_T_Res的T_called_media的信息，例如T_called_media的IP地址和端口号。
AS_T获知UMF_T_Res的T_called_media的信息，可将该T_called_media的信息转发给PCSCF_O。例如AS_T可将T_called_media的信息转发给AS_O，由AS_O再将T_called_media的信息转发给PCSCF_O。
S220b、AS_T向AS_O发送180消息，相应的，AS_O接收AS_T发送的180消息。
AS_T接收响应消息#3，可构造SDP信息，即将SDP信息中的IP地址赋值为UMF_T_Res的T_called_media的IP地址，将SDP信息中的端口赋值为UMF_T_Res的T_called_media的端口号，再向AS_O发送包括SDP信息的180消息。可以理解为，AS_T可通过180消息向AS_O传递T_called_media的IP地址。例如，AS_T可向SCSCF_T发送携带T_called_media的IP地址的180消息，SCSCF_T向SCSCF_O转发携带T_called_media的IP地址的180消息。SCSCF_O向AS_O转发携带T_called_media的IP地址的180消息。
S221b、AS_O向PCSCF_O发送180消息，相应的，PCSCF_O接收AS_O发送的180消息。
该180消息与S220a的180消息携带的内容相同，即该180消息也包括UMF_T_Res的T_called_media的信息。
S222b、PCSCF_O向UMF_O指示UMF_O的T_caller_NW与UMF_T_Res的T_called_media连接。
S223b、PCSCF_O向UE_O发送18x消息，相应的，UE_O接收PCSCF_O发送的18x消息。
PCSCF_O可将从AS_O接收的180消息包括的SDP信息中的IP地址替换为T_caller_UE的IP地址，生成新的18x消息，再转发给UE_O。例如，18x消息可以是183消息。
S224b、UMF_O的T_caller_NW与UMF_T_Res的T_called_media建立连接。
可以理解的是，当T_caller_NW与T_called_media连接，可实现UMF_O与UMF_T_Res之间的通道连接，从而实现UE_O与UMF_T_Res之间的通道连接。
S225b、UMF_O的T_caller_UE与UE_O建立连接。
S226b、UE_O和UE_T之间交互PRACK请求消息/200消息。
AS_T接收PRACK请求消息/或200消息，可确定UMF_O的T_caller_NW与UMF_T_Res的T_called_media已经建立连接。
S227b、AS_T指示UMF_T_Res向UE_O放音。
示例性地，AS_T响应于确定UMF_O的T_caller_NW与UMF_T_Res的T_called_media已经建立连接，可向UMF_T_Res发送指示信息，该指示信息可指示UMF_T_Res提供放音服务，也可以理解为，该指示信息可指示UMF_T_Res开始放音。该指示信息可包括UMF_T_Res的T_called_media的信息，以指示T_called_media向UE_O放音。
S228b、UMF_T_Res向UE_O发送音频流。
UMF_T_Res接收指示信息之后，向UE_O发送音频流。
示例性地，图2的(b)所示的情况下，媒体传输通道如图4的(a)所示，图4的(a)是示出了建立媒体传输通道连接的另一种示意图。图4的(a)是示出了建立媒体传输通道连接的另一种示意图。图4以包括UMF_O、UMF_T、UMF_T_Res、UE_O、UE_T为例。O侧(即主叫侧)的控制面网元可以请求UMF为UE_O和/或UE_T提供媒体流传输服务。UE_T可通过T侧(即被叫侧)的控制面网元请求网络侧提供媒体流传输服务。其中，UMF_O为既能够为UE_O提供接入类媒体流传输服务，又能够为UE_T和/或UE_O提供资源类媒体流传输服务的UMF。UMF_T为UE_T加入呼叫会话过程中，由T侧控制面网元(例如PCSCF_T)为T侧初始选择的UMF，能够为UE_O和/或UE_T提供接入类媒体流传输服务。UMF_T_Res为能够为UE_O和/或UE_T提供资源类媒体流传输服务的UMF。初始选择的UMF也可以理解为PCSCF网元在呼叫会话过程中第一次申请媒体端点时，为PCSCF网元所在侧所选择的UMF。
UE_T在加入呼叫会话过程中，UMF_T会分配与UE_T对接的媒体端点(记为T_called_UE)和与其他UMF对接的媒体端点(记为T_called_NW)。同理，UE_O在加入呼叫会话过程中，UMF_O会分配与UE_O对接的媒体端点(记为T_caller_UE)和与其他UMF对接的媒体端点(记为T_caller_NW)。且在上述接入过程中，UE_T会与T_called_UE连接，UE_O会与T_caller_UE连接。因此，当T_called_NW和T_caller_NW建立连接，可实现UE_O和UE_T之间的媒体传输通道的连接。
然而当UMF_T_Res为能够为UE_T提供媒体流传输服务，由于初始选择的UMF为UMF_T，因此，PCSCF_T并不知道UMF_T_Res上的媒体端点。这种情况下，PCSCF_T请求获取UMF_T_Res上的媒体端点，以实现UMF_T_Res与UE_O和/或UE_T之间的媒体传输通道的连接。例如，PCSCF_T可向UMF_T_Res请求分配媒体端点，UMF_T_Res可分配媒体端点T_called_media，UMF_T_Res通过T_called_media提供媒体流传输服务。当T_called_media与T_caller_NW连接，可为UE_O提供媒体流传输服务。
应理解，上述只是举例说明UMF_T不能提供资源类媒体流传输服务，若上述的UMF_O不能提供资源类媒体流传输服务，PCSCF_O可向UMF_O_Res请求分配媒体端点，UMF_O_Res可分配媒体端点T_caller_media，UMF_O_Res通过T_caller_media提供媒体流传输服务。当T_caller_media与T_called_NW连接，可为UE_T提供媒体流传输服务。媒体传输通道如图4的(b)所示，图4的(b)是示出了建立媒体传输通道连接的又一种示意图，具体情况参考图4的(a)的描述，不同点在于主叫侧由UMF_O_Res提供资源类服务，这里不再赘述。
上述结合图2的(a)至图2的(c)详细介绍了一种被叫AS为主叫播放特殊回铃音的流程，由上述可知，针对不同的场景(如，提供接入服务的UMF和提供特殊回铃音的UMF是否为一个UMF)AS需要执行不同的流程(如，执行图2的(b)或者图2的(c)所示的流程)，也就是说AS需要根据判断结果确定不同的处理流程，降低了AS的处理效率。
例如，图2的(b)中需要执行步骤S217a确定接收到的UMF信息为UMF_T的信息，并且在执行步骤S217a之后无需请求分配新的媒体端点，直接执行步骤S218a至S224a建立媒体端点之间的连接，并执行S225a指示UMF_T上的媒体端点执行服务。
还例如，图2的(c)中需要执行步骤S217b确定接收到的UMF信息不为UMF_T的信息而是UMF_T_Res的信息，并且通过执行步骤S218b请求UMF_T_Res分配媒体端点，然后执行步骤S220b至S226b建立媒体端点之间的连接，并执行S227b指示UMF_T_Res上的媒体端点执行服务。
为了解决上述的AS处理效率低的问题，本申请提供一种通信方法，以期在提供资源类服务的流程中简化AS的操作，提高AS处理效率。
为了便于理解本申请实施例，做出以下几点说明。
第一，在本申请中，“用于指示”可以包括用于直接指示和用于间接指示。当描述某一指示信息用于指示A时，可以包括该指示信息直接指示A或间接指示A，而并不代表该指示信息中一定携带有A。
将指示信息所指示的信息称为待指示信息，则具体实现过程中，对待指示信息进行指示的方式有很多种，例如但不限于，可以直接指示待指示信息，如待指示信息本身或者该待指示信息的索引等。也可以通过指示其他信息来间接指示待指示信息，其中该其他信息与待指示信息之间存在关联关系。还可以仅仅指示待指示信息的一部分，而待指示信息的其他部分则是已知的或者提前约定的。例如， 还可以借助预先约定(例如协议规定)的各个信息的排列顺序来实现对特定信息的指示，从而在一定程度上降低指示开销。同时，还可以识别各个信息的通用部分并统一指示，以降低单独指示同样的信息而带来的指示开销。
第二，在本申请中示出的“至少一个”是指一个或者多个，“多个”是指两个或两个以上。另外，在本申请的实施例中，“第一”、“第二”以及各种数字编号(例如，“#1”、“#2”等)只是为了描述方便进行的区分，并不用来限制本申请实施例的范围。下文各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定，应该理解这样描述的对象在适当情况下可以互换，以便能够描述本申请的实施例以外的方案。此外，在本申请实施例中，“S510”、“S601”、等字样仅为了描述方便作出的标识，并不是对执行步骤的次序进行限定。
第三，本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
第四，本申请实施例中涉及的“保存”，可以是指的保存在一个或者多个存储器中。该一个或者多个存储器，可以是单独的设置，也可以是集成在编码器或者译码器，处理器、或通信装置中。该一个或者多个存储器，也可以是一部分单独设置，一部分集成在译码器、处理器、或通信装置中。存储器的类型可以是任意形式的存储介质，本申请并不对此限定。
第五，本申请实施例中涉及的“协议”可以是指通信领域的标准协议，例如可以包括NR协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
第六，本申请实施例中，“的(of)”，“相应的(corresponding，relevant)”、“对应的(corresponding)”和“关联的(associate)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。
第七，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
第八，本申请说明书附图部分的方法流程图中的虚线框表示可选的步骤。
以下，不失一般性，以网元之间的交互为例详细说明本申请实施例提供的通信方法。
图5是本申请实施例提供的一种通信方法的示意性流程图，包括以下步骤：
S501，主叫发起呼叫请求以及被叫返回180消息的流程。
在主叫发起呼叫请求以及被叫返回180消息的流程中，能够确定得到为第一终端和第二终端提供接入类服务的媒体面网元。
示例性地，第一终端为主叫终端，第二终端为被叫终端；或者，第一终端为被叫终端，第二终端为主叫终端。具体地，确定为第一终端和第二终端提供接入类服务的媒体面网元的流程可以参考上文中图2的(a)所示的流程，提供接入类服务的媒体端点可以沿用图2的(a)所示的标识(如，T_caller_UE、T_caller_NW、T_called_UE和T_called_NW)，这里不再赘述。
为了便于描述，该实施例中以第一终端为主叫终端(如，图2的(a)所示UE_O)，第二终端为被叫终端(如，图2的(a)所示UE_T)为例进行描述。应理解，第一终端为UE_T，第二终端为UE_O的情况下，将下述实施例中的UE_O执行的步骤替换为由UE_T执行，UE_T执行的步骤替换为由UE_O执行即可，不再重复说明。
由图2的(a)所示的流程可知，确定为UE_O和UE_T提供接入类服务的媒体面网元包括：确定为UE_O提供接入类服务的UMF(如，图2的(a)所示UMF_O)，以及确定为UE_T提供接入类服务UMF(如，图2的(a)所示UMF_T)。
该实施例中对于确定为UE_O和UE_T提供接入类服务的媒体面网元的具体流程不做限制，可以参考目前相关技术中的关于确定提供接入类服务的媒体面网元的流程，该实施例中主要涉及应用服务器在接收到呼叫信令之后，如何选择提供资源类服务的媒体面网元，以及如何实现执行资源类服务。
下面以被叫侧应用服务器(如，AS_T)选择提供资源类服务的UMF(如，UMF_T/UMF_T_Res)为例进行说明，应理解，主叫侧应用服务器(如，AS_O)选择提供资源类服务的UMF(如，UMF_O/O_Res) 的情况下，将下述实施例中由被叫侧应用服务器执行的步骤替换为由主叫侧应用服务器执行，被叫侧提供资源类服务的媒体面网元执行的步骤替换为由提供资源类服务的媒体面网元执行即可，不再重复说明。
具体地，为了实现选择提供资源类服务的媒体面网元，图5所示的方法流程还包括：
S511，应用服务器向NRF发送请求消息#1，相应的，NRF接收应用服务器发送的请求消息#1。
参考上述步骤S215a的描述，这里不再赘述。
具体地，该应用服务器为第二终端对应的应用服务器(如，图5中所示的AS_T)。
S512，NRF向AS_T发送媒体面网元的信息，相应的，AS_T接收NRF发送的媒体面网元的信息。
具体地，该实施例中NRF向AS_T发送的媒体面网元的信息可以是UMF_T的信息(如，参考上述步骤S216a中响应消息#1中包括的信息)，还可以是UMF_T_Res的信息(如，参考上述步骤S216b中响应消息#2中包括的信息)。
为了便于描述，下文中将媒体面网元的信息所指示的媒体面网元记为UMF_T/UMF_T_Res。
示例性地，媒体面网元的信息可以是UMF_T/UMF_T_Res的标识(identify，ID)，或者其他可以用于识别UMF_T/UMF_T_Res的信息，本申请中不做限定。
进一步地，该实施例中AS_T接收到上述的媒体面网元的信息之后，无需判断该媒体面网元的信息所指示的UMF_T/UMF_T_Res和提供接入类服务的UMF_T是否为同一个UMF，可以理解为该实施例中AS_T不感知为融合场景还是非融合的场景，直接请求UMF_T/UMF_T_Res分配用于提供资源类服务的媒体端点，图5所示的方法流程还包括：
S520，AS_T向UMF_T/UMF_T_Res发送请求信息，相应的，UMF_T/UMF_T_Res接收来自AS_T的请求信息。
可以理解为，该实施例中AS_T无需判断接收到的媒体面网元的信息所指示的媒体面网元和已经确定的提供接入类服务的UMF_T之间的关系，直接发起媒体端点分配请求即可，对于AS_T来说简化了操作流程，提高了处理效率。而且，该实施例中不再区分融合场景和非融合场景，不同的场景基于相同的处理流程。
该UMF_T/UMF_T_Res为提供资源类服务的UMF(如，图2的(b)中所示的UMF_T或者图2的(c)中所示的UMF_T_Res)。
该请求信息用于请求UMF_T/UMF_T_Res分配用于提供资源类服务的媒体端点。也可以理解为，请求信息用于请求提供放音服务的目标媒体端点，或者说请求信息用于请求目标媒体端点信息。目标媒体端点信息可包括UMF_T/UMF_T_Res提供放音服务所用的IP地址和端口号。其中，UMF_T/UMF_T_Res提供放音服务所用的IP地址和端口号可以理解为第二媒体端点的本端地址包括的IP地址和端口号。
可以理解的是，本申请实施例对请求信息的具体名称不作限制，例如，请求信息也可以称为分配端点请求消息。
示例性地，该请求信息中可包括与UMF_T/UMF_T_Res上第二媒体端点对接的IP地址。如，请求信息中包括远端地址，该远端地址可以理解为与第二媒体端点建立连接的媒体端点的地址，可以称为第二媒体端点的远端地址。
具体地，请求信息中包括的远端地址为远端IP地址和远端端口信息(如，端口号)。
例如，该请求信息中包括UMF_O与T侧UMF对接的媒体端点信息。为了方便描述，将UMF_O与T侧UMF对接的媒体端点信息为UMF_O的T_caller_NW的信息。如，请求信息可包括SDP信息，该SDP信息包括UMF_O的T_caller_NW的IP地址。或者该SDP信息包括UMF_O的T_caller_NW的IP地址和端口号。
还例如，该请求信息中包括UMF_T与T侧UMF对接的媒体端点信息。为了方便描述，将UMF_T与T侧UMF对接的媒体端点信息为UMF_T的T_called_NW的信息。如，请求信息可包括SDP信息，该SDP信息包括UMF_T的T_called_NW的IP地址。或者该SDP信息包括UMF_T的T_called_NW的IP地址和端口号。
应理解，上述的请求信息中包括T_caller_NW的IP地址和端口号，或T_called_NW的IP地址和端口号，只是举例说明请求信息中包括与T侧UMF对接的媒体端点信息可能的情况，对本申请的保护 范围不构成任何的限定，该请求信息中包括的与T侧UMF对接的媒体端点信息还可以是其他媒体端点的信息，这里不再一一举例说明。
具体地，该实施例中请求信息中还包括第一媒体端点的信息，该第一媒体端点的信息包括用于提供接入类服务的媒体端点的信息。
例如，请求信息中还包括T_called_NW的信息，该T_called_NW为上述步骤S501中确定的媒体端点。其中，T_called_NW的信息可以包括T_called_NW所属的UMF的标识(如，UMF-beijing-haidian1)和所述T_called_NW的标识(如，T-2)。如，请求信息为HTTP信息。作为一个示例，该HTTP信息可为：
其中，imsRCIR表示提供Reserve and(or)Configure IMS Resource功能的NFS；字段related_termination_UMF表示第一媒体端点的信息，包含两部分：第一部分为所属的UMF信息，第二部分为媒体端点标识。远端地址10.10.10.10:8888可以理解为T_caller_NW的IP地址。
UMF_T/UMF_T_Res接收到请求信息，可以根据请求信息中包括的第一媒体端点的信息判断该第一媒体端点是否为UMF_T/UMF_T_Res上的媒体端点，图5所示的流程还包括：
S530，UMF_T/UMF_T_Res根据第一媒体端点的信息判断第一媒体端点是否为UMF_T/UMF_T_Res上的媒体端点。
可以理解，该实施例中AS_T无需判断接收到的媒体面网元的信息所指示的媒体面网元和已经确定的提供接入类服务的UMF_T之间的关系，直接发起请求信息，并且通过在请求信息中携带第一媒体端点的信息，由接收请求信息的UMF_T/UMF_T_Res判断UMF_T/UMF_T_Res为能提供接入类服务和资源类服务的UMF，还是为提供资源类服务的UMF。
示例性地，UMF_T/UMF_T_Res根据第一媒体端点的信息判断第一媒体端点是否为UMF_T/UMF_T_Res上的媒体端点得到判断结果，该判断结果包括：第一媒体端点为UMF_T/UMF_T_Res上的媒体端点或第一媒体端点不为UMF_T/UMF_T_Res上的媒体端点。
由上述可知，第一媒体端点的信息包括第一媒体端点所属的UMF信息和第一媒体端点的标识。或者，第一媒体端点的信息包括第一媒体端点的标识，该第一媒体端点的标识中包括有第一媒体端点所属的UMF信息。
UMF_T/UMF_T_Res根据第一媒体端点所属的UMF信息可以确定该第一媒体端点是否为 UMF_T/UMF_T_Res上的媒体端点。
例如，UMF_T/UMF_T_Res根据第一媒体端点所属的UMF信息确定第一媒体端点所属的UMF为该UMF_T/UMF_T_Res，进一步地，UMF_T/UMF_T_Res根据第一媒体端点的标识确定第一媒体端点为UMF_T/UMF_T_Res上已分配的端点。
作为一种可能的实现方式，UMF_T/UMF_T_Res确定第一媒体端点为UMF_T/UMF_T_Res上的媒体端点。可以理解为，上述的判断结果为：第一媒体端点为UMF_T/UMF_T_Res上的媒体端点(或者说第一媒体端点属于UMF_T/UMF_T_Res)。
在该实现方式下，可以理解为分配用于提供资源类服务的第二媒体端点的UMF_T/UMF_T_Res上分配有用于提供接入类服务的媒体端点，也就是说UMF_T/UMF_T_Res即可以提供接入类服务也可以提供资源类服务，可以理解为前文所述的融合场景，即UMF_T/UMF_T_Res与UMF_T为同一个UMF。
具体地，在UMF_T/UMF_T_Res确定第一媒体端点为UMF_T/UMF_T_Res上的媒体端点的情况下，UMF_T/UMF_T_Res可以无需分配新的媒体端点，而是将已分配的第一媒体端点作为用于提供资源类服务的第二媒体端点。该实现方式下，第二媒体端点的本端地址和第一媒体端点的本端地址相同，而第二媒体端点的远端地址和第一媒体端点的远端地址可以相同也可以不同。可以理解为第二媒体端点是UMF_T/UMF_T_Res根据第一媒体端点是否属于所述媒体面网元确定的。
其中，本端地址和远端地址时针对单个媒体端点来说的，某个媒体端点与外部的五元组连接中，本端地址指的是五元组中自身的IP地址和端口，而远端地址指的是五元组中对方的IP地址和端口。
示例性地，该实现方式下，第二媒体端点可以称为第一媒体端点的镜像媒体端点。如，第一媒体端点为T_called_NW，第二媒体端点为T_called_NW’。
需要说明的是，在第一媒体端点和第二媒体端点由不同的标识信息进行标识，也就是说即使UMF_T/UMF_T_Res未分配新的媒体端点，但是对于申请分配第二媒体端点的应用服务器来说确实是获得一个新的媒体端点的信息。
作为另一种可能的实现方式，UMF_T/UMF_T_Res确定第一媒体端点不为UMF_T/UMF_T_Res上的媒体端点。
在该实现方式下，可以理解为分配用于提供资源类服务的第二媒体端点的UMF_T/UMF_T_Res上未分配有用于提供接入类服务的媒体端点，也就是说UMF_T/UMF_T_Res不可以即提供接入类服务还提供资源类服务，可以理解为前文所述的非融合场景，即UMF_T/UMF_T_Res与UMF_T不为同一个UMF。
具体地，在UMF_T/UMF_T_Res确定第一媒体端点不为UMF_T/UMF_T_Res上的媒体端点的情况下，UMF_T/UMF_T_Res分配新的媒体端点，与上述的图2的(c)中所示的分配T_called_media类似。该实现方式下，第二媒体端点的本端地址和第一媒体端点的本端地址不相同。
应理解，UMF_T/UMF_T_Res分配第二媒体端点之后，将UMF_T/UMF_T_Res的信息记录在本地存储器中。例如，如下表2所示：
表2：第一媒体端点为UMF_T/UMF_T_Res上的媒体端点，第二媒体端点为第一媒体端点的镜像媒体端点，UMF_T/UMF_T_Res为前文所示的UMF_T。
或者，如下表3所示：
表3：第一媒体端点不为UMF_T/UMF_T_Res上的媒体端点，UMF_T/UMF_T_Res为前文所示的UMF_T_Res。
进一步地，UMF_T/UMF_T_Res向应用服务器发送第二媒体端点的信息。图5所示的方法流程还包括：
S540，UMF_T/UMF_T_Res向AS_T发送第二媒体端点的信息，相应的，AS_T接收来自UMF_T/UMF_T_Res的第二媒体端点的信息。
示例性地，第二媒体端点的信息可以是第二媒体端点的IP地址和端口号。
如，第二媒体端点的信息通过HTTP响应消息发送给AS_T。作为一个示例，该HTTP响应消息可为：
其中，字段termination_id表示第二媒体端点的唯一标识，例如，取值T-2-Mir，表示是第一媒体端点T-2的镜像媒体端点，或者可以用其他标识信息标识，该实施例中不做限制。第二媒体端点的本端地址为9.9.9.9:9999，与T_called_NW的本端地址相同。
上述步骤S520至S540详细介绍了如何选择提供资源类服务的媒体面网元，以及该提供资源类服务的媒体面网元分配用于提供资源类服务的第二媒体端点的过程，在确定提供资源类服务的第二媒体端点之后，可以实现执行资源类服务。
具体地，该实施例中提供资源类服务流程包括以下两种方式：
方式一：UMF_T/UMF_T_Res向UE_O提供资源类服务，UMF_T/UMF_T_Res上的第二媒体端点提供资源类服务。
为了便于理解，结合图6进行说明，图6是本申请实施例提供的一种提供资源类服务的示意性流程图，包括以下步骤：
S601、AS_T向AS_O发送180消息，相应的，AS_O接收AS_T发送的180消息。
AS_T接收第二媒体端点的信息之后，可构造SDP信息，即将SDP信息中的IP地址赋值为UMF_T/UMF_T_Res的第二媒体端点的IP地址，将SDP信息中的端口赋值为UMF_T/UMF_T_Res的第二媒体端点的端口号，再向AS_O发送包括SDP信息的180消息。可以理解为，AS_T可通过180消息向AS_O传递第二媒体端点的IP地址。例如，AS_T可向SCSCF_T发送携带第二媒体端点的IP地址的180消息，SCSCF_T向SCSCF_O转发携带第二媒体端点的IP地址的180消息。SCSCF_O向AS_O转发携带第二媒体端点的IP地址的180消息。
S602、AS_O向PCSCF_O发送180消息，相应的，PCSCF_O接收AS_O发送的180消息。
该180消息与S602的180消息携带的内容相同，即该180消息也包括第二媒体端点的信息。
S603、PCSCF_O向UMF_O指示UMF_O的T_caller_NW与UMF_T/UMF_T_Res的第二媒体端点连接。
S604、PCSCF_O向UE_O发送18x消息，相应的，UE_O接收PCSCF_O发送的18x消息。
PCSCF_O可将从AS_O接收的180消息包括的SDP信息中的IP地址替换为T_caller_UE的IP地址，生成新的18x消息，再转发给UE_O。例如，18x消息可以是183消息。
S605、UMF_O的T_caller_NW与UMF_T/UMF_T_Res的第二媒体端点建立连接。
可以理解的是，当T_caller_NW与第二媒体端点连接，可实现UMF_O与UMF_T/UMF_T_Res之间的通道连接，从而实现UE_O与UMF_T/UMF_T_Res之间的通道连接。
S606、UMF_O的T_caller_UE与UE_O建立连接。
S607、UE_O和UE_T之间交互PRACK请求消息/200消息。
AS_T接收PRACK请求消息/或200消息，可确定UMF_O的T_caller_NW与UMF_T/UMF_T_Res的第二媒体端点已经建立连接。
S608、AS_T向UMF_T/UMF_T_Res发送指示信息，相应的，UMF_T/UMF_T_Res接收来自AS_T的指示信息。
作为一种可能的实现方式，AS_T响应于确定UMF_O的T_caller_NW与UMF_T/UMF_T_Res的第二媒体端点已经建立连接，可向UMF_T/UMF_T_Res发送指示信息，该指示信息可指示UMF_T/UMF_T_Res提供资源类服务。该指示信息可包括UMF_T/UMF_T_Res的第二媒体端点的信息，以指示第二媒体端点用于提供资源类服务。
S609、UMF_T/UMF_T_Res确定第二媒体端点的本端地址和远端地址不同。
具体地，UMF_T/UMF_T_Res接收指示信息之后，确定第二媒体端点的本端地址和远端地址不同。
S610，UMF_T/UMF_T_Res向UE_O提供资源类服务。
作为一种可能的实现方式，在方式一种，如果UMF_T/UMF_T_Res为前文所述的UMF_T，且第二媒体端点为前文所述的T_called_NW，则UMF_T/UMF_T_Res向UE_O提供资源类服务对应的媒体流传输路径如图3所示。
作为另一种可能的实现方式，在方式一种，如果UMF_T/UMF_T_Res为前文所述的UMF_T_Res，且第二媒体端点为前文所述的T_called_media，则UMF_T/UMF_T_Res向UE_O提供资源类服务对应的媒体流传输路径如图4的(a)所示。
方式二：UMF_T/UMF_T_Res向UE_T提供资源类服务，UMF_T/UMF_T_Res上的第三媒体端点提供资源类服务。
为了便于理解，结合图7进行说明，图7是本申请实施例提供的另一种提供资源类服务的示意性流程图，包括以下步骤：
S701，AS_T向PCSCF_T发送ACK消息，相应的，PCSCF_T接收AS_T发送的ACK消息。
示例性地，ACK消息为200消息的响应消息。AS_T接收第二媒体端点的信息之后，可构造SDP 信息，即将SDP信息中的IP地址赋值为UMF_T/UMF_T_Res的第二媒体端点的IP地址，将SDP信息中的端口赋值为UMF_T/UMF_T_Res的第二媒体端点的端口号，再向PCSCF_T发送包括SDP信息的ACK消息。可以理解为，AS_T可通过ACK消息向PCSCF_T传递第二媒体端点的IP地址。
S702，PCSCF_T向UMF_T指示UMF_T的T_called_NW与UMF_T/UMF_T_Res的第二媒体端点连接。
S703、PCSCF_T向UE_T发送ACK消息，相应的，UE_T接收PCSCF_T发送的ACK消息。
PCSCF_T可将从AS_T接收的ACK消息包括的SDP信息中的IP地址替换为T_called_UE的IP地址，生成新的ACK消息，再转发给UE_T。
S704、AS_T向UMF_T/UMF_T_Res发送指示信息，相应的，UMF_T/UMF_T_Res接收来自AS_T的指示信息。
该指示信息可包括UMF_T/UMF_T_Res的第二媒体端点的信息，以指示第二媒体端点用于提供资源类服务。
S705、UMF_T/UMF_T_Res确定第二媒体端点的本端地址和远端地址相同。
具体地，UMF_T/UMF_T_Res接收指示信息之后，确定第二媒体端点的本端地址和远端地址相同。
UMF_T/UMF_T_Res通过第三媒体端点提供所述资源类服务。第三媒体端点为UMF_T/UMF_T_Res上配置的与所述第二媒体端点对应的媒体端点。UMF_T/UMF_T_Res可以根据指示信息中包括的第二媒体端点的信息确定第三媒体端点。
作为一种可能的实现方式，上述的UMF_T/UMF_T_Res为提供接入服务的UMF_T，则上述的第二媒体端点为前文所示的T_called_NW的镜像端点(如，第二媒体端点的本端地址与T_called_NW相同)，第三媒体端点为前文所示的T_called_UE，T_called_NW和T_called_UE相对应的对应关系保存在UMF_T/UMF_T_Res中，UMF_T/UMF_T_Res可以根据对应关系和T_called_NW的信息确定T_called_UE。
在该实现方式下，UMF_T/UMF_T_Res在接收到指示信息之后，确定第二媒体端点的本端地址和远端地址相同，其中，第二媒体端点的远端地址可以由请求信息中携带IP地址和端口号获知。本申请实施例中规定，在UMF_T/UMF_T_Res分配的第二媒体端点的本端地址和和远端地址相同相同的情况下，由UMF_T/UMF_T_Res上已配置的与第二媒体端点对应的第三媒体端点提供所述资源类服务。
S706，UMF_T/UMF_T_Res向UE_T提供资源类服务。
需要说明的是，在方式二中，由于UMF_T/UMF_T_Res向UE_T提供资源类服务，也就是说无需建立T_caller_NW与UMF_T/UMF_T_Res的第二媒体端点之间的连接，从而在确定为第一终端和第二终端提供接入类服务的媒体面网元的流程中UE_O向PCSCF_O发送的INVITE消息中可以不携带SDP信息。
上述图5所示的实施例中，应用服务器在请求分配用于提供资源类服务的第二媒体端点的请求信息中携带用于提供接入类服务的第一媒体端点的信息，以便于分配第二媒体端点的媒体面网元根据第一媒体端点的信息判断第一媒体端点是否为媒体面网元上的媒体端点，并且媒体面网元可以根据判断结果分配第二媒体端点，其中，第一媒体端点为媒体面网元上的媒体端点可以理解为可以提供资源类服务的媒体面网元和接入类服务的媒体面网元为同一个媒体面网元，对应于融合场景下确定提供资源类服务的媒体面网元；另外第一媒体端点不为媒体面网元上的媒体端点可以理解为可以提供资源类服务的媒体面网元和接入类服务的媒体面网元不为同一个媒体面网元，对应于非融合场景下确定提供资源类服务的媒体面网元。也就是说上述的技术方案中应用服务器无需根据提供接入类服务的媒体面网元和提供资源类服务的媒体面网元是否为同一个媒体面网元确定不同的处理方式，由分配第二媒体端点的媒体面网元确定即可，从而简化了应用服务器的处理难度，提升了应用服务器的处理效率。
应理解，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
还应理解，在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
还应理解，在上述一些实施例中，主要以现有的网络架构中的设备为例进行了示例性说明(如媒 体面网元，应用服务器等)，应理解，对于设备的具体形式本申请实施例不作限定。例如，在未来可以实现同样功能的设备都适用于本申请实施例。
可以理解的是，上述各个方法实施例中，由媒体面网元实现的方法和操作，也可以由可用于媒体面网元的部件实现；由应用服务器实现的方法和操作，也可以由可用于应用服务器的部件实现。
以上，结合图5至图7详细说明了本申请实施例提供的通信方法。上述通信方法主要从媒体面网元和应用服务器之间交互的角度进行了介绍。可以理解的是，媒体面网元和应用服务器，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。
本领域技术人员应该可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
以下，结合图8和图9详细说明本申请实施例提供的通信的装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，部分内容不再赘述。
本申请实施例可以根据上述方法示例对发射端设备或者接收端设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明。
图8为本申请实施例提供的通信装置800的示意性框图。该通信装置800可以包括处理模块810和收发模块820。可选地，还可以包括存储单元，该存储单元可以用于存储指令(代码或者程序)和/或数据。处理模块810和收发模块820可以与该存储单元耦合，例如，处理模块810可以读取存储单元中的指令(代码或者程序)和/或数据，以实现相应的方法。上述各个模块可以独立设置，也可以部分或者全部集成。
一些可能的实施方式中，通信装置800能够对应实现上述方法实施例中媒体面网元的行为和功能，通信装置800可以为媒体面网元，也可以为应用于媒体面网元中的部件(例如芯片或者电路)，也可以是媒体面网元中的芯片或芯片组或芯片中用于执行相关方法功能的一部分。
例如，通信装置800实现图5至图7中至少一个图的实施例中媒体面网元(如，UMF_T/UMF_T_Res)执行的方法。收发模块820用于执行上述UMF_T/UMF_T_Res接收和发送消息有关的操作，例如：用于接收来自应用服务器的请求信息，所述请求信息用于请求所述媒体面网元分配用于提供资源类服务的媒体端点，所述请求信息包括用于提供接入类服务的第一媒体端点的信息；还用于根据向所述应用服务器发送第二媒体端点的信息，所述第二媒体端点是所述媒体面网元根据所述第一媒体端点是否属于所述媒体面网元确定的。处理模块810用于执行上述UMF_T/UMF_T_Res的除接收和发送消息之外的操作。
作为一种可选的实现方式，所述第一媒体端点属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址相同。
作为一种可选的实现方式，所述处理模块810根据所述第一媒体端点属于所述媒体面网元确定不分配新的媒体端点，以所述第一媒体端点的镜像媒体端点作为所述第二媒体端点。
作为一种可选的实现方式，所述第一媒体端点不属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址不同。
作为一种可选的实现方式，所述处理模块810根据所述第一媒体端点不属于所述媒体面网元确定分配新的媒体端点作为所述第二媒体端点。
作为一种可选的实现方式，所述第一媒体端点的信息包括所述第一媒体端点所属的媒体面网元的标识和所述第一媒体端点的标识。
作为一种可选的实现方式，所述收发模块820还用于接收来自应用服务器的指示信息，所述指示信息用于指示执行所述资源类服务，所述指示信息中包括所述第二媒体端点的信息；所述处理模块810，还用于根据所述指示信息执行所述资源类服务。
在另一些可能的实施方式中，通信装置800能够对应实现上述方法实施例中应用服务器(如，AS_T)的行为和功能，通信装置800可以为应用服务器，也可以为应用于应用服务器中的部件(例如芯片或者电路)，也可以是网络功能存储网元中的芯片或芯片组或芯片中用于执行相关方法功能的一部分。
例如，通信装置800实现图5至图7中的实施例中AS_T执行的方法。收发模块820用于执行上述AS_T接收和发送消息有关的操作，例如：用于接收来自服务发现功能网元的媒体面网元的信息；所述收发模块还用于向所述媒体面网元发送请求信息，所述请求信息中包括所述第一媒体端点的信息，所述第一媒体端点的信息包括用于提供接入类服务的媒体端点的信息，所述请求信息用于请求所述媒体面网元分配用于提供资源类服务的媒体端点；所述收发模块还用于接收来自所述媒体面网元的所述第二媒体端点的信息。处理模块810用于执行上述AS_T的除接收和发送消息之外的操作。
作为一种可选的实现方式，所述请求信息中还包括远端地址，所述远端地址用于指示与所述第二媒体端点建立连接的媒体端点的地址。
作为一种可选的实现方式，所述第一媒体端点属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址相同。
作为一种可选的实现方式，所述第一媒体端点不属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址不同。
作为一种可选的实现方式，所述第一媒体端点的信息包括所述第一媒体端点所属的媒体面网元的标识和所述第一媒体端点的标识。
作为一种可选的实现方式，所述收发模块820还用于向所述媒体面网元发送指示信息，所述指示信息用于指示执行所述资源类服务。
应理解，本申请实施例中的处理模块810可以由处理器或处理器相关电路组件实现，收发模块820可以由收发器或收发器相关电路组件或者通信接口实现。
图9为本申请实施例提供的通信装置900的示意性框图。其中，通信装置900可以是终端设备，能够实现本申请实施例提供的方法中媒体面网元的功能。通信装置900也可以是能够支持媒体面网元实现本申请实施例提供的方法中对应的功能的装置，其中，该通信装置900可以为芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。具体的功能可以参见上述方法实施例中的说明。通信装置900也可以是应用服务器，能够实现本申请实施例提供的方法中应用服务器的功能。通信装置900也可以是能够支持应用服务器实现本申请实施例提供的方法中对应的功能的装置，其中，该通信装置900可以为芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。具体的功能可以参见上述方法实施例中的说明。
通信装置900包括一个或多个处理器920，可以用于实现或用于支持通信装置900实现本申请实施例提供的方法中媒体面网元的功能。具体参见方法示例中的详细描述，此处不做赘述。一个或多个处理器920也可以用于实现或用于支持通信装置900实现本申请实施例提供的方法中应用服务器的功能。具体参见方法示例中的详细描述，此处不做赘述。处理器920也可以称为处理单元或处理模块，可以实现一定的控制功能。处理器920可以是通用处理器或者专用处理器等。例如，包括：中央处理器，应用处理器，调制解调处理器，图形处理器，图像信号处理器，数字信号处理器，视频编解码处理器，控制器，存储器，和/或神经网络处理器等。所述中央处理器可以用于对通信装置900进行控制，执行软件程序和/或处理数据。不同的处理器可以是独立的器件，也可以是集成在一个或多个处理器中，例如，集成在一个或多个专用集成电路上。
可选地，通信装置900中包括一个或多个存储器930，用于存储程序指令和/或数据。存储器930和处理器920耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器920可能和存储器930协同操作。处理器920可能执行存储器930中存储的程序指令和/或数据，以使得通信装置900实现相应的方法。所述至少一个存储器中的至少一个可以包括于处理器920中。
通信装置900还可以包括通信接口910，使用任何收发器一类的装置，用于与其他设备或通信网络，如无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)，有线接入网等通信。该通信接口910用于通过传输介质和其它设备进行通信，从而用于通信装置900中的装置可以和其它设备进行通信。示例性地，当该通信装置900为媒体面网元时，该其它设备为应用服 务器；或者，当该通信装置为应用服务器时，该其它设备为媒体面网元。处理器920可以利用通信接口910收发数据。通信接口910具体可以是收发器。
本申请实施例中不限定上述通信接口910、处理器920以及存储器930之间的具体连接介质。本申请实施例在图9中以存储器930、处理器920以及通信接口910之间通过总线940连接，总线在图9中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在本申请实施例中，处理器920可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
存储器930可以是ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信总线940与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器930用于存储执行本申请方案的计算机执行指令，并由处理器920来控制执行。处理器920用于执行存储器930中存储的计算机执行指令，从而实现本申请上述实施例提供的通信方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
可以理解的是，上述实施例中的通信装置可以是媒体面网元(或应用服务器)也可以是电路，也可以是应用于媒体面网元(或应用服务器)中的芯片或者其他具有上述媒体面网元(或应用服务器)的组合器件、部件等。处理模块可以是处理器，例如：中央处理模块(central processing unit，CPU)。处理模块可以是芯片系统的处理器。收发模块或通信接口可以是芯片系统的输入输出接口或接口电路。例如，接口电路可以为代码/数据读写接口电路。所述接口电路，可以用于接收代码指令(代码指令存储在存储器中，可以直接从存储器读取，或也可以经过其他器件从存储器读取)并传输至处理器；处理器可以用于运行所述代码指令以执行上述方法实施例中的方法。又例如，接口电路也可以为通信处理器与收发机之间的信号传输接口电路。
当该通信装置为芯片类的装置或者电路时，该装置可以包括收发单元和处理单元。其中，所述收发单元可以是输入输出电路和/或通信接口；处理单元为集成的处理器或者微处理器或者集成电路。
本申请实施例还提供一种通信系统，具体的，通信系统包括至少一个媒体面网元和至少一个应用服务器。示例性的，通信系统包括用于实现上述图5至图7任意一个或多个图的相关功能的媒体面网元和应用服务器，以及控制面网元。具体请参考上述方法实施例中的相关描述，这里不再赘述。
本申请实施例中还提供一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行图5至图7任意一个或多个图中媒体面网元执行的方法。或者，当其在计算机上运行时，使得计算机执行图5至图7任意图中应用服务器执行的方法。
本申请实施例中还提供一种计算机程序产品，包括指令，当其在计算机上运行时，使得计算机执行图5至图7任意一个或多个图中媒体面网元执行的方法。或者，当其在计算机上运行时，使得计算机执行图5至图7任意一个或多个图中应用服务器执行的方法。
本申请实施例提供了一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现前述方法中媒体面网元的功能；或者用于实现前述方法中应用服务器的功能。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执 行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (31)

  1. 一种通信方法，其特征在于，包括：
    媒体面网元接收来自应用服务器的请求信息，所述请求信息用于请求所述媒体面网元分配用于提供资源类服务的媒体端点，所述请求信息包括用于提供接入类服务的第一媒体端点的信息；
    所述媒体面网元向所述应用服务器发送用于提供资源类服务的第二媒体端点的信息，所述第二媒体端点是所述媒体面网元根据所述第一媒体端点是否属于所述媒体面网元确定的。
  2. 根据权利要求1所述的方法，其特征在于，所述第一媒体端点属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址相同。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    所述媒体面网元根据所述第一媒体端点属于所述媒体面网元确定不分配新的媒体端点，以所述第一媒体端点的镜像媒体端点作为所述第二媒体端点。
  4. 根据权利要求1所述的方法，其特征在于，所述第一媒体端点不属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址不同。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    所述媒体面网元根据所述第一媒体端点不属于所述媒体面网元确定分配新的媒体端点作为所述第二媒体端点。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述第一媒体端点的信息包括所述第一媒体端点所属的媒体面网元的标识和所述第一媒体端点的标识。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述方法还包括：
    所述媒体面网元接收来自应用服务器的指示信息，所述指示信息用于指示执行所述资源类服务，所述指示信息中包括所述第二媒体端点的信息；
    所述媒体面网元根据所述指示信息执行所述资源类服务。
  8. 根据权利要求7所述的方法，其特征在于，所述请求信息中还包括远端地址，所述远端地址用于指示与所述第二媒体端点建立连接的媒体端点的地址。
  9. 根据权利要求8所述的方法，其特征在于，所述第二媒体端点的本端地址与所述远端地址不同的情况下，所述媒体面网元通过所述第二媒体端点提供所述资源类服务；
    所述第二媒体端点的本端地址与所述远端地址相同的情况下，所述媒体面网元通过第三媒体端点提供所述资源类服务，所述第三媒体端点是所述媒体面网元根据所述第二媒体端点的信息确定的。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，所述媒体面网元为统一媒体面功能UMF网元。
  11. 一种通信方法，其特征在于，包括：
    应用服务器接收来自服务发现功能网元的媒体面网元的信息；
    所述应用服务器向所述媒体面网元发送请求信息，所述请求信息用于请求所述媒体面网元分配用于提供资源类服务的媒体端点，所述请求信息包括用于提供接入类服务的第一媒体端点的信息；
    所述应用服务器接收来自所述媒体面网元的第二媒体端点的信息，所述第二媒体端点是所述媒体面网元根据所述第一媒体端点是否属于所述媒体面网元确定的。
  12. 根据权利要求11所述的方法，其特征在于，所述请求信息中还包括远端地址，所述远端地址用于指示与所述第二媒体端点建立连接的媒体端点的地址。
  13. 根据权利要求11或12所述的方法，其特征在于，所述第一媒体端点属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址相同。
  14. 根据权利要求11或12所述的方法，其特征在于，所述第一媒体端点不属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址不同。
  15. 根据权利要求11至14中任一项所述的方法，其特征在于，所述第一媒体端点的信息包括所述第一媒体端点所属的媒体面网元的标识和所述第一媒体端点的标识。
  16. 根据权利要求11至15中任一项所述的方法，其特征在于，所述方法还包括：
    所述应用服务器向所述媒体面网元发送指示信息，所述指示信息用于指示执行所述资源类服务，所述指示信息中包括所述第二媒体端点的信息。
  17. 一种通信方法，其特征在于，包括：
    应用服务器接收来自服务发现功能网元的媒体面网元的信息；
    所述应用服务器向所述媒体面网元发送请求信息，所述请求信息用于请求所述媒体面网元分配用于提供资源类服务的媒体端点，所述请求信息包括用于提供接入类服务的第一媒体端点的信息；
    所述媒体面网元向所述应用服务器发送用于提供资源类服务的第二媒体端点的信息，所述第二媒体端点是所述媒体面网元根据所述第一媒体端点是否属于所述媒体面网元确定的。
  18. 根据权利要求17所述的方法，其特征在于，所述第一媒体端点属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址相同。
  19. 根据权利要求18所述的方法，其特征在于，所述方法还包括：
    所述媒体面网元根据所述第一媒体端点属于所述媒体面网元确定不分配新的媒体端点，以所述第一媒体端点的镜像媒体端点作为所述第二媒体端点。
  20. 根据权利要求17所述的方法，其特征在于，所述第一媒体端点不属于所述媒体面网元，所述第二媒体端点的本端地址和所述第一媒体端点的本端地址不同。
  21. 根据权利要求20所述的方法，其特征在于，所述方法还包括：
    所述媒体面网元根据所述第一媒体端点不属于所述媒体面网元确定分配新的媒体端点作为所述第二媒体端点。
  22. 根据权利要求17至21中任一项所述的方法，其特征在于，所述第一媒体端点的信息包括所述第一媒体端点所属的媒体面网元的标识和所述第一媒体端点的标识。
  23. 根据权利要求17至22中任一项所述的方法，其特征在于，所述方法还包括：
    所述应用服务器向所述媒体面网元发送指示信息，所述指示信息用于指示执行所述资源类服务，所述指示信息中包括所述第二媒体端点的信息。
  24. 根据权利要求23所述的方法，其特征在于，所述请求信息中还包括远端地址，所述远端地址用于指示与所述第二媒体端点建立连接的媒体端点的地址。
  25. 根据权利要求24所述的方法，其特征在于，所述第二媒体端点的本端地址与所述远端地址不同的情况下，所述媒体面网元通过所述第二媒体端点提供所述资源类服务；
    所述第二媒体端点的本端地址与所述远端地址相同的情况下，所述媒体面网元通过第三媒体端点提供所述资源类服务，所述第三媒体端点是所述媒体面网元根据所述第二媒体端点的信息确定的。
  26. 一种通信装置，其特征在于，包括执行如权利要求1至9中任一项所述方法的单元或模块。
  27. 一种通信装置，其特征在于，包括执行如权利要求10至15中任一项所述方法的单元或模块。
  28. 一种通信装置，其特征在于，包括至少一个处理器，
    所述至少一个处理器用于执行存储器中存储的计算机程序，以使得所述装置执行如权利要求1至9中任一项所述的方法；或者，
    所述至少一个处理器用于执行存储器中存储的计算机程序，以使得所述装置执行如权利要求10至15中任一项所述的方法。
  29. 一种通信系统，其特征在于，包括应用服务器和媒体面网元，
    其中，所述媒体面网元用于执行如权利要求1至9中任一项所述的方法，所述应用服务器用于执行如权利要求10至15中任一项所述的方法。
  30. 一种计算机可读存储介质，其特征在于，包括计算机程序，
    当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至9中任一项所述的方法；或者，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求10至15中任一项所述的方法。
  31. 一种计算机程序产品，其特征在于，所述计算机程序产品中包括计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机实现上述权利要求1至9中任一项所述的方法；或者，当所述计算机程序代码在计算机上运行时，使得计算机实现上述权利要求10至15中任一项所述的方法。
PCT/CN2023/103765 2022-08-11 2023-06-29 通信方法、装置和系统 WO2024032213A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210961956.2 2022-08-11
CN202210961956.2A CN117640607A (zh) 2022-08-11 2022-08-11 通信方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2024032213A1 true WO2024032213A1 (zh) 2024-02-15

Family

ID=89850709

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/103765 WO2024032213A1 (zh) 2022-08-11 2023-06-29 通信方法、装置和系统

Country Status (2)

Country Link
CN (1) CN117640607A (zh)
WO (1) WO2024032213A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103516664A (zh) * 2012-06-18 2014-01-15 中国移动通信集团公司 一种基于ims的p2p业务节点选择方法及装置
CN110336746A (zh) * 2019-04-23 2019-10-15 东南大学成贤学院 用户面节点选择方法、系统及存储介质
CN110832948A (zh) * 2017-06-20 2020-02-21 瑞典爱立信有限公司 针对网络中的组通信的资源分配
WO2021151519A1 (en) * 2020-01-30 2021-08-05 Truphone Limited Communications recording
CN113329447A (zh) * 2021-06-07 2021-08-31 广州爱浦路网络技术有限公司 作用于ip多媒体子系统ims切片网络的通信方法及系统
WO2022147697A1 (zh) * 2021-01-06 2022-07-14 华为技术有限公司 一种呼叫处理系统和呼叫处理方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103516664A (zh) * 2012-06-18 2014-01-15 中国移动通信集团公司 一种基于ims的p2p业务节点选择方法及装置
CN110832948A (zh) * 2017-06-20 2020-02-21 瑞典爱立信有限公司 针对网络中的组通信的资源分配
CN110336746A (zh) * 2019-04-23 2019-10-15 东南大学成贤学院 用户面节点选择方法、系统及存储介质
WO2021151519A1 (en) * 2020-01-30 2021-08-05 Truphone Limited Communications recording
WO2022147697A1 (zh) * 2021-01-06 2022-07-14 华为技术有限公司 一种呼叫处理系统和呼叫处理方法
CN113329447A (zh) * 2021-06-07 2021-08-31 广州爱浦路网络技术有限公司 作用于ip多媒体子系统ims切片网络的通信方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on optimisations of UE radio capability signalling (Release 16)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.743, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V1.2.0, 12 March 2019 (2019-03-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 57, XP051722759 *

Also Published As

Publication number Publication date
CN117640607A (zh) 2024-03-01

Similar Documents

Publication Publication Date Title
WO2019184987A1 (zh) 接入ims的方法和通信装置
KR100886548B1 (ko) 인터넷 프로토콜 멀티미디어 서브시스템 네트워크에서단말의 성능 정보를 전달하기 위한 방법 및 시스템
JP4217606B2 (ja) 回路交換及びパケット交換通信
EP1771983B1 (en) A method and device for providing correlation means in hybrid telecommunication networks
EP1958467B1 (en) Method of enabling a combinational service and communication network implementing the service
CN113709190B (zh) 业务设置方法和装置、存储介质及电子设备
RU2452118C2 (ru) Способ передачи информации в системе беспроводной связи и терминал, поддерживающий этот способ
WO2017147959A1 (zh) 一种业务承载方法、通信终端、控制网元s-cscf以及系统
US10681100B2 (en) Method, user equipment and application server for adding media stream of multimedia session
EP2458816B1 (en) Method and apparatuses for changing status of packet switched domain
US11909775B2 (en) Methods and apparatuses for enhancement to IP multimedia subsystem
KR100727069B1 (ko) Ｓｉｐ 기반의 무선 패킷 교환망 시스템에서의 타망 연동방법 및 그 시스템
CN100544371C (zh) 在综合业务中实现能力协商的方法
CN105122761B (zh) 基于分组的呼叫的附加媒体会话的本地控制
WO2006008297A2 (en) Push to watch network element and software architecture
WO2024032213A1 (zh) 通信方法、装置和系统
WO2006089491A1 (fr) Méthode pour réaliser la fonction de passerelle de média, équipement de contrôle d’accès sans fil et système d’accès
KR100657617B1 (ko) Ｓｉｐ 기반의 무선 패킷 교환망 시스템
CN100496049C (zh) Sip多媒体系统中用户面互通方法
WO2023207525A1 (zh) 一种通信方法及装置
CN102215210A (zh) 在ip多媒体子系统中建立会话的方法和装置
KR100727067B1 (ko) Ｓｉｐ 기반의 무선 패킷 교환망 시스템에서의 타망 연동방법 및 그 시스템
WO2022088183A1 (zh) 一种通信方法及装置
EP4351103A1 (en) Call processing method, apparatus, and system
EP4351102A1 (en) Call processing method, apparatus and system

Legal Events

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

Ref document number: 23851440

Country of ref document: EP

Kind code of ref document: A1