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

Abstract

The invention discloses a session management method and device, equipment, a program product and a storage medium, and the method comprises the steps: receiving a first SIP message sent by a terminal, determining N semantic tags corresponding to user intention information according to the user intention information related to a first session carried by the first SIP message, n semantic tags are received, the N semantic tags are packaged into the first SIP message, a second SIP message is obtained, and 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 label controller, a third SIP message sent by the label controller is received, and the third SIP message carries arrangement results of the N semantic labels; and determining a target device according to the arrangement result of the N semantic tags, and sending the third SIP message to the target device.

Description

Technical Field

[0001] The present application relates to the field of core network technology, and in particular to a session management method and apparatus, equipment, program product, and storage medium. Background Art

[0002] Currently, Session Initiation Protocol (SIP) is widely used in real-time communications, such as Voice over Internet Protocol (VoIP) and video conferencing. SIP is mainly used to establish, modify and terminate multimedia sessions. However, existing SIP technology lacks intelligence and has certain limitations. Summary of the invention

[0003] To solve the above technical problems, the present application provides a session management method and apparatus, equipment, program product, and storage medium.

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

[0005] receiving a first SIP message sent by a terminal, determining N semantic tags corresponding to the user intent information according to the user intent information related to the first session carried in the first SIP message, and encapsulating 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;

[0006] Sending a second SIP message to the label controller, and receiving a third SIP message sent by the label controller, where the third SIP message carries the arrangement result of the N semantic labels;

[0007] The target device is determined according to the arrangement result of the N semantic tags, and a third SIP message is sent to the target device.

[0008] The session management method provided by the present application is applied to a tag controller, and the method includes:

[0009] receiving 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, and 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 among the N semantic tags correspond to different services;

[0010] Arrange the N semantic labels to obtain arrangement results of N semantic labels;

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

[0012] The dynamic session management device provided by the present application is applied to a server, and the device includes:

[0013] A first communication unit, configured to receive a first SIP message sent by a terminal;

[0014] A first processing unit is used to determine N semantic tags corresponding to the user intent information according to 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 a second SIP message, where N is a positive integer; different semantic tags in the N semantic tags correspond to different services;

[0015] The first communication unit is further 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 the N semantic tags;

[0016] The first processing unit is further used to determine the target device according to the arrangement result of the N semantic tags;

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

[0018] The session management device provided by the present application is applied to a tag controller, and the device includes:

[0019] a second communication unit, configured to 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 among the N semantic tags correspond to different services;

[0020] A second processing unit is used to arrange the N semantic tags to obtain arrangement results of the N semantic tags;

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

[0022] The dynamic session management device provided in the present application includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute any one of the above-mentioned dynamic session management methods.

[0023] A computer program product provided by the present application includes: a computer program, and the computer program implements any one of the above methods when executed by a processor.

[0024] The computer-readable storage medium provided in the present application is used to store a computer program, and the computer program enables a computer to execute any one of the above methods.

[0025] In the technical solution of the present application, the first SIP message sent by the receiving terminal is determined, 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, and the N semantic tags are 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 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 result of the N semantic tags, and the third SIP message is sent to the target device. In this way, the server can automatically understand the user's intent and automatically process the context of the communication content through the embedded semantic tags and the determination of the target device based on the arranged semantic tags, thereby reducing manual intervention, improving the user experience, and adapting to more intelligent application scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 This is a flow diagram of the session management method provided in the embodiment of the present application. Figure 1 ;

[0027] Figure 2 This is a flow diagram of the session management method provided in the embodiment of the present application. Figure 2 ;

[0028] Figure 3 This is a flow diagram of the session management method provided in the embodiment of the present application. Figure 3 ;

[0029] Figure 4 It is a flowchart of arranging, combining and registering SIP semantic tags according to user semantic intent provided by an embodiment of the present application;

[0030] Figure 5 This is the first application example provided by the present application example;

[0031] Figure 6This is the second application example provided by the present application example;

[0032] Figure 7 The structure of the dynamic session management device provided in the embodiment of the present application is shown in FIG. Figure 1 ;

[0033] Figure 8 The structure of the dynamic session management device provided in the embodiment of the present application is shown in FIG. Figure 2 ;

