Session management method, apparatus and device, program product and storage medium

Abstract

Disclosed in the present application are a session management method, apparatus and device, a program product and a storage medium. The method comprises: receiving a first SIP message sent by a terminal; on the basis of user intention information related to a first session carried in the first SIP message, determining N semantic labels corresponding to the user intention information, and encapsulating the N semantic labels into the first SIP message to obtain a second SIP message, N being a positive integer, and different semantic labels among the N semantic labels being corresponding to different services; sending the second SIP message to a label controller, and receiving a third SIP message sent by the label controller, the third SIP message carrying an orchestration result of the N semantic labels; and determining a target device on the basis of the orchestration result of the N semantic labels, and sending the third SIP message to the target device.

Description

A session management method, apparatus, device, program product, and storage medium

[0001] Cross-references to related applications

[0002] This application is based on and claims priority to Chinese Patent Application No. 202411345806.4, filed on September 25, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of core network technology, and in particular to a session management method, apparatus, device, program product, and storage medium. Background Technology

[0004] Currently, the Session Initiation Protocol (SIP) is widely used in real-time communication, such as Voice over Internet Protocol (VoIP) and video conferencing. The SIP protocol is primarily used to establish, modify, and terminate multimedia sessions. However, related SIP technologies lack intelligence and have certain limitations. Summary of the Invention

[0005] To address the aforementioned technical problems, this application provides a session management method, apparatus, device, program product, and storage medium.

[0006] The session management method provided in this application is applied to a server, and the method includes:

[0007] The receiving terminal sends a first SIP message, determines N semantic tags corresponding to the user intent information based on the user intent information related to the first session carried in the first SIP message, and encapsulates the N semantic tags into the first SIP message to obtain a second SIP message, where N is a positive integer; different semantic tags in the N semantic tags correspond to different services;

[0008] Send the second SIP message to the tag controller and receive the third SIP message sent by the tag controller. The third SIP message carries the arrangement result of N semantic tags.

[0009] The target device is determined based on the arrangement of N semantic tags, and a third SIP message is sent to the target device.

[0010] The session management method provided in this application is applied to a tag controller, and the method includes:

[0011] The terminal receives a second SIP message sent by the server. The second SIP message includes N semantic tags corresponding to the user intent information determined based on the user intent information related to the first session. The second SIP message is obtained by encapsulating the N semantic tags into the first SIP message. The first SIP message carries the user intent information related to the first session. The first SIP message is sent from the terminal to the server. N is a positive integer, and different semantic tags in the N semantic tags correspond to different services.

[0012] Arrange N semantic tags to obtain the arrangement result of N semantic tags;

[0013] A third SIP message is sent to the server, which carries the arrangement result of N semantic tags.

[0014] The dynamic session management device provided in this application is applied to a server, and the device includes:

[0015] The first communication unit is configured to receive the first SIP message sent by the terminal.

[0016] The first processing unit is configured to determine N semantic tags corresponding to the user intent information based on the user intent information related to the first session carried in the first SIP message, and encapsulate the N semantic tags into the first SIP message to obtain the second SIP message, where N is a positive integer; different semantic tags in the N semantic tags correspond to different services.

[0017] The first communication unit is configured to send a second SIP message to the tag controller and receive a third SIP message sent by the tag controller, wherein the third SIP message carries the arrangement result of N semantic tags;

[0018] The first processing unit is configured to determine the target device based on the arrangement result of N semantic tags;

[0019] The first communication unit is configured to send a third SIP message to the target device.

[0020] The session management device provided in this application embodiment is applied to a tag controller, and the device includes:

[0021] The second communication unit is configured to receive a second SIP message sent by a server. The second SIP message includes N semantic tags corresponding to the user intent information determined based on the user intent information related to the first session. The second SIP message is obtained by encapsulating the N semantic tags into a first SIP message. The first SIP message carries the user intent information related to the first session. The first SIP message is sent from the terminal to the server. N is a positive integer, and different semantic tags in the N semantic tags correspond to different services.

[0022] The second processing unit is configured to arrange N semantic tags to obtain an arrangement result of N semantic tags;

[0023] The second communication unit is configured to send a third SIP message to the server, wherein the third SIP message carries the arrangement result of N semantic tags.

[0024] The dynamic session management device provided in this application includes a processor and a memory, wherein the memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute any of the above-described dynamic session management methods.

[0025] This application provides a computer program product comprising: a computer program that, when executed by a processor, implements any of the methods described above.

[0026] The computer-readable storage medium provided in this application is used to store a computer program that causes a computer to perform any of the methods described above.

[0027] In the technical solution of this application, a first SIP message is sent by a receiving terminal. Based on the user intent information related to the first session carried in the first SIP message, N semantic tags corresponding to the user intent information are determined. These N semantic tags are then encapsulated into the first SIP message to obtain a second SIP message, where N is a positive integer. Different semantic tags among the N semantic tags correspond to different services. The second SIP message is sent to a tag controller, and a third SIP message is received from the tag controller. The third SIP message carries the arrangement result of the N semantic tags. Based on the arrangement result of the N semantic tags, a target device is determined, and a third SIP message is sent to the target device. Thus, by using embedded semantic tags and determining the target device based on the arranged semantic tags, the server can automatically understand user intent, automatically process the context of communication content, reduce manual intervention, improve user experience, and adapt to more intelligent application scenarios. Attached Figure Description

[0028] Figure 1 is a flowchart illustrating the session management method provided in an embodiment of this application;

[0029] Figure 2 is a flowchart illustrating the session management method provided in an embodiment of this application.

[0030] Figure 3 is a flowchart illustrating the session management method provided in this embodiment of the application.

[0031] Figure 4 is a schematic diagram of the process of arranging, combining and registering SIP semantic tags according to the user's semantic intent, provided in an embodiment of this application.

[0032] Figure 5 is an application embodiment one provided in this application;

[0033] Figure 6 is an application embodiment two provided in this application;

[0034] Figure 7 is a schematic diagram of the structure of the dynamic session management device provided in an embodiment of this application;

[0035] Figure 8 is a schematic diagram of the structure of the dynamic session management device provided in an embodiment of this application;

[0036] Figure 9 is a schematic structural diagram of a dynamic session management device provided in an embodiment of this application;

