Session management method, storage medium, electronic device, computer program product

Abstract

The embodiment of the application provides a kind of session management method, storage medium, electronic device, computer program product, it is applied to NEF, the method comprises: receiving the first request sent by application function AF;First request is the request for establishing the IP multimedia subsystem (IMS) session between the first session end and the second session end, first request carries the information of first session end, the information of second session end and audio / video media information;First request is sent to IP multimedia subsystem application server (IMS) AS, to call IMS AS to establish IMS session, solve how to in the capability opening framework of IMS AS and NEF for DC, realize the unified processing of audio / video and DC Problem, avoid using additional technology or interface to process audio / video media, realize the uniformity of IMS session management.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a session management method, storage medium, electronic device, and computer program product. Background Technology

[0002] Real-time communication (RTC) based on the IP Multimedia Sub-system (IMS) provides users with real-time interaction of multimedia content, including voice and video. After the application of data channel (DC) technology to real-time communication services, in addition to audio and video interaction, users can also interact with any type of application data and media content through DC, bringing users a rich service experience.

[0003] Next Generation Real-time Communication (NG_RTC) based on the IMS network defines the capabilities open to third-party applications. The relevant interfaces are opened by the IMS Application Server (AS) and Network Exposure Function (NEF). Third-party applications (i.e., Application Functions (AF)) call these interfaces to create, update, and terminate IMS sessions.

[0004] The current capability openness only defines the openness of DC capabilities, meaning that third-party applications can only create, update, and terminate DC channels between users or between users and applications. Creating, updating, and terminating audio / video media requires other technologies, leading to additional complexity in the session establishment, updating, or termination process.

[0005] Therefore, how to implement audio / video media processing within the open framework of IMS AS and NEF for DC capabilities is a problem that needs to be solved. Summary of the Invention

[0006] This application provides a session management method, storage medium, electronic device, and computer program product to at least address the problem in related technologies of how to process audio / video media within the IMS AS and NEF capability open framework for DC.

[0007] According to one embodiment of this application, a session management method is provided, applied to the Network Open Function (NEF), comprising:

[0008] Receive a first request sent by the application function AF; the first request is a request to establish an IP Multimedia Subsystem (IMS) session between a first session client and a second session client, and the first request carries information about the first session client, information about the second session client, and audio and video media information; send the first request to the IP Multimedia Subsystem Application Server (IMS AS) to invoke the IMS AS to establish an IMS session.

[0009] According to another embodiment of this application, a session management method is provided, applied to an IP Multimedia Subsystem Application Server (IMS AS), comprising:

[0010] Receive a first request sent by the Network Open Function (NEF); the first request is a request to establish an IP Multimedia Subsystem (IMS) session between a first session client and a second session client, and the first request carries information about the first session client, information about the second session client, and audio and video media information; establish an IP Multimedia Subsystem (IMS) session based on the audio and video media information carried in the first request.

[0011] According to yet another embodiment of this application, a computer-readable storage medium is also provided, wherein a computer program is stored therein, and the computer program is configured to perform the steps in any of the above method embodiments when it is run.

[0012] According to yet another embodiment of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0013] According to yet another embodiment of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0014] In this embodiment, a first request is received from the application function AF. The first request is a request to establish an IP Multimedia Subsystem (IMS) session between a first session client and a second session client. The first request carries information about the first session client, information about the second session client, and audio / video media information. The first request is sent to the IP Multimedia Subsystem Application Server (IMS AS) to invoke the IMS AS to establish an IMS session. This solves the problem of how to achieve unified processing of audio / video and DC under the IMS AS and NEF's open capability framework for DC, avoiding the use of additional technologies or interfaces to process audio / video media and achieving uniformity in IMS session management. Attached Figure Description

[0015] Figure 1 This is the existing IMS AS and NEF capability open architecture diagram for DC;

[0016] Figure 2 This is a hardware structure block diagram of the computer terminal used in the method embodiments of this application;

[0017] Figure 3 This is a flowchart of a session management method according to an embodiment of this application;

[0018] Figure 4 This is a flowchart of a session management method according to another embodiment of this application;

[0019] Figure 5 This is a schematic diagram illustrating the process of creating a P2P IMS session including audio / video media and a DC according to an embodiment of this application;

[0020] Figure 6 This is a schematic diagram illustrating the process of creating a P2P IMS session containing only audio / video media according to an embodiment of this application;

[0021] Figure 7 This is a schematic diagram illustrating the process of creating an A2P IMS session containing audio / video media and a DC according to an embodiment of this application;

[0022] Figure 8 This is a schematic diagram illustrating the process of creating an A2P IMS session containing only audio / video media according to an embodiment of this application;

[0023] Figure 9 This is a schematic diagram illustrating the process of terminating a P2P IMS session containing audio / video media and a DC, according to an embodiment of this application.

[0024] Figure 10This is a schematic diagram illustrating the process of terminating a P2P IMS session containing only audio / video media according to an embodiment of this application;

[0025] Figure 11 This is a structural block diagram of an electronic device according to an embodiment of this application. Detailed Implementation

[0026] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.

[0027] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0028] In related technologies, NG_RTC defines the capabilities exposed to third-party applications, with IMS AS and NEF providing relevant interfaces. Third-party applications call these interfaces to create, update, and terminate IMS sessions. An IMS session can be a P2P session between two users or an A2P session between an application and a user.

