Communication method and device

Abstract

The invention provides a communication method and device, and relates to the technical field of communication. For a scene in which a session control process is separated from a media negotiation process, a media function entity can send first information to a control function entity after completing media negotiation of a first session. Wherein the first session is a session between the first terminal and the second terminal, the first session is used for transmitting a media stream between the two terminals, and the first session passes through the media function entity. The first information indicates that media negotiation of the first session is completed at the media function entity, or indicates that resources are reserved for the first session. After receiving the first information, the control function entity can send a request to the policy control network according to the first information to request to reserve resources for the first session. According to the method, under the scene that the session control process is separated from the media negotiation process, a resource reservation mechanism is applied to reserve resources for the calling terminal and the called terminal, and the call success rate is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to a communication method and device. BACKGROUND

[0002] In a communication system, one terminal can initiate a call procedure to one or more terminals except itself to perform session control (such as session creation or session update) and media negotiation (such as negotiation of media information used for a call) so as to realize audio / video call among multiple users. In the call procedure, in order to improve the call success rate of the calling terminal, a resource reservation (precondition) mechanism is introduced. Based on the resource reservation mechanism, before the called terminal rings, the network (such as an access network and a core network) where the calling terminal is located and the network (such as an access network and a core network) where the called terminal is located will reserve sufficient resources for this call to establish a bearer between the network and the corresponding terminal. Subsequently, after the user of the called terminal answers the call, the audio / video call between the calling terminal and the called terminal can be realized through the bearer.

[0003] In the above process, the session control process and the media negotiation process are performed simultaneously, which can cause the media negotiation process to be complex and the media negotiation efficiency to be low. Therefore, the idea of separating the session control process and the media negotiation process is proposed. Then, in the scenario where the session control process and the media negotiation process are separated, how to apply the resource reservation mechanism is a problem to be solved urgently. SUMMARY

[0004] The present application provides a communication method and device, which can apply the resource reservation mechanism to reserve resources for the calling terminal and the called terminal in the scenario where the session control process and the media negotiation process are separated, and improve the call success rate.

[0005] To achieve the above object, the present application adopts the following technical solution:

[0006] In a first aspect, a communication method is provided, which can be executed by a control function entity. The control function entity herein can refer to the control function entity itself, or a processor, circuit, module, logic node, chip or chip system in the control function entity that implements the method.

[0007] The method comprises: receiving first information from a media function entity, and sending a first request to a policy control entity according to the first information. The first information indicates that media negotiation of a first session is completed at the media function entity, or the first information indicates that resources are reserved for the first session. The first session is a session between a first terminal and a second terminal, and is used to transmit a media stream between the first terminal and the second terminal. The first session passes through the media function entity. The first request is used to request that resources are reserved for the first session.

[0008] Based on the method provided in the first aspect above, the media function entity can instruct the control function entity to complete the media negotiation for the first session at the media function entity, or the media function entity can instruct to reserve resources for the first session. The control function entity can request the policy control entity to reserve resources for the first session according to the instructions of the media function entity, so as to improve the call success rate of the first session.

[0009] In one possible implementation, receiving the first information from the media function entity includes receiving the first information from the media function entity when the media negotiation of the first session is completed at the media function entity.

[0010] Based on the above possible implementation methods, the control function entity can request the policy control entity to reserve resources for the first session after the media function entity completes the media negotiation for the first session.

[0011] In one possible implementation, the method further includes: sending a second message to a media function entity; the first message indicating that media negotiation for the first session is completed at the media function entity, and the second message being used to subscribe to the media negotiation status of the first session; or, the first message indicating that resources are reserved for the first session, and the second message being used to subscribe to the resource reservation status of the first session.

[0012] Based on the above possible implementations, the control function entity can subscribe to the media negotiation state of the first session from the media function entity, so that the media function entity can send first information to the control function entity according to the perceived media negotiation state of the first session. Alternatively, the control function entity can subscribe to the resource reservation state of the first session from the media function entity, so that the media function entity can send first information to the control function entity according to the perceived resource reservation state of the first session.

[0013] In one possible implementation, the method further includes: receiving first media information from a media function entity, the first media information being media information negotiated for a first session media function entity, the first media information being used by the media function entity to send or receive media streams based on the first media information; and a first request carrying second media information, the second media information being determined based on the first media information.

[0014] Based on the above possible implementations, the control function entity can obtain first media information from the media function entity and send second media information determined based on the first media information to the policy control entity in the first request, so that the policy control entity reserves resources for the first session based on the second media information. For example, the second media information includes all or part of the information in the first media information.

[0015] In one possible implementation, the method further includes: receiving a response to a first request from a policy control entity, the response to the first request indicating whether resource reservation for the first session has been completed; the first request being an authentication / authorization request, and the response to the first request being an authentication / authorization response; or, the first request being a policy authorization request, and the response to the first request being a policy authorization response.

[0016] Based on the above possible implementations, the control function entity can request the policy control entity to reserve resources for the first session through an authentication / authorization request or a policy authorization request. Furthermore, the control function entity can also receive a corresponding response to confirm whether the resource reservation for the first session has been completed.

[0017] In one possible implementation, the first terminal or the second terminal is located in the first communication network; the control function entity is deployed on the proxy call session control function network element in the first communication network, and the media function entity is deployed on the Internet Protocol Multimedia Subsystem Access Media Gateway in the first communication network; or, the control function entity is deployed on the unified session control function network element in the first communication network, and the media function entity is deployed on the media function network element in the first communication network.

[0018] Based on the above possible implementation methods, control function entities and media function entities can be deployed in the network in various ways.

[0019] In one possible implementation, the method is applied to a call process between a first terminal and a second terminal, where the first communication network is either the calling network or the called network.

[0020] Based on the above possible implementation methods, the control function entity and the media function entity can be deployed in the calling network or the called network.

[0021] Secondly, a communication method is provided, which can be executed by a media function entity. Here, "media function entity" can refer to the media function entity itself, or to a processor, circuit, module, logic node, chip, or chip system within the media function entity that implements the method.

[0022] The method includes: receiving or sending first media information, and sending first information to a control function entity based on the first media information. The first media information is media information negotiated by the media function entity for a first session; the first session is a session between a first terminal and a second terminal, used to transmit media streams between the first terminal and the second terminal, and the first session passes through the media function entity. The first information is used to trigger a request for resource reservation for the first session. The first information indicates that media negotiation for the first session is completed at the media function entity, or the first information indicates that resources are reserved for the first session.

[0023] Based on the method provided in the second aspect above, since the first media information is media information negotiated by the media function entity for the first session, the media function entity receiving or sending the first media information indicates that the media negotiation for the first session is complete. In other words, after the media negotiation for the first session is completed, the media function entity can instruct the control function entity that the media negotiation for the first session was completed at the media function entity, or the media function entity can instruct the control function entity to reserve resources for the first session based on the first media information, thereby triggering the control function entity to request resource reservation for the first session and improve the call success rate of the first session.

[0024] In one possible implementation, the method further includes: receiving second information from a control function entity; the first information indicates that media negotiation for the first session is completed at the media function entity, and the second information is used to subscribe to the media negotiation state of the first session; or, the first information indicates that resources are reserved for the first session, and the second information is used to subscribe to the resource reservation state of the first session.

[0025] Based on the above possible implementation methods, the media function entity can send corresponding information to the control function entity according to the content subscribed to by the control function entity. For example, when the second information is used to subscribe to the media negotiation state of the first session, the media function entity, upon sensing that the media negotiation state of the first session is completed, instructs the control function entity that the media negotiation of the first session is completed at the media function entity; when the second information is used to subscribe to the resource reservation state of the first session, the media function entity, upon sensing that resources need to be reserved for the first session, instructs the control function entity to reserve resources for the first session.

[0026] In one possible implementation, sending first information to the control function entity based on first media information includes: the first media information indicating that the media information negotiation of the first session was successful, the first information indicating that the media negotiation of the first session was completed at the media function entity; or, the first media information indicating that the media information negotiation of the first session was successful, and the first terminal and the second terminal support the resource reservation function, the first information indicating that resources are reserved for the first session.

[0027] Based on the above possible implementations, when the first media information indicates that the media information negotiation for the first session is successful, the media function entity can instruct the control function entity that the media negotiation for the first session is completed at the media function entity, causing the control function entity to trigger the reservation of resources for the first session. Alternatively, when the first media information indicates that the media information negotiation for the first session is successful, and both the first terminal and the second terminal support the resource reservation function, the media function entity can instruct the control function entity to reserve resources for the first session, causing the control function entity to trigger the request to reserve resources for the first session.

[0028] In one possible implementation, the first terminal or the second terminal is located in the first communication network; the control function entity is deployed on the proxy call session control function network element in the first communication network, and the media function entity is deployed on the Internet Protocol Multimedia Subsystem Access Media Gateway in the first communication network; or, the control function entity is deployed on the unified session control function network element in the first communication network, and the media function entity is deployed on the media function network element in the first communication network.

[0029] Based on the above possible implementation methods, control function entities and media function entities can be deployed in the network in various ways.

[0030] In one possible implementation, the method is applied to a call process between a first terminal and a second terminal; the first communication network is either the calling network or the called network.

[0031] Based on the above possible implementation methods, the control function entity and the media function entity can be deployed in the calling network or the called network.

[0032] Thirdly, a communication method is provided, which can be executed by a media function entity. Here, "media function entity" can refer to the media function entity itself, or to a processor, circuit, module, logic node, chip, or chip system within the media function entity that implements the method.

[0033] The method includes: receiving or sending first media information, and sending a first request to a policy control entity based on the first media information. The first media information is media information negotiated by a media function entity for a first session; the first session is a session between a first terminal and a second terminal, used to transmit media streams between the first terminal and the second terminal, and the first session passes through the media function entity. The first request is used to request the reservation of resources for the first session.

[0034] Based on the method provided in the third aspect above, since the first media information is media information negotiated by the media function entity for the first session, the media function entity receiving or sending the first media information indicates that the media negotiation for the first session is complete. In other words, after the media negotiation for the first session is completed, the media function entity can trigger the policy control entity to reserve resources for the first session based on the first media information, thereby improving the call success rate of the first session.

[0035] In one possible implementation, sending a first request to a policy control entity based on first media information includes: sending the first request to the policy control entity when the first media information indicates that the media information negotiation for the first session was successful and the first terminal and the second terminal support the resource reservation function.

[0036] Based on the above possible implementation methods, the media function entity can send a first request to the policy control entity to trigger the policy control entity to reserve resources for the first session when the first media information indicates that the media information negotiation for the first session is successful and the first terminal and the second terminal support the resource reservation function.

[0037] In one possible implementation, the method further includes: receiving a response to a first request from a policy control entity, the response to the first request indicating whether resource reservation for the first session has been completed; the first request being an authentication / authorization request, and the response to the first request being an authentication / authorization response; or, the first request being a policy authorization request, and the response to the first request being a policy authorization response.

[0038] Based on the above possible implementation methods, the media function entity can request the policy control entity to reserve resources for the first session through an authentication / authorization request or a policy authorization request. Furthermore, the media function entity can also receive a corresponding response to confirm whether the resource reservation for the first session has been completed.

[0039] In one possible implementation, the first terminal or the second terminal is located in the first communication network; the media function entity is deployed on the Internet Protocol Multimedia Subsystem Access Media Gateway or on the media function network element in the first communication network.

[0040] Based on the above possible implementation methods, various methods can be used to deploy media function entities in the network.

[0041] In one possible implementation, the method is applied to a call process between a first terminal and a second terminal, wherein the first communication network is either the calling network or the called network.

[0042] Based on the above possible implementation methods, the media function entity can be deployed in the calling network or the called network.

[0043] Fourthly, a communication device is provided for implementing the method provided in the first aspect. The communication device can be the control function entity in the first aspect. The communication device includes modules, units, or means that implement the method described above. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0044] In one possible implementation, the communication device may include a processing module and an interface module. The processing module can be used to implement the processing functions described in the first aspect and any possible implementation thereof. The processing module may be, for example, a processor. The interface module, also referred to as an interface unit, is used to implement the sending and / or receiving functions described in the first aspect and any possible implementation thereof. The interface module may consist of an interface circuit, a transceiver, a transceiver unit, or a communication interface.

[0045] In one possible implementation, an interface module is configured to receive first information from a media function entity, the first information indicating that media negotiation for a first session is completed at the media function entity, or the first information indicating that resources are reserved for the first session, the first session being a session between a first terminal and a second terminal, the first session being used to transmit a media stream between the first terminal and the second terminal, the first session passing through the media function entity; and a processing module is configured to control the interface module to send a first request to a policy control entity based on the first information, the first request being used to request the reservation of resources for the first session.

[0046] In one possible implementation, the interface module is specifically configured to receive the first information from the media function entity when the media negotiation of the first session is completed at the media function entity.

[0047] In one possible implementation, the interface module is further configured to send a second message to the media function entity; the first message indicates that media negotiation for the first session is completed at the media function entity, and the second message is used to subscribe to the media negotiation status of the first session; or, the first message indicates that resources are reserved for the first session, and the second message is used to subscribe to the resource reservation status of the first session.

[0048] In one possible implementation, the interface module is further configured to receive first media information from the media function entity, the first media information being media information negotiated by the media function entity for the first session, the first media information being used by the media function entity to send or receive media streams based on the first media information; the first request carries second media information, the second media information being determined based on the first media information.

[0049] In one possible implementation, the interface module is further configured to receive a response to the first request from the policy control entity, the response to the first request indicating whether resource reservation for the first session has been completed; the first request is an authentication / authorization request, and the response to the first request is an authentication / authorization response; or, the first request is a policy authorization request, and the response to the first request is a policy authorization response.

[0050] In one possible implementation, the first terminal or the second terminal is located in a first communication network; the control function entity is deployed on the proxy call session control function network element in the first communication network, and the media function entity is deployed on the Internet Protocol Multimedia Subsystem Access Media Gateway in the first communication network; or, the control function entity is deployed on the unified session control function network element in the first communication network, and the media function entity is deployed on the media function network element in the first communication network.

[0051] In one possible implementation, the first communication network is either the calling network or the called network.

[0052] Fifthly, a communication device is provided for implementing the method provided in the second aspect above. The communication device can be a media function entity as described in the second aspect. The communication device includes modules, units, or means that implement the method described above. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0053] In one possible implementation, the communication device may include a processing module and an interface module. The processing module can be used to implement the processing functions in the second aspect described above and any possible implementation thereof. The processing module may be, for example, a processor. The interface module, also referred to as an interface unit, is used to implement the sending and / or receiving functions in the second aspect described above and any possible implementation thereof. The interface module may consist of an interface circuit, a transceiver, a transceiver unit, or a communication interface.

[0054] In one possible implementation, an interface module is configured to receive or send first media information, which is media information negotiated by the media function entity for a first session. The first session is a session between a first terminal and a second terminal, used to transmit a media stream between the first terminal and the second terminal, and the first session passes through the media function entity. A processing module is configured to control the interface module to send first information to the control function entity based on the first media information. The first information is used to trigger a request for resource reservation for the first session. The first information indicates that the media negotiation of the first session is completed at the media function entity, or the first information indicates that resources are reserved for the first session.

[0055] In one possible implementation, the interface module is further configured to receive second information from the control function entity; the first information indicates that media negotiation for the first session is completed at the media function entity, and the second information is used to subscribe to the media negotiation status of the first session; or, the first information indicates that resources are reserved for the first session, and the second information is used to subscribe to the resource reservation status of the first session.

[0056] In one possible implementation, the first media information indicates that the media information negotiation of the first session was successful, and the first information indicates that the media negotiation of the first session was completed at the media function entity; or, the first media information indicates that the media information negotiation of the first session was successful, and the first terminal and the second terminal support the resource reservation function, and the first information indicates that resources are reserved for the first session.

[0057] In one possible implementation, the first terminal or the second terminal is located in a first communication network; the control function entity is deployed on the proxy call session control function network element in the first communication network, and the media function entity is deployed on the Internet Protocol Multimedia Subsystem Access Media Gateway in the first communication network; or, the control function entity is deployed on the unified session control function network element in the first communication network, and the media function entity is deployed on the media function network element in the first communication network.

[0058] In one possible implementation, the first communication network is either the calling network or the called network.

[0059] Sixthly, a communication device is provided for implementing the method provided in the third aspect. The communication device can be a media function entity as described in the third aspect. The communication device includes modules, units, or means that implement the method described above. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0060] In one possible implementation, the communication device may include a processing module and an interface module. The processing module can be used to implement the processing functions in the second aspect and any possible implementation thereof. The processing module may be, for example, a processor. The interface module, also called an interface unit, is used to implement the sending and / or receiving functions in the third aspect and any possible implementation thereof. The interface module may consist of an interface circuit, a transceiver, a transceiver unit, or a communication interface.

[0061] In one possible implementation, an interface module is configured to receive or send first media information, which is media information negotiated by the media function entity for a first session. The first session is a session between a first terminal and a second terminal, which is used to transmit a media stream between the first terminal and the second terminal. The first session passes through the media function entity. A processing module is configured to control the interface module to send a first request to a policy control entity based on the first media information. The first request is used to request that resources be reserved for the first session.

[0062] In one possible implementation, the processing module, specifically configured to control the interface module to send the first request to the policy control entity when the first media information indicates that the media information negotiation for the first session is successful and the first terminal and the second terminal support the resource reservation function.

[0063] In one possible implementation, the interface module is further configured to receive a response to the first request from the policy control entity, the response to the first request indicating whether resource reservation for the first session has been completed; the first request is an authentication / authorization request, and the response to the first request is an authentication / authorization response; or, the first request is a policy authorization request, and the response to the first request is a policy authorization response.

[0064] In one possible implementation, the first terminal or the second terminal is located in a first communication network; the media function entity is deployed on an Internet Protocol Multimedia Subsystem access media gateway or a media function network element in the first communication network.

[0065] In one possible implementation, the first communication network is either the calling network or the called network.

[0066] A seventh aspect provides a communication device, comprising: a processor; configured to cause the communication device to perform the method described in any of the preceding aspects by executing a computer program (or computer-executable instructions) stored in a memory, and / or by means of logic circuitry. The communication device may be a control function entity as described in the first aspect; or, the communication device may be a media function entity as described in the second aspect; or, the communication device may be a media function entity as described in the third aspect. Optionally, the number of processors may be one or more.

[0067] In one possible implementation, the communication device also includes a memory.

[0068] In one possible implementation, the processor and memory are integrated together; or, the memory is independent of the processor.

[0069] In one possible implementation, the communication device further includes a communication interface for communicating with other devices, such as transmitting or receiving data and / or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0070] In one possible implementation, the communication device is a chip or a chip system. Optionally, when the communication device is a chip system, it can be composed of chips or may include chips and other discrete components.

[0071] Eighthly, a communication device is provided, comprising: a processor and an interface circuit; the interface circuit being configured to receive a computer program or instructions and transmit them to the processor; the processor being configured to execute the computer program or instructions to cause the communication device to perform the method described in any of the preceding aspects. The communication device may be a control function entity as described in the first aspect; or, the communication device may be a media function entity as described in the second aspect; or, the communication device may be a media function entity as described in the third aspect. Optionally, the number of processors may be one or more.

[0072] In one possible implementation, the communication device is a chip or a chip system. Optionally, when the communication device is a chip system, it can be composed of chips or may include chips and other discrete components.

[0073] Ninthly, a computer-readable storage medium is provided that stores instructions which, when executed on a computer, cause the computer to perform the methods described in any of the preceding aspects.

[0074] In a tenth aspect, a computer program product containing instructions is provided, which, when run on a computer, enables the computer to perform the methods described in any of the preceding aspects.

[0075] Eleventhly, a communication system is provided, the communication system including a control function entity for performing the method described in the first aspect above, and / or a media function entity for performing the method described in the second aspect above.

[0076] In a twelfth aspect, a communication system is provided, comprising a media function entity for performing the method described in the third aspect above. The communication system further includes a policy control entity for receiving a first request from the media function entity, the first request being for requesting resources to be reserved for a first session.

[0077] The technical effects of any possible implementation of aspects four through twelfth can be found in the technical effects of any one of aspects one through three above, or different possible implementations of any one of aspects, and will not be repeated here.

[0078] Understandably, provided that the solutions do not contradict each other, the solutions in the above aspects can be combined. Attached Figure Description

[0079] Figure 1A A schematic diagram of an Internet Protocol Multimedia Subsystem (IMS) network provided for this application;

[0080] Figure 1B A schematic diagram of the real-time communication network provided in this application;

[0081] Figure 1C A schematic diagram of the hybrid network of IMS network and real-time communication network provided in this application;

[0082] Figure 1D A schematic diagram illustrating the interaction between the SDP offerer and the SDP answerer provided in this application;

[0083] Figure 2 A schematic diagram of the communication system architecture provided in this application;

[0084] Figure 3 A schematic diagram of the hardware structure of the communication device provided in this application;

[0085] Figure 4 A flowchart illustrating the communication method provided in this application;

[0086] Figure 5 Flowchart of the communication method provided in this application Figure 2 ;

[0087] Figure 6 Flowchart of the communication method provided in this application Figure 3 ;