[0037] Figure 10 is a schematic structural diagram of a chip according to an embodiment of this application. Detailed Implementation

[0038] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0039] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0040] It should also be noted that the terms "first, second, and third" used in the embodiments of this application are only used to distinguish similar objects and do not represent a specific order of objects. It is understood that "first, second, and third" can be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0041] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B.

[0042] Currently, SIP is widely used in real-time communication, such as VoIP and video conferencing. The SIP protocol is primarily used to establish, modify, and terminate multimedia sessions. Related SIP technologies mainly include the following components:

[0043] Session establishment: Initiate a session via a SIP Invite request, which includes basic session parameters (such as media type and bandwidth requirements).

[0044] Session Modification: Adjust session parameters via SIP Update or Reinvite requests.

[0045] Session termination: The session is terminated via a SIP BYE request.

[0046] Service discovery: Basic service discovery and selection are performed through SIP registration requests (REGISTER) and proxy servers.

[0047] The main drawbacks of related SIP technologies include: 1) Lack of intelligence: In related technologies, the SIP protocol lacks intelligent understanding and response to user intent and context when processing session requests. For example, a user in a smart home system requests to turn on the lights, but the system cannot recognize the user's specific intent and environment (such as room brightness and time), and simply executes the light-on operation. In telemedicine applications, a patient submits a consultation request, but the system cannot provide the most suitable doctor and service based on the patient's specific needs and condition. 2) Limitations in session management: Related SIP protocols have some limitations in session management, especially in dynamically adjusting and optimizing session parameters. For example, in video conferencing, when network conditions change, the system cannot adjust video quality and bandwidth allocation in a timely manner, leading to a decline in session quality. In telemedicine applications, when switching from video call to screen sharing, the system cannot switch and adjust media types in a timely manner. Therefore, how to improve the intelligence of SIP technology and reduce the limitations of session management becomes a problem that needs to be considered. To this end, the following technical solutions are proposed in the embodiments of this application.

[0048] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0049] It should be noted that the server and tag controller in this application can be set up separately or together, and this application does not impose any specific limitations on this. In other words, some or all of the steps related to the tag controller can be executed through the server, and some or all of the steps related to the server can also be executed through the tag controller.

[0050] Figure 1 is a flowchart illustrating a session management method provided in an embodiment of this application, applied to a server. As shown in Figure 1, the session management method includes the following steps:

[0051] Step 101: Receive the first SIP message sent by the terminal, determine the N semantic tags corresponding to the user intent information based on the user intent information related to the first session carried in the first SIP message, and encapsulate the N semantic tags into the first SIP message to obtain the second SIP message, where N is a positive integer; different semantic tags in the N semantic tags correspond to different services.

[0052] Step 102: Send the second SIP message to the tag controller and receive the third SIP message sent by the tag controller. The third SIP message carries the arrangement result of N semantic tags.

[0053] Step 103: Determine the target device based on the arrangement of N semantic tags, and send a third SIP message to the target device.

[0054] In some implementations, the aforementioned server may be a SIP server, and the aforementioned tag controller may be a SIP tag controller.

[0055] In some implementations, the server receives a first SIP message sent by the terminal. This first SIP message carries user intent information related to a first session. The server decomposes the user intent information, forming N semantic tags corresponding to the user intent information based on the decomposed intent information. These N semantic tags are then encapsulated into the first SIP message to obtain a second SIP message, where N is a positive integer. Different semantic tags among the N semantic tags correspond to different services. The server sends the second SIP message to a tag controller and receives a third SIP message from the tag controller. This third SIP message carries the arrangement result of the N semantic tags. Subsequently, the server determines the target device based on the arrangement result of the N semantic tags and sends the third SIP message to the target device.

[0056] In some implementations, after the server determines N semantic tags corresponding to the user intent information based on the user intent information, it writes the generated N semantic tags into the tag controller.

[0057] In some embodiments, when the label controller receives N semantic labels sent by the server, it searches and matches them in the label library. If the semantic label exists, the label controller performs service orchestration and service discovery, and writes the orchestration result of the semantic label in the third SIP message and sends it to the server. If the semantic label does not exist in the label library, a new semantic label is generated, and the new semantic label is registered for service. After the service registration, it is written into the label library. Then, the label controller performs service orchestration and service discovery, and writes the orchestration result of the semantic label in the third SIP message and sends it to the server.

[0058] In some embodiments, the semantic label includes one or more of the following information: the service type related to the first session, the priority of the service type related to the first session, the media format required for the first session, and the load status.

[0059] In some embodiments, the server embeds programmable semantic labels in the SIP message header or body to describe the context, intent, or content of the communication. Exemplarily, semantic information is embedded in the INVITE request to indicate that this is a video conference, a medical consultation, or an emergency call.

[0060] In some embodiments, the content of the definition format of the semantic label is as follows:

[0061] Service type: Describes the type of service requested, such as remote medical consultation, smart home control, etc.

[0062] Priority: Describes the priority of the request, such as urgent, general, etc.

[0063] Media format: Describes the required media format, such as audio, video, etc.

[0064] Current load status: Describes the load status of the current device or network.

[0065] Exemplarily, the definition format of the semantic label is as follows:

[0066] <SIP Semantic Label>

[0067] <Service Type>Remote Medical< / Service Type>

[0068] <Priority>High< / Priority>

[0069] <Media Format>Video< / Media Format>

[0070] <Current Load Status>Light / Medium / Heavy< / Current Load Status>

[0071] < / SIP Semantic Label>

[0072] In some implementations, the tag controller dynamically programs and combines N semantic tags, enabling the server to intelligently discover and select services using the semantic tags embedded in SIP messages. For example, a user session intent can be decomposed into at least one semantic tag meta-service, which can be dynamically programmed and combined by the tag controller. Semantic tags can be programmed to describe the requirements and parameters of different services such as telemedicine (semantic tag meta-service 1), smart home (semantic tag meta-service 2), and video conferencing (semantic tag meta-service 3). Each tag's corresponding semantic can also be configured with sub-semantics corresponding to "sub-services of the semantic tag meta-service," thus forming a hierarchical semantic tag service system.

[0073] In some implementations, the tag controller can arrange semantic tags based on the content of N semantic tags.