[0029] Figure 1 This is the existing IMS AS and NEF capability open architecture diagram for DC, such as Figure 1 As shown, a third-party application (i.e., AF, also known as application function, application server, or third-party application server) can send an IMS session request to the NEF. The NEF finds the IMS AS serving the user based on the IMS session request and then forwards the IMS session request to the IMS AS. After receiving the request, the IMS AS notifies the corresponding Data Channel Signaling Function (DCSF). The DCSF can guide the IMS AS to interact with the Media Function (MF) to allocate DC resources on the MF. Then, the IMS AS interacts with other IMS network elements and the terminal UE to complete the creation, updating, and termination of the IMS session.

[0030] However, the current capability openness only defines the openness of DC capabilities, while the creation, updating, and termination of Audio / Video media may be implemented using other technologies, such as the NetAPI defined by OMA. The OMA NetAPI only defines the upper-layer interface called by AF, and does not define the capability openness interface for internal network elements of the IMS network, nor the capability call process.

[0031] The problem that needs to be solved is how to achieve unified processing of audio, video and DC within the open framework of IMS AS and NEF for DC capabilities.

[0032] Based on the aforementioned technical problems, this application proposes a session management method. The technical concept is to add the ability to process audio / video media by opening the capability interfaces of IMS AS and NEF without changing the existing IMS capability open architecture, so as to support the direct calling of audio / video media by third-party applications, thereby avoiding the use of additional technologies or interfaces to process audio / video media and realizing the uniformity and efficiency of IMS session management.

[0033] The methods and embodiments provided in this application can be executed on a mobile terminal, a computer terminal, or a similar computing device. Taking running on a computer terminal as an example, Figure 2 This is a hardware structure block diagram of the computer terminal used in the embodiments of the method of this application. For example... Figure 2 As shown, a computer terminal may include one or more ( Figure 2 Only one is shown in the diagram. A processor 202 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 204 for storing data are also shown. The computer terminal may further include a transmission device 206 for communication functions and an input / output device 208. Those skilled in the art will understand that... Figure 2 The structure shown is for illustrative purposes only and does not limit the structure of the computer terminal described above. For example, the computer terminal may also include components that are more complex than those described above. Figure 2 The more or fewer components shown, or having the same Figure 2 The different configurations shown.

[0034] The memory 204 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the session management method in this embodiment. The processor 202 executes various functional applications and data processing by running the computer program stored in the memory 204, thus implementing the aforementioned method. The memory 204 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 204 may further include memory remotely located relative to the processor 202, and these remote memories can be connected to a computer terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0035] The transmission device 206 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider for the computer terminal. In one example, the transmission device 206 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 206 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0036] This embodiment provides a session management method for the aforementioned computer terminal or IMS capability open architecture, applied to the Network Open Function (NEF). Figure 3 This is a flowchart of a session management method according to an embodiment of this application, such as... Figure 3 As shown, the process includes the following steps:

[0037] Step S301: Receive a first request sent by the application function AF; the first request is a request to establish an IP Multimedia Subsystem (IMS) session between a first session client and a second session client, and the first request carries information about the first session client, information about the second session client, and audio and video media information.

[0038] Step S302: Send the first request to the IP Multimedia Subsystem Application Server (IMS AS) to invoke IMSAS to establish an IMS session.

[0039] Through the above steps, without altering the existing IMS capability open architecture, the ability to process audio / video media is enhanced by adding this capability open interface to IMS AS and NEF. This supports direct calls to audio / video media by third-party applications, thereby avoiding the need for additional technologies or interfaces to process audio / video media and achieving uniformity and efficiency in IMS session management. This solves the problem of how to achieve unified processing of audio / video and data centers within the capability open framework of IMS AS and NEF for data centers.

[0040] In one exemplary embodiment, sending the first request carrying the audio and video media information to the IP Multimedia Subsystem Application Server (IMS AS) includes:

[0041] Obtain the IMS AS information of the first session client; based on the IMS AS information, send the first request to the IMS AS of the first session client.

[0042] In one exemplary embodiment, it further includes:

[0043] The IMS AS receives a first response indicating successful receipt of the first request; the first response carries the session ID of the IMS session created by the IMS AS; the first response carrying the session ID is sent to the AF.

[0044] In one exemplary embodiment, the first request also carries data channel DC information.

[0045] In this embodiment of the application, under the original IMS capability open architecture, it is possible not only to create IMS sessions containing only audio / video media, but also to create IMS sessions containing both audio / video media and DC.

[0046] In one exemplary embodiment, the first session endpoint is a user terminal (UE); the second session endpoint is either a UE or the AF.

[0047] The IMS session in this application embodiment can be a P2P session between two user terminals (UEs) or an A2P session between an application AF and a UE.

[0048] In one exemplary embodiment, the first request further carries notification target address information, and the method further includes:

[0049] Receive the session creation result notification sent by the IMS AS based on the notification target address information; send the session creation result notification to the AF.

[0050] In one exemplary embodiment, it further includes:

[0051] Receive the session creation result response returned by the AF in response to the session creation result notification; send the session creation result response to the IMSAS.

[0052] In one exemplary embodiment, it further includes:

[0053] Receive a second request sent by the AF, the second request being a request to terminate the IMS session, the second request carrying the session ID; obtain the IMS AS information of the first session end, and according to the IMS AS information, send the second request carrying the session ID to the IMS AS of the first session end to invoke the IMS AS to terminate the IMS session.

[0054] In one exemplary embodiment, it further includes:

[0055] The IMS AS receives a second response indicating that it has successfully received the second request, and sends the second response to the AF.

[0056] In one exemplary embodiment, the second request further carries notification target address information, and the method further includes:

[0057] Receive the session termination notification sent by the IMS AS based on the notification target address information; send the session termination notification to the AF and receive the session termination response returned by the AF in response to the session termination notification; send the session termination response to the IMS AS.

[0058] In another embodiment of this application, a session management method is provided for a computer terminal or IMS capability open architecture described above, applied to an IP Multimedia Subsystem Application Server (IMS AS). Figure 4 This is a flowchart of a session management method according to another embodiment of this application, such as... Figure 4 As shown, the process includes the following steps:

[0059] Step S401: Receive a first request sent by the Network Open Function (NEF); the first request is a request to establish an IP Multimedia Subsystem (IMS) session between a first session client and a second session client, and the first request carries information about the first session client, information about the second session client, and audio / video media information.

[0060] Step S402: Establish an IP Multimedia Subsystem (IMS) session based on the audio and video media information carried in the first request.

[0061] Through the above steps, without altering the existing IMS capability open architecture, the ability to process audio / video media is enhanced by adding this capability open interface to IMS AS and NEF. This supports direct calls to audio / video media by third-party applications, thereby avoiding the need for additional technologies or interfaces to process audio / video media and achieving uniformity and efficiency in IMS session management. This solves the problem of how to achieve unified processing of audio / video and data centers within the capability open framework of IMS AS and NEF for data centers.

[0062] In one exemplary embodiment, it further includes:

[0063] In response to successfully receiving the first request, a session ID for the IMS session is created, and a first response carrying the session ID is sent to the NEF.

[0064] In one exemplary embodiment, the first session endpoint is a user terminal (UE); the second session endpoint is a UE or an auto-attached device (AF).

[0065] In one exemplary embodiment, it further includes:

[0066] Based on the audio and video media information carried in the first request, a Session Description Protocol (SDP) containing the audio and video media information is generated.

[0067] In one exemplary embodiment, the step of generating a Session Description Protocol (SDP) containing the audio and video media information carried in the first request further includes:

[0068] The audio and video media information between the first session terminal and the second session terminal is determined through the Media Function (MF) and interacts with the MF to determine the audio and video media resources allocated to the first session terminal and the second session terminal; the SDP is generated based on the allocated audio and video media resources; the SDP includes the audio and video media information corresponding to the audio and video media resources.

[0069] In one exemplary embodiment, establishing an IP Multimedia Subsystem (IMS) session based on the audio and video media information carried in the first request includes:

[0070] Based on the audio and video media information in the SDP, a session initiation request is sent to the first session client and / or the second session client to complete media negotiation with the first session client and / or the second session client regarding the audio and video media information, and to establish the IMS session.

[0071] In one exemplary embodiment, the media negotiation includes at least one of the following:

[0072] Without the MF, the audio and video media information between the first session terminal and the second session terminal is exchanged through the Real-Time Transport Protocol (RTP) channel.

[0073] When the audio and video media information between the first session terminal and the second session terminal passes through the MF, the audio and video media information passes through the RTP channel and is forwarded and exchanged by the MF.

[0074] In one exemplary embodiment, the first request further carries data channel (DC) information, and the step of generating a Session Description Protocol (SDP) containing the audio and video media information based on the audio and video media information carried in the first request further includes:

[0075] Based on the audio / video media information and DC information carried in the first request, an SDP containing the audio / video media information and DC information is generated.

[0076] In one exemplary embodiment, it further includes:

[0077] Based on the DC information carried in the first request, the data channel signaling function DCSF serving the first session terminal is selected, and the DC is determined to have passed through the media function MF via the DCSF.

[0078] In one exemplary embodiment, generating an SDP containing the audio / video media information and the DC information based on the audio / video media information and the DC information carried in the first request includes:

[0079] Based on the instruction to create a session data channel sent by the DCSF, the system interacts with the MF to determine the DC resources allocated to the first session client and the second session client; based on the audio and video media information and the allocated DC resources, the system generates the SDP; wherein the DC information in the SDP is the DC information corresponding to the DC resources.

[0080] In one exemplary embodiment, interacting with the MF according to the instruction to create a session data channel sent by the DCSF includes:

[0081] Send a data channel creation event notification to the DCSF; receive a session data channel creation instruction sent by the DCSF based on the data channel creation event notification; and interact with the MF in response to the session data channel creation instruction.

[0082] In one exemplary embodiment, the data channel creation event notification carries the data channel information, the information of the first session terminal, and the information of the second session terminal; the data channel creation event notification is used to instruct the DCSF to determine, based on the DC information, the information of the first session terminal, and the information of the second session terminal, to create data channel information between the first session terminal and the second session terminal.

[0083] In one exemplary embodiment, establishing an IP Multimedia Subsystem (IMS) session based on the audio and video media information carried in the first request includes:

[0084] Based on the audio and video media information and the DC information in the SDP, a session initiation request is sent to the first session client and / or the second session client to complete media negotiation with the first session client and / or the second session client regarding the audio and video media information, and to establish the IMS session.

[0085] In one exemplary embodiment, the media negotiation includes at least one of the following:

[0086] The first session terminal and the second session terminal exchange audio and video media information via an RTP channel;

[0087] The first session client and the second session client exchange application data through the data channel, and the application data of the data channel is forwarded by the MF.

[0088] In one exemplary embodiment, the first request further carries notification target address information, and the method further includes:

[0089] Based on the notification target address information, a first notification is sent to the NEF, and the first notification carries the IMS session creation result.

[0090] In one exemplary embodiment, sending a first response carrying the session ID to the NEF includes:

[0091] If it is determined that the first request also carries data channel information, and the first session end of the IMS session has subscribed to the data channel information, a first response carrying the session ID is sent to the NEF.