[0088] Figure 7 Flowchart of the communication method provided in this application Figure 4 ;

[0089] Figure 8 Flowchart of the communication method provided in this application Figure 5 ;

[0090] Figure 9 Flowchart of the communication method provided in this application Figure 6 ;

[0091] Figure 10 A schematic diagram of the communication device provided in this application. Detailed Implementation

[0092] Before introducing the technical solution of this application, the relevant technical terms involved in this application are explained. It is understood that these explanations are intended to make this application easier to understand and should not be regarded as a limitation on the scope of protection claimed in this application.

[0093] 1. Terminal

[0094] The terminal in this application is a device with wireless transceiver capabilities, which can be deployed on land, including indoors, outdoors, handheld, or vehicle-mounted; it can also be deployed on water (such as on ships); and it can also be deployed in the air (such as on airplanes, balloons, and satellites). The terminal can also be called a terminal device, which can be user equipment (UE), mobile station (MS), mobile terminal (MT), or a device used to provide voice or data connectivity to users. The UE includes handheld devices with wireless communication capabilities, vehicle-mounted devices (e.g., cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains), wearable devices (e.g., smartwatches, smart bracelets, pedometers), or computing devices. For example, the UE can be a mobile phone, tablet computer, laptop computer, PDA, mobile internet device (MID), satellite terminal, or computer with wireless transceiver capabilities. UE can also be a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless modem, a point-of-sale (POS) machine, customer-premises equipment (CPE), a smart robot, a robotic arm, workshop equipment, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), a wireless terminal in industrial control, a wireless terminal in autonomous driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in intelligent transportation, a wireless terminal in a smart city, a wireless terminal in a smart home, an in-vehicle terminal, a roadside unit (RSU) with terminal functionality, or a flying device (e.g., a smart robot, a hot air balloon, a drone, an airplane), etc. A terminal can also be other devices with terminal functionality; for example, a terminal can be a device that acts as a terminal in device-to-device (D2D) communication.

[0095] By way of example and not limitation, in this application, the terminal can be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into a user's clothing or accessories. For example, wearable devices are not merely hardware devices, but also devices that achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include devices that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as devices that focus on only one type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0096] In this application, the terminal can be a terminal in an Internet of Things (IoT) system. IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technologies, thereby realizing an intelligent network of human-machine interconnection and machine-to-machine interconnection. The terminal in this application can be a terminal in machine-type communication (MTC).

[0097] The terminal in this application can be an on-board module, on-board component, on-board chip, on-board unit (OBU), or telematics box (T-BOX) built into a vehicle as one or more components or units. The vehicle can implement the methods of this application through the built-in on-board module, on-board component, on-board chip, on-board unit, or T-BOX. The terminal can also be a complete vehicle device. Therefore, this application can be applied to vehicle networking, such as vehicle-to-everything (V2X), long-term evolution vehicle (LTE-V), and vehicle-to-vehicle (V2V).

[0098] 2. Call process

[0099] The call process in this application refers to the process by which a terminal, acting as either the caller or the called party, connects with one or more other terminals via a communication network (such as an IMS network, a real-time communication network, or a hybrid network of both) to conduct voice or video calls. The IMS network can be, for example... Figure 1A As shown, real-time communication networks can be as follows: Figure 1B As shown, hybrid networks can be as follows:Figure 1C As shown.

[0100] In this application, the call process can cover the entire process from the start of dialing to the end of the call, or it can cover a portion of the process from the start of dialing to the end of the call, such as the process from the start of dialing to the user picking up the phone; there is no limitation. The call process in this application can be a one-to-one call process or a one-to-many (such as a conference) call process; this application uses a one-to-one call process as an example for illustration, but the relevant solutions can all be used for one-to-many call processes.

[0101] 3. IMS Network

[0102] The IMS network described in this application is an open system based on the Internet Protocol (IP) and providing various multimedia services to users. For example, the IMS network may include one or more of the following network elements: proxy-call session control function (P-CSCF) network element, interrogating-call session control function (I-CSCF) network element, serving-call session control function (S-CSCF) network element, multimedia telephony application server (MMTel AS) network element, interconnection border control functions (IBCF) network element, IMS-access media gateway (IMS-AGW) network element, transition gateway (TrGW) network element, policy and charging control function (PCF) network element, or policy and charging rules function (PCRF) network element. It should be understood that the aforementioned network elements can be deployed independently on various physical devices, or some of the aforementioned network elements can be deployed on the same physical device; this application does not impose any specific limitations.

[0103] In an IMS network, the P-CSCF, I-CSCF, S-CSCF, MMTel AS, and IBCF network elements are control plane or signaling plane network elements used to handle operations related to session control, such as creating or updating sessions. The IMS-AGW and TrGW are media plane network elements used to handle media-related operations, such as media negotiation or transmitting media streams. The session described in this application (such as the first session in the following embodiments) refers to a logical connection between terminals, and this session can pass through one or more media plane network elements. This session can be used to transmit media streams between terminals. The media stream described in this application refers to media data generated by the terminal, such as one or more of audio data, video data, text data, or image data. The functions of each network element are briefly described below.

[0104] The P-CSCF network element is located in the visited network and is the entry node for users to access the IMS network. It is mainly responsible for forwarding signaling between users and the home network.

[0105] The I-CSCF network element is located in the home network and serves as the unified entry point for the home network. It is primarily responsible for allocating or querying S-CSCFs that provide services to users.

[0106] The S-CSCF network element is also located in the home network and is the central node of the IMS network. It is mainly responsible for user registration, authentication, sessions, routing, and service triggering.

[0107] MMTel AS is used to provide multimedia services, such as multimedia conferencing, call waiting, or call hold.

[0108] IBCF network elements are used to provide signaling interoperability with other IP networks.

[0109] IMS-AGW is used to provide media anchor points for accessing the IMS network.

[0110] TrGW is used to provide media interoperability with other IP networks.

[0111] PCF or PCRF network elements (abbreviated as PCF / PCRF network elements) can be used for Quality of Service (QoS) policy control, such as providing QoS control and / or charging control functions for the bearer network (such as the access network or core network). In this application, the PCF / PCRF network element can also be a network element in the core network.

[0112] For example, the architecture of an IMS network can be as follows: Figure 1A As shown. In Figure 1AIn this application, the IMS network 10 includes P-CSCF network element 1005, I / S-CSCF network element 1004, MMTEL AS 1003, MMTEL AS 1007, I / S-CSCF network element 1008, P-CSCF network element 1009, IMS-AGW 1006, IMS-AGW 1010, PCF / PCRF network element 1011, and PCF / PCRF network element 1012. The I / S-CSCF network element includes both I-CSCF and S-CSCF network elements. It should be understood that the I / S-CSCF network element in this application is an abbreviation for both I-CSCF and S-CSCF network elements, but does not imply that the I-CSCF and S-CSCF network elements are the same physical device. In specific applications, the I-CSCF and S-CSCF can be deployed independently on different physical devices or on the same physical device without restriction. This is a unified explanation provided here and will not be repeated later.

[0113] exist Figure 1A In this process, signaling messages (such as invitation requests, 183 messages, or update requests) sent by terminal 1001 can reach terminal 1002 via P-CSCF network element 1005, I / S-CSCF network element 1004, MMTEL AS 1003, I / S-CSCF network element 1004, I / S-CSCF network element 1008, MMTEL AS 1007, I / S-CSCF network element 1008, and P-CSCF network element 1009. Media messages (such as media negotiation requests or media negotiation responses) sent by terminal 1001 (or terminal 1002) can reach terminal 1002 (or terminal 1001) via IMS-AGW 1006 and IMS-AGW 1010. Conversely, signaling messages or media messages sent by terminal 1002 can reach terminal 1001 along the opposite path. The session between terminal 1001 and terminal 1002 can be routed through IMS-AGW 1006 and IMS-AGW 1010, and this session can transmit media streams between terminal 1001 and terminal 1002. Furthermore, P-CSCF network element 1005 or IMS-AGW 1006 can request resources to be reserved for the aforementioned session from PCF / PCRF network element 1011. P-CSCF network element 1009 or IMS-AGW 1010 can request resources to be reserved for the aforementioned session from PCF / PCRF network element 1012.

[0114] Understandably, when terminal 1001 participates in the call process as the calling party and terminal 1002 participates in the call process as the called party, P-CSCF network element 1005, I / S-CSCF network element 1004, MMTEL AS 1003, IMS-AGW 1006, and PCF / PCRF network element 1011 can be regarded as network elements in the calling domain or network elements in the calling network, and P-CSCF network element 1009, I / S-CSCF network element 1008, MMTEL AS 1007, IMS-AGW 1010, and PCF / PCRF network element 1012 can be regarded as network elements in the called domain or network elements in the called network. Similarly, when terminal 1001 participates in the call process as the called party and terminal 1002 participates in the call process as the calling party, P-CSCF network element 1005, I / S-CSCF network element 1004, MMTEL AS1003, IMS-AGW1006, and PCF / PCRF network element 1011 can be regarded as network elements in the called domain or network elements in the called network. P-CSCF network element 1009, I / S-CSCF network element 1008, MMTEL AS1007, IMS-AGW 1010, and PCF / PCRF network element 1012 can be regarded as network elements in the calling domain or network elements in the calling network.

[0115] It should be understood that Figure 1A This is just one example of an IMS network. In specific applications, IMS networks can take other forms. For example, an IMS network can include more than... Figure 1A Show more or fewer network elements, or Figure 1A One or more network elements in the network can be replaced with other network elements that have similar functions, without restriction.

[0116] 4. Real-time communication network

[0117] The real-time communication network described in this application can also provide users with various multimedia services. Compared with the IMS network, the real-time communication network has a simpler network architecture, so it can provide multimedia services to users more promptly. For example, the real-time communication network may include one or more of the following network elements: a unified session control function (USF) network element, a media function (MF) network element, or a PCF / PCRF network element. It should be understood that the above network elements can be deployed independently on various physical devices, or some of the above network elements can be deployed on the same physical device; this application does not impose specific limitations.

[0118] In real-time communication networks, USF (Upper Face File) elements are control plane or signaling plane elements used to handle session control-related operations, such as creating or updating sessions. MF (Media Plane) elements are media plane elements used to handle media-related operations, such as media negotiation or media stream transmission. USF elements can implement session access or session connection control. Optionally, USF elements can also provide signaling interoperability with other IP networks. MF elements can implement media processing functions such as media negotiation and media forwarding. Optionally, MF elements can also provide media interoperability with other IP networks. Furthermore, in real-time communication networks, USF elements can allocate MF elements to terminals based on their proximity to the terminal's access location. For introductions to PCF / PCRF, IBCF, and TrGW elements, please refer to the above descriptions of PCF / PCRF, IBCF, and TrGW elements in IMS networks.

[0119] In real-time communication networks, messages between terminals and the network can be based on real-time communication protocols such as User Datagram Protocol (UDP), Quick UDP Internet Connection (QUIC), WebSocket, or Web Transport, or they can be Session Initiation Protocol (SIP) messages, without restriction. Messages between network elements (or network functions) can be based on protocols such as Hypertext Transfer Protocol (HTTP).

[0120] For example, the architecture of a real-time communication network can be as follows: Figure 1B As shown. In Figure 1B In the real-time communication network 12, there are USF network elements 1203, 1204, MF network elements 1205, MF network elements 1206, PCF / PCRF network elements 1207, and PCF / PCRF network elements 1208. Figure 1BIn this process, signaling messages (such as invitation requests, 183 messages, or update requests) sent by terminal 1201 can reach terminal 1202 via USF network elements 1203 and 1204. Media messages (such as media negotiation requests or media negotiation responses) sent by terminal 1201 can reach terminal 1202 via MF network elements 1205 and 1206. Conversely, signaling messages or media messages sent by terminal 1202 can reach terminal 1201 along the opposite path. The session between terminal 1201 and terminal 1202 can be transmitted via MF network elements 1205 and 1206, and this session can transmit media streams between terminal 1201 and terminal 1202. In addition, USF network element 1203 or MF network element 1205 can request resources to be reserved for the above session from PCF / PCRF network element 1207. USF network element 1204 or MF network element 1206 can request PCF / PCRF network element 1208 to reserve resources for the above session.

[0121] Understandably, when terminal 1201 participates in a call as the calling party and terminal 1202 participates in the call as the called party, USF network elements 1203, MF network elements 1205, and PCF / PCRF network elements 1207 can be considered as network elements in the calling domain or the calling network, while USF network elements 1204, MF network elements 1206, and PCF / PCRF network elements 1208 can be considered as network elements in the called domain or the called network. Similarly, when terminal 1201 participates in a call as the called party and terminal 1202 participates in the call as the calling party, USF network elements 1203, MF network elements 1205, and PCF / PCRF network elements 1207 can be considered as network elements in the called domain or the called network, while USF network elements 1204, MF network elements 1206, and PCF / PCRF network elements 1208 can be considered as network elements in the calling domain or the calling network.

[0122] It should be understood that Figure 1B This is merely an example of a real-time communication network. In specific applications, real-time communication networks can take other forms. For example, a real-time communication network may include... Figure 1B Show more or fewer network elements, or Figure 1B One or more network elements in the network can be replaced with other network elements that have similar functions, without restriction.

[0123] 5. Hybrid network of IMS network and real-time communication network

[0124] The hybrid network described in this application refers to a network in which some terminals are on an IMS network and others are on a real-time communication network during a call. For example, a hybrid network can be as follows: Figure 1C As shown. It should be understood that, Figure 1CThis is just one example of a hybrid network; in specific applications, hybrid networks can take other forms. For example, a hybrid network can include more than... Figure 1C Show more or fewer network elements, or Figure 1C One or more network elements in the network can be replaced with other network elements that have similar functions, without restriction.

[0125] Figure 1C The hybrid network 14 shown includes P-CSCF network element 1405, I / S-CSCF network element 1404, MMTEL AS 1403, USF network element 1406, IMS-AGW 1407, MF network element 1408, PCF / PCRF network element 1409, and PCF / PCRF network element 1410. Figure 1C In this process, signaling messages (such as invitation requests, 183 messages, or update requests) sent by terminal 1401 can reach terminal 1402 via P-CSCF network element 1405, I / S-CSCF network element 1404, MMTEL AS1403, I / S-CSCF network element 1404, and USF network element 1406. Media messages (such as media negotiation requests or media negotiation responses) sent by terminal 1401 can reach terminal 1402 via IMS-AGW 1407 and MF network element 1408. Conversely, signaling messages or media messages sent by terminal 1402 can reach terminal 1401 along the opposite path. The session between terminal 1401 and terminal 1402 can be transmitted via IMS-AGW 1407 and MF network element 1408, and this session can transmit media streams between terminal 1401 and terminal 1402. In addition, P-CSCF network element 1405 or IMS-AGW 1407 can request PCF / PCRF network element 1409 to reserve resources for the aforementioned session. USF network element 1406 or MF network element 1408 can request PCF / PCRF network element 1410 to reserve resources for the aforementioned session.

[0126] Understandably, when terminal 1401 participates in the call process as the calling party and terminal 1402 participates in the call process as the called party, P-CSCF network element 1405, I / S-CSCF network element 1404, MMTEL AS1403, IMS-AGW 1407, and PCF / PCRF network element 1409 can be regarded as network elements in the calling domain or network elements in the calling network, and USF network element 1406, MF network element 1408, and PCF / PCRF network element 1410 can be regarded as network elements in the called domain or network elements in the called network. Similarly, when terminal 1401 participates in the call process as the called party and terminal 1402 participates in the call process as the calling party, P-CSCF network element 1405, I / S-CSCF network element 1404, MMTEL AS1403, IMS-AGW 1407 and PCF / PCRF network element 1409 can be regarded as network elements in the called domain or network elements in the called network, and USF network element 1407, MF network element 1408 and PCF / PCRF network element 1410 can be regarded as network elements in the calling domain or network elements in the calling network.

[0127] 6. SIP

[0128] The SIP described in this application is an application-layer control protocol for multimedia communication over IP networks, proposed and researched by the Internet Engineering Task Force (IETF). SIP can be used to create, modify, or terminate session processes involving one or more participants. Furthermore, SIP can support one or more signaling functions for multimedia communication. For example, SIP signaling can be used to determine the location of terminals participating in the communication, i.e., for user location. And / or, SIP signaling can be used for user communication capability negotiation to determine the media type and / or parameters of the communication. And / or, SIP signaling can be used to determine user willingness to interact, such as determining whether a called user intends to participate in a communication. And / or, SIP signaling can be used to establish a call, such as instructing the called terminal to ring, or determining the session parameters of the calling and called terminals. And / or, SIP signaling can be used for call management, such as call forwarding, terminating calls, modifying session parameters, or invoking services.

[0129] In this application, SIP signaling communication can be used between control plane network elements (or signaling plane network elements).

[0130] 7. SDP

[0131] The SDP described in this application is an application-layer protocol used to describe multimedia sessions. SDP is also a text-based protocol. SIP can use SDP to complete media negotiation between the calling party and the called party. The party initiating the media negotiation can be called the SDP offerer, and the party responding to the media negotiation can be called the SDP answerer.

[0132] For example, such as Figure 1DAs shown, the SDP offeror can send an SDP proposal message (SDPOoffer) to the SDP answerer. Upon receiving the SDP offer, the SDP answerer can send an SDP response message (SDPAnswer) to the SDP offeror. The SDP offer can carry information about the SDP offeror's ability to transmit and receive media, as well as the address information of the media being transmitted and received. The SDP answer carries information about the SDP answerer's response to the SDP offeror. This information can be determined by the SDP answerer based on its own ability to transmit and receive media, its own media address information, and the information in the SDP offer. Taking the negotiation of audio and video media information between the SDP offeror and SDP answerer as an example, the information carried in the SDP offer can be shown in Table 1, and the information carried in the SDP answer can be shown in Table 2. In Table 1, “c=IN IP4 192.168.0.1” represents the IP address of the SDP offerer; “m=audio49170RTP / AVP 0 18” indicates that the audio media port of the SDP offerer is “49170”, and the supported audio codec formats are RTP / AVP 0 (specifically PCMU / 8000) and RTP / AVP 18 (specifically G729 / 8000); “m=video 51372RTP / AVP 31 32” indicates that the video media port of the SDP offerer is “51372”, and the supported video codec formats are RTP / AVP 31 and RTP / AVP 32. In Table 2, “c=IN IP4 192.168.0.3” represents the IP address of the SDP answerer; “m=audio 49172RTP / AVP 0” indicates that the audio media port of the SDP answerer is “49172”, and the audio codec format of the SDP answerer’s response is RTP / AVP 0; “m=video51372RTP / AVP 31” indicates that the video media port of the SDP answerer is “51372”, and the video codec format of the SDP answerer’s response is RTP / AVP 31.

[0133] Table 1

[0134]

[0135] Table 2

[0136]

[0137] Based on the aforementioned media negotiation, the SDP offeror can determine that the audio data sent to the SDP answerer is encoded using "PCMU / 8000", and that the destination address of this audio data is 192.168.0.3, and the destination port is 49172. The received audio data from the SDP answerer is decoded using "PCMU / 8000". The SDP offeror can also determine that the video data sent to the SDP answerer is encoded using "H261 / 90000", and that the destination address of this video data is 192.168.0.3, and the destination port is 51372. The received video data from the SDP answerer is decoded using "H261 / 90000".

[0138] Based on the aforementioned media negotiation, the SDP answerer can determine that the audio data sent to the SDP offerer is encoded using "PCMU / 8000", and that the destination address of this audio data is 192.168.0.1, and the destination port is 49170. The received audio data from the SDP offerer is decoded using "PCMU / 8000". Similarly, the SDP answerer can determine that the video data sent to the SDP offerer is encoded using "H261 / 90000", and that the destination address of this video data is 192.168.0.1, and the destination port is 51372. The received video data from the SDP offerer is decoded using "H261 / 90000".

[0139] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0140] The method provided in this application can be used in various communication systems. For example, the communication system can be a Universal Mobile Telecommunications System (UMTS) system, a Long Term Evolution (LTE) system, a 5th Generation (5G) communication system, a Wireless Fidelity (WiFi) system, a 3rd Generation Partnership Project (3GPP) related communication system, a communication system evolving after 5G, or a system integrating multiple systems, etc., without limitation. Among them, 5G can also be referred to as New Radio (NR). The following uses... Figure 2 The method provided in this application will be described using the communication system 20 shown as an example. Figure 2This is merely an illustrative diagram and does not constitute a limitation on the applicable scenarios of the technical solutions provided in this application.

[0141] like Figure 2 The diagram shown is a schematic diagram of the architecture of the communication system 20 provided in this application. Figure 2 In the communication system 20, there are control function entities 201 and media function entities 202 that are communicatively connected to the control function entities 201. Optionally, the communication system 20 also includes a policy control entity 203. The policy control entity 203 may be communicatively connected to at least one of the control function entities 201 or the media function entities 202.

[0142] The media function entity in this application, such as media function entity 202, can be used to handle media plane functions during a call, such as performing media negotiation and / or transmitting media streams. In some embodiments, after completing media negotiation for the first session, the media function entity can also send first information to the control function network element to instruct that the media negotiation for the first session be completed at the media function entity, or to instruct that resources be reserved for the first session, so that the control function entity can request the policy control entity to reserve resources for the first session. In other embodiments, the media function entity can also request the policy control entity to reserve resources for the first session after completing media negotiation for the first session. Exemplarily, the media function entity can be deployed on an IMS-AGW or MF network element.