[0074] In some implementations, the N semantic tags include multi-level tags, with one or more lower-level tags associated with one or more higher-level tags. For example, in a telemedicine application (semantic tag meta-service 1), semantic tags may include patient information (sub-service 1 of semantic tag meta-service 1), doctor qualification requirements (sub-service 2 of semantic tag meta-service 1), medical device type (sub-service 3 of semantic tag meta-service 1), etc.; in a smart home application (semantic tag meta-service 2), semantic tags may include control commands (sub-service 1 of semantic tag meta-service 2), device status (sub-service 2 of semantic tag meta-service 2), environmental parameters (sub-service 3 of semantic tag meta-service 2), etc.; in a video conferencing application, semantic tags may include meeting topic, participant information, video quality requirements, etc. For example, meta-service 1 may include at least one or more of sub-service 1, sub-service 2, and sub-service 3.

[0075] In some implementations, determining the target device based on the arrangement result of N semantic tags includes: selecting a target device based on the arrangement result of N semantic tags, wherein the target device is a device capable of processing the service corresponding to the arrangement result; or, sending the arrangement result of N semantic tags to a semantic database, wherein the arrangement result of N semantic tags is used by the semantic database to select a target device; and receiving indication information of the target device sent by the semantic database, wherein the target device is a device capable of processing the service corresponding to the arrangement result.

[0076] In some implementations, the server can directly select the optimal service or device (target device) based on the arrangement and description of N semantic tags, and then send a request to the target device or service provider, notifying it of a new operation request. Alternatively, the server sends the arrangement of N semantic tags to a semantic database. This arrangement is used by the semantic database to select the target device. After selecting the target device, the semantic database sends indication information about the target device to the server. The target device is a device capable of processing the service corresponding to the arrangement result. For example, in telemedicine, this involves finding suitable medical equipment and doctors; in smart homes, it involves finding corresponding smart devices; and in video conferencing, it involves finding suitable meeting resources and equipment.

[0077] In some implementations, the first SIP message also carries session parameters of the first session; the method further includes: monitoring network conditions and / or the device status of the target device; adjusting the session parameters according to the network conditions and / or the device status of the target device; and sending a fourth SIP message to the target device, the fourth SIP message carrying the adjusted session parameters.

[0078] In some implementations, the first SIP message carries session parameters for the first session. The server detects network conditions and / or the device status of the target device, and adjusts the session parameters accordingly. Then, the server sends a fourth SIP message carrying the adjusted session parameters to the target device, which updates its device parameters based on the fourth SIP message. For example, the fourth SIP message can be a SIP UPDATE or REINVITE. This ensures the effective transmission of commands.

[0079] In some implementations, the method further includes: receiving a fifth SIP message sent by a terminal, the fifth SIP message carrying updated user intent information; determining M semantic tags corresponding to the updated user intent information, and updating the orchestration result based on the M semantic tags; and sending a sixth SIP message to a target device, the sixth SIP message carrying the updated orchestration result.

[0080] In some implementations, the server receives a fifth SIP message sent by the terminal, which carries updated user intent information; the server determines M semantic tags corresponding to the updated user intent information, updates the orchestration result based on the M semantic tags; and sends a sixth SIP message to the target device, which carries the updated orchestration result.

[0081] In some implementations, when the M semantic tags determined by the server cannot be combined or directly obtained from the aforementioned N semantic tags, a fifth SIP message needs to be sent to the tag controller. The tag controller arranges the M semantic tags and carries the arrangement result in the fifth SIP message, which is then sent to the server. The server selects the target device and / or service based on the SIP message.

[0082] In some implementations, when the M semantic tags determined by the server can be combined or directly obtained from the aforementioned N semantic tags, the server dynamically adjusts the service discovery entry and operates to perform end-to-end service continuity.

[0083] In some implementations, the fifth SIP message can be a SIP Information Request (SIP INFO), and the terminal can send an INFO request to convey dynamically changing semantic information.

[0084] In some implementations, when a user's intent changes during a session, the tag controller is triggered again to rearrange the SIP semantic tags. Subsequently, the server dynamically adjusts session parameters, including bandwidth allocation and media type switching, based on the rearranged semantic tags.

[0085] The technical solution of this application embodiment receives a first SIP message sent by a terminal, determines N semantic tags corresponding to the user intent information of the first session carried in the first SIP message, and encapsulates the N semantic tags into the first SIP message to obtain a second SIP message, where N is a positive integer; different semantic tags in the N semantic tags correspond to different services; the second SIP message is sent to a tag controller, and a third SIP message is received from the tag controller, the third SIP message carrying the arrangement result of the N semantic tags; the target device is determined according to the arrangement result of the N semantic tags, and the third SIP message is sent to the target device. The server, through the embedded semantic tags and the determination of the target device based on the arranged semantic tags, can automatically understand user intent, automatically process the context of communication content, reduce manual intervention, improve user experience, and adapt to more intelligent application scenarios.

[0086] Figure 2 is a second flowchart illustrating the session management method provided in this application embodiment, applied to a tag controller. As shown in Figure 2, the session management method includes the following steps:

[0087] Step 201: Receive a second SIP message sent by the server, wherein the second SIP message includes N semantic tags corresponding to the user intent information determined according to the user intent information related to the first session. The second SIP message is obtained by encapsulating the N semantic tags into the first SIP message. The first SIP message carries the user intent information related to the first session. The first SIP message is sent by the terminal to the server. N is a positive integer, and different semantic tags in the N semantic tags correspond to different services.

[0088] Step 202: Arrange the N semantic tags to obtain the arrangement result of the N semantic tags.

[0089] Step 203: Send the third SIP message to the server, wherein the third SIP message carries the arrangement result of N semantic tags.

[0090] In some implementations, the aforementioned server may be a SIP server, and the aforementioned tag controller may be a SIP tag controller.

[0091] In some implementations, the server receives a first SIP message sent by the terminal. This first SIP message carries user intent information related to a first session. The server decomposes the user intent information, forming N semantic tags corresponding to the user intent information based on the decomposed intent information. These N semantic tags are then encapsulated into the first SIP message to obtain a second SIP message, where N is a positive integer; different semantic tags among the N semantic tags correspond to different services. The second SIP message is then sent to a tag controller. The tag controller receives the second SIP message from the server and arranges the N semantic tags to obtain an arrangement result. A third SIP message is then sent to the server, carrying the arrangement result of the N semantic tags. Subsequently, the server determines the target device based on the arrangement result of the N semantic tags and sends the third SIP message to the target device.