[0092] In one exemplary embodiment, it further includes:

[0093] The system receives a second request from the NEF carrying the session ID, terminates the IMS session, and sends a second response to the NEF confirming that the second request has been successfully received; the second request is a request to terminate the IMS session.

[0094] In one exemplary embodiment, where the first request only carries the audio and video media information, it further includes:

[0095] Send a session termination request to the first session endpoint and / or the second session endpoint to terminate the IMS session.

[0096] In one exemplary embodiment, if the first request carries the audio / video media information and the DC information, it further includes:

[0097] The DC between the first session client and the second session client is determined to be via the MF, and the DC resource on the MF is released; a session termination request is sent to the first session client and / or the second session client to terminate the IMS session, and the DCSF is notified to terminate the IMS session.

[0098] In one exemplary embodiment, the second request further carries notification target address information, and the method further includes:

[0099] Based on the notification target address information, a session termination notification is sent to the NEF; and a session termination response is received from the NEF.

[0100] The IMS session management process of this application will be further illustrated below through several specific embodiments:

[0101] Example 1 includes a P2P IMS session creation process for audio / video media and DC.

[0102] Taking the creation of a P2P IMS session between UE A and UE B initiated by a third-party application server AF as an example, where the first session endpoint is UE B and the second session endpoint is UE A, for example, Figure 5 This is a schematic diagram illustrating the process of creating a P2P IMS session including audio / video media and a DC according to an embodiment of this application, as shown below. Figure 5 As shown, the specific steps may include:

[0103] In the S500, the third-party application server AF can create a P2P IMS session between UE A and UE B, which includes audio / video media information and DC information to be established.

[0104] S501, the third-party application server AF can send a request to NEF to establish a P2P IMS session between UE A and UE B. The request includes audio / video media information and DC information.

[0105] In one embodiment, the request may also carry notification target address information, which can be used to notify the result of the IMS session creation request.

[0106] For example, NEF can use the notification target address information provided by the third-party application server AF to send a notification to the third-party application server informing it of the result of its request. This notification mechanism allows the third-party application server to track the status of the session establishment process it initiated in real time, thereby enabling it to take further action based on the final result of the session establishment (success or failure).

[0107] S502, NEF can query the Home Subscriber Server (HSS) to obtain the IMS AS information of the serving UE B, i.e. Figure 5 In this example, IMS AS-2 refers to the IMS AS serving UE B. The following steps in this embodiment 1 are described using IMS AS-2.

[0108] S503, NEF sends a request to IMS AS-2 to establish an IMS session (i.e., an IMS session creation request). The IMS session creation request includes information about UE A and UE B, as well as audio / video media information and DC information. In one embodiment, the IMS session creation request may also carry notification target address information.

[0109] In step S503 above, the ability to process audio / video media is added to the original interface, which is an improvement on the functionality of the IMS AS-2 and NEF interfaces. That is, IMS AS-2 can not only handle DC-related session requests, but also handle audio and video media session requests simultaneously.

[0110] S504, IMS AS-2 determines whether UE B has subscribed to DC services based on the DC information contained in the received IMS session creation request. If so, it can send a response to NEF indicating successful reception of the request, which may include the session ID created.

[0111] S505, NEF sends a response to the third-party application server, carrying the created session ID in the response.

[0112] S506, IMS AS-2 can select the DCSF serving UE B based on the DC information contained in the received IMS session creation request, i.e. Figure 5 In this example, DCSF-2 refers to the DCSF serving UE B. The following steps in this embodiment 1 are described using DCSF-2.

[0113] In step S506 above, based on the received DC information, the DCSF-2 serving UE B can be selected so that DC resource allocation and media negotiation can be carried out subsequently, ensuring the correct allocation of DC resources.

[0114] S507, IMS AS can send a DC creation event notification to DCSF. The DC creation event notification can include information about UE B and UE A, as well as DC information (such as the DC type of P2P, application binding information, etc.).

[0115] S508, DCSF-2 can determine, based on the DC information in the received DC creation event notification and related policies, whether to create a DC between UE B and UE A; and determine whether the DC between UE B and UE A needs to go through MF-2.

[0116] Here, MF-2 can refer to the MF corresponding to UE B.

[0117] S509, DCSF-2 can send instructions to IMS AS to create a DC between UE B and UE A, that is, to create a P2P DC.

[0118] S510, IMS AS-2 can interact with MF-2 according to the received instructions to allocate DC resources for UE B and UE A.

[0119] In steps S509-S510 above, an internal processing and resource allocation mechanism is introduced, namely the interaction between DCSF-2 and IMS AS-2, and the interaction between IMS AS and MF, to complete the allocation of DC resources. By establishing a coordination mechanism between IMS AS-2 and DCSF-2, and between IMS AS-2 and MF-2, efficient allocation of audio, video and DC resources is ensured.

[0120] S511, IMS AS returns a response to the instruction in step S509 to DCSF to create a DC between UE B and UE A.

[0121] S512, DCSF-2 returns a response to IMS AS-2 for step S507, DC creation event notification.

[0122] S513, IMS AS-2 can generate an SDP containing audio / video information and DC information based on the audio / video media information received in step S503 and the DC information determined after interaction with DCSF-2 and MF-2.

[0123] For example, during session establishment, SDP is a session description protocol used to describe media information in a multimedia session. It contains information such as the format, encoding, address, and port of all media streams (such as audio, video, and data channels) in the session. When IMS AS-2 generates SDP based on the audio / video media information and the DC information determined after interaction with DCSF-2 and MF-2, the DC information in the SDP describes the media parameters of the data channel.