[0143] The control function entity in this application, such as control function entity 201, can be used to handle control plane or signaling plane functions during a call, such as performing session control. The control function entity can also receive first information from a media function entity. This first information indicates that media negotiation for the first session is completed at the media function entity, or indicates that resources are reserved for the first session. Subsequently, the control function entity can request resources to be reserved for the first session from the policy control entity based on the first information. For example, the control function entity can be deployed on a P-CSCF network element or a USF network element.

[0144] The policy control entity in this application, such as policy control entity 203, can receive requests from control function entities or media function entities to reserve resources for the first session. For example, the policy control entity can be deployed on a policy control network element, such as a PCF network element or a PCRF network element.

[0145] Understandably, the aforementioned communication system 20 can be applied to various communication networks, such as IMS networks or real-time communication networks, or hybrid networks of IMS networks and real-time communication networks, etc., which will be elaborated below.

[0146] Scenario 1: Communication system 20 is used in the IMS network.

[0147] In one possible design, control function entity 201 is deployed on the P-CSCF network element in the first communication network, media function entity 202 is deployed on the IMS-AGW in the first communication network, and policy control entity 203 is deployed on the PCF / PCRF network element in the first communication network. The first communication network is either the calling network or the called network.

[0148] As an example, when communication system 20 is applied... Figure 1A In the IMS network 10 shown, control function entity 201 is deployed on P-CSCF network element 1005, media function entity 202 is deployed on IMS-AGW 1006, and policy control entity 203 is deployed on PCF / PCRF network element 1011. Alternatively, control function entity 201 is deployed on P-CSCF network element 1009, media function entity 202 is deployed on IMS-AGW 1010, and policy control entity 203 is deployed on PCF / PCRF network element 1012.

[0149] Scenario 2: Communication system 20 is used in a real-time communication network.

[0150] In one possible design, control function entity 201 is deployed on the USF network element in the first communication network, media function entity 202 is deployed on the MF network element in the first communication network, and policy control entity 203 is deployed on the PCF / PCRF network element in the first communication network. The first communication network is either the calling network or the called network.

[0151] As an example, when communication system 20 is applied... Figure 1B In the real-time communication network 12 shown, control function entity 201 is deployed on USF network element 1203, media function entity 202 is deployed on MF network element 1205, and policy control entity 203 is deployed on PCF / PCRF network element 1207. Alternatively, control function entity 201 is deployed on USF network element 1204, media function entity 202 is deployed on MF network element 1206, and policy control entity 203 is deployed on PCF / PCRF network element 1208.

[0152] Scenario 3: Communication system 20 is used in a hybrid network.

[0153] In one possible design, control function entity 201 is deployed on the P-CSCF network element in the first communication network, media function entity 202 is deployed on the IMS-AGW network element in the first communication network, and policy control entity 203 is deployed on the PCF / PCRF network element in the first communication network. Alternatively, control function entity 201 is deployed on the USF network element in the first communication network, media function entity 202 is deployed on the MF network element in the first communication network, and policy control entity 203 is deployed on the PCF / PCRF network element in the first communication network. Wherein, the first communication network is the calling network; or, the first communication network is the called network.

[0154] As an example, when communication system 20 is applied... Figure 1C In the hybrid network 14 shown, control function entity 201 is deployed on P-CSCF network element 1405, media function entity 202 is deployed on IMS-AGW 1407, and policy control entity 203 is deployed on PCF / PCRF network element 1409. Alternatively, control function entity 201 is deployed on USF network element 1406, media function entity 202 is deployed on MF network element 1408, and policy control entity 203 is deployed on PCF / PCRF network element 1410.

[0155] Understandable. Figure 2 The communication system 20 shown is for illustrative purposes only and is not intended to limit the technical solutions of this application. Those skilled in the art should understand that in specific implementations, the communication system 20 may also include other devices, and the number of control function entities, media function entities, or policy control entities may be determined according to specific needs without limitation.

[0156] Optionally, this application Figure 2 The entities in the application (such as control function entity 201 or media function entity 202) can also be referred to as communication devices. They can be general-purpose devices or special-purpose devices. This application does not make any specific limitations on this.

[0157] Optionally, this application Figure 2 The functions of each entity (e.g., control function entity 201 or media function entity 202) can be implemented by a single device, by multiple devices, or by one or more functional modules within a single device; this application does not impose specific limitations on this. It is understood that the aforementioned functions can be network elements within hardware devices, software functions running on dedicated hardware, a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0158] In its specific implementation, this application Figure 2Each entity in the code (such as control function entity 201 or media function entity 202, etc.) can adopt... Figure 3 The shown composition structure, or including Figure 3 The components shown. Figure 3 The diagram shows a hardware structure of a communication device applicable to this application. The communication device 30 includes at least one processor 301 and at least one communication interface 304 for implementing the method provided in this application. The communication device 30 may also include a communication line 302 and a memory 303.

[0159] The processor 301 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.

[0160] Communication line 302 may include a path for transmitting information between the aforementioned components, such as a bus.

[0161] Communication interface 304 is used for communication with other devices or communication networks. Communication interface 304 can be any transceiver-like device, such as an Ethernet interface, a radio access network (RAN) interface, a wireless local area network (WLAN) interface, a transceiver, pins, a bus, interface circuits, or transceiver circuits, etc.

[0162] The memory 303 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM), cache, or other type of dynamic storage device capable of storing information and instructions. It may also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. The memory may exist independently and be coupled to the processor 301 via communication line 302. The memory 303 may also be integrated with the processor 301. The memory provided in this application is generally non-volatile.

[0163] The memory 303 stores computer execution instructions involved in the scheme provided in this application, and the processor 301 controls the execution of these instructions. The processor 301 executes the computer execution instructions stored in the memory 303 to implement the method provided in this application. Alternatively, in this application, the processor 301 may execute the processing-related functions of the method provided below, and the communication interface 304 may be responsible for communicating with other devices or communication networks. This application does not specifically limit the specific implementation of this method.

[0164] Optionally, the computer execution instructions in this application may also be referred to as application code, and this application does not specifically limit them.

[0165] The coupling in this application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules.

[0166] As one embodiment, processor 301 may include one or more CPUs, for example Figure 3 CPU0 and CPU1 in the CPU.

[0167] As one embodiment, the communication device 30 may include multiple processors, such as Figure 3Processors 301 and 307 are described herein. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor here may refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0168] As one embodiment, the communication device 30 may further include an output device 305 and / or an input device 306. The output device 305 is coupled to the processor 301 and can display information in various ways. For example, the output device 305 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 306 is coupled to the processor 301 and can receive user input in various ways. For example, the input device 306 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0169] Understandable. Figure 3 The structural composition shown does not constitute a limitation on the communication device, except... Figure 3 In addition to the components shown, the communication device may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0170] The method provided in this application will now be described with reference to the accompanying drawings. The entities or network elements in the following embodiments may possess... Figure 3 The components shown are not described in detail.

[0171] It is understood that in this application, the media function entity or control function entity may perform some or all of the steps in this application. These steps are merely examples, and this application may also perform other steps or variations thereof. Furthermore, the steps may be performed in different orders as presented in this application, and it is not necessary to perform all the steps in this application.

[0172] It is understood that the methods described below in this application use media function entities and control function entities as examples to illustrate the method, but this application does not limit the execution entities of the interaction. For example, the media function entity in the method provided in the following embodiments of this application may also be a chip, chip system, or processor that supports the media function entity in implementing the method, or it may be a logic node, logic module, or software that can implement all or part of the functions of the media function entity; similarly, the control function entity in the method provided below may also be a chip, chip system, or processor that supports the control function entity in implementing the method, or it may be a logic node, logic module, or software that can implement all or part of the functions of the control function entity.

[0173] like Figure 4 The diagram illustrates a communication method provided in this application. This communication method can be applied to a call process between a first terminal and a second terminal. For example, the process of a first terminal calling a second terminal, or the process of a second terminal calling a first terminal. Figure 1A Taking the IMS network 10 shown as an example, the first terminal is terminal 1001, and the second terminal is terminal 1002; Figure 1B Taking the real-time communication network 12 shown as an example, the first terminal is terminal 1201, and the second terminal is terminal 1202; Figure 1C Taking the hybrid network 14 shown as an example, the first terminal is terminal 1401, and the second terminal is terminal 1402. This communication method may include the following steps:

[0174] S401: The media function entity sends first information to the control function entity. Correspondingly, the control function entity receives the first information from the media function entity.

[0175] In this application, the aforementioned media functional entity can be Figure 2 The media function entity 202 in the communication system 20 shown above, the aforementioned control function entity may be... Figure 2 The control function entity 201 in the communication system 20 shown. In this application, the media function entity and the control function entity may be located in the same communication network as the first terminal; or the media function entity and the control function entity may be located in the same communication network as the second terminal. For example, the media function entity, the control function entity, and the first terminal are located in the calling network; or, the media function entity, the control function entity, and the second terminal are located in the called network; or, the media function entity, the control function entity, and the first terminal are located in the called network; or, the media function entity, the control function entity, and the second terminal are located in the calling network.

[0176] In this application, the first information may instruct media negotiation for the first session to be completed at the media function entity, or the first information may instruct resources to be reserved for the first session. The first session is a session between a first terminal and a second terminal. The first session can be used to transmit media streams between the first terminal and the second terminal, and the first session passes through the aforementioned media function entity. Furthermore, the first information can be used to trigger a request for resource reservation for the first session. In other words, after receiving the first information, the control function entity can trigger a request for resource reservation for the first session.

[0177] One possible design, in order for the control function entity to determine which session to request resource reservation for, may include a first identifier that may indicate the first session.

[0178] For example, to indicate the first session, the first identifier can be the identifier of the first session. Alternatively, the first identifier can be an identifier associated with the first session, such as the media context ID corresponding to the first session. In this application, for ease of description, the example of the first identifier being the media context ID corresponding to the first session will be used for illustration, and will not be repeated hereafter.

[0179] In this application, the media context corresponding to the first session includes media information negotiated for the first session, such as media information proposed by a media function entity (e.g., SDP Offer 1 sent by a media function entity to another media function entity), and / or media information received by a media function entity in response to another media function entity (e.g., SDP Answer 1 sent by another media function entity based on the aforementioned SDP Offer 1), and / or media information received by a media function entity in response to another media function entity (e.g., SDP Offer 2 sent by another media function entity to the media function entity), and / or media information received by the media function entity in response to another media function entity (e.g., SDP Answer 2 responded by the media function entity based on the aforementioned SDP Offer 2). The media context corresponding to the first session may also include the aforementioned first identifier.

[0180] Optionally, the first information may also include at least one of the following: event information associated with the first information, third media information, or first media information. The event information is used to indicate an event associated with the first information, such as a resource reservation event. For example, the event information may include the fields "MediaPrecondition" or "Precondition".

[0181] The aforementioned third media information refers to the media information proposed during media negotiation for the first session. The first media information is the media information negotiated by the media function entity for the first session, such as media information responded to based on the third media information. The first media information can be used by the media function entity to send or receive media streams based on the first media information. For example, the third media information may be all or part of the information in the aforementioned SDP Offer 1, and the first media information may be all or part of the information in the aforementioned SDP Answer 1. As another example, the third media information may be all or part of the information in the aforementioned SDP Offer 2, and the first media information may be all or part of the information in the aforementioned SDP Answer 2.

[0182] Understandably, the first information may not include the first media information or the third media information. The media function entity may send the first media information or the third media information to the control function entity through other information, so that the control function entity may request the policy control entity to reserve resources for the first session based on the first media information or the third media information.

[0183] Optionally, the event information associated with the first identifier and the first information can be carried in the header field or message body of the first information.

[0184] For example, taking the event information associated with the first identifier and the first information as carried in the header field of the first information, the content of the first information can be as shown in Table 3. Here, "Media-Context-ID" and "Event" are the header fields of the first information, "eadgeadgfdddaegddaefadge@uac101.domain11.com" is the first identifier, "MediaPrecondition" indicates a resource reservation event, the information included in "SDP offer" is third-party media information, and the content included in "SDP answer" is first-party media information. "192.168.176.1" is the IP address of the media function entity sending the third-party media information, and "192.168.176.2" is the IP address of the media function entity sending the first-party media information.

[0185] Table 3

[0186]

[0187] One possible implementation is that, if the media negotiation for the first session is completed at the media function entity, the media function entity sends the first message to the control function entity.

[0188] For example, after receiving or sending the first media information, the media function entity sends first information to the control function entity based on the first media information. For instance, if the first media information indicates that media information negotiation for the first session was successful (e.g., the first media information includes audio / video port information and codec format information responded by other media function entities), the first information indicates that media negotiation for the first session was completed at the media function entity. If the first media information indicates that media information negotiation for the first session was successful, and both the first and second terminals support resource reservation functionality (e.g., the first media information includes attribute lines "a = des:qos mandatory local sendrecv" and "a = des:qos mandatory remote sendrecv"), the first information indicates that resources are reserved for the first session.

[0189] One possible implementation involves the control function entity sending second information to the media function entity. Correspondingly, the media function entity receives the second information from the control function entity. Subsequently, the media function entity sends first information to the control function entity based on the second information.

[0190] In this application, when the first information indicates that media negotiation for the first session is completed at the media function entity, the second information is used to subscribe to the media negotiation status of the first session. For example, the second information is a MediaStatusSubscribe message / request, and the first information is a MediaStatusNotify message / response. When the first information indicates that resources are reserved for the first session, the second information is used to subscribe to the resource reservation status of the first session. For example, the second information is a SessionEventSubscribe message / request, and the first information is a SessionEventNotify message / response. That is, the media function entity can send the first information to the control function entity when the control function entity subscribes to the corresponding information.

[0191] It should be understood that in specific applications, the control function entity may also choose not to send the second information to the media function entity, and the media function entity may send the first information to the control function entity according to the agreement or the agreement between the control function entity and the media function entity.

[0192] One possible design is that, in order for the media function entity to identify which session the second information is for, the second information may include a first identifier.

[0193] Optionally, the second information may also include at least one of the following: event information or address information of the control function entity associated with the second information.

[0194] In this application, the aforementioned event information is used to indicate the event associated with the second information, such as a resource reservation event. For example, the event information includes the fields "MediaPrecondition" or "Precondition".

[0195] In this application, the address information of the control function entity includes the IP address of the control function entity. Optionally, the address information of the control function entity also includes the port identifier or port number corresponding to the IP address. For example, the address information of the control function entity includes: 192.168.176.4:5060. Where "192.168.176.4" is the IP address of the control function entity, and "5060" is the port number corresponding to the IP address. Alternatively, the address information of the control function entity includes the hostname or domain name of the control function entity. Optionally, the address information of the control function entity also includes the port identifier or port number corresponding to the hostname or domain name. For example, the address information of the control function entity includes: uas.domain11.com:5060. Where "uas.domain11.com" is the hostname of the control function entity, and "5060" is the port number corresponding to the hostname.

[0196] Optionally, the event information associated with the first identifier and the first information, and the address information of the control function entity can be carried in the header field or message body of the second information.

[0197] For example, the content of the second information can be as shown in Table 4. Among them, "Media-Context-ID", "Media-Conn-Info" and "Event" are the header fields of the second information, "eadgeadgfdddaegddaefadge@uac101.domain11.com" is the first identifier, "192.168.176.4:6060" is the address information of the control function entity, and "MediaPrecondition" indicates the resource reservation event.

[0198] Table 4

[0199]

[0200] S402: The control function entity sends a first request to the policy control entity based on the first information. Accordingly, the policy control entity receives the first request from the control function entity.

[0201] In this application, the aforementioned policy control entity can be Figure 2 The policy control entity 203 in the communication system 20 shown. The first request is used to request that resources be reserved for the first session.

[0202] One possible implementation is that if the first information indicates that media negotiation for the first session is completed at the media function entity, the control function entity, after determining that the first terminal and the second terminal support the resource reservation function (e.g., the first media information includes attribute lines "a=des:qos mandatory local sendrecv" and "a=des:qos mandatoryremote sendrecv"), sends a first request to the policy control entity. If the first information indicates that resources are reserved for the first session, the control function entity can directly send the first request to the policy control entity.

[0203] One possible design is that the first request carries second media information. The second media information is determined based on at least one of the first media information or the third media information. For example, the second media information includes all or part of the information in the first media information, and / or all or part of the information in the third media information. For instance, the second media information includes IP address information from the first media information, and / or port information from the first media information, and / or information about the media type (e.g., audio or video media) from the first media information, and / or bandwidth information (e.g., negotiated maximum and / or minimum bandwidth) from the first media information, and / or IP address information from the second media information, and / or port information from the second media information.

[0204] Understandably, upon receiving the first request, the policy control entity can trigger the establishment of a bearer for either the first or second terminal. For example, if the control entity and the first terminal are located in the same communication network, such as the calling or called network, the policy control entity will trigger the establishment of a dedicated bearer with the access network and / or a dedicated bearer with the core network for the first terminal based on the first request. Subsequently, the first terminal can send or receive media streams through this dedicated bearer during a call with the second terminal. Similarly, if the control entity and the second terminal are located in the same communication network, such as the calling or called network, the policy control entity will trigger the establishment of a dedicated bearer with the access network and / or a dedicated bearer with the core network for the second terminal based on the first request. Subsequently, the second terminal can send or receive media streams through this dedicated bearer during a call with the first terminal.

[0205] Optionally, the policy control entity sends a response to the first request to the control function entity, and correspondingly, the control function entity receives a response to the first request from the policy function entity. The response to the first request indicates whether resource reservation for the first session has been completed. Optionally, the response to the first request may also indicate the wireless access technology used by the first or second terminal, such as 5G or 4G.

[0206] For example, the first request is an authentication / authorization request (AAR), and the response to the first request is an authentication / authorization answer (AAA). Alternatively, the first request is a policy authorization request (e.g., PolicyAuthorization_Create), and the response to the first request is a policy authorization response. Of course, the first request and its response can also be other messages; there are no restrictions.

[0207] based on Figure 4 The method shown allows the media function entity to send a first message to the control function entity after completing media negotiation, instructing the media negotiation of the first session to be completed at the media function entity, or instructing to reserve resources for the first session, thereby triggering the control function entity to request the policy control entity to reserve resources for the first session, so as to improve the call success rate of the first session.

[0208] Understandably, the actions of the media function entity or control function entity in the above steps can be performed by... Figure 3 The processor 301 in the communication device 30 shown calls the application code stored in the memory 303 to execute it, and this application does not impose any restrictions on this.

[0209] To better understand the communication method provided in this application, the following will be combined with... Figure 1A The IMS network 10 shown and Figure 1B The real-time communication network 12 shown illustrates the communication method provided in this application.

[0210] First of all, with Figure 1A The method provided in this application is illustrated using the IMS network 10 shown as an example.

[0211] like Figure 5 The diagram illustrates another communication method provided in this application, which can be applied to a call process between terminal 1001 and terminal 1002. This communication method may include the following steps:

[0212] S501: Terminal 1001 sends a first invitation request to P-CSCF network element 1005. Correspondingly, P-CSCF network element 1005 receives the first invitation request from terminal 1001.

[0213] In one possible implementation, if terminal 1001 determines that it is initiating a voice call or video call to terminal 1002, then terminal 1001 can initiate a session establishment process to establish a first session. For example, terminal 1001 sends a first invitation request to P-CSCF network element 1005 to trigger the session establishment process.

[0214] The first session is between terminals 1001 and 1002, used to transmit media streams between them. Terminals 1001 and 1002 can be understood as the endpoints of the first session. In addition to terminals 1001 and 1002, the first session also passes through IMS-AGW 1006 and IMS-AGW 1010. Further details about the first session can be found in [reference needed]. Figure 4 The method shown describes the first session.

[0215] The first invitation request does not carry an SDP Offer. The first invitation request may carry the address information of terminal 1001 and the number of terminal 1002. For example, the address information of terminal 1001 includes the IP address of terminal 1001. Optionally, the address information of terminal 1001 may also include the port identifier or port number corresponding to the IP address. Another example is that the address information of terminal 1001 includes the hostname or domain name of terminal 1001. Optionally, the address information of terminal 1001 may also include the port identifier or port number corresponding to the hostname or domain name. Optionally, the first invitation request may also carry a first identifier. The description of the first identifier can be found above. Figure 4 The description of the first identifier in the method shown will not be repeated.

[0216] Optionally, the header field or message body of the first invitation request carries the address information of terminal 1001 and the first identifier. For example, the first invitation request may include the content shown in Table 5. Here, “Media-Conn-Info” and “Media-Context-ID” are the header fields of the first invitation request, “eadgeadgfdddaegddaefadge@ue1001.domain11.com” is the first identifier, and “192.168.176.1:5060” is the address information of terminal 1001. “192.168.176.1:5060” can also be replaced with “ue1001.domain11.com:5060”.

[0217] Table 5

[0218]