[0092] In some implementations, after the server determines N semantic tags corresponding to the user intent information based on the user intent information, it writes the generated N semantic tags into the tag controller.

[0093] In some implementations, the semantic tag includes one or more of the following information: the service type associated with the first session, the priority of the service type associated with the first session, the media format required for the first session, and the load status.

[0094] In some implementations, the server embeds programmable semantic tags in the SIP message header or body to describe the context, intent, or content of the communication. For example, semantic information might be embedded in an INVITE request to indicate that it is a video conference, medical consultation, or emergency call.

[0095] In some embodiments, the content of the definition format of semantic tags is as follows:

[0096] Service type: Describes the type of service requested, such as remote medical consultation, smart home control, etc.

[0097] Priority: Describes the priority of the request, such as urgent, normal, etc.

[0098] Media format: Describes the required media format, such as audio, video, etc.

[0099] Current load status: Describes the load status of the current device or network.

[0100] Exemplarily, the definition format of semantic tags is as follows:

[0101] <SIP semantic tag>

[0102] <Service type>Remote medical< / Service type>

[0103] <Priority>High< / Priority>

[0104] <Media format>Video< / Media format>

[0105] <Current load status>Light / Medium / Heavy< / Current load status>

[0106] < / SIP semantic tag>

[0107] In some embodiments, the tag controller performs dynamic programming and combination on N semantic tags, and then the server uses the semantic tags embedded in the SIP message to implement intelligent service discovery and selection. Exemplarily, the user session intent can be decomposed into at least one semantic tag meta-service, and the meta-service can be dynamically programmed and combined in the tag controller. The semantic tags can be programmed to describe the requirements and parameters of different services such as remote medical (semantic tag meta-service 1), smart home (semantic tag meta-service 2), video conferencing (semantic tag meta-service 3), etc. The semantics corresponding to each tag can also set sub-semantics corresponding to "sub-services of the semantic tag meta-service" to form a hierarchical semantic tag service system.

[0108] In some embodiments, the tag controller can perform semantic tag orchestration according to the content of N semantic tags.

[0109] In some implementations, the N semantic tags include multi-level tags, with one or more lower-level tags associated with one or more higher-level tags. For example, in a telemedicine application (semantic tag meta-service 1), semantic tags may include patient information (sub-service 1 of semantic tag meta-service 1), doctor qualification requirements (sub-service 2 of semantic tag meta-service 1), medical device type (sub-service 3 of semantic tag meta-service 1), etc.; in a smart home application (semantic tag meta-service 2), semantic tags may include control commands (sub-service 1 of semantic tag meta-service 2), device status (sub-service 2 of semantic tag meta-service 2), environmental parameters (sub-service 3 of semantic tag meta-service 2), etc.; in a video conferencing application, semantic tags may include meeting topic, participant information, video quality requirements, etc. For example, meta-service 1 may include at least one or more of sub-service 1, sub-service 2, and sub-service 3.

[0110] In some implementations, the tag controller dynamically programs the semantic tags according to specific application requirements.

[0111] In some implementations, after receiving the second SIP message sent by the server, the method further includes: if there is no semantic tag in the tag library, then registering the service based on the semantic tag and writing the semantic tag into the tag library.

[0112] In some implementations, when the tag controller receives N semantic tags from the server, it searches and matches them in the tag library. If the semantic tag exists, the tag controller performs service orchestration and service discovery, and writes the semantic tag orchestration result in a third SIP message, which is then sent to the server. If the semantic tag does not exist in the tag library, a new semantic tag is generated, and the new semantic tag is registered for service registration. After service registration, it is written to the tag library. Subsequently, the tag controller performs service orchestration and service discovery, and writes the semantic tag orchestration result in a third SIP message, which is then sent to the server.

[0113] In some implementations, when a user's intent changes during a session, the tag controller is triggered again to rearrange the SIP semantic tags. Subsequently, the server dynamically adjusts session parameters, including bandwidth allocation and media type switching, based on the rearranged semantic tags.

[0114] The technical solution of this application embodiment receives a second SIP message sent by a server. The second SIP message includes N semantic tags corresponding to the user intent information determined based on the user intent information related to the first session. The second SIP message is obtained by encapsulating the N semantic tags into a first SIP message, which carries the user intent information related to the first session. The first SIP message is sent from the terminal to the server; N is a positive integer, and different semantic tags among the N semantic tags correspond to different services. A third SIP message is sent to the server, carrying the arrangement result of the N semantic tags. Thus, the tag controller obtains the third SIP message by arranging the semantic tags and sends it to the server. The server can then determine the target device based on the arrangement result of the semantic tags, automatically understand user intent, automatically process the context of communication content, reduce manual intervention, improve user experience, and adapt to more intelligent application scenarios.

[0115] The technical solutions of the embodiments of this application are illustrated below with specific application examples.

[0116] Based on the foregoing embodiments, the server is a SIP server and the tag controller is a SIP tag controller. It should be noted that the SIP server and SIP tag controller in this application embodiment can be configured separately or combined; this application does not specifically limit this. Based on this, the session management method provided by the embodiments of this application will be further described.

[0117] The main drawbacks of related SIP technologies include: Lack of intelligence: When processing session requests, related SIP protocols lack intelligent understanding and response to user intent and context. For example, a user in a smart home system requests to turn on a light, but the system cannot recognize the user's specific intent and environment (such as room brightness and time), simply executing the light-on operation. In telemedicine applications, a patient requests a consultation, but the system cannot provide the most suitable doctor and service based on the patient's specific needs and condition. Limitations in session management: Related SIP protocols have limitations in session management, particularly in dynamically adjusting and optimizing session parameters. For example, in video conferencing, when network conditions change, the system cannot adjust video quality and bandwidth allocation in a timely manner, leading to a decline in session quality. In telemedicine applications, when switching from video call to screen sharing, the system cannot switch and adjust media types in a timely manner. This application aims to solve the above technical problems by proposing a method for dynamically adjusting and optimizing SIP protocols based on semantic information, combining semantic communication with SIP. The specific description is as follows:

[0118] The embodiment of this application proposes a combination of dynamic semantic communication and SIP. By introducing dynamic semantic tags, intelligent service discovery and selection are achieved, and by dynamically analyzing semantic information, session parameters are adjusted and optimized in real time to enhance session management capabilities. Figure 3 is the third schematic flow diagram of the session management method provided by the embodiment of this application. As shown in Figure 3, the method includes the following steps:

[0119] Step 301: The server decomposes the intention of the SIP session initiated by the user.

[0120] Step 302: The server forms multiple SIP semantic tags according to the intention decomposition information and writes them into the tag controller.

[0121] Step 303: The tag controller arranges and combines the semantic tags in the tag control to achieve intelligent service discovery and selection.

[0122] Step 304: The server performs dynamic session management based on semantic information.

[0123] Specifically, it mainly includes the following technical points:

[0124] (1) Design and combination of user semantic intention and SIP semantic tags

[0125] Programmable semantic tags are embedded in the SIP message header or body to describe the context, intention or content of the communication. For example, semantic information is embedded in the INVITE request to indicate that this is a video conference, medical consultation or emergency call. The definition format of the semantic tag is as follows:

[0126] Service type: Describes the type of service requested, such as remote medical consultation, smart home control, etc.

[0127] Priority: Describes the priority of the request, such as urgent, general, etc.

[0128] Media format: Describes the required media format, such as audio, video, etc.

[0129] Current load status: Describes the load status of the current device or network.

[0130] The definition format of the semantic tag is as follows:

[0131] <SIP semantic tag>

[0132] <Service type>Remote medical< / Service type>

[0133] <Priority>High< / Priority>

[0134] <Media format>Video< / Media format>

[0135] <Current load status>Light / Medium / Heavy< / Current load status>

[0136] < / SIP semantic tag>

[0137] Figure 4 is a schematic flowchart of the arrangement, combination and registration of SIP semantic tags according to the semantic intention of the user provided by an embodiment of the present application. As shown in Figure 4, the following steps are included:

[0138] Step 401: The user initiates a SIP session.

[0139] Step 402: Session semantic analysis, and the session intention is decomposed into tags.

[0140] Step 403: Search and match in the tag library.

[0141] When there is no matching result, steps 404 to 406 are executed, otherwise step 406 is directly executed.

[0142] Step 404: Generate a new SIP semantic tag.

[0143] Step 405: Register the new semantic tag for the service and write it into the tag library.

[0144] Step 406: The SIP tag controller performs service orchestration and service discovery.

[0145] Step 407: Establish the session service.

[0146] Among them, step 402 is executed by the server, and steps 403 to 406 are executed by the tag controller.

[0147] (2) Discovery and selection of dynamic semantic services based on user intentions

[0148] The user session intention can be decomposed into semantic tag meta-services one by one, and the meta-services can be dynamically programmed and combined in the tag controller. The SIP server uses the semantic tags embedded in the SIP message to achieve intelligent service discovery and selection. For example, the semantic tags can be programmed to describe the requirements and parameters of different services such as telemedicine (semantic tag meta-service 1), smart home (semantic tag meta-service 2), video conferencing (semantic tag meta-service 3), etc. The corresponding semantics of each tag can also set sub-semantics corresponding to "sub-services of the semantic tag meta-service" to form a hierarchical semantic tag service system.

[0149] The specific technical solution is as follows:

[0150] Dynamic Semantic Content: The tag controller dynamically programs semantic tags according to specific application requirements. For example, in telemedicine applications (semantic tag meta-service 1), semantic tags can include patient information (sub-service 1 of semantic tag meta-service 1), doctor qualification requirements (sub-service 2 of semantic tag meta-service 1), medical equipment type (sub-service 3 of semantic tag meta-service 1), etc.; in smart home applications (semantic tag meta-service 2), semantic tags can include control commands (sub-service 1 of semantic tag meta-service 2), device status (sub-service 2 of semantic tag meta-service 2), environmental parameters (sub-service 3 of semantic tag meta-service 2), etc.; in video conferencing applications, semantic tags can include meeting topic, participant information, video quality requirements, etc.

[0151] Intelligent service discovery and selection:

[0152] The SIP label controller accepts service registrations from each meta-service and its sub-services, and generates meta-service semantic labels and sub-service labels.

[0153] The SIP server parses the user intent, decomposes the user intent, generates semantic tags, writes them into a SIP message, and sends them to the SIP tag controller.

[0154] The SIP tag controller organizes the user's semantics and sends them to the SIP server. After receiving the SIP message containing the semantic tags, the SIP server parses and understands the semantic content.

[0155] Based on the semantic tags, the SIP server queries the device database and service registry to find the most suitable services and devices. For example, in telemedicine, it finds suitable medical equipment and doctors; in smart homes, it finds corresponding smart devices; and in video conferencing, it finds suitable meeting resources and equipment.

[0156] Based on the description of the semantic tags, the SIP server selects the optimal service and device, and initiates a SIP INVITE request to the relevant device or service provider to notify it of the new operation request.

[0157] Figure 5 is an application embodiment one provided by the present application. As shown in Figure 5, it includes the following steps:

[0158] Step 501: The user terminal sends a SIP INVITE (containing user intent information) to the SIP server.

[0159] The user terminal initiates a SIP request to the SIP server. This request can be sent via SIP INVITE, and the SIP request contains call intent information.

[0160] Step 502: The SIP server performs semantic decomposition based on the user intent information to form SIP semantic tags.

[0161] Step 503: The SIP server sends the SIP INVITE containing the semantic tags to the tag controller.

[0162] Step 504: The tag controller arranges and combines semantic tags.

[0163] Step 505: The tag controller sends the SIP INVITE containing the orchestrated combination to the SIP server.

[0164] Step 506: The SIP server sends a service discovery request to the semantic database (including the service registry).

[0165] Step 507: Semantic database makes semantic decisions: select services and devices.

[0166] Step 508: The semantic database sends the selected services and devices to the SIP server.

[0167] Based on the query results, the semantic database informs the SIP server to select the most suitable service and device.

[0168] In another implementation, the SIP server can directly select target devices and services based on semantic tags.

[0169] Step 509: The SIP server sends a SIP INVITE to the selected service or device.

[0170] The SIP server sends a SIP INVITE request to the selected service or device.