[0124] The DC information in SDP is determined after interaction, ensuring that the UE can understand and establish a data channel connection, thereby enabling the exchange of application data during the session.

[0125] S514, IMS AS-2 can send a session initiation request to UE B, where the SDP contains audio / video information and DC information.

[0126] S515, IMS AS-2 and UE B completed media negotiations for Audio / Video and DC.

[0127] S516, IMS AS-2 can send a session initiation request to UE A, where SDP contains audio / video information and DC information.

[0128] S517, IMS AS-2 and UE A completed media negotiations for Audio / Video and DC.

[0129] S518, UE A and UE B exchange audio / video media via the RTP channel.

[0130] S519, UE A and UE B exchange application data through the DC channel; the application data in the DC channel is forwarded by MF-2.

[0131] S520, if the request in step S501 carries notification target address information, IMS AS-2 can notify NEF of the session creation result.

[0132] S521, NEF notifies the third-party application server of the session creation result.

[0133] S522, the third-party application server returns a notification response to NEF.

[0134] S523, NEF returns a notification response to IMS AS-2.

[0135] Example 2: P2P IMS Session Creation Process Including Only Audio / Video Media

[0136] Taking the creation of a P2P IMS session between UE A and UE B initiated by a third-party application server AF as an example, where the first session endpoint is UE B and the second session endpoint is UE A, for example, Figure 6 This is a schematic diagram illustrating the process of creating a P2P IMS session containing only audio / video media according to an embodiment of this application, as shown below. Figure 6 As shown, the specific steps may include:

[0137] In S600, the third-party application server AF can create a P2P IMS session between UE A and UE B, containing only audio / video media information. Figure 6 In this example, IMS AS-2 refers to the IMS AS serving UE B. The following steps in this embodiment 2 are described using IMS AS-2.

[0138] S601, the third-party application server AF can send a request to NEF to establish a P2P IMS session between UE A and UE B, and the request only contains audio / video media information.

[0139] In one embodiment, the request may also carry notification target address information, which can be used to notify the result of the IMS session creation request.

[0140] S602, NEF can query the Home Subscriber Server (HSS) to obtain the IMS AS information of the UE B.

[0141] S603, NEF sends a request to IMS AS-2 to establish an IMS session (i.e., an IMS session creation request). The IMS session creation request carries information about UE A and UE B, as well as audio / video media information. In one embodiment, the IMS session creation request may also carry notification target address information.

[0142] S604, IMS AS-2 can send a response to NEF indicating a successful reception request, including the created session ID.

[0143] S605, NEF sends a response to the third-party application server, carrying the created session ID in the response.

[0144] S606, IMS AS-2 can determine whether the audio / video media exchanged between UE A and UE B needs to pass through the network side MF-2. If so, MF-2 can be selected and step S607 can be executed; otherwise, step S608 can be executed.

[0145] Here, MF-2 can refer to the MF corresponding to UE B.

[0146] S607, IMS AS-2 interacts with MF-2 to allocate audio / video media resources for UE B and UE A, and generates an SDP containing audio / video media information corresponding to the allocated audio / video media resources based on the allocated audio / video media resources.

[0147] S608, IMS AS-2 generates an SDP containing the audio / video media information based on the audio / video media information carried in the IMS session creation request in step S603.

[0148] S609, IMS AS-2 can send a session initiation request to UE B, where the SDP contains audio / video information.

[0149] S610, IMS AS-2 and UE B completed media negotiations for audio / video.

[0150] S611, IMS AS-2 can send a session initiation request to UE A, where the SDP contains audio / video information.

[0151] S612, IMS AS-2 and UE A completed media negotiations for Audio / Video and DC.

[0152] If the media interaction between UE A and UE B does not go through MF-2, then proceed to step S613; otherwise, proceed to step S613'.

[0153] S613, UE A and UE B directly exchange audio / video media via the RTP channel.

[0154] S613', UE A and UE B exchange audio / video media via RTP channel and MF-2 forwarding.

[0155] S614, if the request in step S601 carries notification target address information, IMS AS-2 can notify NEF of the session creation result.

[0156] S615, NEF notifies the third-party application server of the session creation result.

[0157] S616, the third-party application server returns a notification response to NEF.

[0158] S617, NEF returns a notification response to IMS AS-2.

[0159] Example 3 includes an A2P IMS session creation process for audio / video media and DC.

[0160] Taking the creation of an A2P IMS session between the application server and the UE initiated by a third-party application server (AF) as an example, where the first session endpoint is the UE and the second session endpoint is the AF, for example... Figure 7 This is a schematic diagram illustrating the process of creating an A2P IMS session including audio / video media and a DC according to an embodiment of this application, as shown below. Figure 7 As shown, the specific steps may include:

[0161] In S700, the third-party application server (AF) can create an A2P IMS session for the UE, which includes audio / video media information and the DC information to be established.

[0162] S701, the third-party application server AF can send a request to NEF to establish an A2P IMS session between AF and UE. The request includes audio / video media information and DC information.

[0163] In one embodiment, the request may also carry notification target address information, which can be used to notify the result of the IMS session creation request.

[0164] S702, NEF can query the Home Subscriber Server (HSS) to obtain the IMS AS information of the UE B.

[0165] S703, the NEF sends a request to the IMS AS to establish an IMS session (i.e., an IMS session creation request). The IMS session creation request includes information about the UE, the application server AF, audio / video media information, and DC information. In one embodiment, the IMS session creation request may also carry notification target address information.