[0219] S502: P-CSCF network element 1005 sends a first session creation request to IMS-AGW 1006. Correspondingly, IMS-AGW 1006 receives the first session creation request from P-CSCF network element 1005.

[0220] The first session creation request is used to request the creation of a session. The first session creation request does not carry an SDPOffer. The first session creation request carries the address information of terminal 1001. Optionally, the first session creation request may also carry a first identifier. For example, the header field or message body of the first session creation request carries the address information of terminal 1001 and the first identifier. It should be understood that if the first invitation request does not carry the first identifier, the P-CSCF network element 1005 can generate the first identifier and carry it in the first session creation request.

[0221] For example, the content included in the first session creation request can be as shown in Table 6. Here, "Media-Conn-Info" and "Media-Context-ID" are the header fields of the first session creation request, "eadgeadgfdddaegddaefadge@ue1001.domain11.com" is the first identifier, and "192.168.176.1:5060" is the address information of terminal 1001. "192.168.176.1:5060" can also be replaced with "ue1001.domain11.com:5060".

[0222] Table 6

[0223]

[0224] S503: IMS-AGW 1006 sends a first session creation response to P-CSCF network element 1005. Correspondingly, P-CSCF network element 1005 receives the first session creation response from IMS-AGW 1006.

[0225] One possible implementation is that after receiving the first session creation request, IMS-AGW 1006 saves the request and allocates address information for itself. For example, IMS-AGW 1006 allocates first address information and second address information. The first address information is used to connect IMS-AGW 1006 to terminal 1001, and the second address information is used to connect IMS-AGW 1006 to IMS-AGW 1010. The content of the first and second address information is similar to that of the address information of terminal 1001, and can be referred to the previous description of the address information of terminal 1001, which will not be repeated here.

[0226] One possible design is that the first session creation response does not carry an SDP Answer. The first session creation response carries first address information and second address information. Optionally, the first session creation response also carries a first identifier. For example, the first address information, second address information, and first identifier are carried in the header field or message body of the first session creation response. It should be understood that if the first identifier is not carried in the first session creation request, the IMS-AGW 1006 can generate the first identifier and carry it in the first session creation response.

[0227] For example, the content included in the first session creation response can be as shown in Table 7. Here, “Media-Conn-Info” and “Media-Context-ID” are the header fields of the first session creation response, “eadgeadgfdddaegddaefadge@ue1001.domain11.com” is the first identifier, “192.168.176.2:5060” is the first address information, and “192.168.176.3:5061” is the second address information. “192.168.176.2:5060” can also be replaced with “agw1006.domain11.com:5060”, and “192.168.176.3:5061” can also be replaced with “agw1006.domain11.com:5061”.

[0228] Table 7

[0229]

[0230] Understandably, to enable the P-CSCF network element 1005 to identify which device the first and second address information connects to, the positions of the first and second address information in Table 7 are pre-agreed upon or specified in the protocol. For example, the protocol may specify that the address information located earlier connects IMS-AGW 1006 to terminal 1001, while the address information located later connects IMS-AGW 1006 to IMS-AGW 1010. Of course, in specific applications, the P-CSCF network element 1005 can also identify which device the first and second address information connects to in other ways. For example, the first and second address information can be carried in different header fields, such as the first address information being carried in the header field "Media-Conn-Outer" and the second address information being carried in the header field "Media-Conn-Inner". Alternatively, the number ranges corresponding to the first and second address information may be different. Or, the first session creation request and the first session creation response may also carry an identifier for each address information.

[0231] S504: P-CSCF network element 1005 sends a second invitation request to P-CSCF network element 1009. Correspondingly, P-CSCF network element 1009 receives the second invitation request from P-CSCF network element 1005.

[0232] In one possible implementation, the second invitation request sent by P-CSCF network element 1005 can reach P-CSCF network element 1009 via I / S-CSCF network element 1004, MMTEL AS1003, I / S-CSCF network element 1004, I / S-CSCF network element 1008, MMTEL AS1007, and I / S-CSCF network element 1008 in sequence.

[0233] The second invitation request does not carry the SDP Offer. The second invitation request may carry second address information. Optionally, the second invitation request may also carry a first identifier. For example, the second address information and the first identifier may be carried in the header field or message body of the second invitation request.

[0234] For example, the content included in the second invitation request can be as shown in Table 8. Here, “Media-Conn-Info” and “Media-Context-ID” are the header fields of the second invitation request, “eadgeadgfdddaegddaefadge@ue1001.domain11.com” is the first identifier, and “192.168.176.3:5061” is the second address information. “192.168.176.3:5061” can also be replaced with “agw1006.domain11.com:5061”.

[0235] Table 8

[0236]

[0237] S505: P-CSCF network element 1009 sends a second session creation request to IMS-AGW 1010. Correspondingly, IMS-AGW 1010 receives the second session creation request from P-CSCF network element 1009.

[0238] The second session creation request is used to request the creation of a session. The second session creation request does not carry an SDPOffer. The second session creation request carries second address information. Optionally, the second session creation request may also carry a first identifier. For example, the second address information and the first identifier may be carried in the header field or message body of the second session creation request. It should be understood that if the second invitation request does not carry the first identifier, the P-CSCF network element 1009 may generate the first identifier and carry it in the second session creation request.

[0239] For example, the content included in the second session creation request can be as shown in Table 9. Here, "Media-Conn-Info" and "Media-Context-ID" are the header fields of the second session creation request, "eadgeadgfdddaegddaefadge@ue1001.domain11.com" is the first identifier, and "192.168.176.3:5061" is the second address information. "192.168.176.3:5061" can also be replaced with "agw1006.domain11.com:5061".

[0240] Table 9

[0241]

[0242] S506: IMS-AGW 1010 sends a second session creation response to P-CSCF network element 1009. Correspondingly, P-CSCF network element 1009 receives the second session creation response from IMS-AGW 1010.

[0243] One possible implementation is that after receiving the second session creation request, IMS-AGW 1010 saves the second session creation request and allocates address information for IMS-AGW 1010. For example, IMS-AGW 1010 allocates third and fourth address information. The third address information is used to connect IMS-AGW 1010 to IMS-AGW 1006, and the fourth address information is used to connect IMS-AGW 1010 to terminal 1002. The content of the third and fourth address information is similar to that of the address information of terminal 1001 described above; please refer to the previous description of the address information of terminal 1001, which will not be repeated here.

[0244] One possible design is that the second session creation response does not carry an SDP Answer. The second session creation response carries third and fourth address information. Optionally, the second session creation response also carries a first identifier. For example, the third address information, fourth address information, and first identifier are carried in the header field or message body of the second session creation response. It should be understood that if the second session creation request does not carry the first identifier, the IMS-AGW 1010 can generate the first identifier and carry it in the second session creation response.

[0245] For example, the content included in the second session creation response can be as shown in Table 10. Here, “Media-Conn-Info” and “Media-Context-ID” are the header fields of the second session creation response, “eadgeadgfdddaegddaefadge@ue1001.domain11.com” is the first identifier, “192.168.176.4:5060” is the third address information, and “192.168.176.5:5061” is the fourth address information. “192.168.176.4:5060” can also be replaced with “agw1010.domain11.com:5060”, and “192.168.176.5:5061” can also be replaced with “agw1010.domain11.com:5061”.

[0246] Table 10

[0247]

[0248] Understandably, to enable the P-CSCF network element 1009 to identify which device the third and fourth address information are connected to, the positions of the third and fourth address information in Table 10 are pre-agreed upon or specified in the protocol. Besides this, in specific applications, the P-CSCF network element 1009 can also identify which device the third and fourth address information are connected to in other ways. For example, the third and fourth address information can be carried in different header fields, such as the fourth address information being carried in the header field "Media-Conn-Outer" and the third address information being carried in the header field "Media-Conn-Inner". Alternatively, the number ranges corresponding to the third and fourth address information may be different. Or, the second session creation request and the second session creation response may also carry an identifier for each address information.

[0249] S507: P-CSCF network element 1009 sends a third invitation request to terminal 1002. Correspondingly, terminal 1002 receives the third invitation request from P-CSCF network element 1009.

[0250] The third invitation request does not carry the SDP Offer. The third invitation request may carry fourth address information. Optionally, the third invitation request may also carry a first identifier. For example, the header field or message body of the third invitation request may carry both the fourth address information and the first identifier.

[0251] For example, the content included in a third invitation request can be as shown in Table 11. Here, "Media-Conn-Info" and "Media-Context-ID" are the header fields of the third invitation request, "eadgeadgfdddaegddaefadge@ue1001.domain11.com" is the first identifier, and "192.168.176.5:5061" is the fourth address information. "192.168.176.5:5061" can also be replaced with "agw1010.domain11.com:5061".

[0252] Table 11

[0253]

[0254] S508: Terminal 1002 sends a response (e.g., message 183) to P-CSCF network element 1009 regarding the third invitation request. Correspondingly, P-CSCF network element 1009 receives the response from terminal 1002 to the third invitation request.

[0255] The response to the third invitation request does not carry an SDP Answer. The response to the third invitation request does carry the address information of terminal 1002. The content of the address information of terminal 1002 is similar to that of the address information of terminal 1001 described above; please refer to the previous description of the address information of terminal 1001, and it will not be repeated here.

[0256] Optionally, the response to the third invitation request may also carry a first identifier. For example, the address information of terminal 1002 and the first identifier may be carried in the header field or message body of the response to the third invitation request. It should be understood that if the third invitation request does not carry the first identifier, terminal 1002 may generate the first identifier and carry it in the response to the third invitation request.

[0257] For example, the response to a third invitation request may include the content shown in Table 12. Here, "Media-Conn-Info" and "Media-Context-ID" are the header fields of the response to the third invitation request, "eadgeadgfdddaegddaefadge@ue1001.domain11.com" is the first identifier, and "192.168.176.6:5060" is the address information of terminal 1002. "192.168.176.6:5060" can also be replaced with "ue1002.domain11.com:5060".

[0258] Table 12

[0259]

[0260] S509: P-CSCF network element 1009 sends a first session update request to IMS-AGW 1010. Correspondingly, IMS-AGW 1010 receives the first session update request from P-CSCF network element 1009.

[0261] The first session update request carries the address information of terminal 1002. Optionally, the first session update request also carries a first identifier. For example, the header field or message body of the first session update request carries the address information of terminal 1002 and the first identifier.

[0262] For example, the content included in the first session update request can be as shown in Table 13. Here, "Media-Conn-Info" and "Media-Context-ID" are the header fields of the first session update request, "eadgeadgfdddaegddaefadge@ue1001.domain11.com" is the first identifier, and "192.168.176.6:5060" is the address information of terminal 1002. "192.168.176.6:5060" can also be replaced with "ue1002.domain11.com:5060".

[0263] Table 13

[0264]

[0265] Understandably, after receiving the first session update request, the IMS-AGW 1010 can save the request. Optionally, the IMS-AGW 1010 can also send a first session update response (SessionUpdateResponse) to the P-CSCF network element 1009 to indicate whether the first session update request was successfully received.

[0266] S510: P-CSCF element 1009 sends a response (e.g., message 183) to P-CSCF element 1005 to the second invitation request. Correspondingly, P-CSCF element 1005 receives the response from P-CSCF element 1009 to the second invitation request.

[0267] In one possible implementation, the response to the second invitation request sent by P-CSCF network element 1009 can be routed sequentially through I / S-CSCF network element 1008, MMTEL AS1007, I / S-CSCF network element 1008, I / S-CSCF network element 1004, MMTEL AS1003, and I / S-CSCF network element 1004 to reach P-CSCF network element 1005.

[0268] The response to the second invitation request does not carry an SDP Answer. The response to the second invitation request carries third address information. Optionally, the response to the second invitation request may also carry a first identifier. For example, the third address information and the first identifier may be carried in the header field or message body of the response to the second invitation request.

[0269] For example, the response to the second invitation request may include the content shown in Table 14. Here, "Media-Conn-Info" and "Media-Context-ID" are the header fields of the response to the second invitation request, "eadgeadgfdddaegddaefadge@ue1001.domain11.com" is the first identifier, and "192.168.176.4:5060" is the third address information. "192.168.176.4:5060" can also be replaced with "agw1010.domain11.com:5060".

[0270] Table 14

[0271]

[0272] Understandably, this application does not restrict the execution order of S509 and S510. For example, S509 can be executed first and then S510, or S510 can be executed first and then S509, or S509 and S510 can be executed simultaneously.

[0273] S511: P-CSCF network element 1005 sends a second session update request to IMS-AGW 1006. Correspondingly, IMS-AGW 1006 receives the second session update request from P-CSCF network element 1005.

[0274] The second session update request carries third address information. Optionally, the second session update request may also carry a first identifier. For example, the third address information and the first identifier may be carried in the header field or message body of the second session update request.

[0275] For example, the content included in the second session update request can be as shown in Table 15. Here, "Media-Conn-Info" and "Media-Context-ID" are the header fields of the second session update request, "eadgeadgfdddaegddaefadge@ue1001.domain11.com" is the first identifier, and "192.168.176.4:5060" is the third address information. "192.168.176.4:5060" can also be replaced with "agw1010.domain11.com:5060".

[0276] Table 15

[0277]

[0278] Understandably, after receiving the second session update request, the IMS-AGW 1006 can save the request. Optionally, the IMS-AGW 1006 can also send a second session update response to the P-CSCF network element 1005 to indicate whether the second session update request was successfully received.

[0279] S512: The P-CSCF network element 1005 sends a response (such as message 183) to the terminal 1001 to the first invitation request. Correspondingly, the terminal 1001 receives the response from the P-CSCF network element 1005 to the first invitation request.

[0280] The response to the first invitation request does not carry an SDP Answer. The response to the first invitation request carries first address information. Optionally, the response to the first invitation request may also carry a first identifier. For example, the first address information and the first identifier may be carried in the header field or message body of the response to the first invitation request.

[0281] For example, the response to the first invitation request may include the content shown in Table 16. Here, "Media-Conn-Info" and "Media-Context-ID" are the header fields of the response to the first invitation request, "eadgeadgfdddaegddaefadge@ue1001.domain11.com" is the first identifier, and "192.168.176.2:5060" is the first address information. "192.168.176.2:5060" can also be replaced with "agw1006.domain11.com:5060".

[0282] Table 16

[0283]

[0284] Understandably, this application does not restrict the execution order of S511 and S512. For example, S511 can be executed first and then S512, or S512 can be executed first and then S511, or S511 and S512 can be executed simultaneously.

[0285] At this point, the session creation process between terminal 1001, P-CSCF network element 1005, P-CSCF network element 1009, and terminal 1002 has been completed. During this process, terminal 1001 obtains the address information of IMS-AGW 1006, as shown in the first address information. IMS-AGW 1006 obtains the address information of terminal 1001 and IMS-AGW 1010, as shown in the third address information. IMS-AGW 1010 obtains the address information of terminal 1002 and IMS-AGW 1006, as shown in the second address information. Terminal 1002 obtains the address information of IMS-AGW 1010, as shown in the fourth address information. Subsequently, terminal 1001, IMS-AGW 1006, IMS-AGW 1010, and terminal 1002 can perform media negotiation based on their respective obtained address information, which will be explained in detail below.

[0286] S513: P-CSCF network element 1009 sends the second information to IMS-AGW 1010. Correspondingly, IMS-AGW 1010 receives the second information from P-CSCF network element 1009.

[0287] Optionally, the IMS-AGW 1010 can send a third message to the P-CSCF network element 1009 to indicate whether the subscription was successful.

[0288] S514: P-CSCF network element 1005 sends the second information to IMS-AGW 1006. Correspondingly, IMS-AGW 1006 receives the second information from P-CSCF network element 1005.

[0289] For example, the second information in S513 and S514 can be shown in Table 17.

[0290] Table 17

[0291]

[0292] Optionally, the IMS-AGW 1006 can send a third message to the P-CSCF network element 1005 to indicate whether the subscription was successful.

[0293] Understandably, further details regarding the second information in S513 and S514 can be found above. Figure 4 The method shown describes the second information. Furthermore, Figure 5The diagram is drawn with S513 and S514 executed after S512. However, in specific applications, P-CSCF network elements 1009 and 1005 can send second information to subscribe to relevant information once they detect the establishment of the first session. For example, S513 is executed after S508 and before S521, and S514 is executed after S510 and before S522.

[0294] S515: Terminal 1001 sends a Media Negotiation Request 1 to IMS-AGW 1006 based on the first address information. Correspondingly, IMS-AGW 1006 receives the Media Negotiation Request 1 from Terminal 1001.

[0295] One possible implementation is that if the first address information includes the IP address of IMS-AGW 1006, then terminal 1001 can directly send a media negotiation request 1 to IMS-AGW 1006. If the first address information includes the hostname or domain name of IMS-AGW 1006, then terminal 1001 can query the IP address of IMS-AGW 1006 based on the first address information and send a media negotiation request 1 to IMS-AGW 1006 according to the IP address of IMS-AGW 1006.

[0296] The media negotiation request 1 carries a first identifier and media information proposed by terminal 1001. The media information proposed by terminal 1001 may include information about terminal 1001's ability to send and receive media (such as information about the encoding / decoding methods supported by terminal 1001 and whether terminal 1001 supports resource reservation), as well as address information for sending and receiving media. The media information proposed by terminal 1001 may be, for example, a first SDP Offer. The media negotiation request 1 can be a SIP message or a real-time communication protocol message transmitted based on UDP, QUIC, HTTP, WebSocket, or WebTransport.

[0297] For example, taking Media Negotiation Request 1 for negotiating audio media information, and Media Negotiation Request 1 as an example of a real-time communication protocol message transmitted based on UDP, QUIC, WebSocket, or WebTransport, the content included in Media Negotiation Request 1 can be as shown in Table 18. Here, “eadgeadgfdddaegddaefadge@ue1001.domain11.com” is the first identifier, and the information included in “SDP” is the first SDP Offer. “a=des:qos mandatory local sendrecv” indicates that terminal 1001 supports resource reservation.

[0298] Table 18

[0299]

[0300] S516: IMS-AGW 1006 sends Media Negotiation Request 2 to IMS-AGW 1010 based on the third address information. Correspondingly, IMS-AGW 1010 receives Media Negotiation Request 2 from IMS-AGW 1006.

[0301] One possible implementation is that after receiving Media Negotiation Request 1, IMS-AGW 1006 can match the first session based on the first identifier and send Media Negotiation Request 2 to IMS-AGW 1010 based on the third address information.

[0302] Understandably, if the third address information includes the IP address of IMS-AGW 1010, then IMS-AGW 1006 can directly send Media Negotiation Request 2 to IMS-AGW 1010. If the third address information includes the hostname or domain name of IMS-AGW 1010, then IMS-AGW 1006 can query the IP address of IMS-AGW 1010 based on the third address information and send Media Negotiation Request 2 to IMS-AGW 1010 according to the IP address of IMS-AGW 1010.

[0303] The Media Negotiation Request 2 carries a first identifier and media information proposed by IMS-AGW 1006, such as a second SDP Offer. The Media Negotiation Request 2 can be a SIP message or a real-time communication protocol message transmitted via UDP, QUIC, HTTP, WebSocket, or WebTransport. The second SDP Offer is determined based on the first SDP Offer. For example, IMS-AGW 1006 can modify the IP address and port information in the first SDP Offer to the IP address and port information allocated by IMS-AGW 1006, but IMS-AGW 1006 does not modify attribute lines related to resource reservation, such as the "cuur" and "des" attribute lines.

[0304] For example, taking Media Negotiation Request 2 as an example of a real-time communication protocol message transmitted based on UDP, QUIC, WebSocket, or WebTransport, the content included in Media Negotiation Request 2 can be as shown in Table 19. Here, “eadgeadgfdddaegddaefadge@ue1001.domain11.com” is the first identifier, and the information included in “SDP” is the second SDP Offer. IMS-AGW 1006 modifies the IP address “192.168.176.1” in the first SDP Offer to “192.168.176.3”, and modifies the audio media port “19024” in the first SDP Offer to “19028”.

[0305] Table 19

[0306]

[0307] S517: IMS-AGW 1010 sends a media negotiation request 3 to terminal 1002 based on the address information of terminal 1002. Correspondingly, terminal 1002 receives the media negotiation request 3 from IMS-AGW 1010.

[0308] One possible implementation is that after receiving the media negotiation request 1, the IMS-AGW 1006 can match the first session according to the first identifier and send the media negotiation request 3 to the terminal 1002 according to the address information of the terminal 1002.

[0309] Understandably, if the address information of terminal 1002 includes the IP address of terminal 1002, then IMS-AGW 1010 can directly send media negotiation request 3 to terminal 1002. If the address information of terminal 1002 includes the hostname or domain name of terminal 1002, then IMS-AGW 1010 can query the IP address of terminal 1002 based on the address information of terminal 1002, and send media negotiation request 3 to terminal 1002 according to the IP address of terminal 1002.

[0310] The Media Negotiation Request 3 carries the first identifier and the media information proposed by IMS-AGW 1010. The proposed media information may be, for example, a third SDP Offer. The Media Negotiation Request 3 can be a SIP message or a real-time communication protocol message transmitted via UDP, QUIC, HTTP, WebSocket, or WebTransport. The third SDP Offer is determined based on the second SDP Offer. For example, IMS-AGW 1010 can modify the IP address and port information in the second SDP Offer to the IP address and port information allocated by IMS-AGW 1010, but IMS-AGW 1010 does not modify the attribute lines related to resource reservation.