[0034] Fig. 9 is a schematic structural diagram of a dynamic session management device provided in an embodiment of the present application;

[0035] Fig.10 It is a schematic structural diagram of the chip of an embodiment of the present application. DETAILED DESCRIPTION

[0036] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0037] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it will be 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.

[0038] It should also be pointed out that the terms "first\second\third" involved in the embodiments of the present application are only used to distinguish similar objects and do not represent a specific ordering of the objects. It can be understood that "first\second\third" can be interchanged in a specific order or sequence where permitted, so that the embodiments of the present application described here can be implemented in an order other than that illustrated or described here.

[0039] The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that there may be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the objects associated before and after are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0040] Currently, SIP is widely used in real-time communications, such as VoIP and video conferencing. The SIP protocol is mainly used to establish, modify and terminate multimedia sessions. The existing SIP technology mainly includes the following parts:

[0041] Session establishment: A session is initiated through a SIP INVITE request, which includes basic session parameters (such as media type and bandwidth requirements).

[0042] Session modification: adjust session parameters through SIP UPDATE or REINVITE requests.

[0043] Session termination: The session is terminated through a SIP BYE request.

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

[0045] The shortcomings of the existing SIP technology mainly include: Lack of intelligence: The existing SIP protocol lacks intelligent understanding and response to user intentions and context when processing session requests. For example: the user sends a request to turn on the light in the smart home system, but the system cannot recognize the user's specific intentions and environment (such as the brightness and time of the room), and simply performs the light-on operation. In telemedicine applications, patients send consultation requests, but the system cannot provide the most suitable doctors and services based on the patient's specific needs and condition. Limitations of session management: The existing SIP protocol has some limitations in session management, especially in dynamically adjusting and optimizing session parameters. For example: in a video conference, when the network conditions change, the system cannot adjust the video quality and bandwidth allocation in time, resulting in a decrease in session quality. In telemedicine applications, when it is necessary to switch from a video call to screen sharing, the system cannot switch and adjust the media type in time, so 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 of the embodiments of the present application are proposed.

[0046] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0047] It should be noted that the server and tag controller in this application can be set separately or combined, and this application does not make specific restrictions on this. In other words, some or all steps related to the tag controller can be executed by the server, and some or all steps related to the server can also be executed by the tag controller.

[0048] Figure 1 This is a flow diagram of the session management method provided in the embodiment of the present application. Figure 1 , applied to the server, such as Figure 1 As shown, the session management method includes the following steps:

[0049] Step 101: Receive a first SIP message sent by a terminal, 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 a second SIP message, where N is a positive integer; different semantic tags among the N semantic tags correspond to different services.

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

[0051] Step 103: Determine a target device according to the arrangement results of the N semantic tags, and send a third SIP message to the target device.

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

[0053] In some embodiments, the server receives a first SIP message sent by a terminal, the first SIP message carries user intent information related to a first session, the server decomposes the user intent information, forms N semantic tags corresponding to the user intent information according to the intent decomposition information, and encapsulates the N semantic tags into the first SIP message to obtain a second SIP message, wherein 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 sent by the tag controller is received, wherein the third SIP message carries the arrangement result of the N semantic tags, and then the server determines the target device according to the arrangement result of the N semantic tags, and sends the third SIP message to the target device.

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

[0055] In some embodiments, when the label controller receives N semantic labels sent by the server, it looks up 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 service registration is performed on the new semantic label. After service registration, it is written into the label library. Then, the label controller performs server orchestration and service discovery, and writes the orchestration of the semantic label in the third SIP message and sends it to the server.

[0056] 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.

[0057] In some embodiments, programmable semantic labels are embedded 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.

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

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

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

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

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

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

[0064] <SIP semantic label>

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

[0066] <Priority>High< / Priority>

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

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

[0069] < / SIP semantic label>

[0070] In some embodiments, the tag controller dynamically programs and combines 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 intention can be decomposed into semantic tag meta-services, and the meta-services can be dynamically programmed and combined in 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). The semantics corresponding to each tag can also set sub-semantics corresponding to the "sub-service of the semantic tag meta-service" to form a hierarchical semantic tag service system.