[0166] S704, the IMS AS determines whether the UE has subscribed to the DC service based on the DC information contained in the received IMS session creation request. If so, it can send a response to the NEF indicating successful receipt of the request, which may include the session ID created.

[0167] S705, NEF sends a response to the third-party application server, carrying the created session ID in the response.

[0168] S706, the IMS AS can select the DCSF serving UE B based on the DC information contained in the received IMS session creation request.

[0169] S707, IMS AS can send DC creation event notification to DCSF. The DC creation event notification can include UE information, AF information, and DC information (such as A2P DC type, application binding information, etc.).

[0170] S708, the DCSF can determine the creation of a DC between the UE and AF based on the DC information in the received DC creation event notification and related policies; and determine that the DC between the UE and AF needs to go through the MF.

[0171] S709, DCSF can send an instruction to IMS AS to create a DC between UE and AF, that is, an instruction to create an A2P DC.

[0172] In the S710, the IMS AS can interact with the MF based on the received instructions to allocate DC resources for the UE and AF.

[0173] S711, IMS AS returns a response to DCSF to the instruction in step S709 to create a DC between UE and AF.

[0174] S712, DCSF returns a response to IMS AS for step S707, DC creation event notification.

[0175] S713, the IMS AS can generate an SDP containing audio / video information and DC information based on the audio / video media information received in step S703 and the DC information determined after interaction with DCSF and MF.

[0176] S714, the IMS AS can send a session initiation request to the UE, where the SDP contains audio / video information and DC information.

[0177] S715, IMS AS completes media negotiations with UE for Audio / Video and DC.

[0178] S716, UE and AF exchange audio / video media via RTP channel.

[0179] S717, UE and AF exchange application data through DC channel; the application data in DC channel is forwarded by MF.

[0180] S718, if the request in step S701 carries notification target address information, the IMS AS can notify the NEF of the session creation result.

[0181] S719, NEF notifies the third-party application server of the session creation result.

[0182] S720, the third-party application server returns a notification response to NEF.

[0183] S721, NEF returns a notification response to IMS AS.

[0184] Example 4: A2P IMS Session Creation Process Including Only Audio / Video Media

[0185] Taking the creation of an A2P IMS session between the application server and the UE initiated by a third-party application server as an example, where the first session endpoint is the UE and the second session endpoint is the AF, for example, Figure 8 This is a schematic diagram illustrating the process of creating an A2P IMS session containing only audio / video media according to an embodiment of this application, as shown below. Figure 8 As shown, the specific steps may include:

[0186] In S800, the third-party application server AF can create an A2P IMS session for the UE, which only contains audio / video media information.

[0187] In step S801, the NEF sends a request to the IMS AS to establish an IMS session (i.e., an IMS session creation request). The IMS session creation request includes information about the UE, the application server AF, and audio / video media information. In one embodiment, the IMS session creation request may also carry notification target address information.

[0188] S802, NEF can query the Home Subscriber Server (HSS) to obtain the IMS AS information of the serving UE.

[0189] In step S803, the NEF sends a request to the IMS AS to establish an IMS session (i.e., an IMS session creation request). The IMS session creation request includes information about the UE, the application server AF, and audio / video media information. In one embodiment, the IMS session creation request may also carry notification target address information.

[0190] S804, IMS AS can send a response to NEF indicating a successful reception request, including the session ID created.

[0191] S805, NEF sends a response to the third-party application server AF, carrying the created session ID in the response.

[0192] S806, the IMS AS can determine whether the audio / video media exchanged between the UE and AF needs to pass through the network-side MF. If so, the MF can be selected and step S807 can be executed; otherwise, step S808 can be executed.

[0193] S807, the IMS AS interacts with the MF to allocate audio / video media resources to the UE and AF, and generates an SDP containing audio / video media information corresponding to the allocated audio / video media resources based on the allocated audio / video media resources.

[0194] S808, the IMS AS generates an SDP containing the audio / video media information based on the audio / video media information carried in the IMS session creation request in step S803.

[0195] S809, the IMS AS can send a session initiation request to the UE, where the SDP contains audio / video information.

[0196] S810, IMS AS and UE complete audio / video media negotiation.

[0197] S811, UE and AF exchange audio / video media via RTP channel.

[0198] S812, if the request in step S801 carries notification target address information, the IMS AS can notify the NEF of the session creation result.

[0199] S813, NEF notifies the third-party application server of the session creation result.

[0200] S814, the third-party application server returns a notification response to NEF.

[0201] S815, NEF returns a notification response to IMS AS.

[0202] Example 5 includes a P2P IMS session termination procedure for audio / video media and DC.

[0203] Taking the termination of an ongoing P2P IMS session between UE A and UE B initiated by a third-party application server as an example, where the first session endpoint is UE B and the second session endpoint is UE A, for example... Figure 9 This is a schematic diagram illustrating the process of terminating a P2P IMS session containing audio / video media and a DC, according to an embodiment of this application. Figure 9 As shown, the specific steps may include:

[0204] S900, the third-party application server AF terminates the P2P IMS session between UE A and UE B, which includes audio / video media and DC media.

[0205] S901, the third-party application server AF sends a request to NEF to terminate the IMS session in order to terminate the P2P IMS session between UE A and UE B. The request carries the session ID of the IMS session.

[0206] S902, NEF queries HSS to obtain IMS AS information of serving UE B.

[0207] S903, NEF sends a request to IMS AS to terminate the IMS session. The request to terminate the IMS session includes the session ID information of the IMS session.

[0208] S904, IMS AS can send a response to NEF indicating a successful reception request.