[0171] Step 510: The user terminal sends a semantically changed SIP INVITE to the SIP server.

[0172] Step 511: The SIP server dynamically adjusts the service discovery entry and performs end-to-end service continuity.

[0173] Based on changes in user semantics, the SIP server dynamically adjusts the service discovery entry point and performs end-to-end service continuity. In some embodiments, if the SIP server can recombine the semantic tags corresponding to the new semantic changes based on the previous semantic tags, the SIP server dynamically adjusts the service discovery entry point and performs end-to-end service continuity; otherwise, it needs to regenerate new semantic tags and send them to the tag controller for corresponding semantic tag orchestration.

[0174] Step 512: The service or device sends a SIP 200 OK / ACK to the user terminal.

[0175] The service or device receives and confirms the request, and completes the corresponding operation.

[0176] In this way, the SIP server can dynamically select and discover the optimal service based on the content of the semantic tags, realizing intelligent service discovery and selection to meet the needs of different application scenarios.

[0177] (III) Dynamic Session Management

[0178] This paper addresses the limitations of session management in related technologies by employing a dynamic session management mechanism based on semantic information. The specific technical solution is as follows:

[0179] During a SIP session, continuously analyze and monitor the session status, network conditions, and user needs.

[0180] If the user's intent changes during the session, the SIP tag controller will be triggered again to rearrange the SIP semantic tags and dynamically adjust session parameters, including bandwidth allocation and media type switching.

[0181] Figure 6 is an application embodiment two provided by the present application, taking smart home as an example, as shown in Figure 6, including the following steps:

[0182] Step 601: The user terminal sends a SIP INVITE (containing user intent information) to the SIP server.

[0183] User terminal initiates SIP request: The user initiates a SIP INVITE request through the smart home control terminal. The request contains semantic information of the specific operation (such as controlling the lights "control_lights").

[0184] Step 602: Parse the intent information and generate a tag arrangement service.

[0185] In some embodiments, step 602 is implemented as follows: the SIP server performs semantic decomposition based on user intent information to form SIP semantic tags; the SIP server sends the SIP INVITE containing the semantic tags to the tag controller; the tag controller arranges and combines the semantic tags; the tag controller sends the SIP INVITE containing the arranged and combined tags to the SIP server.

[0186] SIP server parses semantic information: After receiving a request, the SIP server parses the semantic information in the request to understand the user's specific intent (such as controlling the lights).

[0187] Step 603: The SIP server sends a service discovery request to the semantic database.

[0188] Service discovery request: Based on the parsed semantic information, the SIP server sends a service discovery request to the device database to query available smart home devices.

[0189] Step 604: Semantic database performs semantic decision-making: optimal device selection.

[0190] Based on the query results from the device database, the SIP server selects the most suitable smart home device (such as a smart light) to handle the request and sends the most suitable device to the SIP server.

[0191] Step 605: The SIP server sends a SIP INVITE to the selected smart home device.

[0192] The SIP server sends a SIP INVITE request, which means the SIP server sends a SIP INVITE request to the selected smart home device to notify the device that there is a new operation request.

[0193] Step 606: The smart home device sends a SIP 200 OK response to the user terminal.

[0194] The smart home device accepts the request, confirms acceptance of the operation, and sends a SIP 200 OK response to the user terminal to confirm the completion of the operation.

[0195] Step 607: The user terminal sends a SIP ACK to the smart home device.

[0196] The user terminal sends a SIP ACK request to the smart home device. After receiving the SIP 200 OK response, the user terminal sends a SIP ACK request to confirm that the session has officially started.

[0197] Step 608: The SIP server dynamically adjusts session parameters.

[0198] The SIP server dynamically adjusts session parameters based on real-time network and device conditions to ensure the effective transmission of control commands.

[0199] Step 609: The SIP server sends a SIP UPDATE / REINVITE request to the smart home device.

[0200] The SIP server adjusts device parameters. Based on the user's semantic intent (such as adjusting the brightness of lights), the SIP server sends a SIP UPDATE or REINVITE request to update the device parameters.

[0201] Step 610: The user terminal sends real-time semantic information to the SIP server.

[0202] The user terminal transmits real-time semantic information to the SIP server. During operation, the user can send INFO requests to transmit dynamically changing semantic information (such as a temperature adjustment request). The server can generate new semantic tags based on the new semantic information, or obtain the semantic tags corresponding to the new semantic information from previous semantic tags. Then, the SIP server sends new SIP messages to the smart home devices.

[0203] Step 611: The smart home device sends a SIP 200 OK to the user terminal.

[0204] Confirm session establishment: After confirming that the session has been successfully established, the device sends a SIP 200 OK response to the user terminal to notify that the operation is complete and update the status.

[0205] Step 612: Real-time monitoring and dynamic adjustment of the SIP server.

[0206] SIP server real-time monitoring and dynamic adjustment means that the SIP server continuously monitors the session status and network conditions, and dynamically adjusts session parameters (such as light brightness, temperature, etc.) based on real-time analysis results.

[0207] Step 613: The user terminal sends a SIP BYE to the smart home device to terminate the session.

[0208] Terminate Session: The user or device sends a SIP BYE request to terminate the operation connection and confirm the end of the session.

[0209] The technical solution of this application proposes a method for dynamically combining and adjusting SIP semantic information tags based on intent decomposition. The method includes: a SIP server decomposing the SIP session intent into SIP semantic tags, each corresponding to a meta-service; a SIP tag controller orchestrating and combining the SIP semantic tags and sending them to the server; the SIP server parsing the semantic tags and performing intelligent service discovery and selection; and dynamically analyzing semantic information to adjust and optimize session parameters in real time based on the user's semantic intent, including bandwidth allocation and media type switching. The definition format of the SIP semantic tags includes service type, priority, media format, current load status, and user intent. The service corresponding to the SIP semantic tag can also contain sub-services, forming hierarchical service tags for more granular service orchestration and combination. By adding programmable semantic tags to the SIP registration request, the SIP server is intelligently provided with the capabilities and service information of the user terminal and service provider based on semantic changes. A session is initiated through a SIP INVITE request, and the SIP server intelligently performs service discovery and selection based on the parsed programmable semantic tag information and semantic changes. Based on semantics, session parameters are dynamically adjusted via SIP UPDATE or REINVITE requests to ensure communication quality. Semantic information is also transmitted via INFO requests to ensure real-time adjustment of session parameters. The SIP server continuously monitors session status and network conditions, and dynamically adjusts session parameters based on real-time analysis results. This application's embodiments cover various aspects of a semantically information-based dynamic adjustment and optimization method for the SIP protocol, aiming to improve the intelligence level of communication systems and user experience. Specifically, it features protocol scalability: the proposed SIP extension protocol has good compatibility and scalability, adapting to more intelligent application scenarios in the future. The new technology can be applied to more intelligent and complex communication scenarios, such as intelligent customer service, telemedicine, and smart homes, expanding market space. Enhanced intelligence level: by embedding semantic tags, the system can automatically understand and process the context and intent of communication content, reducing manual intervention. Dynamic session management: by analyzing semantic information in real time, the system can dynamically adjust session parameters, improving user experience. Intelligent communication systems can provide higher quality services and increase user satisfaction. Furthermore, communication systems with intelligent and efficient characteristics can gain an advantage in market competition.