[0071] In some implementations, the semantic tags may be arranged according to the contents of the N semantic tags.

[0072] In some embodiments, the N semantic tags include multiple levels of tags, and one or more tags of the next level are associated with one or more tags of the previous level. Exemplarily, in telemedicine applications (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 smart home applications (semantic tag meta-service 2), semantic tags may include control instructions (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 may include conference topics, participant information, video quality requirements, etc. Exemplarily, meta-service 1 may include at least one or more of sub-service 1, sub-service 2, and sub-service 3.

[0073] In some embodiments, determining a target device based on the orchestration results of N semantic tags includes: selecting a target device based on the orchestration results of the N semantic tags, where the target device is a device that can process a service corresponding to the orchestration results; or, sending the orchestration results of the N semantic tags to a semantic database, where the orchestration results of the N semantic tags are used by the semantic database to select a target device; and receiving indication information of the target device sent by the semantic database, where the target device is a device that can process the service corresponding to the orchestration results.

[0074] In some embodiments, the server can directly select the optimal service or device (target device) based on the arrangement results of N semantic tags and the descriptions of N semantic tags, and initiate a request to the target device or service provider to notify it of a new operation request. Alternatively, the server sends the arrangement results of N semantic tags to the semantic database, and the arrangement results of N semantic tags are used by the semantic database to select the target device. After the semantic database selects the target device, it sends indication information of the target device to the server. The target device is a device that can process the service corresponding to the arrangement result. For example, in telemedicine, find suitable medical equipment and doctors; in smart homes, find corresponding smart devices; in video conferencing, find suitable conference resources and equipment.

[0075] In some embodiments, the first SIP message also carries session parameters of the first session; the method further includes: monitoring network conditions and / or device status of the target device; adjusting the session parameters according to the network conditions and / or 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.

[0076] In some implementations, the first SIP message carries the session parameters of the first session, and the server detects the network status and / or the device status of the target device, and adjusts the session parameters of the first session according to the network status and / or the device status of the target device; thereafter, the server sends a fourth SIP message carrying the adjusted session parameters to the target device, and the target device updates the device parameters according to the fourth SIP message. Exemplarily, the fourth SIP message may be a SIP UPDATE or a REINVITE. In this way, effective transmission of the command is ensured.

[0077] In some embodiments, the method further includes: receiving a fifth SIP message sent by the 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 according to the M semantic tags; and sending a sixth SIP message to the target device, the sixth SIP message carrying the updated orchestration result.

[0078] In some embodiments, the server receives a fifth SIP message sent by the terminal, the fifth SIP message carrying updated user intent information; the server determines M semantic tags corresponding to the updated user intent information, and updates the orchestration result according to the M semantic tags; and sends a sixth SIP message to the target device, the sixth SIP message carrying the updated orchestration result.

[0079] In some embodiments, when the M semantic tags determined by the server cannot be combined or directly obtained from the aforementioned N semantic tags, they need to be sent to the tag controller. The tag controller arranges them according to the M semantic tags, carries the arranged results in a SIP message, and sends it to the server. The server selects a target device and / or service based on the SIP message.

[0080] 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 connection.

[0081] In some implementations, the fifth SIP message may be a SIP INFO, and the terminal may send an INFO request to transmit dynamically changing semantic information.

[0082] In some implementations, when the user intent changes during a session, the tag controller is triggered again to rearrange the SIP semantic tags. Then, the server dynamically adjusts session parameters according to the rearranged semantic tags, including bandwidth allocation, media type switching, etc.

[0083] The technical solution of the embodiment of the present application is to receive the first SIP message sent by the terminal, and determine the user intent information related to the first session carried by the first SIP message; determine N semantic tags corresponding to the user intent information, 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; send the second SIP message to the tag controller, receive the third SIP message sent by the tag controller, and the third SIP message carries the arrangement result of the N semantic tags; determine the target device according to the arrangement result of the N semantic tags, and send the third SIP message to the target device. The server can automatically understand the user's intent and automatically process the context of the communication content by embedding the semantic tags and determining the target device according to the arranged semantic tags, thereby reducing manual intervention, improving the user experience, and adapting to more intelligent application scenarios.

[0084] Figure 2 This is a flow diagram of the session management method provided in the embodiment of the present application. Figure 2 , applied to the label controller, such as Figure 2 As shown, the session management method includes the following steps:

[0085] 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, and the second SIP message is obtained by encapsulating the N semantic tags into the first SIP message, and 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 among the N semantic tags correspond to different services.

[0086] Step 202: Arrange the N semantic tags to obtain arrangement results of N semantic tags.

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

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

[0089] In some embodiments, the server receives a first SIP message sent by a terminal, the first SIP message carries user intent information related to a first session, the server decomposes the user intent information, forms N semantic tags corresponding to the user intent information according to the intent decomposition information, and encapsulates the N semantic tags into the first SIP message to obtain a second SIP message, wherein 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, the tag controller receives the second SIP message sent by the server, and arranges the N semantic tags to obtain an arrangement result of the 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, after which the server determines the target device according to the arrangement result of the N semantic tags, and sends the third SIP message to the target device.

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

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

[0092] In some embodiments, programmable semantic tags are embedded 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, medical consultation, or emergency call.

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

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

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

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

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

[0098] Exemplarily, the definition format of the semantic tag is as follows:

[0099] <SIP semantic tag>

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

[0101] <Priority>High< / Priority>

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

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

[0104] < / SIP semantic tag>

[0105] 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 individual semantic tag meta-services, and the meta-services 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 sub-semantics corresponding to each tag can also be set to "sub-services of the semantic tag meta-service" to form a hierarchical semantic tag service system.

[0106] In some embodiments, the semantic tags can be arranged according to the content of the N semantic tags.

[0107] In some embodiments, the N semantic tags include multiple levels of tags, and one or more tags of the next level are associated with one or more tags of the previous level. Exemplarily, in telemedicine applications (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 smart home applications (semantic tag meta-service 2), semantic tags may include control instructions (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 may include conference topics, participant information, video quality requirements, etc. Exemplarily, meta-service 1 may include at least one or more of sub-service 1, sub-service 2, and sub-service 3.

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

[0109] In some implementations, 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, registering a service according to the semantic tag and writing the semantic tag into the tag library.

[0110] In some embodiments, after the tag controller receives N semantic tags sent by the server, it searches and matches from the tag library. If the semantic tag exists, the tag controller performs service orchestration and service discovery, and writes the orchestration of the semantic tag in a third SIP message and sends it 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. After the service is registered, it is written into the tag library. After that, the tag controller performs server orchestration and service discovery, and writes the orchestration of the semantic tag in a third SIP message and sends it to the server.

[0111] In some implementations, when the user intent changes during a session, the tag controller is triggered again to rearrange the SIP semantic tags. Then, the server dynamically adjusts session parameters according to the rearranged semantic tags, including bandwidth allocation, media type switching, etc.

[0112] The technical solution of the embodiment of the present application is to receive a second SIP message sent by a 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, and the second SIP message is obtained by encapsulating the N semantic tags into the first SIP message, and 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 among the N semantic tags correspond to different services. A third SIP message is sent to the server, wherein the third SIP message carries the arrangement result of the N semantic tags. In this way, the tag controller obtains the third SIP message by arranging the semantic tags and sends it to the server, so that the server can determine the target device according to the arrangement result of the semantic tags, automatically understand the user intent, automatically process the context of the communication content, reduce manual intervention, and improve the user experience. At the same time, it can also adapt to more intelligent application scenarios.

[0113] The technical solution of the embodiment of the present application is illustrated below with reference to specific application examples.

[0114] Based on the above embodiment, the server is a SIP server and the tag controller is a SIP tag controller. It should be noted that the SIP server and the SIP tag controller in the embodiment of the present application can be set separately or combined, and the present application does not make specific limitations on this. Based on this, the session management method provided in the embodiment of the present application is further described.

[0115] The shortcomings of existing SIP technology mainly include: Lack of intelligence: The existing SIP protocol lacks intelligent understanding and response to user intentions and context when processing session requests. For example: A user sends a request to turn on the lights in a smart home system, but the system cannot recognize the user's specific intentions and environment (such as the brightness and time of the room), and simply performs the light-on operation. In telemedicine applications, patients send consultation requests, but the system cannot provide the most suitable doctors and services based on the patient's specific needs and condition. Limitations of session management: The existing SIP protocol has some limitations in session management, especially in dynamically adjusting and optimizing session parameters. For example: In a video conference, when the network conditions change, the system cannot adjust the video quality and bandwidth allocation in time, resulting in a decrease in session quality. In telemedicine applications, when it is necessary to switch from a video call to screen sharing, the system cannot switch and adjust the media type in time. The embodiment of the present application aims to solve the above-mentioned technical problems, proposes to combine semantic communication with SIP, and provides a SIP protocol dynamic adjustment and optimization method based on semantic information. The specific description is as follows:

[0116] An embodiment of the present 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 It is a flowchart of the session management method provided by the embodiment of the present application Figure 3 , such as Figure 3 shown, including the following steps:

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

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

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

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

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

[0122] (1) Design and combination of user semantic intent and SIP semantic tags

[0123] Embed programmable semantic tags in the SIP message header or body to describe the context, intent, or content of the communication. For example, embed semantic information 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:

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

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

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

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

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

[0129] <SIP semantic tag>

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

[0131] <Priority>High< / Priority>

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

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

[0134] < / SIP semantic tag>

[0135] Figure 4 It is a schematic flow chart for arranging, combining and registering SIP semantic tags according to the semantic intention of users provided by the embodiments of the present application. As Figure 4 shown, it includes the following steps:

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

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

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

[0139] When there is no matching result, execute Step 404 to Step 406, otherwise directly execute Step 406.

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

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

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

[0143] Step 407: Establish a session service.

[0144] Among them, Step 402 is executed by the server, and Steps 403 to 406 are executed by the tag controller.

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

[0146] 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 be set with sub-semantics corresponding to "sub-services of the semantic tag meta-service" to form a hierarchical semantic tag service system.

[0147] The specific technical solution is as follows:

[0148] Dynamic semantic content: The tag controller dynamically programs semantic tags according to specific application requirements. For example, in telemedicine applications (semantic tag metaservice 1), semantic tags can include patient information (subservice 1 of semantic tag metaservice 1), doctor qualification requirements (subservice 2 of semantic tag metaservice 1), medical device type (subservice 3 of semantic tag metaservice 1), etc.; in smart home applications (semantic tag metaservice 2), semantic tags can include control instructions (subservice 1 of semantic tag metaservice 2), device status (subservice 2 of semantic tag metaservice 2), environmental parameters (subservice 3 of semantic tag metaservice 2), etc.; in video conferencing applications, semantic tags can include meeting topics, participant information, video quality requirements, etc.

[0149] Intelligent service discovery and selection:

[0150] The SIP tag controller accepts service registrations of each meta-service and its sub-services, and forms meta-service semantic tags and sub-service tags.

[0151] The SIP server parses the user's intent, decomposes the user's intent, generates a semantic tag, writes it into the SIP message, and sends it to the SIP tag controller.

[0152] The SIP tag controller composes the user semantics and sends it to the SIP server. After receiving the SIP message containing the semantic tag, the SIP server parses and understands the semantic content.

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

[0154] The SIP server selects the best service and device based on the description of the semantic tag, and initiates a SIP INVITE request to the relevant device or service provider to notify it of a new operation request.

[0155] Figure 5 This is the first application example provided by the present application example. Figure 5 As shown, the following steps are included:

[0156] Step 501: The user terminal sends a SIP INVITE (including user intention information) to the SIP server.

[0157] The user terminal initiates a SIP request to the SIP server. The request may be sent via a SIP INVITE, wherein the SIP request includes call intention information.

[0158] Step 502: The SIP server performs semantic decomposition according to the user intention information to form a SIP semantic tag.

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

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

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

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

[0163] Step 507: Semantic database makes semantic decisions: selects services and devices

[0164] Step 508: The semantic database sends the selected service and device to the SIP server.

[0165] The semantic database tells the SIP server to select the most suitable service and device based on the query results.

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

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

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

[0169] Step 510: The user terminal sends a SIP INVITE with semantic changes to the SIP server.

[0170] Step 511: The SIP server dynamically adjusts the service discovery entry and operates to perform end-to-end service connection.

[0171] According to the user semantic change, the SIP server dynamically adjusts the service discovery entry and operates to perform end-to-end service continuation. Exemplarily, if the SIP server can reassemble the semantic tag corresponding to the new semantic change based on the previous semantic tag, the SIP server dynamically adjusts the service discovery entry and operates to perform end-to-end service continuation, otherwise it needs to regenerate a new semantic tag and send it to the tag controller for the arrangement of the corresponding semantic tag.

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

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

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

[0175] (III) Dynamic Session Management

[0176] The limitations of session management in the prior art are solved through a dynamic session management mechanism based on semantic information. The specific technical solution is as follows:

[0177] During the SIP session, the session status, network conditions and user needs are continuously analyzed and monitored.

[0178] If the user intent changes during a 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.

[0179] Figure 6 This is the second application example provided by the present application embodiment, taking smart home as an example. Figure 6 As shown, the following steps are included:

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

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

[0182] Step 602: parse the intent information and form a tag arrangement service.

[0183] Specifically, step 602 is implemented in the following manner: the SIP server performs semantic decomposition according to the user intent information to form a SIP semantic tag; the SIP server sends the SIP INVITE containing the semantic tag 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.

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

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

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

[0187] Step 604: The semantic database performs semantic decision making: optimal device selection.

[0188] Based on the query results of the device database, the SIP server selects the smart home device (such as a smart light) that is most suitable for processing the request and sends the most suitable device to the SIP server.

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

[0190] The SIP server sends a SIP INVITE request, that is, the SIP server sends a SIP INVITE request to the selected smart home device to notify the device of a new operation request.

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

[0192] The smart home device accepts the request. After receiving the request, the smart home device confirms acceptance of the operation and sends a SIP 200OK response to the user terminal to confirm that the operation is completed.

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

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

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

[0196] The SIP server dynamically adjusts session parameters, that is, according to the real-time network status and device status, the SIP server dynamically adjusts session parameters to ensure the effective transmission of control commands.

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

[0198] The SIP server adjusts the device parameters. According to the user's semantic intention (such as adjusting the light brightness), the SIP server sends a SIP UPDATE or REINVITE request to update the device parameters.

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

[0200] The user terminal transmits real-time semantic information to the SIP server. During operation, the user can send an INFO request to transmit dynamically changing semantic information (such as a temperature adjustment request). The server can generate a new semantic tag based on the new semantic information, or obtain the semantic tag corresponding to the new semantic information from the previous semantic tag, and then the SIP server sends a new SIP message to the smart home device.

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

[0202] Confirm session establishment: After the device confirms that the session is successfully established, it sends a SIP 200OK response to the user terminal to notify the completion of the operation and update the status.

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

[0204] Real-time monitoring and dynamic adjustment of SIP server, that is, SIP server continuously monitors session status and network conditions, and dynamically adjusts session parameters (such as light brightness, temperature, etc.) according to real-time analysis results.

[0205] Step 613: The user terminal sends a SIP BYE message to the smart home device: terminating the session.

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

[0207] The technical solution of the embodiment of the present application proposes a method for dynamically combining and adjusting SIP semantic information tags of intention decomposition, including: the SIP server can decompose the SIP session intention into SIP semantic tags, each SIP semantic tag corresponds to a meta-service; the SIP tag controller arranges and combines the SIP semantic tags and sends them to the server; the SIP server parses the semantic tags, and the SIP server performs intelligent service discovery and selection; the semantic information is dynamically analyzed, and the session parameters are adjusted and optimized in real time according to the user's semantic intention, including bandwidth allocation and media type switching. Among them, the definition format of the SIP semantic tag includes service type, priority, media format, current load status and user intention; the service corresponding to the SIP semantic tag can also include sub-services to form a hierarchical service tag for more detailed service arrangement and combination. By adding programmable semantic tags to the SIP registration request, the capabilities and service information of the user terminal and service provider are intelligently provided to the SIP server according to the semantic changes. A session is initiated by a SIP INVITE request, and the SIP server intelligently discovers and selects services according to the semantic changes based on the parsed programmable semantic tag information. Based on semantics, session parameters are dynamically adjusted through SIP UPDATE or REINVITE requests to ensure communication quality. Based on semantics, dynamically changing semantic information is transmitted through INFO requests to ensure real-time adjustment of session parameters. The SIP server continuously monitors the session status and network status, and dynamically adjusts session parameters based on semantics according to real-time analysis results. The embodiments of this application cover various aspects of the SIP protocol dynamic adjustment and optimization method based on semantic information, aiming to improve the intelligence level and user experience of the communication system. Specifically, it has protocol extensibility: the proposed SIP extension protocol has good compatibility and extensibility, and can adapt 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 home, to expand the market space. Improved intelligence level: By embedding semantic tags, the system can automatically understand and process the context and intent of the communication content, reducing manual intervention. Dynamic session management: By analyzing semantic information in real time, the system can dynamically adjust session parameters to improve user experience. Intelligent communication systems can provide higher quality services and improve user satisfaction. In addition, communication systems with intelligent and efficient characteristics can gain advantages in market competition.

[0208] Figure 7 The structure of the dynamic session management device provided in the embodiment of the present application is shown in FIG. Figure 1 , applied to the server, such as Figure 7 As shown, the dynamic session management device includes:

[0209] The first communication unit 701 is used to receive a first SIP message sent by a terminal;

[0210] The first processing unit 702 is used to determine N semantic tags corresponding to the user intent information according to 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 a second SIP message, where N is a positive integer; different semantic tags in the N semantic tags correspond to different services;

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

[0212] The first processing unit 702 is further configured to determine a target device according to the arrangement result of the N semantic tags;

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

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

[0215] In some embodiments, the first processing unit 702 is configured to select a target device according to the orchestration results of the N semantic tags, where the target device is a device that can process the service corresponding to the orchestration results; or, send the orchestration results of the N semantic tags to a semantic database, where the orchestration results of the N semantic tags are used by the semantic database to select a target device; and receive indication information of the target device sent by the semantic database, where the target device is a device that can process the service corresponding to the orchestration results.

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

[0217] In some implementations, the first communication unit 701 is used to receive a fifth SIP message sent by the terminal, the fifth SIP message carrying updated user intent information; the first processing unit 701 is used 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 used to send a sixth SIP message to the target device, the sixth SIP message carrying the updated orchestration result.

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

[0219] Figure 8 The structure of the dynamic session management device provided in the embodiment of the present application is shown in FIG. Figure 2 , applied to the label controller, such as Figure 8 As shown, the dynamic session management device includes:

[0220] The second communication unit 801 is used to 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, and the second SIP message is obtained by encapsulating the N semantic tags into the first SIP message, and 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;

[0221] The second processing unit 802 is used to arrange the N semantic tags to obtain arrangement results of N semantic tags;

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

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

[0224] In some embodiments, the device also includes: a first registration unit 803; the first registration unit 803 is used to, after receiving the second SIP message sent by the server, if there is no semantic tag in the tag library, register the service according to the semantic tag and write the semantic tag into the tag library.

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

[0226] Fig. 9900 is a schematic structural diagram of a dynamic session management device provided in an embodiment of the present application. The dynamic session management device may be a server or a tag controller. Fig. 9 The dynamic session management device 900 shown includes a processor 910, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0227] Alternatively, if Fig. 9 As shown, the dynamic session management device 900 may further include a memory 920. The processor 910 may call and run a computer program from the memory 920 to implement the method in the embodiment of the present application.

[0228] The memory 920 may be a separate device independent of the processor 910 , or may be integrated into the processor 910 .

[0229] Alternatively, if Fig. 9 As shown, the dynamic session management device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

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

[0231] Optionally, the dynamic session management device 900 may specifically be a server in an embodiment of the present application, and the dynamic session management device 900 may implement the corresponding processes implemented by the server in each method in the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0232] Optionally, the dynamic session management device 900 may specifically be a tag controller of an embodiment of the present application, and the dynamic session management device 900 may implement the corresponding processes implemented by the tag controller in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0233] Fig.10 It is a schematic structural diagram of the chip of an embodiment of the present application. Fig.10 The chip 1000 shown includes a processor 1010, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0234] Alternatively, if Fig.10 As shown, the chip 1000 may further include a memory 1020. The processor 1010 may call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application.