[0209] S905, NEF sends a response to the third-party application server AF.

[0210] S906, the IMS AS determines that the DC between UE A and UE B in the session has passed through the MF, interacts with the MF, and releases the DC resources on the MF.

[0211] S907, the IMS AS can send a Bye request (i.e., session end request) to the UE B to end the IMS session on the UE B side. The IMS session includes audio / video and DC media.

[0212] S908, the IMS AS can send a Bye request to the UE A to end the IMS session on the UE A side. The IMS session includes audio / video and DC media.

[0213] S909, IMS AS notifies DCSF of the end of the IMS session event.

[0214] S910, if the third-party application server carries notification target address information when creating the IMS session, the IMS AS can send a session termination notification to the NEF.

[0215] S911, NEF sends a session termination notification to the third-party application server.

[0216] S912, the third-party application server returns a notification response to NEF.

[0217] S913, NEF returns a notification response to IMS AS.

[0218] Example 6: P2P IMS Session Termination Procedure Containing Only Audio / Video Media

[0219] Taking the termination of an ongoing P2P IMS session between UE A and UE B initiated by a third-party application server as an example, where the first session endpoint is UE B and the second session endpoint is UE A, for example... Figure 10 This is a schematic diagram illustrating the termination process of a P2P IMS session containing only audio / video media according to an embodiment of this application. Figure 10 As shown, the specific steps may include:

[0220] S1000, the third-party application server AF terminates the P2P IMS session between UE A and UE B, which contains audio / video media.

[0221] S1001, the third-party application server AF sends a request to NEF to terminate the IMS session in order to terminate the P2P IMS session between UE A and UE B. The request carries the session ID of the IMS session.

[0222] S1002, NEF queries HSS to obtain IMS AS information of serving UE B.

[0223] S1003, NEF sends a request to IMS AS to terminate the IMS session. The request to terminate the IMS session includes the session ID information of the IMS session.

[0224] S1004, IMS AS can send a response to NEF indicating that it has successfully received the request in step S1003.

[0225] S1005, NEF sends a response to the request in step S1001 to the third-party application server AF.

[0226] S1006, the IMS AS can send a Bye request (i.e., session end request) to the UE B to end the IMS session on the UE B side. The IMS session only includes audio / video.

[0227] S1007, IMS AS can send a Bye request to UE A to end the IMS session on the UE A side. The IMS session only includes audio / video.

[0228] S1008, if the third-party application server carries notification target address information when creating the IMS session, IMSAS can send a session termination notification to NEF.

[0229] S1009, NEF sends a session termination notification to the third-party application server.

[0230] S1010, the third-party application server returns a notification response to NEF.

[0231] S1011, NEF returns a notification response to IMS AS.

[0232] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0233] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when run.

[0234] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0235] Figure 11 This is a structural block diagram of an electronic device according to an embodiment of this application, such as... Figure 11 As shown, embodiments of this application also provide an electronic device 110, including a memory 1101 and a processor 1102. The memory 1101 stores a computer program, and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0236] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0237] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0238] Embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0239] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0240] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A method for processing a session, characterized in that, Applied to Network Openness Functions (NEF), including: Receive a first request sent by the application function AF; the first request is a request to establish an IP Multimedia Subsystem (IMS) session between a first session client and a second session client, and the first request carries information about the first session client, information about the second session client, and audio and video media information; The first request is sent to the IP Multimedia Subsystem Application Server (IMS AS) to invoke the IMS AS to establish an IMS session.

2. The method according to claim 1, characterized in that, Sending the first request carrying the audio and video media information to the IP Multimedia Subsystem Application Server (IMS AS) includes: Obtain the IMS AS information of the first session client; Based on the IMS AS information, the first request is sent to the IMS AS of the first session terminal.

3. The method according to claim 1, characterized in that, Also includes: The IMS AS receives a first response indicating successful receipt of the first request. The first response carries the session ID of the IMS session created by the IMS AS; The first response carrying the session ID is sent to the AF.

4. The method according to claim 1, characterized in that, The first request also carries data channel DC information.

5. The method according to claim 1, characterized in that, The first session terminal is a user terminal (UE); the second session terminal is either a UE or the AF.

6. The method according to claim 1, characterized in that, The first request also carries notification target address information, and the method further includes: Receive the session creation result notification sent by the IMS AS based on the notification target address information; The session creation result notification is sent to the AF.

7. The method according to claim 6, characterized in that, Also includes: Receive the AF response in response to the session creation result notification returned by the session creation result; Send the session creation result response to the IMS AS.

8. The method according to claim 3, characterized in that, Also includes: Receive a second request sent by the AF, the second request being a request to terminate the IMS session, the second request carrying the session ID; Obtain the IMS AS information of the first session client, and based on the IMS AS information, send the second request carrying the session ID to the IMS AS of the first session client to invoke the IMS AS to terminate the IMS session.

9. The method according to claim 8, characterized in that, Also includes: The IMS AS receives a second response indicating that it has successfully received the second request, and sends the second response to the AF.

10. The method according to claim 8, characterized in that, The second request also carries notification target address information, and the method further includes: Receive the session termination notification sent by the IMS AS based on the notification target address information; Send the session end notification to the AF, and receive the session end response returned by the AF in response to the session end notification; Send the session end response to the IMS AS.

11. A method for managing sessions, characterized in that, Applications in the IP Multimedia Subsystem Application Server (IMS AS) include: Receive a first request sent by the Network Open Function (NEF); the first request is a request to establish an IP Multimedia Subsystem (IMS) session between a first session client and a second session client, and the first request carries information about the first session client, information about the second session client, and audio and video media information; Based on the audio and video media information carried in the first request, establish an IP Multimedia Subsystem (IMS) session.