[0311] For example, taking Media Negotiation Request 3 as an example of a real-time communication protocol based on UDP, QUIC, WebSocket, or WebTransport, the content included in Media Negotiation Request 3 can be as shown in Table 20. Here, “eadgeadgfdddaegddaefadge@ue1001.domain11.com” is the first identifier, and the information included in “SDP” is the third SDP Offer. IMS-AGW 1010 modifies the IP address “192.168.176.3” in the second SDP Offer to “192.168.176.5”, and modifies the audio media port “19028” in the second SDP Offer to “19032”.

[0312] Table 20

[0313]

[0314]

[0315] S518: Terminal 1002 sends a Media Negotiation Response 3 to IMS-AGW 1010 based on the fourth address information. Correspondingly, IMS-AGW 1010 receives the Media Negotiation Response 3 from Terminal 1002.

[0316] In one possible implementation, after receiving the media negotiation request 3, terminal 1002 determines the media negotiation result and sends a media negotiation response 3 to IMS-AGW 1010 based on the fourth address information. The media negotiation response 3 carries the media negotiation result. For example, the media negotiation response 3 carries media information responded by terminal 1002, such as a third SDP answer. The media negotiation response 3 can be a SIP message or a real-time communication protocol message transmitted based on UDP, QUIC, HTTP, WebSocket, or WebTransport. Optionally, the media negotiation response 3 also carries a first identifier.

[0317] For example, taking media negotiation response 3 as an example of a real-time communication protocol based on UDP, QUIC, WebSocket, or WebTransport, the content included in media negotiation response 3 can be as shown in Table 21. Here, "eadgeadgfdddaegddaefadge@ue1001.domain11.com" is the first identifier, and the information included in "SDP" is the third SDP Answer. "192.168.176.6" is the IP address of terminal 1002, and "19036" is the audio media port provided by terminal 1002. The attribute line "a=des:qos mandatory remote sendrecv" indicates that terminal 1002 supports resource reservation.

[0318] Table 21

[0319]

[0320]

[0321] S519: IMS-AGW 1010 sends Media Negotiation Response 2 to IMS-AGW 1006 based on the second address information. Correspondingly, IMS-AGW 1006 receives Media Negotiation Response 2 from IMS-AGW 1010.

[0322] Media negotiation response 2 carries media information related to the IMS-AGW 1010 response, such as a second SDP answer. Media negotiation response 2 can be a SIP message or a real-time communication protocol message transmitted via UDP, QUIC, HTTP, WebSocket, or WebTransport. Optionally, media negotiation response 2 may also carry a first identifier.

[0323] For example, taking Media Negotiation Response 2 as an example of a real-time communication protocol based on UDP, QUIC, WebSocket, or WebTransport, the content included in Media Negotiation Response 2 can be as shown in Table 22. Here, “eadgeadgfdddaegddaefadge@ue1001.domain11.com” is the first identifier, and the information included in “SDP” is the second SDP Answer. IMS-AGW 1010 modifies the IP address “192.168.176.6” in the third SDP Answer to “192.168.176.4”, and modifies the audio media port “19036” in the third SDP Answer to “19040”.

[0324] Table 22

[0325]

[0326] S520: IMS-AGW 1006 sends Media Negotiation Response 1 to Terminal 1001 based on the address information of Terminal 1001. Correspondingly, Terminal 1001 receives Media Negotiation Response 1 from IMS-AGW 1006.

[0327] Media negotiation response 1 carries media information of the IMS-AGW 1006 response, such as the first SDP Answer. Media negotiation response 1 can be a SIP message or a real-time communication protocol message transmitted via UDP, QUIC, HTTP, WebSocket, or WebTransport. Optionally, media negotiation response 1 may also carry a first identifier.

[0328] For example, taking Media Negotiation Response 1 as an example of a real-time communication protocol based on UDP, QUIC, WebSocket, or WebTransport, the content of Media Negotiation Response 1 can be as shown in Table 23. Here, “eadgeadgfdddaegddaefadge@ue1001.domain11.com” is the first identifier, and the information included in “SDP” is the first SDP Answer. IMS-AGW 1006 modifies the IP address “192.168.176.4” in the second SDP Answer to “192.168.176.2”, and modifies the audio media port “19040” in the second SDP Answer to “19044”.

[0329] Table 23

[0330]

[0331]

[0332] At this point, media negotiation was completed among Terminal 1001, IMS-AGW 1006, IMS-AGW 1010, and Terminal 1002.

[0333] S521: IMS-AGW 1010 sends the first information to P-CSCF network element 1009. Correspondingly, P-CSCF network element 1009 receives the first information from IMS-AGW 1010.

[0334] In one possible implementation, the IMS-AGW 1010 determines, based on the media negotiation response 3, that the media negotiation for the first session is complete, or that resource reservation is required for the first session, and sends the first message to the P-CSCF network element 1009. The first message may indicate that the media negotiation for the first session is completed at the IMS-AGW 1010, or indicate that resources are reserved for the first session.

[0335] For example, in S521, the first information may include a first identifier, event information associated with the first information, and a third SDP Offer (and...). Figure 4 All or part of the information in the SDP Offer 1 (corresponding to the method shown), and the third SDP servlet (and) Figure 4 The information in SDP Answer 1 (as shown in the method) can be all or part of the information. For example, the content of the first information can be as shown in Table 24. Among them, eadgeadgfdddaegddaefadge@ue1001.domain11.com is the first identifier, "MediaPrecondition" is the event information associated with the first information, "SDP offer" includes content from the aforementioned third SDP Offer, and "SDP answer" includes content from the aforementioned third SDP Answer.

[0336] Table 24

[0337]

[0338]

[0339] S522: P-CSCF network element 1009 sends a first request to PCF / PCRF network element 1012 based on the first information. Correspondingly, PCF / PCRF network element 1012 receives the first request from P-CSCF network element 1009.

[0340] For example, in S522, the first request may carry all or part of the information in the third SDP Offer (such as IP address and port number) and all or part of the information in the third SDP Answer (such as IP address, port number, media type information or bandwidth information, etc.).

[0341] Understandably, after receiving the first request, PCF / PCRF network element 1012 can establish a bearer with the access network and / or with the core network for terminal 1002. This bearer can be a dedicated bearer for terminal 1002. Terminal 1002 can send or receive media streams through this dedicated bearer during subsequent calls.

[0342] Optionally, the PCF / PCRF network element 1012 sends a response to the first request to the P-CSCF network element 1009 to indicate whether the resource reservation for the first session has been completed.

[0343] S523: IMS-AGW 1006 sends the first information to P-CSCF network element 1005. Correspondingly, P-CSCF network element 1005 receives the first information from IMS-AGW 1006.

[0344] In one possible implementation, the IMS-AGW 1006 determines, based on the media negotiation response 2, that the media negotiation for the first session is complete, or that resource reservation is required for the first session, and sends the first message to the P-CSCF network element 1005. The first message may indicate that the media negotiation for the first session is completed at the IMS-AGW 1006, or indicate that resources are reserved for the first session.

[0345] For example, in S523, the first information may include a first identifier, event information associated with the first information, and a first SDP Offer (and...). Figure 4 All or part of the information in the SDP Offer 2 (corresponding to the method shown), and the first SDP servlet (and) Figure 4 The information in SDP Answer 2 (as shown in the method) can be all or part of the information. For example, the content of the first information can be as shown in Table 25. Among them, eadgeadgfdddaegddaefadge@ue1001.domain11.com is the first identifier, "MediaPrecondition" is the event information associated with the first information, "SDP offer" includes content from the aforementioned first SDP Offer, and "SDP answer" includes content from the aforementioned first SDP Answer.

[0346] Table 25

[0347]

[0348]

[0349] S524: P-CSCF network element 1005 sends a first request to PCF / PCRF network element 1011 based on the first information. Correspondingly, PCF / PCRF network element 1011 receives the first request from P-CSCF network element 1005.

[0350] For example, in S524, the first request may carry all or part of the information in the first SDP Offer (such as IP address and port number) and all or part of the information in the first SDP Answer (such as IP address, port number, media type information or bandwidth information, etc.).

[0351] Understandably, after receiving the first request, PCF / PCRF network element 1011 can establish a bearer with the access network and / or with the core network for terminal 1001. This bearer can be a dedicated bearer for terminal 1001. Terminal 1001 can then send or receive media streams through this dedicated bearer during subsequent calls.

[0352] Optionally, the PCF / PCRF network element 1011 sends a response to the first request to the P-CSCF network element 1005 to indicate whether the resource reservation for the first session has been completed.

[0353] Understandably, the specific processes of S521-S522 and S523-S524 are the same as those described above. Figure 4 The processes S401 to S402 in the method shown are similar, and you can refer to the corresponding descriptions in S401 to S402 above. Furthermore, Figure 5 The drawing is based on the assumption that S521-S522 and S523-S524 are executed after S520. However, in practical applications, IMS-AGW 1010 and IMS-AGW 1006 can send the first message to trigger resource reservation once they detect the completion of media negotiation. For example, S521-S522 can be executed after S518, and S523-S524 can be executed after S519.

[0354] S525: Terminal 1001 sends a media negotiation request 4 to IMS-AGW 1006 based on the first address information. Correspondingly, IMS-AGW 1006 receives the media negotiation request 4 from terminal 1001.

[0355] One possible implementation is that after the terminal 1001 recognizes that the bearer between the terminal 1001 and the access network and the core network has been successfully established, it sends a media negotiation request 4 to the IMS-AGW 1006 according to the first address information to update the resource reservation status of the terminal 1001.

[0356] For example, the content included in Media Negotiation Request 4 can be as shown in Table 26. The attribute line “a=curr:qos local sendrecv” indicates that resource reservation for terminal 1001 has been completed.

[0357] Table 26

[0358]

[0359] S526: IMS-AGW 1006 sends a media negotiation request 5 to IMS-AGW 1010 based on the third address information. Correspondingly, IMS-AGW 1010 receives the media negotiation request 5 from IMS-AGW 1006.

[0360] For example, the content of media negotiation request 5 may be as shown in Table 27.

[0361] Table 27

[0362]

[0363] S527: IMS-AGW 1010 sends a media negotiation request 6 to terminal 1002 based on the address information of terminal 1002. Correspondingly, terminal 1002 receives the media negotiation request 6 from IMS-AGW 1010.

[0364] For example, a media negotiation request may include the content shown in Table 28.

[0365] Table 28

[0366]

[0367]

[0368] S528: Terminal 1002 sends a media negotiation response 6 to IMS-AGW 1010 based on the fourth address information. Correspondingly, IMS-AGW 1010 receives the media negotiation response 6 from terminal 1002.

[0369] One possible implementation is that after the terminal 1002 recognizes that the bearer between the terminal 1002 and the access network and the core network has been successfully established, it sends a media negotiation response 6 to the IMS-AGW 1010 according to the fourth address information to update the resource reservation status of the terminal 1002.

[0370] For example, the content included in media negotiation response 6 can be shown in Table 29. The attribute line “a=curr:qos remote sendrecv” indicates that resource reservation for terminal 1002 has been completed.

[0371] Table 29

[0372]

[0373] S529: IMS-AGW 1010 sends Media Negotiation Response 5 to IMS-AGW 1006 based on the second address information. Correspondingly, IMS-AGW 1006 receives Media Negotiation Response 5 from IMS-AGW 1010.

[0374] For example, the content of media negotiation response 5 may be as shown in Table 30.

[0375] Table 30

[0376]

[0377] S530: IMS-AGW 1006 sends a media negotiation response 4 to terminal 1001 based on the address information of terminal 1001. Correspondingly, terminal 1001 receives the media negotiation response 4 from IMS-AGW 1006.

[0378] For example, the content of media negotiation response 4 may be as shown in Table 31.

[0379] Table 31

[0380]

[0381] S531: Terminal 1001, IMS-AGW 1006, IMS-AGW 1010 and terminal 1002 transmit media streams based on media negotiation results.

[0382] One possible implementation is that after terminal 1002 rings and is picked up, the users of terminal 1001 and terminal 1002 conduct voice or video calls, and the media stream is transmitted between terminal 1001, IMS-AGW 1006, IMS-AGW 1010 and terminal 1002 based on the media negotiation result.

[0383] based on Figure 5The method shown allows terminal 1001, P-CSCF network element 1005, P-CSCF network element 1009, and terminal 1002 to create a first session. During the creation of the first session, media negotiation is not performed; instead, the address information required for media negotiation is carried to each device. Subsequently, terminal 1001, IMS-AGW 1006, IMS-AGW 1010, and terminal 1002 can perform media negotiation based on the corresponding address information. This method separates session creation from media negotiation. Furthermore, after P-CSCF network element 1005 detects the successful establishment of the first session, it can subscribe to the media negotiation status or resource reservation status from IMS-AGW 1006. This allows IMS-AGW 1006 to send first information to P-CSCF network element 1005 when it detects that media negotiation is complete or that resource reservation is required, thereby triggering resource reservation. Similarly, after P-CSCF network element 1009 detects the successful establishment of the first session, it can subscribe to the media negotiation status or resource reservation status from IMS-AGW 1010. This allows IMS-AGW 1010 to send the first message to P-CSCF network element 1009 when it detects that media negotiation is complete or that resource reservation is needed, thereby triggering resource reservation. Through this method, a resource reservation mechanism can be applied in scenarios where the session creation process and the media negotiation process are separated, reserving resources for terminals 1001 and 1002 to improve the call success rate of the first session.

[0384] Understandably, the actions of IMS-AGW 1006, P-CSCF network element 1005, IMS-AGW 1010, or P-CSCF network element 1009 in the above steps can be performed by... Figure 3 The processor 301 in the communication device 30 shown calls the application code stored in the memory 303 to execute it, and this application does not impose any restrictions on this.

[0385] The following is based on Figure 1B The method provided in this application is illustrated using the real-time communication network 12 shown as an example.

[0386] like Figure 6 The diagram illustrates another communication method provided in this application, which can be applied to a call process between terminal 1201 and terminal 1202. This communication method may include the following steps:

[0387] S601: Terminal 1201 sends a first session connection request to USF network element 1203. Correspondingly, USF network element 1203 receives the first session connection request from terminal 1201.

[0388] In one possible implementation, if terminal 1201 determines that it is initiating a voice call or video call to terminal 1202, then terminal 1201 can initiate a session establishment process to establish a first session. For example, terminal 1201 sends a first session connection request to USF network element 1203 to trigger the session establishment process.

[0389] The first session is between terminals 1201 and 1202, used to transmit media streams between them. Terminals 1201 and 1202 can be considered as endpoints of the first session. In addition to terminals 1201 and 1202, the first session also passes through MF network elements 1205 and 1206. Further details about the first session can be found in [reference needed]. Figure 4 The method described herein describes the first session. The first session connection request does not carry an SDP Offer. The first session connection request may carry the address information of terminal 1201 and the number of terminal 1202. Optionally, the first session connection request may also carry a first identifier. For example, the header field or message body of the first session connection request carries the address information of terminal 1201 and the first identifier. The description of the address information of terminal 1201 can be found above. Figure 5 The description of the address information of terminal 1001 in the method shown above, and the introduction of the first identifier, can be found in the above description. Figure 4 The description of the first identifier in the method shown will not be repeated.

[0390] For example, the content of the first session connection request can be as shown in Table 32. Here, “Callee”, “Media-Conn-Info”, and “Media-Context-ID” are the header fields of the first session connection request; “+8618812345678” is the number of terminal 1202; “eadgeadgfdddaegddaefadge@ue1201.domain11.com” is the first identifier; and “192.168.176.1:6060” is the address information of terminal 1201. “192.168.176.1:6060” can also be replaced with “ue1201.domain11.com:6060”.

[0391] Table 32

[0392]

[0393] S602: USF network element 1203 sends a first session creation request to MF network element 1205. Correspondingly, MF network element 1205 receives the first session creation request from USF network element 1203.

[0394] One possible implementation is that the USF network element 1203 can determine the MF network element 1205 based on the location information of the terminal 1201, and send a first session creation request to the MF network element 1205. The location information of the terminal 1201 can be reported by the terminal 1201 during registration or reported through the first session connection request. Optionally, in addition to the location information of the terminal 1201, the USF network element 1203 can also determine the MF network element 1205 based on the load of the MF network element.

[0395] The first session creation request is used to request the creation of a session. The first session creation request does not carry an SDPOffer. The first session creation request carries the address information of terminal 1201. Optionally, the first session creation request may also carry a first identifier. For example, the header field or message body of the first session creation request carries the address information of terminal 1201 and the first identifier. It should be understood that if the first session connection request does not carry the first identifier, the USF network element 1203 can generate the first identifier and carry it in the first session creation request.

[0396] For example, the contents of the first session creation request may be as shown in Table 33.

[0397] Table 33

[0398]

[0399] S603: MF network element 1205 sends a first session creation response (SessionCreateResponse) to USF network element 1203. Correspondingly, USF network element 1203 receives the first session creation response from MF network element 1205.

[0400] One possible implementation is that after receiving the first session creation request, MF network element 1205 saves the first session creation request and allocates address information for MF network element 1205. For example, MF network element 1205 allocates first address information and second address information. The first address information is used to connect MF network element 1205 to terminal 1201, and the second address information is used to connect MF network element 1205 to MF network element 1206. The contents of the first address information and the second address information are the same as... Figure 5 In the method shown, the address information of terminal 1001 includes similar content. Please refer to the previous introduction of the address information of terminal 1001, which will not be repeated here.

[0401] One possible design is that the first session creation response does not carry an SDP Answer. The first session creation response carries first address information and second address information. Optionally, the first session creation response also carries a first identifier. For example, the first address information, second address information, and first identifier are carried in the header field or message body of the first session creation response. It should be understood that if the first identifier is not carried in the first session creation request, the MF network element 1205 can generate the first identifier and carry it in the first session creation response.

[0402] For example, the content included in the first session creation response can be as shown in Table 34. Among them, "192.168.176.3:6060" is the first address information, and "192.168.176.4:6061" is the second address information.

[0403] Table 34

[0404]

[0405] Understandably, to enable the USF network element 1203 to identify which device the first and second address information are connected to, the positions of the first and second address information in Table 34 are pre-agreed upon or specified in the protocol. Besides this, in specific applications, the USF network element 1203 can also identify which device the first and second address information are connected to in other ways. For example, the first and second address information can be carried in different header fields, such as the first address information being carried in the header field "Media-Conn-Outer" and the second address information being carried in the header field "Media-Conn-Inner". Alternatively, the number ranges corresponding to the first and second address information may be different. Or, the first session creation request and the first session creation response may also carry an identifier for each address information.

[0406] S604: USF network element 1203 sends a second session connection request to USF network element 1204. Correspondingly, USF network element 1204 receives the second session connection request from USF network element 1203.

[0407] One possible implementation is that USF network element 1203 determines the USF network element 1204 that can provide services to terminal 1202 based on the registration information of the terminal 1202's number, and sends a second session connection request to USF network element 1204.

[0408] The second session connection request does not carry an SDP Offer. The second session connection request may carry second address information. Optionally, the second session connection request may also carry a first identifier. For example, the second address information and the first identifier may be carried in the header field or message body of the second session connection request. For example, the content included in the second session connection request may be as shown in Table 35.

[0409] Table 35

[0410]

[0411] S605: USF network element 1204 sends a second session creation request to MF network element 1206. Correspondingly, MF network element 1206 receives the second session creation request from USF network element 1204.

[0412] One possible implementation is that USF network element 1204 can determine MF network element 1206 based on the location information of terminal 1202, and send a second session creation request to MF network element 1206. The location information of terminal 1202 can be reported by terminal 1202 during registration. Optionally, in addition to the location information of terminal 1202, USF network element 1204 can also determine MF network element 1206 based on the load of the MF network element.

[0413] The second session creation request is used to request the creation of a session. The second session creation request does not carry an SDPOffer. The second session creation request carries second address information. Optionally, the second session creation request may also carry a first identifier. For example, the second address information and the first identifier may be carried in the header field or message body of the second session creation request. It should be understood that if the second session connection request does not carry the first identifier, the USF network element 1204 can generate the first identifier and carry it in the second session creation request. The specific format of the second session creation request is similar to that of the first session creation request; please refer to the previous description of the first session creation request, which will not be repeated here.

[0414] S606: MF network element 1206 sends a second session creation response to USF network element 1204. Correspondingly, USF network element 1204 receives the second session creation response from MF network element 1206.

[0415] In one possible implementation, after receiving the second session creation request, MF network element 1206 saves the second session creation request and allocates address information for MF network element 1206. For example, MF network element 1206 allocates third address information and fourth address information. The third address information is used to connect MF network element 1206 to MF network element 1205, and the fourth address information is used to connect MF network element 1206 to terminal 1202. The content of the third and fourth address information is the same as... Figure 5In the method shown, the address information of terminal 1001 includes similar content. Please refer to the previous introduction of the address information of terminal 1001, which will not be repeated here.