[0235] The memory 1020 may be a separate device independent of the processor 1010 , or may be integrated into the processor 1010 .

[0236] Optionally, the chip 1000 may further include an input interface 1030. The processor 1010 may control the input interface 1030 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

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

[0238] Optionally, the chip can be applied to the server in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the server in each method of the embodiments of the present application, which will not be described here for the sake of brevity.

[0239] Optionally, the chip can be applied to the tag controller in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the tag controller in each method of the embodiment of the present application, which will not be described here for the sake of brevity.

[0240] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0241] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0242] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as 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 RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

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

[0244] An embodiment of the present application also provides a computer program product, including a computer program.

[0245] Optionally, the computer program product can be applied to the server in the embodiments of the present 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 the present application. For the sake of brevity, it will not be repeated here.

[0246] Optionally, the computer program product can be applied to the tag controller in the embodiments of the present 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 the present application. For the sake of brevity, they are not repeated here.

[0247] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0248] Optionally, the computer-readable storage medium can be applied to the server in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the server in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0249] Optionally, the computer-readable storage medium can be applied to the tag controller in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the tag controller in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0250] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example 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 performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

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

[0252] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0254] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0255] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0256] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A session management method, characterized in that: Applied to a server, the method comprises: receiving a first SIP message sent by a terminal, determining N semantic tags corresponding to the user intent information according to the user intent information related to the first session carried in the first SIP message, and encapsulating 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; Sending the second SIP message to the label controller, and receiving a third SIP message sent by the label controller, wherein the third SIP message carries the arrangement result of the N semantic labels; A 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.

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