12. The method according to claim 11, characterized in that, Also includes: In response to successfully receiving the first request, a session ID for the IMS session is created, and a first response carrying the session ID is sent to the NEF.

13. The method according to claim 11, characterized in that, The first session terminal is a user terminal (UE); the second session terminal is a UE or an auto-attached terminal (AF).

14. The method according to claim 12, characterized in that, Also includes: Based on the audio and video media information carried in the first request, a Session Description Protocol (SDP) containing the audio and video media information is generated.

15. The method according to claim 14, characterized in that, The step of generating a Session Description Protocol (SDP) containing the audio and video media information carried in the first request further includes: The audio and video media information between the first session terminal and the second session terminal is determined to be the audio and video media resources allocated to the first session terminal and the second session terminal by interacting with the media function MF. The SDP is generated based on the allocated audio and video media resources; the SDP includes the audio and video media information corresponding to the audio and video media resources.

16. The method according to claim 14 or 15, characterized in that, The step of establishing an IP Multimedia Subsystem (IMS) session based on the audio and video media information carried in the first request includes: Based on the audio and video media information in the SDP, a session initiation request is sent to the first session client and / or the second session client to complete media negotiation with the first session client and / or the second session client regarding the audio and video media information, and to establish the IMS session.

17. The method according to claim 16, characterized in that, in, The media consultation includes at least one of the following: Without the MF, the audio and video media information between the first session terminal and the second session terminal is exchanged through the Real-Time Transport Protocol (RTP) channel. When the audio and video media information between the first session terminal and the second session terminal passes through the MF, the audio and video media information passes through the RTP channel and is forwarded and exchanged by the MF.

18. The method according to claim 14, characterized in that, The first request also carries data channel DC information, and the step of generating a Session Description Protocol (SDP) containing the audio and video media information based on the audio and video media information carried in the first request further includes: Based on the audio / video media information and DC information carried in the first request, an SDP containing the audio / video media information and DC information is generated.

19. The method according to claim 18, characterized in that, Also includes: Based on the DC information carried in the first request, the data channel signaling function DCSF serving the first session terminal is selected, and the DC is determined to have passed through the media function MF via the DCSF.

20. The method according to claim 19, characterized in that, The step of generating an SDP containing the audio / video media information and the DC information carried in the first request includes: Based on the instruction to create a session data channel sent by the DCSF, interact with the MF to determine the DC resources allocated to the first session end and the second session end; The SDP is generated based on the audio and video media information and the allocated DC resources; wherein the DC information in the SDP is the DC information corresponding to the DC resources.

21. The method according to claim 20, characterized in that, The step of interacting with the MF according to the instruction to create a session data channel sent by the DCSF includes: Send a data channel creation event notification to the DCSF; Receive the session data channel creation instruction sent by the DCSF based on the data channel creation event notification; In response to the instruction to create a session data channel, interact with the MF.

22. The method according to claim 21, characterized in that, The data channel creation event notification carries the data channel information, the information of the first session end, and the information of the second session end; The data channel creation event notification is used to instruct the DCSF to determine, based on the DC information, the information of the first session terminal, and the information of the second session terminal, to create data channel information between the first session terminal and the second session terminal.

23. The method according to claim 18 or 20, characterized in that, The step of establishing an IP Multimedia Subsystem (IMS) session based on the audio and video media information carried in the first request includes: Based on the audio and video media information and the DC information in the SDP, a session initiation request is sent to the first session client and / or the second session client to complete media negotiation with the first session client and / or the second session client regarding the audio and video media information, and to establish the IMS session.

24. The method according to claim 19, characterized in that, in, The media consultation includes at least one of the following: The first session terminal and the second session terminal exchange audio and video media information via an RTP channel; The first session client and the second session client exchange application data through the data channel, and the application data of the data channel is forwarded by the MF.

25. The method according to claim 11, characterized in that, The first request also carries notification target address information, and the method further includes: Based on the notification target address information, a first notification is sent to the NEF, and the first notification carries the IMS session creation result.

26. The method according to claim 12, characterized in that, Sending a first response carrying the session ID to the NEF includes: If it is determined that the first request also carries data channel information, and the first session end of the IMS session has subscribed to the data channel information, a first response carrying the session ID is sent to the NEF.

27. The method according to claim 19, characterized in that, Also includes: The system receives a second request from the NEF carrying the session ID, terminates the IMS session, and sends a second response to the NEF confirming that the second request has been successfully received; the second request is a request to terminate the IMS session.

28. The method according to claim 27, characterized in that, If the first request only carries the audio and video media information, it also includes: Send a session termination request to the first session endpoint and / or the second session endpoint to terminate the IMS session.

29. The method according to claim 27, characterized in that, If the first request carries the audio / video media information and the DC information, it further includes: Determine that the DC between the first session end and the second session end passes through the MF, interacts with the MF, and releases the DC resources on the MF; Send a session termination request to the first session endpoint and / or the second session endpoint to terminate the IMS session, and notify the DCSF to terminate the IMS session.

30. The method according to claim 27, characterized in that, The second request also carries notification target address information, and the method further includes: Based on the notification target address information, a session end notification is sent to the NEF; Receive the session termination response returned by the NEF.

31. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 10, or the steps of the method described in any one of claims 11 to 30.

32. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 10, or the steps of the method described in any one of claims 11 to 30.

33. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1 to 10, or implements the steps of the method according to any one of claims 11 to 30.

Images