[0416] One possible design is that the second session creation response does not carry the SDP Answer. The second session creation response carries third and fourth address information. Optionally, the second session creation response also carries a first identifier. For example, the third and fourth address information and the first identifier are carried in the header field or message body of the second session creation response. It should be understood that if the second session creation request does not carry the first identifier, the MF network element 1206 can generate the first identifier and carry it in the second session creation response. The specific format of the second session creation response is similar to that of the first session creation response; please refer to the previous description of the first session creation response, which will not be repeated here.

[0417] S607: USF network element 1204 sends a third session connection request to terminal 1202. Correspondingly, terminal 1202 receives the third session connection request from USF network element 1204.

[0418] The third session connection request does not carry an SDP Offer. The third session connection request may carry fourth address information. Optionally, the third session connection request may also carry a first identifier. For example, the header field or message body of the third session connection request may carry the fourth address information and the first identifier. The specific format of the third session connection request is similar to that of the first and second session connection requests; please refer to the corresponding descriptions above.

[0419] S608: Terminal 1202 sends a third session connection response (SessionConnectResponse) to USF network element 1204. Correspondingly, USF network element 1204 receives the third session connection response from terminal 1202.

[0420] The third session connection response does not carry an SDP Answer. Instead, it carries the address information of terminal 1202. Optionally, the third session connection response may also carry a first identifier. For example, the address information of terminal 1202 and the first identifier may be carried in the header field or message body of the third session connection response. It should be understood that if the third session connection request does not carry the first identifier, terminal 1202 may generate the first identifier and carry it in the third session connection response.

[0421] For example, the content included in the third session connection response can be as shown in Table 36. Here, "Media-Conn-Info" and "Media-Context-ID" are the header fields of the third session connection response, "eadgeadgfdddaegddaefadge@ue1201.domain11.com" is the first identifier, and "192.168.176.6:6060" is the address information of terminal 1202. "192.168.176.6:6060" can also be replaced with "ue1202.domain11.com:6060".

[0422] Table 36

[0423]

[0424] S609: USF element 1204 sends a first session update request to MF element 1206. Correspondingly, MF element 1206 receives the first session update request from USF element 1204.

[0425] The first session update request carries the address information of terminal 1202. Optionally, the first session update request also carries a first identifier. For example, the header field or message body of the first session update request carries the address information of terminal 1202 and the first identifier. For example, the content included in the first session update request may be as shown in Table 37.

[0426] Table 37

[0427]

[0428] Understandably, after receiving the first session update request, MF network element 1206 can save the request. Optionally, MF network element 1206 can also send a first session update response (SessionUpdateResponse) to USF network element 1204 to indicate whether the first session update request was successfully received.

[0429] S610: USF network element 1204 sends a second session connection response to USF network element 1203. Correspondingly, USF network element 1203 receives the second session connection response from USF network element 1204.

[0430] The second session connection response does not carry an SDP Answer. The second session connection response carries third address information. Optionally, the second session connection response may also carry a first identifier. For example, the third address information and the first identifier may be carried in the header field or message body of the second session connection response.

[0431] For example, the content included in the second session connection response can be as shown in Table 38. Among them, "Media-Conn-Info" and "Media-Context-ID" are the header fields of the second session connection response, "eadgeadgfdddaegddaefadge@ue1201.domain11.com" is the first identifier, and "192.168.176.4:6060" is the third address information.

[0432] Table 38

[0433]

[0434] Understandably, this application does not restrict the execution order of S609 and S610. For example, S609 can be executed first and then S610, or S610 can be executed first and then S609, or S609 and S610 can be executed simultaneously.

[0435] S611: USF network element 1203 sends a second session update request to MF network element 1205. Correspondingly, MF network element 1205 receives the second session update request from USF network element 1203.

[0436] The second session update request carries third address information. Optionally, the second session update request also carries a first identifier. For example, the third address information and the first identifier are carried in the header field or message body of the second session update request. The format of the second session update request is similar to that of the first session update request described above, and will not be repeated here.

[0437] Understandably, after receiving the second session update request, MF network element 1205 can save the request. Optionally, MF network element 1205 can also send a second session update response to USF network element 1203 to indicate whether the second session update request was successfully received.

[0438] S612: USF network element 1203 sends a first session connection response to terminal 1201. Correspondingly, terminal 1201 receives the first session connection response from USF network element 1203.

[0439] The first session connection response does not carry an SDP Answer. The first session connection response carries first address information. Optionally, the first session connection response may also carry a first identifier. For example, the first address information and the first identifier are carried in the header field or message body of the first session connection response. The format of the first session connection response is similar to that of the second and third session connection responses described above, and will not be repeated here.

[0440] Understandably, this application does not restrict the execution order of S611 and S612. For example, S611 can be executed first and then S612, or S612 can be executed first and then S611, or S611 and S612 can be executed simultaneously.

[0441] At this point, the session creation process between terminal 1201, USF network element 1203, USF network element 1204, and terminal 1202 has been completed. During this process, terminal 1201 obtains the address information of MF network element 1205, as shown in the first address information. MF network element 1205 obtains the address information of terminal 1201 and MF network element 1206, as shown in the third address information. MF network element 1206 obtains the address information of terminal 1202 and MF network element 1205, as shown in the second address information. Terminal 1202 obtains the address information of MF network element 1206, as shown in the fourth address information. Subsequently, terminal 1201, MF network element 1205, MF network element 1206, and terminal 1202 can perform media negotiation based on their respective obtained address information, which will be explained in detail below.

[0442] S613: USF network element 1204 sends the second information to MF network element 1206. Correspondingly, MF network element 1206 receives the second information from USF network element 1204.

[0443] For example, the second information in S613 can be shown in Table 39. Among them, "192.168.176.2:6060" is the address information of USF network element 1204.

[0444] Table 39

[0445]

[0446] Optionally, MF element 1206 can send a third message to USF element 1204 to indicate whether the subscription was successful.

[0447] S614: USF network element 1203 sends the second information to MF network element 1205. Correspondingly, MF network element 1205 receives the second information from USF network element 1203.

[0448] For example, the second information in S614 can be shown in Table 40. Among them, "192.168.176.3:6060" is the address information of USF network element 1203.

[0449] Table 40

[0450]

[0451] Optionally, MF element 1205 can send a third message to USF element 1203 to indicate whether the subscription was successful.

[0452] Understandably, further details regarding the second information in S613 and S614 can be found above. Figure 4 The method shown describes the second information. Furthermore, Figure 6 The diagram is drawn with S613 and S614 executed after S612. However, in specific applications, USF network elements 1203 and 1204 can send second information to subscribe to relevant information once they detect the establishment of the first session. For example, S613 is executed after S608 and before S621, and S614 is executed after S610 and before S622.

[0453] S615: Terminal 1201 sends a Media Negotiation Request 1 to MF network element 1205 based on the first address information. Correspondingly, MF network element 1205 receives the Media Negotiation Request 1 from terminal 1201.

[0454] One possible implementation is that terminal 1201 generates a media negotiation request 1 based on the call type and its own encoding / decoding capabilities.

[0455] The media negotiation request 1 carries a first identifier and media information proposed by terminal 1201. The media information proposed by terminal 1201 may include information about terminal 1201's ability to send and receive media (such as information about the encoding / decoding methods supported by terminal 1201 and whether terminal 1201 supports resource reservation), as well as address information for sending and receiving media. The media information proposed by terminal 1201 may be, for example, a first SDP Offer. The media negotiation request 1 can be a SIP message or a real-time communication protocol message based on UDP, QUIC, HTTP, WebSocket, or WebTransport.

[0456] For example, taking Media Negotiation Request 1 for negotiating video media information, and Media Negotiation Request 1 as an example of a real-time communication protocol message transmitted based on UDP, QUIC, WebSocket, or WebTransport, the content included in Media Negotiation Request 1 can be as shown in Table 41. Here, “eadgeadgfdddaegddaefadge@ue1201.domain11.com” is the first identifier, and the information included in “SDP” is the first SDP Offer. “a=des:qos mandatory local sendrecv” indicates that terminal 1201 supports resource reservation.

[0457] Table 41

[0458]

[0459] S616: MF network element 1205 sends a media negotiation request 2 to MF network element 1206 based on the third address information. Correspondingly, MF network element 1206 receives the media negotiation request 2 from MF network element 1205.

[0460] One possible implementation is that after receiving Media Negotiation Request 1, MF Network Element 1205 can match the first session according to the first identifier and send Media Negotiation Request 2 to MF Network Element 1206 according to the third address information.

[0461] The Media Negotiation Request 2 carries the first identifier and the media information proposed by MF network element 1205. The media information proposed by MF network element 1205 is, for example, the second SDP Offer. Media Negotiation Request 2 can be a SIP message or a real-time communication protocol message transmitted based on UDP, QUIC, HTTP, WebSocket, or WebTransport. The second SDP Offer is determined based on the first SDP Offer. For example, MF network element 1205 can modify the IP address and port information in the first SDP Offer to the IP address and port information allocated by MF network element 1205. However, MF network element 1205 does not modify attribute lines related to resource reservation, such as the "cuur" and "des" attribute lines.

[0462] For example, Media Negotiation Request 2 is a real-time communication protocol message based on HTTP transmission. The content of Media Negotiation Request 2 can be shown in Table 42.

[0463] Table 42

[0464]

[0465] S617: MF network element 1206 sends a media negotiation request 3 to terminal 1202 based on the address information of terminal 1202. Correspondingly, terminal 1202 receives the media negotiation request 3 from MF network element 1206.

[0466] One possible implementation is that after receiving the media negotiation request 1, the MF network element 1205 can match the first session according to the first identifier and send the media negotiation request 3 to the terminal 1202 according to the address information of the terminal 1202.

[0467] The Media Negotiation Request 3 carries the first identifier and the media information proposed by MF network element 1206. The media information proposed by MF network element 1206 is, for example, the third SDP Offer. Media Negotiation Request 3 can be a SIP message or a real-time communication protocol message transmitted based on UDP, QUIC, HTTP, WebSocket, or WebTransport. The third SDP Offer is determined based on the second SDP Offer. For example, MF network element 1206 can modify the IP address and port information in the second SDP Offer to the IP address and port information allocated by MF network element 1206. However, MF network element 1206 does not modify attribute lines related to resource reservation, such as the "cuur" and "des" attribute lines.

[0468] For example, taking Media Negotiation Request 3 as an example of a real-time communication protocol message transmitted based on UDP, QUIC, WebSocket, or WebTransport, the content included in Media Negotiation Request 3 can be as shown in Table 43. Here, “eadgeadgfdddaegddaefadge@ue1201.domain11.com” is the first identifier, and the information included in “SDP” is the third SDP Offer. “192.168.176.5” is the fourth address information.

[0469] Table 43

[0470]

[0471] S618: Terminal 1202 sends a Media Negotiation Response 3 to MF network element 1206 based on the fourth address information. Correspondingly, MF network element 1206 receives the Media Negotiation Response 3 from terminal 1202.

[0472] In one possible implementation, after receiving the media negotiation request 3, terminal 1202 determines the media negotiation result based on call similarity and its own encoding / decoding capabilities, and sends a media negotiation response 3 to MF network element 1206 based on the fourth address information. The media negotiation response 3 carries the media negotiation result. For example, the media negotiation response 3 carries media information responded by terminal 1202, such as a third SDP answer. The media negotiation response 3 can be a SIP message, or a real-time communication protocol message transmitted based on UDP, QUIC, HTTP, WebSocket, or WebTransport. Optionally, the media negotiation response 3 also carries a first identifier.

[0473] For example, taking media negotiation response 3 as an example of a real-time communication protocol message transmitted based on UDP, QUIC, WebSocket, or WebTransport, the content included in media negotiation response 3 can be as shown in Table 44. The attribute line "a=des:qosmandatory remote sendrecv" indicates that terminal 1202 supports resource reservation.

[0474] Table 44

[0475]

[0476]

[0477] S619: MF network element 1206 sends media negotiation response 2 to MF network element 1205 based on the second address information. Correspondingly, MF network element 1205 receives media negotiation response 2 from MF network element 1206.

[0478] The media negotiation response 2 carries media information from the MF network element 1206's response, such as a second SDP answer. The media negotiation response 2 can be a SIP message or a real-time communication protocol message transmitted via UDP, QUIC, HTTP, WebSocket, or WebTransport. Optionally, the media negotiation response 2 may also carry a first identifier.

[0479] For example, Media Negotiation Response 2 is a real-time communication protocol message based on HTTP transmission. The contents of Media Negotiation Response 2 can be shown in Table 45.

[0480] Table 45

[0481]

[0482] S620: MF network element 1205 sends Media Negotiation Response 1 to terminal 1201 based on the address information of terminal 1201. Correspondingly, terminal 1201 receives Media Negotiation Response 1 from MF network element 1205.

[0483] The media negotiation response 1 carries media information from the MF network element 1205's response, such as the first SDP Answer. The media negotiation response 1 can be a SIP message or a real-time communication protocol message transmitted via UDP, QUIC, HTTP, WebSocket, or WebTransport. Optionally, the media negotiation response 1 may also carry a first identifier.

[0484] For example, taking Media Negotiation Response 1 as an example of a real-time communication protocol message transmitted based on UDP, QUIC, WebSocket, or WebTransport, the content included in Media Negotiation Response 1 can be as shown in Table 46. Here, “eadgeadgfdddaegddaefadge@ue1201.domain11.com” is the first identifier, and the information included in “SDP” is the first SDP Answer. “192.168.176.2” is the first address information.

[0485] Table 46

[0486]

[0487] At this point, media negotiation is completed between terminal 1201, MF network element 1205, MF network element 1206, and terminal 1202.

[0488] S621: MF network element 1206 sends the first information to USF network element 1204. Correspondingly, USF network element 1204 receives the first information from MF network element 1206.

[0489] In one possible implementation, MF network element 1206 determines, based on media negotiation response 3, that the media negotiation of the first session is complete, or that resource reservation is required for the first session, and sends first information to USF network element 1204. The first information may instruct that the media negotiation of the first session be completed at MF network element 1206, or instruct that resources be reserved for the first session.

[0490] For example, in S621, the first information may include a first identifier, event information associated with the first information, and a third SDP Offer (and...). Figure 4 The information in SDP Offer 1 (corresponding to the method shown) and the third SDP offer Figure 4 The information in SDP Answer 1 (as shown in the method) can be all or part of the information. For example, the content of the first information can be as shown in Table 47. Here, eadgeadgfdddaegddaefadge@ue1201.domain11.com is the first identifier, "MediaPrecondition" is the event information associated with the first information, "SDP offer" includes content from the aforementioned third SDP Offer, and "SDP answer" includes content from the aforementioned third SDP Answer.

[0491] Table 47

[0492]

[0493]

[0494] S622: USF network element 1204 sends a first request to PCF / PCRF network element 1208 based on the first information. Correspondingly, PCF / PCRF network element 1208 receives the first request from USF network element 1204.

[0495] For example, in S622, the first request may carry all or part of the information in the third SDP Offer (such as IP address and port number) and all or part of the information in the third SDP Answer (such as IP address, port number, media type information or bandwidth information, etc.).

[0496] Understandably, after receiving the first request, PCF / PCRF network element 1208 can establish a bearer with the access network and / or with the core network for terminal 1202. This bearer can be a dedicated bearer for terminal 1202. Terminal 1208 can then send or receive media streams through this dedicated bearer during subsequent calls.

[0497] Optionally, PCF / PCRF network element 1208 sends a response to the first request to USF network element 1204 to indicate whether the resource reservation for the first session is complete.

[0498] S623: MF network element 1205 sends the first information to USF network element 1203. Correspondingly, USF network element 1203 receives the first information from MF network element 1205.

[0499] In one possible implementation, MF network element 1205 determines, based on media negotiation response 2, that the media negotiation of the first session is complete, or that resource reservation is required for the first session, and sends first information to USF network element 1203. The first information may instruct that the media negotiation of the first session be completed at MF network element 1205, or instruct that resources be reserved for the first session.

[0500] For example, in S623, the first information may include a first identifier, event information associated with the first information, and a first SDP Offer (and...). Figure 4 All or part of the information in the SDP Offer 2 (corresponding to the method shown), and the first SDP servlet (and) Figure 4The information in SDP Answer 2 (as shown in the method) can be all or part of the information. For example, the content of the first information can be as shown in Table 48. In this table, eadgeadgfdddaegddaefadge@ue1201.domain11.com is the first identifier, "MediaPrecondition" is the event information associated with the first information, "SDP offer" includes content from the aforementioned first SDP Offer, and "SDP answer" includes content from the aforementioned first SDP Answer.

[0501] Table 48

[0502]

[0503]

[0504] S624: USF network element 1203 sends a first request to PCF / PCRF network element 1207 based on the first information. Correspondingly, PCF / PCRF network element 1207 receives the first request from USF network element 1203.

[0505] For example, in S624, the first request may carry all or part of the information in the first SDP Offer (such as IP address and port number) and all or part of the information in the first SDP Answer (such as IP address, port number, media type information or bandwidth information, etc.).

[0506] Understandably, after receiving the first request, PCF / PCRF network element 1207 can establish a bearer with the access network and / or with the core network for terminal 1201. This bearer can be a dedicated bearer for terminal 1201. Terminal 1201 can send or receive media streams through this dedicated bearer during subsequent calls.

[0507] Optionally, PCF / PCRF network element 1207 sends a response to the first request to USF network element 1203 to indicate whether the resource reservation for the first session is complete.

[0508] Understandably, the specific processes of S621-S622 and S623-S624 are similar to those described above. Figure 4 The processes S401 to S402 in the method shown are similar, and you can refer to the corresponding descriptions in S401 to S402 above. Furthermore, Figure 6The code is drawn so that S621-S622 and S623-S624 are executed after S620. However, in practical applications, MF network elements 1205 and 1206 can send the first message to trigger resource reservation once they detect that media negotiation is complete. For example, S621-S622 can be executed after S618, and S623-S624 can be executed after S619.

[0509] S625: Terminal 1201 sends a media negotiation request 4 to MF network element 1205 based on the first address information. Correspondingly, MF network element 1205 receives the media negotiation request 4 from terminal 1201.

[0510] One possible implementation is that after the terminal 1201 recognizes that the bearer between the terminal 1201 and the access network and the core network has been successfully established, it sends a media negotiation request 4 to the MF network element 1205 according to the first address information to update the resource reservation status of the terminal 1201.

[0511] For example, the content of media negotiation request 4 can be as shown in Table 49. Among them, the attribute line "a=curr:qos local sendrecv" indicates that the resource reservation of terminal 1201 has been completed.

[0512] Table 49

[0513]

[0514] S626: MF network element 1205 sends a media negotiation request 5 to MF network element 1206 based on the third address information. Correspondingly, MF network element 1206 receives the media negotiation request 5 from MF network element 1205.

[0515] For example, the content of media negotiation request 5 may be as shown in Table 50.

[0516] Table 50

[0517]

[0518] S627: MF network element 1206 sends a media negotiation request 6 to terminal 1202 based on the address information of terminal 1202. Correspondingly, terminal 1202 receives the media negotiation request 6 from MF network element 1206.

[0519] For example, the content of media negotiation request 6 may be as shown in Table 51.

[0520] Table 51

[0521]

[0522]

[0523] S628: Terminal 1202 sends a Media Negotiation Response 6 to MF network element 1206 based on the fourth address information. Correspondingly, MF network element 1206 receives the Media Negotiation Response 6 from terminal 1202.

[0524] One possible implementation is that after the terminal 1202 recognizes that the bearer between the terminal 1202 and the access network and the core network has been successfully established, it sends a media negotiation response 6 to the MF network element 1206 according to the fourth address information to update the resource reservation status of the terminal 1202.

[0525] For example, the content included in Media Negotiation Response 6 can be as shown in Table 52. The attribute line “a=des:qosmandatory remote sendrecv” indicates that terminal 1202 supports resource reservation.

[0526] Table 52

[0527]

[0528] S629: MF network element 1206 sends a media negotiation response 5 to MF network element 1205 based on the second address information. Correspondingly, MF network element 1205 receives the media negotiation response 5 from MF network element 1206.

[0529] For example, the content of media negotiation response 5 may be as shown in Table 53.

[0530] Table 53

[0531]

[0532]

[0533] S630: MF network element 1205 sends a media negotiation response 4 to terminal 1201 based on the address information of terminal 1201. Correspondingly, terminal 1201 receives the media negotiation response 4 from MF network element 1205.

[0534] For example, the content of media negotiation response 4 may be as shown in Table 54.

[0535] Table 54

[0536]

[0537] S631: Terminal 1201, MF network element 1205, MF network element 1206 and terminal 1202 transmit frequency media streams based on media negotiation results.

[0538] One possible implementation is that after terminal 1202 rings and is picked up, the user of terminal 1201 and the user of terminal 1202 can make a voice call or a video call. The media stream is transmitted between terminal 1201, MF network element 1205, MF network element 1206 and terminal 1202 based on the media negotiation result.