[0210] Figure 7 is a schematic diagram of the structure of the dynamic session management device provided in an embodiment of this application, applied to a server. As shown in Figure 7, the dynamic session management device includes:

[0211] The first communication unit 701 is configured to receive a first SIP message sent by the terminal.

[0212] The first processing unit 702 is configured to determine N semantic tags corresponding to the user intent information based on the user intent information related to the first session carried in the first SIP message, and encapsulate the N semantic tags into the first SIP message to obtain the second SIP message, where N is a positive integer; different semantic tags in the N semantic tags correspond to different services.

[0213] The first communication unit 701 is configured to send a second SIP message to the tag controller and receive a third SIP message sent by the tag controller, wherein the third SIP message carries the arrangement result of N semantic tags;

[0214] The first processing unit 702 is configured to determine the target device based on the arrangement result of N semantic tags;

[0215] The first communication unit 701 is configured to send a third SIP message to the target device.

[0216] In some implementations, the semantic tag includes one or more of the following information: the service type associated with the first session, the priority of the service type associated with the first session, the media format required for the first session, and the load status.

[0217] In some embodiments, the first processing unit 702 is configured to select a target device based on the arrangement result of N semantic tags, wherein the target device is a device capable of processing the service corresponding to the arrangement result; or, send the arrangement result of N semantic tags to a semantic database, wherein the arrangement result of N semantic tags is used by the semantic database to select a target device; and receive indication information of the target device sent by the semantic database, wherein the target device is a device capable of processing the service corresponding to the arrangement result.

[0218] In some implementations, the first SIP message also carries session parameters of the first session; the first processing unit 702 is configured to monitor network conditions and / or the device status of the target device; and adjust the session parameters according to the network conditions and / or the device status of the target device; the first communication unit 701 is configured to send a fourth SIP message to the target device, the fourth SIP message carrying the adjusted session parameters.

[0219] In some implementations, the first communication unit 701 is configured to receive a fifth SIP message sent by a terminal, the fifth SIP message carrying updated user intent information; the first processing unit 701 is configured to determine M semantic tags corresponding to the updated user intent information and update the orchestration result according to the M semantic tags; the first communication unit 701 is configured to send a sixth SIP message to a target device, the sixth SIP message carrying the updated orchestration result.

[0220] Those skilled in the art should understand that the functions of each unit in the dynamic session management device shown in Figure 7 can be understood with reference to the relevant description of the aforementioned method. The functions of each unit in the dynamic session management device shown in Figure 7 can be implemented by a program running on a processor, or by specific logic circuits.

[0221] Figure 8 is a schematic diagram of the structure of the dynamic session management device provided in this application embodiment, applied to a tag controller. As shown in Figure 8, the dynamic session management device includes:

[0222] The second communication unit 801 is configured to receive a second SIP message sent by a server. The second SIP message includes N semantic tags corresponding to the user intent information determined based on the user intent information related to the first session. The second SIP message is obtained by encapsulating the N semantic tags into a first SIP message. The first SIP message carries the user intent information related to the first session. The first SIP message is sent from the terminal to the server. N is a positive integer, and different semantic tags in the N semantic tags correspond to different services.

[0223] The second processing unit 802 is configured to arrange N semantic tags to obtain an arrangement result of N semantic tags;

[0224] The second communication unit 803 is configured to send a third SIP message to the server, wherein the third SIP message carries the arrangement result of N semantic tags.

[0225] In some implementations, the semantic tag includes one or more of the following information: the service type associated with the first session, the priority of the service type associated with the first session, the media format required for the first session, and the load status.

[0226] In some embodiments, the apparatus further includes: a first registration unit 803; the first registration unit 803 is configured to, after receiving a second SIP message sent by the server, perform service registration based on the semantic tag if there is no semantic tag in the tag library, and write the semantic tag into the tag library.

[0227] Those skilled in the art should understand that the functions of each unit in the dynamic session management device shown in Figure 8 can be understood with reference to the relevant description of the aforementioned method. The functions of each unit in the dynamic session management device shown in Figure 8 can be implemented by a program running on a processor, or by specific logic circuits.

[0228] Figure 9 is a schematic structural diagram of a dynamic session management device 900 provided in an embodiment of this application. The dynamic session management device can be a server or a tag controller. The dynamic session management device 900 shown in Figure 9 includes a processor 910, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0229] Optionally, as shown in FIG9, the dynamic session management device 900 may further include a memory 920. The processor 910 may retrieve and run computer programs from the memory 920 to implement the methods described in the embodiments of this application.

[0230] The memory 920 can be a separate device independent of the processor 910, or it can be integrated into the processor 910.

[0231] Optionally, as shown in FIG9, the dynamic session management device 900 may further include a transceiver 930, which the processor 910 may control to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0232] The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include antennas, and the number of antennas may be one or more.

[0233] Optionally, the dynamic session management device 900 may specifically be a server in the embodiments of this application, and the dynamic session management device 900 may implement the corresponding processes implemented by the server in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0234] Optionally, the dynamic session management device 900 may specifically be a tag controller in the embodiments of this application, and the dynamic session management device 900 may implement the corresponding processes implemented by the tag controller in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0235] Figure 10 is a schematic structural diagram of a chip according to an embodiment of this application. The chip 1000 shown in Figure 10 includes a processor 1010, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0236] Optionally, as shown in FIG10, chip 1000 may further include memory 1020. Processor 1010 can call and run computer programs from memory 1020 to implement the methods in the embodiments of this application.