3. The method according to claim 1, characterized in that: The determining the target device according to the arrangement result of the N semantic tags includes: selecting a target device according to the arrangement result of the N semantic tags, the target device being a device capable of processing the service corresponding to the arrangement result; or, Sending the arrangement result of the N semantic tags to a semantic database, where the arrangement result of the N semantic tags is used by the semantic database to select a target device; receiving indication information of the target device sent by the semantic database, where 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, characterized in that The first SIP message also carries session parameters of the first session; and the method further includes: Monitor network status and / or device status of target devices; adjusting the session parameters according to the network status and / or the device status of the target device; A fourth SIP message is sent to the target device, where the fourth SIP message carries the adjusted session parameter.

5. The method according to any one of claims 1 to 3, characterized in that The method further comprises: receiving a fifth SIP message sent by the terminal, wherein the fifth SIP message carries updated user intent information; Determine M semantic tags corresponding to the updated user intent information, and update the arrangement result according to the M semantic tags; A sixth SIP message is sent to the target device, where the sixth SIP message carries the updated arrangement result.

6. A dynamic session management method, characterized in that: Applied to a tag controller, the method includes: 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, and the second SIP message is obtained by encapsulating the N semantic tags into the first SIP message, and 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 among the N semantic tags correspond to different services; Arranging the N semantic tags to obtain arrangement results 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, characterized in that The semantic tag includes one or more of the following information: a service type related to the first session, a priority of the service type related to the first session, a media format required by the first session, and a load status.

8. The method according to claim 6, characterized in that 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, service registration is performed according to the semantic tag, and the semantic tag is written into the tag library.

9. A dynamic session management device, characterized in that: Applied to a server, the device comprises: A first communication unit, configured to receive a first SIP message sent by a terminal; a first processing unit, configured to determine N semantic tags corresponding to the user intent information according to the user intent information related to the first session carried by 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 further configured to send the second SIP message to the label controller, and receive a third SIP message sent by the label controller, wherein the third SIP message carries the arrangement result of the N semantic labels; The first processing unit is further used to determine the target device according to the arrangement result of the N semantic tags; The first communication unit is further configured to send the third SIP message to the target device.

10. A dynamic session management device, characterized in that: Applied to a tag controller, the device comprises: a second communication unit, configured to 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 among the N semantic tags correspond to different services; A second processing unit, configured to arrange the N semantic tags to obtain arrangement results of N semantic tags; The second communication unit is further 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, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 8.

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

13. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 8.

Images