[0539] based on Figure 6 The method shown allows terminal 1201, USF network element 1203, USF network element 1204, and terminal 1202 to create a first session. During the creation of the first session, media negotiation is not performed; instead, the address information required for media negotiation is carried to each device. Subsequently, terminal 1201, MF network element 1205, MF network element 1206, and terminal 1202 can perform media negotiation based on the corresponding address information. This method separates session creation from media negotiation. Furthermore, after USF network element 1203 detects the successful establishment of the first session, it can subscribe to the media negotiation status or resource reservation status from MF network element 1205. This allows MF network element 1205 to send first information to USF network element 1203 when it detects that media negotiation is complete or that resource reservation is required, thereby triggering resource reservation. Similarly, after USF network element 1204 detects the successful establishment of the first session, it can subscribe to the media negotiation status or resource reservation status from MF network element 1206. This allows MF network element 1206 to send a first message to USF network element 1204 to trigger resource reservation when it detects that media negotiation is complete or that resource reservation is required. Through this method, a resource reservation mechanism can be applied in scenarios where the session creation process and media negotiation process are separated, reserving resources for terminals 1201 and 1202 to improve the call success rate of the first session.

[0540] Understandably, the actions of MF network element 1205, USF network element 1203, MF network element 1206, or USF network element 1204 in the above steps can be performed by... Figure 3 The processor 301 in the communication device 30 shown calls the application code stored in the memory 303 to execute it, and this application does not impose any restrictions on this.

[0541] Understandable, except Figure 1A and Figure 1B In addition to the network architecture shown, the communication method provided in this application can also be applied to other network architectures, such as... Figure 1C The network architecture shown is illustrated. The communication method provided in this application is applied to... Figure 1C The network architecture shown is similar to that applied to Figure 1A The network architecture shown and Figure 1BThe network architecture shown is similar. For example, when P-CSCF element 1405 detects the establishment of a first session, it sends a second message to IMS-AGW 1407 to subscribe to the media negotiation state or resource reservation state of the first session. When IMS-AGW 1407 detects that the media negotiation of the first session has been completed, it sends a first message to P-CSCF element 1405 to indicate that the media negotiation of the first session is completed at IMS-AGW 1407, or to indicate that resources are reserved for the first session. After receiving the first message, P-CSCF element 1405 sends a first request to PCF / PCRF element 1409 to request resource reservation for the first session. After receiving the first request, PCF / PCRF element 1409 can establish a bearer with the access network and / or with the core network for terminal 1401. Similarly, upon sensing the establishment of the first session, USF network element 1406 sends a second message to MF network element 1408 to subscribe to the media negotiation state or resource reservation state of the first session. Upon sensing the completion of media negotiation for the first session, MF network element 1408 sends a first message to USF network element 1406, instructing that media negotiation for the first session be completed at MF network element 1408, or instructing that resources be reserved for the first session. After receiving the first message, USF network element 1406 sends a first request to PCF / PCRF network element 1410, requesting resource reservation for the first session. Upon receiving the first request, PCF / PCRF network element 1410 can establish a bearer with the access network and / or with the core network for terminal 1402.

[0542] for Figure 1C The network architecture shown indicates that the first session is between terminals 1401 and 1402, used to transmit media streams between them. Terminals 1401 and 1402 can be understood as the endpoints of the first session. In addition to terminals 1401 and 1402, the first session also passes through IMS-AGW 1407 and MF network element 1408.

[0543] Understandable, Figures 4-6 In the method shown, the entity requesting resource reservation for the first session from the policy control entity is the control function entity. However, in practical applications, the entity requesting resource reservation for the first session from the policy control entity could also be the media function entity. This will be explained in detail below.

[0544] like Figure 7 As shown, this application provides another communication method that can be applied to a call process between a first terminal and a second terminal. For example, the process of the first terminal calling the second terminal, or the process of the second terminal calling the first terminal. Figure 1ATaking the IMS network 10 shown as an example, the first terminal is terminal 1001, and the second terminal is terminal 1002; Figure 1B Taking the real-time communication network 12 shown as an example, the first terminal is terminal 1201, and the second terminal is terminal 1202; Figure 1C Taking the hybrid network 14 shown as an example, the first terminal is terminal 1401, and the second terminal is terminal 1402. This communication method may include the following steps:

[0545] S701: The media function entity receives or sends the first media information.

[0546] Among them, the aforementioned media functional entities can be Figure 2 Media function entity 202 in the communication system 20 shown. Figure 7 In the method shown, the media function entity can be located in the same communication network as the first terminal; or the media function entity can be located in the same communication network as the second terminal. For example, the media function entity and the first terminal are located in the calling network; or the media function entity and the second terminal are located in the called network; or the media function entity and the first terminal are located in the called network; or the media function entity and the second terminal are located in the calling network.

[0547] exist Figure 7 In the method shown, the first media information is the media information negotiated by the media function entity for the first session. The first media information is used by the media function entity to send or receive media streams. For example, the first media information is the SDP Answer 1 received by the media function entity after sending SDP Offer 1 to another media function entity. Or, for example, before S701, the media function entity receives SDP Offer 2 from another media function entity, and the first media information is the SDP Answer 2 sent by that media function entity to the other media function entity based on SDP Offer 2. In other words, the first media information is received by the media function entity from or sent to other media function entities; that is, the media function entity has completed the media negotiation for the first session. A description of the first session can be found above. Figure 4 The corresponding description in the method shown.

[0548] S702: The media function entity sends a first request to the policy control entity based on the first media information. Accordingly, the policy control entity receives the first request from the media function entity.

[0549] In this application, the aforementioned policy control entity can be Figure 2 The policy control entity 203 in the communication system 20 shown. The first request is used to request that resources be reserved for the first session.

[0550] One possible implementation is that, if the first media information indicates that the media information negotiation of the first session is successful (e.g., the first media information includes audio and video port information and codec format information responded by other media function entities), and the first terminal and the second terminal support resource reservation functions (e.g., the first media information includes attribute lines “a=des:qosmandatory local sendrecv” and “a=des:qos mandatory remote sendrecv”), the media function entity sends a first request to the policy control entity.

[0551] One possible design involves the first request carrying second media information. This second media information is determined based on at least one of the first media information or a third media information. The third media information is the proposed media information during media negotiation for the first session, and the first media information is the media information responded to based on the third media information. For example, the third media information could be the aforementioned SDP Offer 1, and the first media information could be the aforementioned SDP Answer 1. Another example is the aforementioned SDP Offer 2, and the first media information could be the aforementioned SDP Answer 2.

[0552] For example, the aforementioned second media information includes all or part of the information in the first media information, and / or all or part of the information in the third media information. For instance, the second media information may include IP address information from the first media information, and / or port information from the first media information, and / or information about the media type (e.g., audio or video media) from the first media information, and / or bandwidth information (e.g., negotiated maximum and / or minimum bandwidth) from the first media information, and / or IP address information from the second media information, and / or port information from the second media information.

[0553] Understandably, upon receiving the first request, the policy control entity can trigger the establishment of a bearer for either the first or second terminal. For example, if the media function entity and the first terminal are located in the same communication network, such as the calling or called network, the policy control entity, based on the first request, triggers the establishment of a dedicated bearer for the first terminal with the access network and / or with the core network. Subsequently, the first terminal can send or receive media streams through this dedicated bearer during a call with the second terminal. Similarly, if the media function entity and the second terminal are located in the same communication network, such as the calling or called network, the policy control entity, based on the first request, triggers the establishment of a dedicated bearer for the second terminal with the access network and / or with the core network. Subsequently, the second terminal can send or receive media streams through this dedicated bearer during a call with the first terminal.

[0554] Optionally, the policy control entity sends a response to the first request to the media function entity, and the media function entity receives a response to the first request from the policy function entity. The response to the first request indicates whether resource reservation for the first session has been completed. Optionally, the response to the first request may also indicate the wireless access technology used by the first or second terminal, such as 5G or 4G.

[0555] For example, the first request is AAR, and the response to the first request is AAA. Alternatively, the first request is a policy authorization request (e.g., PolicyAuthorization_Create), and the response to the first request is a policy authorization response. Of course, the first request and its response can also be other messages; there are no restrictions.

[0556] based on Figure 7 The method shown allows the media function entity to request the policy control entity to reserve resources for the first session after completing media negotiation, thereby improving the call success rate of the first session.

[0557] Understandably, the actions of the media function entities in the above steps can be performed by... Figure 3 The processor 301 in the communication device 30 shown calls the application code stored in the memory 303 to execute it, and this application does not impose any restrictions on this.

[0558] To better understand the communication method provided in this application, the following will be combined with... Figure 1A The IMS network 10 shown and Figure 1B The real-time communication network 12 shown illustrates the communication method provided in this application.

[0559] First of all, with Figure 1A The method provided in this application is illustrated using the IMS network 10 shown as an example.

[0560] like Figure 8 The diagram illustrates another communication method provided in this application, which can be applied to a call process between terminal 1001 and terminal 1002. This communication method may include the following steps:

[0561] S801: Terminal 1001 sends a first invitation request to P-CSCF network element 1005. Correspondingly, P-CSCF network element 1005 receives the first invitation request from terminal 1001.

[0562] S802: P-CSCF network element 1005 sends a first session creation request to IMS-AGW 1006. Correspondingly, IMS-AGW 1006 receives the first session creation request from P-CSCF network element 1005.

[0563] S803: IMS-AGW 1006 sends a first session creation response to P-CSCF network element 1005. Correspondingly, P-CSCF network element 1005 receives the first session creation response from IMS-AGW 1006.

[0564] S804: P-CSCF element 1005 sends a second invitation request to P-CSCF element 1009. Correspondingly, P-CSCF element 1009 receives the second invitation request from P-CSCF element 1005.

[0565] S805: P-CSCF network element 1009 sends a second session creation request to IMS-AGW 1010. Correspondingly, IMS-AGW 1010 receives the second session creation request from P-CSCF network element 1009.

[0566] S806: IMS-AGW 1010 sends a second session creation response to P-CSCF network element 1009. Correspondingly, P-CSCF network element 1009 receives the second session creation response from IMS-AGW 1010.

[0567] S807: P-CSCF network element 1009 sends a third invitation request to terminal 1002. Correspondingly, terminal 1002 receives the third invitation request from P-CSCF network element 1009.

[0568] S808: Terminal 1002 sends a response (e.g., message 183) to P-CSCF network element 1009 regarding the third invitation request. Correspondingly, P-CSCF network element 1009 receives the response from terminal 1002 to the third invitation request.

[0569] S809: P-CSCF network element 1009 sends a first session update request to IMS-AGW 1010. Correspondingly, IMS-AGW 1010 receives the first session update request from P-CSCF network element 1009.

[0570] S810: P-CSCF element 1009 sends a response (e.g., message 183) to P-CSCF element 1005 to the second invitation request. Correspondingly, P-CSCF element 1005 receives the response from P-CSCF element 1009 to the second invitation request.

[0571] S811: P-CSCF network element 1005 sends a second session update request to IMS-AGW 1006. Correspondingly, IMS-AGW 1006 receives the second session update request from P-CSCF network element 1005.

[0572] S812: The P-CSCF network element 1005 sends a response (such as message 183) to the terminal 1001 to the first invitation request. Correspondingly, the terminal 1001 receives the response from the P-CSCF network element 1005 to the first invitation request.

[0573] The specific processes of S801 to S812 are similar to those of S501 to S512, and can be referred to the descriptions in S501 to S512, which will not be repeated here.

[0574] S813: Terminal 1001 sends a Media Negotiation Request 1 to IMS-AGW 1006 based on the first address information. Correspondingly, IMS-AGW 1006 receives the Media Negotiation Request 1 from Terminal 1001.

[0575] S814: IMS-AGW 1006 sends Media Negotiation Request 2 to IMS-AGW 1010 based on the third address information. Correspondingly, IMS-AGW 1010 receives Media Negotiation Request 2 from IMS-AGW 1006.

[0576] S815: IMS-AGW 1010 sends a media negotiation request 3 to terminal 1002 based on the address information of terminal 1002. Correspondingly, terminal 1002 receives the media negotiation request 3 from IMS-AGW 1010.

[0577] S816: Terminal 1002 sends a Media Negotiation Response 3 to IMS-AGW 1010 based on the fourth address information. Correspondingly, IMS-AGW 1010 receives the Media Negotiation Response 3 from Terminal 1002.

[0578] S817: IMS-AGW 1010 sends Media Negotiation Response 2 to IMS-AGW 1006 based on the second address information. Correspondingly, IMS-AGW 1006 receives Media Negotiation Response 2 from IMS-AGW 1010.

[0579] S818: IMS-AGW 1006 sends Media Negotiation Response 1 to Terminal 1001 based on the address information of Terminal 1001. Correspondingly, Terminal 1001 receives Media Negotiation Response 1 from IMS-AGW 1006.

[0580] The specific processes of S813 to S818 are similar to those of S513 to S520. Please refer to the descriptions in S513 to S520 above, and they will not be repeated here.

[0581] S819: IMS-AGW 1010 sends a first request to PCF / PCRF network element 1012. Correspondingly, PCF / PCRF network element 1012 receives the first request from IMS-AGW 1010.

[0582] For example, in S819, the first request may carry all or part of the information from the third SDP Offer (such as IP address and port number) and all or part of the information from the third SDP Answer (such as IP address, port number, media type information, or bandwidth information). The third SDP Offer and... Figure 7 The method shown corresponds to SDP Offer 1, and the third SDP Answer corresponds to... Figure 7 This corresponds to SDP Answer 1 in the method shown.

[0583] Understandably, after receiving the first request, PCF / PCRF network element 1012 can establish a bearer with the access network and / or with the core network for terminal 1002. This bearer can be a dedicated bearer for terminal 1002. Terminal 1002 can send or receive media streams through this dedicated bearer during subsequent calls.

[0584] Optionally, the PCF / PCRF network element 1012 sends a response to the first request to the IMS-AGW 1010 to indicate whether the resource reservation for the first session has been completed.

[0585] S820: IMS-AGW 1006 sends a first request to PCF / PCRF network element 1011. Correspondingly, IMS-AGW 1006 receives a first request from P-CSCF network element 1005.

[0586] For example, in S820, the first request may carry all or part of the information from the first SDP Offer (such as IP address and port number) and all or part of the information from the first SDP Answer (such as IP address, port number, media type information, or bandwidth information). The first SDP Offer and... Figure 7 The method shown corresponds to SDP Offer 2, the first SDP Answer and Figure 7 This corresponds to SDP Answer 2 in the method shown.

[0587] Understandably, after receiving the first request, PCF / PCRF network element 1011 can establish a bearer with the access network and / or with the core network for terminal 1001. This bearer can be a dedicated bearer for terminal 1001. Terminal 1001 can then send or receive media streams through this dedicated bearer during subsequent calls.

[0588] Optionally, the PCF / PCRF network element 1011 sends a response to the first request to the IMS-AGW 1006 to indicate whether the resource reservation for the first session has been completed.

[0589] Understandably, the specific processes of S819 and S820 are similar to those described above. Figure 7 The process in S702 of the method shown is similar; please refer to the corresponding description in S702 above. Furthermore, Figure 8 The diagram is drawn based on the assumption that S819 and S820 execute after S818. However, in specific applications, IMS-AGW 1010 and IMS-AGW 1006 can send the first request to request resource reservation once they detect that media negotiation is complete. For example, S819 can execute after S816, and S820 can execute after S817.

[0590] S821: Terminal 1001 sends a media negotiation request 4 to IMS-AGW 1006 based on the first address information. Correspondingly, IMS-AGW 1006 receives the media negotiation request 4 from terminal 1001.

[0591] S822: IMS-AGW 1006 sends a media negotiation request 5 to IMS-AGW 1010 based on the third address information. Correspondingly, IMS-AGW 1010 receives the media negotiation request 5 from IMS-AGW 1006.

[0592] S823: IMS-AGW 1010 sends a media negotiation request 6 to terminal 1002 based on the address information of terminal 1002. Correspondingly, terminal 1002 receives the media negotiation request 6 from IMS-AGW 1010.

[0593] S824: Terminal 1002 sends a media negotiation response 6 to IMS-AGW 1010 based on the fourth address information. Correspondingly, IMS-AGW 1010 receives the media negotiation response 6 from terminal 1002.

[0594] S825: IMS-AGW 1010 sends Media Negotiation Response 5 to IMS-AGW 1006 based on the second address information. Correspondingly, IMS-AGW 1006 receives Media Negotiation Response 5 from IMS-AGW 1010.

[0595] S826: IMS-AGW 1006 sends a media negotiation response 4 to terminal 1001 based on the address information of terminal 1001. Correspondingly, terminal 1001 receives the media negotiation response 4 from IMS-AGW 1006.

[0596] S827: Terminal 1001, IMS-AGW 1006, IMS-AGW 1010 and terminal 1002 transmit media streams based on media negotiation results.

[0597] The specific processes of S821 to S827 are similar to those of S525 to S531. Please refer to the descriptions in S525 to S531 above, and they will not be repeated here.

[0598] based on Figure 8 The method shown allows terminal 1001, P-CSCF network element 1005, P-CSCF network element 1009, and terminal 1002 to create a first session. During the creation of the first session, media negotiation is not performed; instead, the address information required for media negotiation is carried to each device. Subsequently, terminal 1001, IMS-AGW 1006, IMS-AGW 1010, and terminal 1002 can perform media negotiation based on the corresponding address information. This method separates session creation from media negotiation. Furthermore, IMS-AGW 1006 can request resource reservation when it detects that media negotiation is complete and resources need to be reserved. Similarly, IMS-AGW 1010 can request resource reservation when it detects that media negotiation is complete and resources need to be reserved. This method allows for the application of a resource reservation mechanism in scenarios where the session creation process is separated from the media negotiation process, reserving resources for terminal 1001 and terminal 1002 to improve the call success rate of the first session.

[0599] Understandably, the actions of IMS-AGW 1006, P-CSCF network element 1005, IMS-AGW 1010, or P-CSCF network element 1009 in the above steps can be performed by... Figure 3 The processor 301 in the communication device 30 shown calls the application code stored in the memory 303 to execute it, and this application does not impose any restrictions on this.

[0600] The following is based on Figure 1B The method provided in this application is illustrated using the real-time communication network 12 shown as an example.

[0601] like Figure 9 The diagram illustrates another communication method provided in this application, which can be applied to a call process between terminal 1201 and terminal 1202. This communication method may include the following steps:

[0602] S901: Terminal 1201 sends a first session connection request to USF network element 1203. Correspondingly, USF network element 1203 receives the first session connection request from terminal 1201.

[0603] S902: USF element 1203 sends a first session creation request to MF element 1205. Correspondingly, MF element 1205 receives the first session creation request from USF element 1203.

[0604] S903: MF network element 1205 sends a first session creation response (SessionCreateResponse) to USF network element 1203. Correspondingly, USF network element 1203 receives the first session creation response from MF network element 1205.

[0605] S904: USF network element 1203 sends a second session connection request to USF network element 1204. Correspondingly, USF network element 1204 receives the second session connection request from USF network element 1203.

[0606] S905: USF network element 1204 sends a second session creation request to MF network element 1206. Correspondingly, MF network element 1206 receives the second session creation request from USF network element 1204.

[0607] S906: MF network element 1206 sends a second session creation response to USF network element 1204. Correspondingly, USF network element 1204 receives the second session creation response from MF network element 1206.

[0608] S907: USF network element 1204 sends a third session connection request to terminal 1202. Correspondingly, terminal 1202 receives the third session connection request from USF network element 1204.

[0609] S908: Terminal 1202 sends a third session connection response (SessionConnectResponse) to USF network element 1204. Correspondingly, USF network element 1204 receives the third session connection response from terminal 1202.

[0610] S909: USF element 1204 sends a first session update request to MF element 1206. Correspondingly, MF element 1206 receives the first session update request from USF element 1204.

[0611] S910: USF network element 1204 sends a second session connection response to USF network element 1203. Correspondingly, USF network element 1203 receives the second session connection response from USF network element 1204.

[0612] Understandably, this application does not restrict the execution order of S609 and S610. For example, S609 can be executed first and then S610, or S610 can be executed first and then S609, or S609 and S610 can be executed simultaneously.

[0613] S911: USF network element 1203 sends a second session update request to MF network element 1205. Correspondingly, MF network element 1205 receives the second session update request from USF network element 1203.

[0614] S912: USF network element 1203 sends a first session connection response to terminal 1201. Correspondingly, terminal 1201 receives the first session connection response from USF network element 1203.

[0615] The specific processes of S901 to S912 are similar to those of S601 to S612, and can be referred to the descriptions in S601 to S612, which will not be repeated here.

[0616] S913: Terminal 1201 sends a Media Negotiation Request 1 to MF network element 1205 based on the first address information. Correspondingly, MF network element 1205 receives the Media Negotiation Request 1 from terminal 1201.

[0617] S914: MF network element 1205 sends a media negotiation request 2 to MF network element 1206 based on the third address information. Correspondingly, MF network element 1206 receives the media negotiation request 2 from MF network element 1205.

[0618] S915: MF network element 1206 sends a media negotiation request 3 to terminal 1202 based on the address information of terminal 1202. Correspondingly, terminal 1202 receives the media negotiation request 3 from MF network element 1206.

[0619] S916: Terminal 1202 sends a Media Negotiation Response 3 to MF network element 1206 based on the fourth address information. Correspondingly, MF network element 1206 receives the Media Negotiation Response 3 from terminal 1202.