[0237] The memory 1020 can be a separate device independent of the processor 1010, or it can be integrated into the processor 1010.

[0238] Optionally, the chip 1000 may also include an input interface 1030. The processor 1010 can control the input interface 1030 to communicate with other devices or chips, specifically, to acquire information or data sent by other devices or chips.

[0239] Optionally, the chip 1000 may also include an output interface 1040. The processor 1010 can control the output interface 1040 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0240] Optionally, the chip can be applied to the server in the embodiments of this application, and the chip can implement the corresponding processes implemented by the server in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0241] Optionally, the chip can be applied to the tag controller in the embodiments of this application, and the chip can implement the corresponding processes implemented by the tag controller in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0242] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0243] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0244] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0245] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0246] This application also provides a computer program product, including a computer program.

[0247] Optionally, the computer program product can be applied to the server in the embodiments of this application, and when the computer program is executed by the processor, it implements the corresponding processes implemented by the server in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0248] Optionally, the computer program product can be applied to the tag controller in the embodiments of this application, and when the computer program is executed by the processor, it implements the corresponding processes implemented by the tag controller in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0249] This application also provides a computer-readable storage medium for storing computer programs.

[0250] Optionally, the computer-readable storage medium can be applied to the server in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the server in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0251] Optionally, the computer-readable storage medium can be applied to the tag controller in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the tag controller in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0252] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software 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.

[0253] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0254] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of 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 system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0255] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0256] In addition, 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.

[0257] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to related technologies, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0258] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology 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 session management method applied to a server, the method comprising: The receiving terminal sends a first SIP message, determines N semantic tags corresponding to the user intent information based on the first session-related user intent information carried in the first SIP message, and encapsulates the N semantic tags into the first SIP message to obtain a second SIP message, where N is a positive integer; Different semantic tags among the N semantic tags correspond to different services; The second SIP message is sent to the tag controller, and the third SIP message sent by the tag controller is received. The third SIP message carries the arrangement result of the N semantic tags. The target device is determined based on the arrangement of the N semantic tags, and the third SIP message is sent to the target device.

2. The method according to claim 1, wherein, The semantic tag includes one or more of the following information: the service type related to the first session, the priority of the service type related to the first session, the media format required by the first session, and the load status.

3. The method according to claim 1, wherein, The step of determining the target device based on the arrangement of the N semantic tags includes: A target device is selected based on the arrangement result of the N semantic tags, wherein the target device is a device capable of processing the service corresponding to the arrangement result; or... The arrangement result of the N semantic tags is sent to the semantic database, and the arrangement result of the N semantic tags is used by the semantic database to select a target device; the indication information of the target device sent by the semantic database is received, and the target device is a device that can process the service corresponding to the arrangement result.

4. The method according to any one of claims 1 to 3, wherein, The first SIP message also carries session parameters of the first session; the method further includes: Monitor network conditions and / or the device status of the target device; Adjust the session parameters based on the network conditions and / or the device status of the target device; A fourth SIP message is sent to the target device, the fourth SIP message carrying the adjusted session parameters.

5. The method according to any one of claims 1 to 3, wherein, The method further includes: Receive a fifth SIP message sent by the terminal, the fifth SIP message carrying updated user intent information; Determine M semantic tags corresponding to the updated user intent information, and update the arrangement result based on the M semantic tags; A sixth SIP message is sent to the target device, the sixth SIP message carrying the updated orchestration result.

6. A dynamic session management method applied to a tag controller, the method comprising: The system receives a second SIP message sent by a server. The second SIP message includes N semantic tags corresponding to the user intent information determined based on the user intent information related to the first session. The second SIP message is obtained by encapsulating the N semantic tags into a first SIP message. The first SIP message carries the user intent information related to the first session. The first SIP message is sent from the terminal to the server. N is a positive integer, and different semantic tags in the N semantic tags correspond to different services. The N semantic tags are arranged to obtain the arrangement result of N semantic tags; A third SIP message is sent to the server, wherein the third SIP message carries the arrangement result of the N semantic tags.

7. The method according to claim 6, wherein, The semantic tag includes one or more of the following information: the service type related to the first session, the priority of the service type related to the first session, the media format required by the first session, and the load status.

8. The method according to claim 6, wherein, After receiving the second SIP message sent by the server, the method further includes: If the semantic tag does not exist in the tag library, then service registration is performed based on the semantic tag, and the semantic tag is written into the tag library.

9. A dynamic session management device, applied to a server, the device comprising: The first communication unit is configured to receive the first SIP message sent by the terminal. The first processing unit is configured to determine N semantic tags corresponding to the user intent information based on the first session-related user intent information carried in the first SIP message, and encapsulate the N semantic tags into the first SIP message to obtain a second SIP message, where N is a positive integer; Different semantic tags among the N semantic tags correspond to different services; The first communication unit is configured to send the second SIP message to the tag controller and receive a third SIP message sent by the tag controller, wherein the third SIP message carries the arrangement result of the N semantic tags; The first processing unit is configured to determine the target device based on the arrangement result of the N semantic tags; The first communication unit is configured to send the third SIP message to the target device.

10. A dynamic session management device, applied to a tag controller, the device comprising: The second communication unit is configured to receive a second SIP message sent by a server. The second SIP message includes N semantic tags corresponding to the user intent information determined based on the user intent information related to the first session. The second SIP message is obtained by encapsulating the N semantic tags into a first SIP message. The first SIP message carries the user intent information related to the first session. The first SIP message is sent from the terminal to the server. N is a positive integer, and different semantic tags in the N semantic tags correspond to different services. The second processing unit is configured to arrange the N semantic tags to obtain an arrangement result of N semantic tags; The second communication unit is configured to send a third SIP message to the server, wherein the third SIP message carries the arrangement result of the N semantic tags.

11. A dynamic session management device, comprising: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 8.

12. A computer program product, comprising: A computer program that, when executed by a processor, implements the method according to any one of claims 1 to 8.

13. A computer-readable storage medium for storing a computer program that causes a computer to perform the method as described in any one of claims 1 to 8.

Images