[0620] S917: MF network element 1206 sends media negotiation response 2 to MF network element 1205 based on the second address information. Correspondingly, MF network element 1205 receives media negotiation response 2 from MF network element 1206.

[0621] S918: MF network element 1205 sends Media Negotiation Response 1 to terminal 1201 based on the address information of terminal 1201. Correspondingly, terminal 1201 receives Media Negotiation Response 1 from MF network element 1205.

[0622] The specific processes of S913 to S918 are similar to those of S613 to S620. Please refer to the descriptions in S613 to S620 above, and they will not be repeated here.

[0623] S919: MF network element 1206 sends a first request to PCF / PCRF network element 1208. Correspondingly, PCF / PCRF network element 1208 receives the first request from MF network element 1206.

[0624] For example, in S919, the first request may carry all or part of the information from the third SDP Offer (such as IP address and port number) and all or part of the information from the third SDP Answer (such as IP address, port number, media type information, or bandwidth information). The third SDP Offer and... Figure 7 The method shown corresponds to SDP Offer 1, and the third SDP Answer corresponds to... Figure 7 This corresponds to SDP Answer 1 in the method shown.

[0625] Understandably, after receiving the first request, PCF / PCRF network element 1208 can establish a bearer with the access network and / or with the core network for terminal 1202. This bearer can be a dedicated bearer for terminal 1202. Terminal 1202 can send or receive media streams through this dedicated bearer during subsequent calls.

[0626] Optionally, PCF / PCRF network element 1208 sends a response to the first request to MF network element 1206 to indicate whether the resource reservation for the first session has been completed.

[0627] S920: MF network element 1205 sends a first request to PCF / PCRF network element 1207. Correspondingly, PCF / PCRF network element 1207 receives the first request from USF network element 1203.

[0628] For example, in S920, the first request may carry all or part of the information from the first SDP Offer (such as IP address and port number) and all or part of the information from the first SDP Answer (such as IP address, port number, media type information, or bandwidth information). The first SDP Offer and... Figure 7 The method shown corresponds to SDP Offer 2, the first SDP Answer and Figure 7 This corresponds to SDP Answer 2 in the method shown.

[0629] Understandably, after receiving the first request, PCF / PCRF network element 1207 can establish a bearer with the access network and / or with the core network for terminal 1201. This bearer can be a dedicated bearer for terminal 1201. Terminal 1201 can send or receive media streams through this dedicated bearer during subsequent calls.

[0630] Optionally, PCF / PCRF network element 1207 sends a response to the first request to MF network element 1205 to indicate whether the resource reservation for the first session has been completed.

[0631] Understandably, the specific processes of the S919 and S920 are similar to those described above. Figure 7 The process in S702 of the method shown is similar; please refer to the corresponding description in S702 above. Furthermore, Figure 9 The diagram is based on the assumption that S919 and S920 execute after S918. However, in practical applications, MF network elements 1205 and 1206 can send the first request to request resource reservation once they detect the completion of media negotiation. For example, S919 can execute after S916, and S920 can execute after S917.

[0632] S921: Terminal 1201 sends a media negotiation request 4 to MF network element 1205 based on the first address information. Correspondingly, MF network element 1205 receives the media negotiation request 4 from terminal 1201.

[0633] S922: MF network element 1205 sends a media negotiation request 5 to MF network element 1206 based on the third address information. Correspondingly, MF network element 1206 receives the media negotiation request 5 from MF network element 1205.

[0634] S923: MF network element 1206 sends a media negotiation request 6 to terminal 1202 based on the address information of terminal 1202. Correspondingly, terminal 1202 receives the media negotiation request 6 from MF network element 1206.

[0635] S924: Terminal 1202 sends a Media Negotiation Response 6 to MF network element 1206 based on the fourth address information. Correspondingly, MF network element 1206 receives the Media Negotiation Response 6 from terminal 1202.

[0636] S925: MF network element 1206 sends a media negotiation response 5 to MF network element 1205 based on the second address information. Correspondingly, MF network element 1205 receives the media negotiation response 5 from MF network element 1206.

[0637] S926: MF network element 1205 sends a media negotiation response 4 to terminal 1201 based on the address information of terminal 1201. Correspondingly, terminal 1201 receives the media negotiation response 4 from MF network element 1205.

[0638] S927: Terminal 1201, MF network element 1205, MF network element 1206 and terminal 1202 transmit frequency media streams based on media negotiation results.

[0639] The specific processes of S921 to S927 are similar to those of S625 to S631. Please refer to the descriptions in S625 to S631 above, and they will not be repeated here.

[0640] based on Figure 9 The method shown allows terminal 1201, USF network element 1203, USF network element 1204, and terminal 1202 to create a first session. During the creation of the first session, media negotiation is not performed; instead, the address information required for media negotiation is carried to each device. Subsequently, terminal 1201, MF network element 1205, MF network element 1206, and terminal 1202 can perform media negotiation based on the corresponding address information. This method separates session creation from media negotiation. Furthermore, MF network element 1205 can request resource reservation when it detects that media negotiation is complete and resources need to be reserved. Similarly, MF network element 1206 can request resource reservation when it detects that media negotiation is complete and resources need to be reserved. This method allows for the application of a resource reservation mechanism in scenarios where the session creation process is separated from the media negotiation process, reserving resources for terminal 1201 and terminal 1202 to improve the call success rate of the first session.

[0641] Understandably, the actions of MF network element 1205, USF network element 1203, MF network element 1206, or USF network element 1204 in the above steps can be performed by... Figure 3 The processor 301 in the communication device 30 shown calls the application code stored in the memory 303 to execute it, and this application does not impose any restrictions on this.

[0642] Understandable, except Figure 1A and Figure 1B In addition to the network architecture shown, Figure 7 The communication method shown can also be applied to other network architectures, such as Figure 1C The network architecture is shown. Figure 7 The communication method shown is applied to Figure 1C The network architecture shown is similar to that applied to Figure 1A The network architecture shown and Figure 1BThe network architecture shown is similar. For example, after sensing the completion of media negotiation for the first session, IMS-AGW 1407 sends a first request to PCF / PCRF network element 1409, requesting to reserve resources for the first session. Upon receiving the first request, PCF / PCRF network element 1409 can establish a bearer with the access network and / or with the core network for terminal 1401. Similarly, after sensing the completion of media negotiation for the first session, MF network element 1408 sends a first request to PCF / PCRF network element 1410, requesting to reserve resources for the first session. Upon receiving the first request, PCF / PCRF network element 1410 can establish a bearer with the access network and / or with the core network for terminal 1402.

[0643] for Figure 1C The network architecture shown indicates that the first session is between terminals 1401 and 1402, used to transmit media streams between them. Terminals 1401 and 1402 can be understood as the endpoints of the first session. In addition to terminals 1401 and 1402, the first session also passes through IMS-AGW 1407 and MF network element 1408.

[0644] The various embodiments mentioned above in this application can be combined without contradiction, and no limitation is imposed.

[0645] The above mainly describes the solution provided in this application from the perspective of interaction between various network elements. Correspondingly, this application also provides a communication device, which can be a control function entity in the above method embodiments, or a device containing the above control function entity, or a component that can be used for the control function entity; or, the communication device can be a media function entity in the above method embodiments, or a device containing the above media function entity, or a component that can be used for the media function entity. It is understood that, in order to implement the above functions, the above control function entity or media function entity includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the unit and algorithm operations of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0646] This application can divide the control function entity or media function entity into functional modules based on the above method examples. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It is understood that the module division in this application is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0647] For example, when dividing the functional modules using an integrated approach. Figure 10 A schematic diagram of a communication device 100 is shown. The communication device 100 includes an interface module 101 and a processing module 102. The interface module 101, also known as an interface unit, is used to perform transmit and receive operations, and may be, for example, an interface circuit, a transceiver, a transceiver unit, or a communication interface. The processing module 102, also known as a processing unit, is used to perform operations other than transmit and receive operations, and may be, for example, a processing circuit or a processor.

[0648] In some embodiments, the communication device 100 may further include a storage module. Figure 10 (Not shown in the image) is used to store program instructions and data.

[0649] For example, the communication device 100 is used to implement the functions of the control function entity. The communication device 100 is, for example, a... Figure 4 The control function entity described in the illustrated embodiment.

[0650] The interface module 101 is used to receive first information from the media function entity. For example, the interface module 101 can be used to execute S401.

[0651] The processing module 102 is used to control the interface module 101 to send a first request to the policy control entity based on the first information. For example, the processing module 102 can be used to execute S402.

[0652] When used to implement the functions of a control function entity, other functions that the communication device 100 can implement can be referred to. Figure 4 The relevant descriptions of the embodiments shown will not be elaborated upon further.

[0653] Alternatively, by way of example, the communication device 100 is used to implement the functions of a media function entity. The communication device 100 is, for example, a... Figure 4 The media function entity described in the illustrated embodiment.

[0654] The interface module 101 is used to receive or send first media information.

[0655] The processing module 102 is used to control the interface module 101 to send first information to the control function entity based on the first media information. For example, the processing module 102 can be used to execute S401.

[0656] When used to implement the functions of a media function entity, other functions that the communication device 100 can implement can be referred to. Figure 4 The relevant descriptions of the embodiments shown will not be elaborated upon further.

[0657] Alternatively, by way of example, the communication device 100 is used to implement the functions of a media function entity. The communication device 100 is, for example, a... Figure 7 The media function entity described in the illustrated embodiment.

[0658] The processing module 102 is used to receive or send first media information. For example, the interface module 101 can be used to execute S701.

[0659] The processing module 102 is used to control the interface module 101 to send a first request to the policy control entity based on the first media information. For example, the processing module 102 can be used to execute S702.

[0660] When used to implement the functions of a media function entity, other functions that the communication device 100 can implement can be referred to. Figure 7 The relevant descriptions of the embodiments shown will not be elaborated upon further.

[0661] In a simplified embodiment, those skilled in the art will recognize that the communication device 100 can employ... Figure 3 The form shown. For example, Figure 3 The processor 301 can call computer execution instructions stored in the memory 303 to cause the communication device 100 to execute the method described in the above embodiments.

[0662] For example, Figure 10 The functions / implementation processes of interface module 101 and processing module 102 can be accessed through... Figure 3 The processor 301 in the memory calls computer execution instructions stored in the memory 303 to implement the function. Alternatively, Figure 10 The function / implementation process of the processing module 102 can be achieved through... Figure 3 The processor 301 in the memory calls computer execution instructions stored in the memory 303 to implement this. Figure 10 The function / implementation process of interface module 101 can be accessed through... Figure 3 It is implemented using the communication interface 304.

[0663] It is understood that one or more of the above modules or units can be implemented by software, hardware, or a combination of both. When any of the above modules or units are implemented by software, the software exists as computer program instructions and is stored in memory. The processor can be used to execute the program instructions and implement the above method flow. The processor can be built into a system-on-a-chip (SoC) or ASIC, or it can be a separate semiconductor chip. In addition to the core that executes the software instructions for computation or processing, the processor may further include necessary hardware accelerators, such as field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), or logic circuits that implement dedicated logic operations.

[0664] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, SoC, FPGA, PLD, application-specific digital circuit, hardware accelerator, or non-integrated discrete device, which can run the necessary software or perform the above method flow independently of software.

[0665] Optionally, this application also provides a chip system, including: at least one processor and an interface, wherein the at least one processor is coupled to a memory via the interface, and when the at least one processor executes a computer program or instructions in the memory, the method in any of the above method embodiments is executed. In one possible implementation, the chip system further includes a memory. Optionally, the chip system may be composed of chips or may include chips and other discrete devices; this application does not specifically limit this.

[0666] Optionally, this application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be implemented by a computer program instructing related hardware. This program can be stored in the aforementioned computer-readable storage medium. When executed, the program can include the processes described in the above method embodiments. The computer-readable storage medium can be an internal storage unit of the communication device in any of the foregoing embodiments, such as the hard disk or memory of the communication device. The aforementioned computer-readable storage medium can also be an external storage device of the communication device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the communication device. Further, the aforementioned computer-readable storage medium can include both internal storage units and external storage devices of the communication device. The aforementioned computer-readable storage medium is used to store the aforementioned computer program and other programs and data required by the aforementioned communication device. The aforementioned computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0667] Optionally, this application also provides a computer program product. All or part of the processes in the above method embodiments can be executed by a computer program instructing related hardware. This program can be stored in the above computer program product, and when executed, it can include the processes described in the above method embodiments.

[0668] Optionally, this application also provides computer instructions. All or part of the processes in the above method embodiments can be executed by computer instructions instructing related hardware (such as a computer, processor, control function entity, or media function entity). The program can be stored in the aforementioned computer-readable storage medium or the aforementioned computer program product.

[0669] Optionally, this application also provides a communication system, including: Figure 4 The control function entity and / or media function entity in the method shown.

[0670] Optionally, this application also provides a communication system, including: Figure 7 The strategy control entity and / or media function entity in the method shown.

[0671] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0672] It is understood that "communication connection" in this application can be a direct connection or an indirect connection; furthermore, it can refer to an electrical connection. For example, the connection of two electrical components A and B can refer to a direct connection between A and B, or an indirect connection between A and B through other electrical components or connection media, enabling the transmission of electrical signals between A and B; similarly, the connection of two devices A and B can refer to a direct connection between A and B, or an indirect connection between A and B through other communication devices or communication media, enabling communication between A and B.

[0673] It is understood that the message names between various network elements or the names of various parameters in the messages in the above embodiments of this application are just examples, and other names may be used in the specific implementation. This application does not make any specific limitations on this.

[0674] It is understood that in this application, " / " can indicate that the objects before and after it are in an "or" relationship. For example, A / B can mean A or B. "And / or" can be used to describe three relationships between the related objects. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. Here, A and B can be singular or plural. Furthermore, expressions like "at least one of A, B, and C" or "at least one of A, B, or C" are generally used to indicate any of the following: A exists alone; B exists alone; C exists alone; A and B exist simultaneously; A and C exist simultaneously; B and C exist simultaneously; A, B, and C exist simultaneously. The above examples using three elements (A, B, and C) illustrate the optional entries for this item. When the expression contains more elements, its meaning can be obtained according to the aforementioned rules.

[0675] To facilitate the description of the technical solutions of this application, the terms "first" and "second" may be used to distinguish technical features with the same or similar functions. The terms "first" and "second" do not limit the number or execution order, nor do they imply that they are necessarily different. In this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" or "for example" should not be construed as being more preferred or advantageous than other embodiments or design schemes. The use of "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner for ease of understanding.

[0676] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of this application, the sequence number of each process does not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of this application.

[0677] It is understood that in this application, "when," "under the circumstances," "if," and "if" all refer to the corresponding processing that will be carried out under certain objective circumstances, and are not time-limited, nor do they require that there must be a judgment action when implemented, nor do they imply any other limitations.

[0678] In this application, "simultaneously" can be understood as at the same point in time, within a period of time, or within the same cycle.

[0679] It is understood that some optional features in this application can be implemented independently in certain scenarios without relying on other features, such as the current solution upon which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus provided in this application can also implement these features or functions, which will not be elaborated here.

[0680] It is understood that the same step or step with the same function or technical feature in this application can be referenced and learned from each other in different embodiments.

[0681] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0682] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0683] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0684] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, Applied to a control function entity, the method includes: Receive first information from a media function entity, the first information indicating that media negotiation of the first session is completed at the media function entity, or the first information indicating that resources are reserved for the first session, the first session is a session between a first terminal and a second terminal, the first session is used to transmit media streams between the first terminal and the second terminal, and the first session passes through the media function entity; Based on the first information, a first request is sent to the policy control entity, the first request being used to request that resources be reserved for the first session.

2. The method according to claim 1, characterized in that, The receipt of the first information from the media function entity includes: If the media negotiation of the first session is completed at the media function entity, the first information is received from the media function entity.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Send the second message to the media function entity; The first information indicates that media negotiation for the first session is completed at the media function entity, and the second information is used to subscribe to the media negotiation state of the first session; or, The first information indicates that resources are reserved for the first session, and the second information is used to subscribe to the resource reservation status of the first session.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: Receive first media information from the media function entity, the first media information being media information negotiated by the media function entity for the first session, and the first media information being used by the media function entity to send or receive media streams based on the first media information; The first request carries second media information, which is determined based on the first media information.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Receive a response to the first request from the policy control entity, the response to the first request indicating whether resource reservation for the first session has been completed; The first request is an authentication / authorization request, and the response to the first request is an authentication / authorization response; or, the first request is a policy authorization request, and the response to the first request is a policy authorization response.

6. The method according to any one of claims 1-5, characterized in that, The first terminal or the second terminal is located in the first communication network; The control function entity is deployed on the proxy call session control function network element in the first communication network, and the media function entity is deployed on the Internet Protocol Multimedia Subsystem Access Media Gateway in the first communication network; or... The control function entity is deployed on the unified session control function network element in the first communication network, and the media function entity is deployed on the media function network element in the first communication network.

7. The method according to claim 6, characterized in that, The method is applied to the call process between the first terminal and the second terminal, wherein the first communication network is either the calling network or the called network.

8. A communication method, characterized in that, Applied to media function entities, the method includes: Receive or send first media information, the first media information being media information negotiated by the media function entity for a first session, the first session being a session between a first terminal and a second terminal, the first session being used to transmit media streams between the first terminal and the second terminal, and the first session passing through the media function entity; The first information is sent to the control function entity based on the first media information, and the first information is used to trigger the reservation of resources for the first session request. The first information indicates that media negotiation for the first session is completed at the media function entity, or the first information indicates that resources are reserved for the first session.

9. The method according to claim 8, characterized in that, The method further includes: Receive second information from the control function entity; The first information indicates that media negotiation for the first session is completed at the media function entity, and the second information is used to subscribe to the media negotiation status of the first session; or, The first information indicates that resources are reserved for the first session, and the second information is used to subscribe to the resource reservation status of the first session.

10. The method according to claim 8 or 9, characterized in that, Sending the first information to the control function entity based on the first media information includes: The first media information indicates that the media information negotiation for the first session was successful; the first information indicates that the media negotiation for the first session was completed at the media function entity; or, The first media information indicates that the media information negotiation for the first session was successful, and that the first terminal and the second terminal support the resource reservation function, with the first information indicating that resources are reserved for the first session.

11. The method according to any one of claims 8-10, characterized in that, The first terminal or the second terminal is located in the first communication network; The control function entity is deployed on the proxy call session control function network element in the first communication network, and the media function entity is deployed on the Internet Protocol Multimedia Subsystem Access Media Gateway in the first communication network; or... The control function entity is deployed on the unified session control function network element in the first communication network, and the media function entity is deployed on the media function network element in the first communication network.

12. The method according to claim 11, characterized in that, The method is applied to the call process between the first terminal and the second terminal; the first communication network is either the calling network or the called network.

13. A communication method, characterized in that, Applied to media function entities, the method includes: Receive or send first media information, the first media information being media information negotiated by the media function entity for a first session, the first session being a session between a first terminal and a second terminal, the first session being used to transmit media streams between the first terminal and the second terminal, and the first session passing through the media function entity; A first request is sent to the policy control entity based on the first media information. The first request is used to request that resources be reserved for the first session.

14. The method according to claim 13, characterized in that, Sending the first request to the policy control entity based on the first media information includes: If the first media information indicates that the media information negotiation for the first session was successful, and the first terminal and the second terminal support the resource reservation function, the first request is sent to the policy control entity.

15. The method according to claim 13 or 14, characterized in that, The method further includes: Receive a response to the first request from the policy control entity, the response to the first request indicating whether resource reservation for the first session has been completed; The first request is an authentication / authorization request, and the response to the first request is an authentication / authorization response; or, the first request is a policy authorization request, and the response to the first request is a policy authorization response.

16. The method according to any one of claims 13-15, characterized in that, The first terminal or the second terminal is located in the first communication network; the media function entity is deployed on the Internet Protocol Multimedia Subsystem Access Media Gateway or on the media function network element in the first communication network.

17. The method according to claim 16, characterized in that, The method is applied to the call process between the first terminal and the second terminal, wherein the first communication network is the calling network or the called network.

18. A communication device, characterized in that, It includes a unit or module for performing the method as described in any one of claims 1 to 7, or includes a unit or module for performing the method as described in any one of claims 8 to 12, or includes a unit or module for performing the method as described in any one of claims 13 to 17.

19. A communication device, characterized in that, include: A processor coupled to a memory for storing a program or instructions that, when executed by the processor, cause the apparatus to perform the method as claimed in any one of claims 1 to 7, or the method as claimed in any one of claims 8 to 12, or the method as claimed in any one of claims 13 to 17.

20. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1 to 7, or the method as described in any one of claims 8 to 12, or the method as described in any one of claims 13 to 17.

21. A computer program product, said computer program product comprising computer program code, characterized in that, When the computer program code is run on a computer, it causes the computer to implement the method of any one of claims 1 to 7, or the method of any one of claims 8 to 12, or the method of any one of claims 13 to 17.

22. A communication system, characterized in that, include: The means for performing the method of any one of claims 1 to 7, and / or the means for performing the method of any one of claims 8 to 12.

Images