Communication method, apparatus and device, and storage medium

Abstract

The present application relates to the technical field of communications, and discloses a communication method, apparatus and device, and a storage medium. The communication method in embodiments of the present application comprises: a first communication device receives a first message sent by a second communication device, the first message being used for notifying terminal related first information, and the first information being used for indicating at least one of the following: an independently guided DC has been established; an independent application DC has been established; an independent IMS DC session becomes a normal IMS session; a normal IMS session becomes an independent IMS DC session; a locally guided DC has been established; a remotely guided DC has been established; a local terminal initiates establishment of an application DC; a peer terminal initiates establishment of an application DC; application information corresponding to an established application DC; and information of a guided DC corresponding to an established application DC.

Description

Communication method, device, equipment and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application number 202410337065.9 filed in China on March 22, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a communication method, apparatus, device and storage medium. Background Art

[0004] The communication standard introduces a mechanism for establishing a data channel (DC) during a call. This DC allows for additional services during a call, such as screen sharing, location sharing, and file transfer, providing a better user experience. Different services correspond to different DC applications, which can be dynamically downloaded to the terminal during a call, eliminating the need for pre-installation and facilitating user experience.

[0005] Currently, communication standards define methods for exposing terminal status. Consumers (e.g., third-party servers) can send subscription requests to producers (e.g., clients). The subscription requests include events for which subscriptions are requested, such as Internet Protocol Multimedia Subsystem (IMS) DC application events and IMS session events (IMS session status changes), so as to obtain the terminal status when the terminal uses a DC application.

[0006] However, currently only IMS services such as the above-mentioned IMS DC application download and IMS session status change are considered. The terminal status opened by the producer to the third-party server is not comprehensive enough, which makes it impossible to accurately judge the terminal status when the terminal uses DC. Summary of the Invention

[0007] The embodiments of the present application provide a communication method, apparatus, device, and storage medium, which can solve the problem of being unable to accurately determine the terminal status when the terminal uses DC.

[0008] In a first aspect, a communication method is provided, the method comprising: a first communication device receives a first message sent by a second communication device, the first message being used to notify a terminal of first information related thereto, the first information being used to indicate at least one of the following: an independent boot DC has been established; an independent application DC has been established; an independent Internet Protocol Multimedia Subsystem (IMS) DC session has become a normal IMS session; a normal IMS session has become an independent IMS DC session; a local boot DC has been established; a remote boot DC has been established; the local terminal initiates the establishment of an application DC; the opposite terminal initiates the establishment of an application DC; application information corresponding to the established application DC; information of the boot DC corresponding to the established application DC.

[0009] According to a second aspect, a communication method is provided, which includes: a second communication device sends a first message to a first communication device, the first message is used to notify the terminal of first information related to the terminal, and the first information is used to indicate at least one of the following: an independent boot DC has been established; an independent application DC has been established; an independent IMS DC session has become a normal IMS session; a normal IMS session has become an independent IMS DC session; a local boot DC has been established; a remote boot DC has been established; the local terminal initiates the establishment of an application DC; the opposite terminal initiates the establishment of an application DC; application information corresponding to the established application DC; information of the boot DC corresponding to the established application DC.

[0010] According to a third aspect, a communication device is provided, comprising: a receiving module configured to receive a first message sent by a second communication device, the first message being used to notify a terminal of first information related thereto, the first information being used to indicate at least one of the following: an independent bootstrap DC has been established; an independent application DC has been established; an independent IMS DC session has been converted to a normal IMS session; a normal IMS session has been converted to an independent IMS DC session; a local bootstrap DC has been established; a remote bootstrap DC has been established; a local terminal has initiated establishment of an application DC; a remote terminal has initiated establishment of an application DC; application information corresponding to the established application DC; and information about a bootstrap DC corresponding to the established application DC.

[0011] In a fourth aspect, a communication device is provided, comprising: a sending module, configured to send a first message to a first communication device, the first message being used to notify a terminal of first information related thereto, the first information being used to indicate at least one of the following: an independent bootstrap DC has been established; an independent application DC has been established; an independent IMS DC session has been converted to a normal IMS session; a normal IMS session has been converted to an independent IMS DC session; a local bootstrap DC has been established; a remote bootstrap DC has been established; a local terminal has initiated establishment of an application DC; a remote terminal has initiated establishment of an application DC; application information corresponding to the established application DC; and information about a bootstrap DC corresponding to the established application DC.

[0012] In a fifth aspect, a communication device is provided, which terminal includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0013] In a sixth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive a first message sent by a second communication device, the first message is used to notify the terminal of first information related thereto, and the first information is used to indicate at least one of the following: an independent boot DC has been established; an independent application DC has been established; an independent IMS DC session has become a normal IMS session; a normal IMS session has become an independent IMS DC session; a local boot DC has been established; a remote boot DC has been established; the local terminal initiates the establishment of an application DC; the opposite terminal initiates the establishment of an application DC; application information corresponding to the established application DC; information of the boot DC corresponding to the established application DC.

[0014] In the seventh aspect, a communication device is provided, which network side device includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the second aspect are implemented.

[0015] In an eighth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is used to send a first message to a first communication device, the first message being used to notify a terminal of first information related thereto, the first information being used to indicate at least one of the following: an independent boot DC has been established; an independent application DC has been established; an independent IMS DC session has become a normal IMS session; a normal IMS session has become an independent IMS DC session; a local boot DC has been established; a remote boot DC has been established; the local terminal initiates the establishment of an application DC; the opposite terminal initiates the establishment of an application DC; application information corresponding to the established application DC; information of the boot DC corresponding to the established application DC.

[0016] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0017] In the tenth aspect, a wireless communication system is provided, comprising: a first communication device and a second communication device, wherein the first communication device can be used to execute the steps of the method described in the first aspect, and the second communication device can be used to execute the steps of the method described in the second aspect.

[0018] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0019] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the communication method described in the first aspect, or to implement the steps of the communication method described in the second aspect.

[0020] In an embodiment of the present application, a first communication device can receive a notification message sent by a second communication device to obtain relevant information about an event that has occurred, that is, first information related to the terminal. In this way, this solution relatively comprehensively opens the terminal status to the first communication device, allowing the first communication device to obtain more terminal status, such as content related to an independent DC, whether the DC is related to the terminal on the local end or the terminal on the opposite end, etc., thereby more accurately determining the terminal status when the terminal uses the DC application. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] FIG1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application;

[0022] FIG2 is a flow chart of a communication method according to an embodiment of the present application;

[0023] FIG3 is a second flow chart of a communication method provided in an embodiment of the present application;

[0024] FIG4 is a third flow chart of a communication method provided in an embodiment of the present application;

[0025] FIG5 is a fourth flow chart of a communication method provided in an embodiment of the present application;

[0026] FIG6 is a fifth flow chart of a communication method provided in an embodiment of the present application;

[0027] FIG7 is a sixth flowchart of a communication method provided in an embodiment of the present application;

[0028] FIG8 is a seventh flowchart of a communication method provided in an embodiment of the present application;

[0029] FIG9 is a flowchart of an eighth embodiment of a communication method provided by the present application;

[0030] FIG10 is a schematic diagram of a structure of a communication device according to an embodiment of the present application;

[0031] FIG11 is a second structural diagram of a communication device provided in an embodiment of the present application;

[0032] FIG12 is a third structural diagram of a communication device provided in an embodiment of the present application;

[0033] FIG13 is a fourth structural diagram of a communication device provided in an embodiment of the present application;

[0034] FIG14 is a schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application;

[0035] FIG15 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application;

[0036] FIG16 is a schematic diagram of a hardware structure of a network side device according to an embodiment of the present application;

[0037] FIG17 is a second schematic diagram of the hardware structure of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0039] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0040] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0041] The terms "at least one" and "at least one of" in this application refer to any one, any two, or a combination of more than two of the objects included. For example, at least one of a, b, and c can be represented by: "a", "b", "c", "a and b", "a and c", "b and c", and "a, b, and c", where a, b, and c can be single or multiple. Similarly, "at least two" means two or more, and its meaning is similar to "at least one".

[0042] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0043] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer, a laptop computer, a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device, an aircraft (flight vehicle), a vehicle user equipment (VUE), a ship-borne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), a teller machine, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. In addition to the above-mentioned terminal devices, it can also be a chip in the terminal, such as a modem chip, a system-on-chip (SoC). It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AS) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0044] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0045] Currently, the 3GPP standard defines a method for exposing terminal status. Consumers (e.g., third-party servers) can subscribe to the following information from producers:

[0046] IMS DC application event: When a specific user downloads an IMS DC application, the producer reports the corresponding event to the consumer.

[0047] IMS session events: When the session status or media of a specific IMS session changes, the producer reports the corresponding event to the consumer.

[0048] Supplementary service events: When a supplementary service is activated for a specific IMS session, the producer reports the corresponding event to the consumer.

[0049] 3rd Party Registration Event: When the producer receives a 3rd Party Registration request, the producer reports the corresponding event to the consumer.

[0050] The existing technology only considers IMS services such as IMS DC application download and IMS session status changes. The terminal status opened by the producer to the third-party server is not comprehensive enough, which makes it impossible to accurately judge the terminal status when the terminal uses DC and unable to provide better services to users.

[0051] The embodiment of the present application provides a communication method, in which a first communication device can receive a notification message sent by a second communication device to obtain relevant information about an event that has occurred, that is, first information related to the terminal. In this way, through this solution, the terminal status is more comprehensively opened to the first communication device, allowing the first communication device to obtain more terminal status, such as content related to independent DC, whether the DC is related to the terminal on the local end or the terminal on the opposite end, etc., thereby more accurately determining the terminal status when the terminal uses the DC application.

[0052] It should be noted that the producer reports the corresponding event to the consumer, which can also be understood or replaced by: the producer sends information corresponding to the event to the consumer, or the producer sends relevant information about the event to the consumer, or the producer sends corresponding information to the consumer.

[0053] The following explains some concepts and / or terms involved in a communication method, apparatus, device, and storage medium provided in an embodiment of the present application.

[0054] The 3GPP standard introduces a mechanism for establishing DC during a call. DC enables additional services during a call, such as screen sharing, location sharing, and file transfer, providing a better user experience. Different services correspond to different DC applications, which can be dynamically downloaded to the terminal during a call, eliminating the need for pre-installation and facilitating user use. There are two types of DC:

[0055] Bootstrap DC: used to download DC applications from a data channel server (e.g., Data Channel Signaling Function (DCSF)).

[0056] Application DC: used to transmit DC application data.

[0057] A DC can be established along with services such as voice calls, video calls, or text messages, or it can be established without voice calls, video calls, or text messages. The latter is called a standalone DC.

[0058] The bootstrap DC is usually established by the terminal. For example, when terminal-1 and terminal-2 communicate, terminal-1 can request to establish a bootstrap DC with the local DCSF (the DCSF providing services for terminal-1), or request to establish a bootstrap DC with the remote DCSF (the DCSF providing services for terminal-2).

[0059] Application DC can be established by the terminal or by the network server. For example, when terminal-1 and terminal-2 communicate, terminal-1 can request to establish application DC; or the other terminal can also request to establish application DC; or terminal-1 can request to establish application DC with the network server; or the network server can request to establish application DC with terminal-1.

[0060] The communication method provided in the embodiments of the present application is described in detail below through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0061] The present invention provides a communication method, and Figure 2 shows a flow chart of the communication method provided by the present invention. As shown in Figure 2, the communication method provided by the present invention may include the following steps 201 and 202.

[0062] Step 201: A second communication device sends a first message to a first communication device.

[0063] Step 202: The first communication device receives a first message sent by the second communication device.

[0064] In the embodiment of the present application, the first message is used to notify the terminal of related first information, and the first information is used to indicate at least one of the following:

[0065] A standalone bootstrap data channel has been established.

[0066] A standalone application data channel (DC) has been established.

[0067] The independent IMS DC session becomes a normal IMS session;

[0068] Normal IMS sessions become independent IMS DC sessions;

[0069] A local boot DC has been established;

[0070] A remote boot DC has been established;

[0071] The local terminal initiates the establishment of the application DC;

[0072] The peer terminal initiates the establishment of an application DC;

[0073] Application information corresponding to the established application DC;

[0074] Information about the boot DC corresponding to the established application DC.

[0075] It should be noted that a normal IMS session can be understood as a non-independent IMS session. A normal IMS session can also be called a Multimedia Telephony (MMTEL) IMS session or an MMTEL session.

[0076] Optionally, in the embodiment of the present application, the independent IMS DC session may include at least one of the following: an independent bootstrap DC and an independent application DC.

[0077] It should be noted that the IMS DC session can be understood as a DC session.

[0078] Optionally, in the embodiment of the present application, voice, video or messaging media is added to the independent IMS DC session, and the independent IMS DC session can be converted into a normal IMS session.

[0079] Optionally, in an embodiment of the present application, voice, video or messaging media is deleted on the basis of a normal IMS session, and the normal IMS session becomes an independent IMS DC session.

[0080] It should be noted that the local bootstrap DC may also be referred to as the bootstrap DC connected to the local DCSF or the originating bootstrap DC, and the remote bootstrap DC may also be referred to as the bootstrap DC connected to the remote DCSF or the terminating bootstrap DC.

[0081] In the embodiment of the present application, the first communication device may be a consumer device, such as a third-party server, and the second communication device may be a producer device.

[0082] Optionally, in an embodiment of the present application, the above-mentioned consumer may be a network function (NF) service consumer.

[0083] Optionally, in the embodiment of the present application, the consumer may be any one of the following: an application function (AF) server, a network exposure function (NEF) server, a DC application server (AS), or a home subscriber server (HSS). The producer may be a DCSF or an IMS AS.

[0084] Optionally, in the embodiment of the present application, the consumer may be a DCSF, and the producer may be an IMS AS or an HSS.

[0085] Optionally, in an embodiment of the present application, the first message may be a notification message, such as Notify_Request.

[0086] Optionally, in an embodiment of the present application, in combination with Figure 2, as shown in Figure 3, before the above-mentioned step 201, the communication method provided in the embodiment of the present application also includes the following steps 301 and 302.

[0087] Step 301: A first communication device sends a second message to a second communication device.

[0088] Step 302: The second communication device receives a second message sent by the first communication device.

[0089] In this embodiment of the present application, the second message includes a first event, and the first event includes at least one of the following:

[0090] Establish an event to independently guide DC;

[0091] Establish an event for independent application DC;

[0092] The event in which an independent IMS DC session becomes a normal IMS session;

[0093] The event in which a normal IMS session becomes an independent IMS DC session;

[0094] Events for establishing a local bootstrap DC;

[0095] Establishing remote bootstrap DC events;

[0096] The local terminal initiates the event of establishing an application DC;

[0097] The peer terminal initiates the establishment of an application DC.

[0098] Optionally, in the embodiment of the present application, the second message may be a subscription message (or subscription request) for requesting to subscribe to the first information related to the terminal. For example, the second message may be a Subscribe_Request.

[0099] Optionally, in the embodiment of the present application, the first communication device may send the second message to the second communication device via an intermediate NF. The specific interaction process is described in the following embodiment and is not described here in detail.

[0100] Optionally, in the embodiment of the present application, when the consumer is AF, NEF or DC AS, the intermediate NF may be HSS, and the producer may be DCSF or IMS AS.

[0101] Optionally, in an embodiment of the present application, when the above-mentioned consumer is a DCSF or a NEF, the intermediate NF may be an HSS, and the producer may be an IMS AS.

[0102] Optionally, in the embodiment of the present application, when the above-mentioned consumer is AF, NEF or DC AS, the intermediate NF may be DCSF, and the producer may be IMS AS.

[0103] Optionally, in an embodiment of the present application, when the above-mentioned consumer is AF or DC AS, the intermediate NF may be DCSF or NEF, and the producer may be IMS AS.

[0104] Optionally, in an embodiment of the present application, when the second message includes the first event, the first information is used to indicate at least one of the following:

[0105] An independent boot DC has been established;

[0106] An independent application DC has been established;

[0107] The independent IMS DC session becomes a normal IMS session;

[0108] Normal IMS sessions become independent IMS DC sessions;

[0109] A local bootstrap DC has been established;

[0110] A remote boot DC has been established;

[0111] The local terminal initiates the establishment of the application DC;

[0112] The peer terminal initiates the establishment of an application DC.

[0113] Example 1-1, for event 1-1: establishing an independent boot DC or an independent application DC. The consumer subscribes to the producer for the event of establishing an independent boot DC or an independent application DC for the terminal (i.e., the consumer sends a second message to the producer). When the producer determines that the terminal has established an independent boot DC or an independent application DC, it sends a notification message (i.e., the first message) to the consumer to notify that an independent boot data channel DC has been established or an independent application DC has been established (i.e., the first information). The second message includes the first event (event 1-1), which is the event of establishing an independent boot DC or an independent application DC.

[0114] It should be noted that the terminal has established a bootstrap DC, which can be understood or replaced by: the terminal has completed the establishment of the bootstrap DC, or the terminal and the DCSF have established a bootstrap DC, or the network side has established a bootstrap DC for the terminal. The following is the same and will not be repeated.

[0115] It should be noted that the terminal has established an application DC, which can be understood or replaced as: the terminal has completed the establishment of the application DC, or the application DC has been established between the terminal and the other end (the other end UE or DC AS), or the network side has established an application DC for the terminal. The same will not be repeated later.

[0116] Example 1-2, for event 1-2: an independent IMS DC session becomes a normal IMS session. The consumer subscribes to the producer for the event that the independent IMS DC session becomes a normal IMS session (i.e., the consumer sends a second message to the producer). When the producer determines that the terminal's independent IMS DC session becomes a normal IMS session, it sends a notification message (i.e., a first message) to the consumer to notify the independent IMS DC session that the independent IMS DC session has become a normal IMS session (i.e., the first information). The second message includes the first event (event 1-2), which is the event that the independent IMS DC session becomes a normal IMS session.

[0117] Example 1-3, for event 1-3: a normal IMS session becomes an independent IMS DC session. The consumer subscribes to the producer for the event that a normal IMS session becomes an independent IMS DC session (i.e., the consumer sends a second message to the producer). When the producer determines that the terminal's normal IMS session becomes an independent IMS DC session, it sends a notification message (i.e., a first message) to the consumer to notify the consumer that the normal IMS session has become an independent IMS DC session (i.e., the first information). The second message includes the first event (event 1-3), which is the event that a normal IMS session becomes an independent IMS DC session.

[0118] Example 1-4, for event 1-4: establishing a local boot DC or a remote boot DC. The consumer subscribes to the producer for the event that the terminal has established a local boot DC or a remote boot DC (i.e., the consumer sends a second message to the producer). When the producer determines that the terminal has established a local boot DC or a remote boot DC, it sends a notification message (i.e., a first message) to the consumer to notify it that a local boot DC or a remote boot DC (i.e., the first information) has been established. The second message includes the first event (event 1-4), which is the event of establishing a local boot DC or the event of establishing a remote boot DC.

[0119] Example 1-5, for event 1-5: the local terminal initiates an application DC establishment request, or the peer terminal initiates an application DC establishment request. The consumer subscribes to the producer for the event of the local terminal initiating an application DC establishment request, or the peer terminal initiating an application DC establishment request (i.e., the consumer sends a second message to the producer). When the producer determines that the terminal initiates an application DC establishment request, or receives an application DC establishment request initiated by the peer terminal, it sends a notification message (i.e., the first message) to the consumer to notify the local terminal to initiate the establishment of the application DC, or the peer terminal initiates the establishment of the application DC (i.e., the first information). The second message includes the first event (event 1-5), which is the event of the local terminal initiating the establishment of the application DC (also called the originating application DC event), or the event of the peer terminal initiating the establishment of the application DC (also called the terminating application DC event).

[0120] In the embodiment of the present application, the consumer subscribes to a specific event (i.e., the first event) from the producer. When the specific event is met, the producer sends a notification message to the consumer to notify the consumer of the information of the first event, i.e., the first information related to the terminal. In this way, this solution more comprehensively opens the terminal status to the consumer, allowing the consumer to learn more about the terminal status, such as content related to the independent DC, whether the DC is related to the terminal on the local end or the terminal on the opposite end, etc., thereby more accurately judging the terminal status when the terminal uses the DC application.

[0121] Optionally, in an embodiment of the present application, in combination with Figure 2, as shown in Figure 4, before the above-mentioned step 201, the communication method provided in the embodiment of the present application also includes the following steps 401 and 402.

[0122] Step 401: A first communication device sends a third message to a second communication device.

[0123] Step 402: The second communication device receives a third message sent by the first communication device.

[0124] In the embodiment of the present application, the third message includes the second event and first indication information, and the first indication information is used to indicate relevant information of the second event.

[0125] Optionally, in the embodiment of the present application, the third message may be a subscription message, used to request subscription of the first information related to the terminal. For example, the third message may be Subscribe_Request.

[0126] Optionally, in an embodiment of the present application, the above-mentioned second event includes at least one of the following: an event of establishing a boot DC; an event of establishing an application DC; an event of establishing a DC; an event of establishing an IMS session; an event of establishing or modifying a normal IMS session; an event of establishing or modifying an independent IMS DC session; an event of establishing an IMS DC application.

[0127] Optionally, in an embodiment of the present application, the second event includes at least one of the following: an event of establishing a bootstrap DC, an event of establishing an application DC, an event of establishing a DC, and an event of establishing an IMS session. The first indication information is used to indicate at least one of the following:

[0128] The DC is an independent boot DC or a dependent boot DC;

[0129] The DC is an independent application DC or a dependent application DC;

[0130] A DC is either an independent DC or a dependent DC.

[0131] It can be understood that in this case, the first communication device sends a second event (general event) and the first indication information to the second communication device, so that the second communication device sends a notification message when it determines that the terminal has established an independent boot DC or an independent application DC, that is, sends a notification message when a specific event occurs. In other words, when the second event occurs and the DC at the time of the second event is the independent boot DC, independent application DC, or independent DC indicated by the first indication information, it is considered that a specific event has occurred, that is, the second event and the first indication information combined correspond to a specific event.

[0132] Example 2-1: For event 2-1 + first indication information (corresponding to event 1-1 above), the consumer subscribes to the producer for the event of the terminal establishing an independent boot DC, independent application DC, or independent DC (i.e., the consumer sends a third message to the producer). When the producer determines that the terminal has established an independent boot DC, independent application DC, or independent DC, it sends a notification message (i.e., the first message) to the consumer to notify that an independent boot data channel DC or an independent application DC has been established (i.e., the first information). The third message includes the second event (event 2-1) and the first indication information. The second event is an event of establishing a bootstrap DC, and the first indication information is used to indicate whether the DC is an independent bootstrap DC or a non-independent bootstrap DC, or is used to indicate whether the DC is an independent DC or a non-independent DC; or, the second event is an event of establishing an application DC, and the first indication information is used to indicate whether the DC is an independent application DC or a non-independent application DC, or is used to indicate whether the DC is an independent DC or a non-independent DC; or, the second event is an event of establishing a DC, and the first indication information (hereinafter referred to as indication information a) is used to indicate at least one of the following: whether the DC is an independent bootstrap DC or a non-independent bootstrap DC, whether the DC is an independent application DC or a non-independent application DC, or whether the DC is an independent DC or a non-independent DC. Or, the second event is an event of establishing an IMS session, and the first indication information (hereinafter referred to as indication information b) is used to indicate at least one of the following: whether the DC is an independent bootstrap DC or a non-independent bootstrap DC, whether the DC is an independent application DC or a non-independent application DC, or whether the DC is an independent DC or a non-independent DC.

[0133] It should be noted that when the second event is an IMS session establishment event, the DC refers to the DC already established by the terminal, including the bootstrap DC or the application DC. For example, when the terminal completes the establishment of the bootstrap DC, the DC refers to the established bootstrap DC; when the terminal completes the establishment of the application DC, the DC refers to the established application DC.

[0134] Exemplarily, the first indication information may be 1-bit information. For example, a value of 1 for the first indication information indicates that the system is in standalone mode, and a value of 0 for the first indication information indicates that the system is not in standalone mode (non-standalone mode may also be referred to as normal mode). Alternatively, a value of 0 for the first indication information indicates that the system is in standalone mode, and a value of 1 for the first indication information indicates that the system is not in standalone mode.

[0135] Exemplarily, the indication information a and the indication information b may be different parameters, each indicating whether it is standalone or not standalone through 1 bit.

[0136] Alternatively, the indication information a and indication information b can be the same parameter, which can be implemented through multi-bit encoding, where the first bit value of 1 represents a standalone bootstrap DC, and the first bit value of 0 represents a non-standalone bootstrap DC; the second bit value of 1 represents a standalone application DC, and the second bit value of 0 represents a non-standalone application DC. For example, 11 represents both a standalone bootstrap DC and a standalone application DC; 10 represents a standalone bootstrap DC but not a standalone application DC; 01 represents a standalone application DC but not a standalone bootstrap DC; and 00 represents neither a standalone bootstrap DC nor a standalone application DC.

[0137] Optionally, in an embodiment of the present application, the second event includes at least one of the following: an event of establishing or modifying a normal IMS session, an event of establishing an IMS session. The first indication information is used to indicate at least one of the following:

[0138] The IMS session is obtained by change or not;

[0139] The IMS session is derived from an independent IMS DC session or is not derived from an independent IMS DC session.

[0140] It can be understood that in this case, the first communication device sends the second event (general event) and the first indication information to the second communication device, so that the second communication device sends a notification message when it determines that the IMS session established by the terminal is obtained by a change, or the independent IMS DC session of the terminal is changed to a normal IMS session, that is, the notification message is sent when a specific event occurs. In other words, when the second event occurs and the IMS session at the time of the second event is obtained by the change indicated by the first indication information or is obtained by changing from an independent IMS DC session, it is considered that a specific event has occurred, that is, the second event and the first indication information combined correspond to a specific event.

[0141] Example 2-2, for event 2-2+first indication information (corresponding to the above-mentioned event 1-2). The consumer subscribes to the producer for the event that the independent IMS DC session becomes a normal IMS session (i.e., the consumer sends a third message to the producer). When the producer determines that the IMS session established by the terminal is changed, or the independent IMS DC session of the terminal becomes a normal IMS session, a notification message (i.e., the first message) is sent to the consumer to notify that the independent IMS DC session has become a normal IMS session (i.e., the first information). The third message includes the second event (event 2-2) and the first indication information. The second event is an event of establishing or modifying a normal IMS session, or an event of establishing an IMS session.

[0142] Exemplarily, the first indication information can be 1-bit information. For example, the value of the first indication information is 1, which means that the IMS session is obtained by change, or the IMS session is obtained by change from an independent IMS DC session; the value of the first indication information is 0, which means that the IMS session is not obtained by change, or the IMS session is not obtained by change from an independent IMS DC session. Alternatively, the value of the first indication information is 0, which means that the IMS session is obtained by change, or the IMS session is obtained by change from an independent IMS DC session; the value of the first indication information is 1, which means that the IMS session is not obtained by change, or the IMS session is not obtained by change from an independent IMS DC session.

[0143] Optionally, in an embodiment of the present application, the second event includes at least one of the following: an event of establishing or modifying an independent IMS DC session, an event of establishing an IMS session. The first indication information is used to indicate at least one of the following:

[0144] The IMS DC session is obtained by change or not;

[0145] The IMS DC session is derived from a normal IMS session or is not derived from a normal IMS session.

[0146] It can be understood that in this case, the first communication device sends the second event (general event) and the first indication information to the second communication device, so that the second communication device sends a notification message when it determines that the IMS session established by the terminal is changed, or the normal IMS session of the terminal is changed to an independent IMS DC session, that is, the notification message is sent when a specific event occurs. In other words, when the second event occurs and the IMS session at the time of the second event is the result of the change indicated by the first indication information or is changed from a normal IMS session, it is considered that a specific event has occurred, that is, the second event and the first indication information together correspond to a specific event.

[0147] Example 2-3, for event 2-3 + first indication information (corresponding to the above events 1-3). The consumer subscribes to the producer for the event that the normal IMS session becomes an independent IMS DC session (i.e., the consumer sends a third message to the producer). When the producer determines that the IMS session established by the terminal is changed, or the normal IMS session of the terminal becomes an independent IMS DC session, a notification message (i.e., the first message) is sent to the consumer to notify that the normal IMS session has become an independent IMS DC session (i.e., the first information). The third message includes the second event (event 2-3) and the first indication information. The second event is an event of establishing or modifying an independent IMS DC session, or an event of establishing an IMS session.

[0148] Exemplarily, the first indication information may be 1-bit information. For example, a value of 1 for the first indication information indicates that the IMS session is obtained through a change, or that the IMS session is obtained through a change from a normal IMS session; a value of 0 for the first indication information indicates that the IMS session is not obtained through a change, or that the IMS session is not obtained through a change from a normal IMS session. Alternatively, a value of 0 for the first indication information indicates that the IMS session is obtained through a change, or that the IMS session is obtained through a change from a normal IMS session; a value of 1 for the first indication information indicates that the IMS session is not obtained through a change, or that the IMS session is not obtained through a change from a normal IMS session.

[0149] It should be noted that the first indication information corresponding to the above event 2-2 and event 2-3 may be different parameters, each representing a different meaning through 1 bit.

[0150] Alternatively, the first indication information corresponding to events 2-2 and 2-3 can be the same parameter, which can be implemented through joint coding. For example, 1 represents that the IMS session is derived from an independent IMS DC session, and 0 represents that the IMS session is derived from a normal IMS session. Alternatively, 0 represents that the IMS session is derived from an independent IMS DC session, and 1 represents that the IMS session is derived from a normal IMS session.

[0151] Optionally, in the embodiment of the present application, the second event includes at least one of the following: an event of establishing a bootstrap DC, an event of establishing an IMS session. The first indication information is used to indicate at least one of the following:

[0152] DC is local or not local;

[0153] The DC is either remote or not remote.

[0154] It can be understood that in this case, the first communication device sends the second event (general event) and the first indication information to the second communication device, so that the second communication device sends a notification message when it determines that the terminal has established a local boot DC or has established a remote boot DC, that is, when a specific event occurs. In other words, when the second event occurs and the DC at the time of the second event is the DC indicated by the first indication information, the DC is local or the DC is remote, then it is considered that a specific event has occurred, that is, the second event and the first indication information combined correspond to a specific event.

[0155] Example 2-4, for event 2-4 + first indication information (corresponding to the above events 1-4). The consumer subscribes to the producer for the event that the terminal establishes a local boot DC or a remote boot DC (i.e., the consumer sends a third message to the producer). When the producer determines that the terminal has established a local boot DC or a remote boot DC, it sends a notification message (i.e., the first message) to the consumer to notify that a local boot DC has been established or a remote boot DC has been established (i.e., the first information). The third message includes the second event (event 2-4) and the first indication information. The second event is an event of establishing a boot DC or an event of establishing an IMS session.

[0156] Exemplarily, the first indication information may be 1-bit information. For example, a value of 1 in the first indication information indicates that the DC is local, and a value of 0 in the first indication information indicates that the DC is not local. Alternatively, a value of 0 in the first indication information indicates that the DC is local, and a value of 1 in the first indication information indicates that the DC is not local.

[0157] Exemplarily, the first indication information may be 1-bit information. For example, a value of 1 for the first indication information indicates that the DC is remote, and a value of 0 for the first indication information indicates that the DC is not remote. Alternatively, a value of 0 for the first indication information indicates that the DC is remote, and a value of 1 for the first indication information indicates that the DC is not remote.

[0158] Exemplarily, the first indication information is used to indicate whether the DC is locally booted or remotely booted. For example, a value of 1 in the first indication information indicates that the DC is locally booted, while a value of 0 in the first indication information indicates that the DC is remotely booted. Alternatively, a value of 0 in the first indication information indicates that the DC is locally booted, while a value of 1 in the first indication information indicates that the DC is remotely booted.

[0159] Optionally, in an embodiment of the present application, the second event includes at least one of the following: an event of establishing an application DC, an event of establishing an IMS DC application, and an event of establishing an IMS session. The first indication information is used to indicate at least one of the following:

[0160] DC is initiated by the local terminal or not;

[0161] DC is initiated by the peer terminal or not.

[0162] It can be understood that in this case, the first communication device sends a second event (general event) and the first indication information to the second communication device, so that the second communication device sends a notification message when it determines that the terminal initiates an application DC establishment request, or receives an application DC establishment request initiated by the opposite terminal, that is, when a specific event occurs. In other words, when the second event occurs and the DC at the time of the second event is the DC indicated by the first indication information, the DC is initiated by the local terminal or the DC is initiated by the opposite terminal, then it is considered that a specific event has occurred, that is, the second event and the first indication information together correspond to a specific event.

[0163] Example 2-5, for event 2-5 + first indication information (corresponding to the above-mentioned event 1-5). The consumer subscribes to the producer for the event that the local terminal initiates an application DC establishment request, or the peer terminal initiates an application DC establishment request (that is, the consumer sends a third message to the producer). When the producer determines that the terminal initiates an application DC establishment request, or receives an application DC establishment request initiated by the peer terminal, it sends a notification message (that is, the first message) to the consumer to notify the local terminal to initiate the establishment of the application DC, or the peer terminal initiates the establishment of the application DC (that is, the first information). The third message includes the second event (event 2-5) and the first indication information. The second event is an event for establishing an application DC, or an event for establishing an IMS DC application, or an event for establishing an IMS session.

[0164] Exemplarily, the first indication information may be 1-bit information. For example, a value of 1 in the first indication information indicates that the DC was initiated by the local terminal, and a value of 0 in the first indication information indicates that the DC was not initiated by the local terminal. Alternatively, a value of 0 in the first indication information indicates that the DC was initiated by the local terminal, and a value of 1 in the first indication information indicates that the DC was not initiated by the local terminal.

[0165] Exemplarily, the first indication information may be 1-bit information. For example, a value of 1 in the first indication information indicates that the DC is initiated by the peer terminal, and a value of 0 in the first indication information indicates that the DC is not initiated by the peer terminal. Alternatively, a value of 0 in the first indication information indicates that the DC is initiated by the peer terminal, and a value of 1 in the first indication information indicates that the DC is not initiated by the peer terminal.

[0166] Optionally, in an embodiment of the present application, the second event includes an event of establishing an application DC. The first indication information is used to indicate at least one of the following:

[0167] Application information corresponding to the application DC;

[0168] Information about the boot DC corresponding to the application DC.

[0169] It can be understood that in this case, the first communication device sends the second event (general event) and the first indication information to the second communication device, so that the second communication device determines that the information corresponding to the application DC established by the terminal meets the specific information provided by the consumer, that is, when a specific event occurs, it sends a notification message. In other words, when the second event occurs and the application information corresponding to the application DC indicated by the first indication information or the corresponding guidance DC information meets the specific information, it is considered that a specific event has occurred, that is, the second event and the first indication information combined correspond to the specific event.

[0170] Example 2-6, for event 2-6 + first indication information. The consumer subscribes to the producer for the event of the application DC established by the terminal that meets the specific information (i.e., the consumer sends a third message to the producer). When the producer determines that the information corresponding to the application DC established by the terminal meets the specific information provided by the consumer, it sends a notification message (i.e., the first message) to the consumer to notify the application information corresponding to the established application DC, or the information of the boot DC corresponding to the established application DC (i.e., the first information). The third message includes the second event (event 2-6) and the first indication information, and the second event is the event of establishing the application DC.

[0171] For example, the consumer subscribes to the producer for an event that the terminal uses a screen sharing app. When the application corresponding to the application DC is the screen sharing app, the producer sends a notification message to the consumer.

[0172] Exemplarily, the first indication information may be the application information or the information of the guide DC, that is, when the producer determines that the established application DC complies with the specific information provided by the consumer, the producer sends a notification message to the consumer.

[0173] Optionally, in an embodiment of the present application, the above-mentioned application information includes at least one of the following: application type (application type), application identification (application ID), and application binding information (application binding information).

[0174] It should be noted that the above-mentioned information about the bootstrap DC is information about the bootstrap DC associated with the application DC, for example, the bootstrap DC through which the application corresponding to the application DC is downloaded. Optionally, the above-mentioned information about the bootstrap DC may be a stream ID of the bootstrap DC.

[0175] In the embodiment of the present application, the consumer subscribes to a specific event (i.e., the second event + the first indication information) from the producer. When the specific event is met, the producer sends a notification message to the consumer to inform the consumer of the information of the event that occurred, i.e., the first information related to the terminal. In this way, this solution more comprehensively opens the terminal status to the consumer, allowing the consumer to learn more about the terminal status, such as content related to the independent DC, whether the DC is related to the terminal on the local end or the terminal on the opposite end, etc., thereby more accurately judging the terminal status when the terminal uses the DC application.

[0176] Optionally, in an embodiment of the present application, in combination with Figure 2, as shown in Figure 5, before the above-mentioned step 201, the communication method provided in the embodiment of the present application also includes the following steps 501 and 502.

[0177] Step 501: A first communication device sends a fourth message to a second communication device.

[0178] Step 502: The second communication device receives a fourth message sent by the first communication device.

[0179] In an embodiment of the present application, the above-mentioned fourth message includes a second event and second indication information, and the second indication information is used to obtain at least one of the following: information corresponding to the boot DC; information corresponding to the application DC; information corresponding to the IMS session; information corresponding to the IMS DC session.

[0180] Optionally, in an embodiment of the present application, when the fourth message includes the second event, or includes the second event and second indication information, the first information includes the second event and third indication information, and the third indication information is used to indicate relevant information about the second event. That is, after determining that the second event has occurred, the second communication device sends the second event and the third indication information to the first communication device. That is, the first information is obtained by combining the second event and the third indication information.

[0181] It should be noted that the solution for the second event and the third indication information is similar to the solution for the second event and the first indication information. Please refer to the description of the second event and the first indication information in the above embodiment, and no further details will be given here.

[0182] In the embodiment of the present application, the consumer subscribes to a general event (i.e., the second event) from the producer. When the producer sends a notification message to the consumer, it uses the information of the event that occurred, i.e., the first information related to the terminal. In this way, this solution more comprehensively opens the terminal status to the consumer, allowing the consumer to learn more about the terminal status, such as content related to the independent DC, whether the DC is related to the terminal on the local end or the terminal on the opposite end, etc., thereby more accurately judging the terminal status when the terminal uses the DC application.

[0183] Exemplarily, the interaction process of the communication method provided in the embodiment of the present application is described below through specific implementation methods.

[0184] Implementation method 1: The consumer requests a specific event from the producer, and when the specific event is met, the producer sends a notification message to the consumer.

[0185] As shown in FIG6 , the communication method provided in the embodiment of the present application includes the following steps 20 to 25 .

[0186] Step 20: The NF service consumer sends a subscription message to the producer. The subscription message includes the first event, or the second event and the first indication information.

[0187] For example, the subscription message may be Subscribe_Request.

[0188] Step 21: The producer creates a new event subscription resource and starts detecting subscribed events.

[0189] Step 22: The producer sends a response message to the NF service consumer.

[0190] For example, the response message may be Subscribe_Request response.

[0191] Step 23: The producer determines that the subscribed event occurs.

[0192] Step 24: The producer sends a notification message to the NF service consumer to notify the terminal of the first information.

[0193] For example, the notification message may be Notify_Request.

[0194] Step 25: The NF service consumer sends a response message to the producer.

[0195] For example, the response message may be Notify_Request response.

[0196] Optionally, in the embodiment of the present application, for event 1-1 described in the above embodiment:

[0197] The above step 20 is specifically step 20a: the consumer subscribes to the producer for an event of establishing an independent boot DC or an independent application DC of the terminal (ie, the consumer sends a subscription message to the producer).

[0198] The above step 24 is specifically step 24a: when the producer determines that the terminal has established an independent boot DC or an independent application DC, it sends a notification message to the consumer.

[0199] In the above step 20a, the subscription message includes a first event (event 1-1), which is an event of establishing an independent boot DC or an event of establishing an independent application DC.

[0200] Alternatively, in step 20a above, the subscription message includes a second event (event 2-1 described in the above embodiment) and first indication information. The second event includes at least one of the following: an event of establishing a bootstrap DC, an event of establishing an application DC, an event of establishing a DC, and an event of establishing an IMS session. The first indication information is used to indicate at least one of the following:

[0201] The DC is an independent boot DC or a dependent boot DC;

[0202] The DC is an independent application DC or a dependent application DC;

[0203] A DC is either an independent DC or a dependent DC.

[0204] Optionally, in the embodiment of the present application, for events 1-2 described in the above embodiment:

[0205] The above step 20 is specifically step 20b: the consumer subscribes to the producer for an event that the independent IMS DC session becomes a normal IMS session (ie, the consumer sends a subscription message to the producer).

[0206] The above step 24 is specifically step 24b: when the producer determines that the independent IMS DC session of the terminal becomes a normal IMS session, it sends a notification message to the consumer.

[0207] In the above step 20b, the subscription message includes a first event (event 1-2), and the first event is an event in which the independent IMS DC session is changed into a normal IMS session.

[0208] Alternatively, in step 20b above, the subscription message includes a second event (event 2-2 described in the above embodiment) and first indication information. The second event includes at least one of the following: an event of establishing or modifying a normal IMS session, or an event of establishing an IMS session. The first indication information is used to indicate at least one of the following:

[0209] The IMS session is obtained by change or not;

[0210] The IMS session is derived from an independent IMS DC session or is not derived from an independent IMS DC session.

[0211] Optionally, in the embodiments of the present application, for events 1-3 described in the above embodiments:

[0212] The above step 20 is specifically step 20c: the consumer subscribes to the producer for an event that a normal IMS session becomes an independent IMS DC session (ie, the consumer sends a subscription message to the producer).

[0213] The above step 24 is specifically step 24c: when the producer determines that the normal IMS session of the terminal is changed into an independent IMS DC session, it sends a notification message to the consumer.

[0214] In the above step 20c, the subscription message includes the first event (event 1-3), and the first event is the event that a normal IMS session is changed into an independent IMS DC session.

[0215] Alternatively, in step 20c, the subscription message includes a second event (events 2-3 described in the above embodiment) and first indication information. The second event includes at least one of the following: an event of establishing or modifying an independent IMS DC session, or an event of establishing an IMS session. The first indication information is used to indicate at least one of the following:

[0216] The IMS DC session is obtained by change or not;

[0217] The IMS DC session is derived from a normal IMS session or is not derived from a normal IMS session.

[0218] Optionally, in the embodiments of the present application, for events 1-4 described in the above embodiments:

[0219] The above step 20 is specifically step 20d: the consumer subscribes to the producer for an event of establishing a local bootstrap DC or a remote bootstrap DC at the terminal (ie, the consumer sends a subscription message to the producer).

[0220] The above step 24 is specifically step 24d: when the producer determines that the terminal has established a local boot DC or a remote boot DC, it sends a notification message to the consumer.

[0221] In the above step 20d, the subscription message includes the first event (event 1-4), and the first event is an event of establishing a local boot DC, or an event of establishing a remote boot DC.

[0222] Alternatively, in step 20d, the subscription message includes a second event (events 2-4 described in the above embodiment) and first indication information. The second event includes at least one of the following: an event of establishing a bootstrap DC, an event of establishing an IMS session. The first indication information is used to indicate at least one of the following:

[0223] DC is local or not local;

[0224] The DC is either remote or not remote.

[0225] Optionally, in the embodiments of the present application, for events 1-5 described in the above embodiments:

[0226] The above step 20 is specifically step 20e: the consumer subscribes to the producer for the event that the local terminal initiates an application DC establishment request, or the peer terminal initiates an application DC establishment request (ie, the consumer sends a subscription message to the producer).

[0227] The above step 24 is specifically step 24e: when the producer determines that the terminal initiates an application DC establishment request, or receives an application DC establishment request initiated by the opposite terminal, it sends a notification message to the consumer.

[0228] In the above step 20e, the subscription message includes the first event (event 1-5), which is the event of the local terminal initiating the establishment of the application DC (also called the originating application DC event), or the event of the peer terminal initiating the establishment of the application DC (also called the terminating application DC event).

[0229] Alternatively, in step 20e, the subscription message includes a second event (events 2-5 described in the above embodiment) and first indication information. The second event includes at least one of the following: an event of establishing an application DC, an event of establishing an IMS DC application, or an event of establishing an IMS session. The first indication information is used to indicate at least one of the following:

[0230] DC is initiated by the local terminal or not;

[0231] DC is initiated by the peer terminal or not.

[0232] Optionally, in the embodiment of the present application, for events 2-6 described in the above embodiment:

[0233] The above step 20 is specifically step 20f: the consumer subscribes to the producer for an event created by the application DC of the terminal that meets the specific information (ie, the consumer sends a subscription message to the producer).

[0234] The above step 24 is specifically step 24f: when the producer determines that the information corresponding to the application DC established by the terminal meets the specific information provided by the consumer, it sends a notification message to the consumer.

[0235] In step 20f above, the subscription message includes a second event (events 2-6 described in the above embodiment) and first indication information. The second event includes an event for establishing an application DC. The first indication information is used to indicate at least one of the following:

[0236] Application information corresponding to the application DC;

[0237] Information about the boot DC corresponding to the application DC.

[0238] It should be noted that, for the description of the above steps 20 to 25 and related solutions, please refer to the description in the above embodiment, which will not be repeated here.

[0239] Implementation method 2: The consumer requests a specific event from the producer via an intermediate NF. When the specific event is met, the producer sends a notification message to the consumer.

[0240] As shown in FIG. 7 , the communication method provided in the embodiment of the present application includes the following steps 30 to 42 .

[0241] Step 30: The NF service consumer sends a subscription message to the intermediate NF. The subscription message includes the first event, or the second event and the first indication information.

[0242] Step 31: The intermediate NF determines the producer.

[0243] Step 32: The intermediate NF sends a subscription message to the producer. The subscription message includes the first event, or the second event and the first indication information.

[0244] It should be noted that the subscription message in step 30 and the subscription message in step 32 may be the same or different. For example, the subscription message may be Subscribe_Request.

[0245] Step 33: The producer creates a new event subscription resource and starts detecting subscribed events.

[0246] Step 34: The producer sends a response message to the intermediate NF.

[0247] Step 35: The intermediate NF sends a response message to the NF service consumer.

[0248] It should be noted that the response message in step 34 and the response message in step 35 may be the same or different. For example, the response message in step 34 may be a Subscribe_Request response, and the response message in step 35 may be an Ndcsf_EE_Subscribe_Request response.

[0249] Step 36: The producer determines that the subscribed event occurs.

[0250] Step 37: The producer sends a notification message to the intermediate NF to notify the terminal of the first information.

[0251] Step 38: The intermediate NF sends a notification message to the NF service consumer to notify the terminal of the first information.

[0252] It should be noted that the notification message in step 37 and the notification message in step 38 may be the same or different. For example, the notification message may be Notify_Request.

[0253] Step 39: The NF service consumer sends a response message to the intermediate NF.

[0254] Step 40: The intermediate NF sends a response message to the producer.

[0255] It should be noted that the response message in step 39 and the response message in step 40 may be the same or different. For example, the response message may be Notify_Request response.

[0256] Step 41: The producer directly sends a notification message to the NF service consumer to notify the terminal of the first information.

[0257] For example, the notification message may be Notify_Request.

[0258] Step 42: The NF service consumer sends a response message directly to the producer.

[0259] For example, the response message may be Notify_Request response.

[0260] It should be noted that the execution relationship between the above steps 37 to 40 and the above steps 41 to 42 is an "or" relationship, that is, after the above step 36, the above steps 37 to 40 can be executed, or the above steps 41 to 42 can also be executed.

[0261] It should be noted that, for the specific implementation scheme of the above-mentioned steps 30 and 37 (or step 41), that is, when the first event includes events 1-1 to 1-5 respectively, and the second event includes events 2-1 to 2-6 respectively, the specific implementation steps of the above-mentioned steps 30 and 37 (or step 41) can be found in the description of the above-mentioned embodiment 1, and will not be repeated here.

[0262] Implementation method three: The consumer requests a general event from the producer, and the producer carries the indication information when sending a notification to the consumer.

[0263] As shown in FIG8 , the communication method provided in the embodiment of the present application includes the following steps 50 to 55 .

[0264] Step 50: The NF service consumer sends a subscription message to the producer, where the subscription message includes the second event.

[0265] For example, the subscription message may be Subscribe_Request.

[0266] Optionally, in an embodiment of the present application, the above subscription message also includes second indication information.

[0267] Step 51: The producer creates a new event subscription resource and starts detecting subscribed events.

[0268] Step 52: The producer sends a response message to the NF service consumer.

[0269] For example, the response message may be Subscribe_Request response.

[0270] Step 53: The producer determines that the subscribed event occurs.

[0271] Step 54: The producer sends a notification message to the NF service consumer to notify the terminal of the first information related to the terminal, where the first information includes the second event and the third indication information.

[0272] For example, the notification message may be Notify_Request.

[0273] Step 55: The NF service consumer sends a response message to the producer.

[0274] For example, the response message may be Notify_Request response.

[0275] Optionally, in an embodiment of the present application, when the second event is event 2-1 described in the above embodiment, that is, the second event includes at least one of the following: an event of establishing a bootstrap DC, an event of establishing an application DC, an event of establishing a DC, and an event of establishing an IMS session:

[0276] The second indication information is used to obtain at least one of the following: information corresponding to the boot DC and information corresponding to the application DC.

[0277] The above step 54 is specifically step 54a: when the producer determines that the terminal has established a boot DC or an application DC, it sends a notification message to the consumer to notify the terminal of the first information related to the first event, where the first information includes the second event and the third indication information. The third indication information is used to indicate at least one of the following:

[0278] The DC is an independent boot DC or a dependent boot DC;

[0279] The DC is an independent application DC or a dependent application DC;

[0280] A DC is either an independent DC or a dependent DC.

[0281] Optionally, in an embodiment of the present application, when the second event is event 2-2 described in the above embodiment, that is, the second event includes at least one of the following: an event of establishing or modifying a normal IMS session, or an event of establishing an IMS session:

[0282] The second indication information is used to obtain information corresponding to the IMS session.

[0283] The above step 54 is specifically step 54b: when the producer determines that a normal IMS session is established or modified, it sends a notification message to the consumer to notify the terminal of first information related to the second event and third indication information. The third indication information is used to indicate at least one of the following:

[0284] The IMS session is obtained by change or not;

[0285] The IMS session is derived from an independent IMS DC session or is not derived from an independent IMS DC session.

[0286] Optionally, in an embodiment of the present application, when the second event is event 2-3 described in the above embodiment, that is, the second event includes at least one of the following: an event of establishing or modifying an independent IMS DC session, or an event of establishing an IMS session:

[0287] The second indication information is used to obtain information corresponding to the IMS DC session.

[0288] Step 54 is specifically step 54c: when the producer determines that an independent IMS DC session is established or modified, or an IMS DC session is established, the producer sends a notification message to the consumer, notifying the terminal of first information related to the event, the first information including the second event and third indication information. The third indication information is used to indicate at least one of the following:

[0289] The IMS DC session is obtained by change or not;

[0290] The IMS DC session is derived from a normal IMS session or is not derived from a normal IMS session.

[0291] Optionally, in the embodiment of the present application, when the second event is event 2-4 described in the embodiment, that is, the second event includes at least one of the following: an event of establishing a bootstrap DC and an event of establishing an IMS session:

[0292] The above-mentioned second indication information is used to obtain information corresponding to the boot DC.

[0293] The above step 54 is specifically step 54d: when the producer determines that the terminal has established a bootstrap DC, it sends a notification message to the consumer to notify the terminal of the first information related to the first event, where the first information includes the second event and the third indication information. The third indication information is used to indicate at least one of the following:

[0294] DC is local or not local;

[0295] The DC is either remote or not remote.

[0296] Optionally, in an embodiment of the present application, when the second event is event 2-5 described in the above embodiment, that is, the second event includes at least one of the following: an event of establishing an application DC, an event of establishing an IMS DC application, and an event of establishing an IMS session:

[0297] The above-mentioned second indication information is used to obtain information corresponding to the application DC.

[0298] The above step 54 is specifically step 54e: when the producer determines that the terminal has established the application DC, it sends a notification message to the consumer to notify the terminal of the first information related to the application DC, where the first information includes the second event and the third indication information. The third indication information is used to indicate at least one of the following:

[0299] DC is initiated by the local terminal or not;

[0300] DC is initiated by the peer terminal or not.

[0301] Optionally, in the embodiment of the present application, when the second event is the event 2-6 described in the embodiment above, that is, the second event includes an event of establishing an application DC:

[0302] The above-mentioned second indication information is used to obtain information corresponding to the application DC.

[0303] The above step 54 is specifically step 54f: when the producer determines that the terminal has established the application DC, it sends a notification message to the consumer to notify the terminal of the first information related to the application DC, where the first information includes the second event and the third indication information. The third indication information is used to indicate at least one of the following:

[0304] Application information corresponding to the application DC;

[0305] Information about the boot DC corresponding to the application DC.

[0306] It should be noted that, for the description of the above steps 50 to 55 and related solutions, please refer to the description in the above embodiment, which will not be repeated here.

[0307] Implementation method 4: The consumer requests a general event from the producer via an intermediate NF. The producer carries the indication information when sending a notification to the consumer.

[0308] As shown in FIG9 , the communication method provided in the embodiment of the present application includes the following steps 60 to 72 .

[0309] Step 60: The NF service consumer sends a subscription message to the intermediate NF, where the subscription message includes the second event.

[0310] Optionally, in an embodiment of the present application, the above subscription message also includes second indication information.

[0311] Step 61: The intermediate NF determines the producer.

[0312] Step 62: The intermediate NF sends a subscription message to the producer, where the subscription message includes the second event.

[0313] It should be noted that the subscription message in step 60 and the subscription message in step 62 may be the same or different. For example, the subscription message may be Subscribe_Request.

[0314] Step 63: The producer creates a new event subscription resource and starts detecting subscribed events.

[0315] Step 64: The producer sends a response message to the intermediate NF.

[0316] Step 65: The intermediate NF sends a response message to the producer.

[0317] It should be noted that the response message in step 64 and the response message in step 65 may be the same or different. For example, the response message in step 64 may be a Subscribe_Request response, and the response message in step 65 may be an Ndcsf_EE_Subscribe_Request response.

[0318] Step 66: The producer determines that the subscribed event occurs.

[0319] Step 67: The producer sends a notification message to the intermediate NF to notify the terminal of the first information related thereto, where the first information includes the second event and the third indication information.

[0320] Step 68: The intermediate NF sends a notification message to the NF service consumer to notify the terminal of first information related to the terminal, where the first information includes the second event and the third indication information.

[0321] It should be noted that the notification message in step 67 and the notification message in step 68 may be the same or different. For example, the notification message may be Notify_Request.

[0322] Step 69: The NF service consumer sends a response message to the intermediate NF.

[0323] Step 70: The intermediate NF sends a response message to the producer.

[0324] It should be noted that the response message in step 69 and the response message in step 70 may be the same or different. For example, the response message may be Notify_Request response.

[0325] Step 71: The producer directly sends a notification message to the NF service consumer to notify the terminal of first information related to the terminal, where the first information includes the second event and the third indication information.

[0326] For example, the notification message may be Notify_Request.

[0327] Step 72: The NF service consumer sends a response message directly to the producer.

[0328] For example, the response message may be Notify_Request response.

[0329] It should be noted that the execution relationship between the above steps 67 to 70 and the above steps 71 to 72 is an "or" relationship, that is, after the above step 66, the above steps 67 to 70 can be executed, or the above steps 71 to 72 can also be executed.

[0330] It should be noted that when the second event includes events 2-1 to 2-6, the second indication information, the specific implementation scheme of the above step 67 or step 71, and the description of the third indication information can be found in the description of the above embodiment 3 and will not be repeated here.

[0331] The embodiment of the present application provides a communication method, in which a first communication device can receive a notification message sent by a second communication device to obtain relevant information about an event that has occurred, that is, first information related to the terminal. In this way, through this solution, the terminal status is more comprehensively opened to the first communication device, allowing the first communication device to obtain more terminal status, such as content related to independent DC, whether the DC is related to the terminal on the local end or the terminal on the opposite end, etc., thereby more accurately determining the terminal status when the terminal uses the DC application.

[0332] Each of the above-mentioned method embodiments, or various possible implementation methods in each method embodiment, can be executed separately, or any two or more of them can be executed in combination with each other. The specific implementation can be determined according to actual usage requirements, and the embodiments of this application do not limit this.

[0333] The communication method provided in the embodiment of the present application can be executed by a communication device. In the embodiment of the present application, the communication device provided in the embodiment of the present application is described by taking the communication method executed by the communication device as an example.

[0334] FIG10 shows a possible structural diagram of a communication device involved in an embodiment of the present application. As shown in FIG10 , the communication device 80 may include: a receiving module 81 .

[0335] Among them, the receiving module 81 is used to receive a first message sent by the second communication device, the first message is used to notify the terminal of first information related to the first information, and the first information is used to indicate at least one of the following: an independent boot DC has been established; an independent application DC has been established; an independent IMS DC session has become a normal IMS session; a normal IMS session has become an independent IMS DC session; a local boot DC has been established; a remote boot DC has been established; the local terminal initiates the establishment of an application DC; the opposite terminal initiates the establishment of an application DC; application information corresponding to the established application DC; information of the boot DC corresponding to the established application DC.

[0336] In one possible implementation, as shown in FIG11 in conjunction with FIG10 , the communication apparatus 80 further includes a sending module 82. The sending module 82 is configured to send a second message to the second communication device, where the second message includes a first event, and the first event includes at least one of the following:

[0337] Establish an event to independently guide DC;

[0338] Establish an event for independent application DC;

[0339] The event in which an independent IMS DC session becomes a normal IMS session;

[0340] The event in which a normal IMS session becomes an independent IMS DC session;

[0341] Events for establishing a local bootstrap DC;

[0342] Establishing remote bootstrap DC events;

[0343] The local terminal initiates the event of establishing an application DC;

[0344] The peer terminal initiates the establishment of an application DC.

[0345] In one possible implementation, as shown in FIG11 in combination with FIG10 , the communication apparatus 80 further includes a sending module 82. The sending module 82 is configured to send a third message to the second communication device, where the third message includes the second event and first indication information, where the first indication information is used to indicate relevant information about the second event.

[0346] In a possible implementation, the second event includes at least one of the following: an event of establishing a bootstrap DC, an event of establishing an application DC, an event of establishing a DC, and an event of establishing an IMS session;

[0347] The first indication information is used to indicate at least one of the following:

[0348] The DC is an independent boot DC or a dependent boot DC;

[0349] The DC is an independent application DC or a dependent application DC;

[0350] A DC is either an independent DC or a dependent DC.

[0351] In a possible implementation, the second event includes at least one of the following: an event of establishing or modifying a normal IMS session, an event of establishing an IMS session;

[0352] The first indication information is used to indicate at least one of the following:

[0353] The IMS session is obtained by change or not;

[0354] The IMS session is derived from an independent IMS DC session, or is not derived from an independent IMS DC session;

[0355] In a possible implementation, the second event includes at least one of the following: an event of establishing or modifying an independent IMS DC session, an event of establishing an IMS session;

[0356] The first indication information is used to indicate at least one of the following:

[0357] The IMS DC session is obtained by change or not;

[0358] The IMS DC session is derived from a normal IMS session or is not derived from a normal IMS session.

[0359] In a possible implementation, the second event includes at least one of the following: an event of establishing a bootstrap DC, an event of establishing an IMS session;

[0360] The first indication information is used to indicate at least one of the following:

[0361] DC is local or not local;

[0362] The DC is either remote or not remote.

[0363] In a possible implementation, the second event includes at least one of the following: an event of establishing an application DC, an event of establishing an IMS DC application, and an event of establishing an IMS session;

[0364] The first indication information is used to indicate at least one of the following:

[0365] DC is initiated by the local terminal or not;

[0366] DC is initiated by the peer terminal or not.

[0367] In a possible implementation, the second event includes an event of establishing an application DC;

[0368] The first indication information is used to indicate at least one of the following:

[0369] Application information corresponding to the application DC;

[0370] Information about the boot DC corresponding to the application DC.

[0371] In a possible implementation, the application information includes at least one of the following: application type, application identifier, and application binding information.

[0372] In one possible implementation, as shown in FIG11 in combination with FIG10 , the communication apparatus 80 further includes a sending module 82. The sending module 82 is configured to send a fourth message to the second communication device, where the fourth message includes a second event and second indication information, where the second indication information is used to obtain at least one of the following:

[0373] Information corresponding to the guide DC;

[0374] Information corresponding to the application DC;

[0375] Information corresponding to the IMS session;

[0376] Information corresponding to the IMS DC session.

[0377] An embodiment of the present application provides a communication device that can receive a notification message sent by a second communication device to obtain relevant information about an event that has occurred, that is, first information related to the terminal. This solution relatively comprehensively opens the terminal status to the communication device, allowing the communication device to obtain more terminal status, such as content related to an independent DC, whether the DC is related to the terminal on the local end or the terminal on the opposite end, etc., thereby more accurately determining the terminal status when the terminal is using a DC application.

[0378] The communication device provided in the embodiment of the present application can implement the various processes implemented in the above-mentioned communication method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0379] The communication device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0380] FIG12 shows a possible structural diagram of a communication device involved in an embodiment of the present application. As shown in FIG12 , a communication device 90 may include: a sending module 91 .

[0381] Among them, the sending module 91 is used to send a first message to the first communication device, the first message is used to notify the terminal of the first information related to the first information, and the first information is used to indicate at least one of the following: an independent boot DC has been established; an independent application DC has been established; an independent IMS DC session has become a normal IMS session; a normal IMS session has become an independent IMS DC session; a local boot DC has been established; a remote boot DC has been established; the local terminal initiates the establishment of an application DC; the opposite terminal initiates the establishment of an application DC; application information corresponding to the established application DC; information of the boot DC corresponding to the established application DC.

[0382] In one possible implementation, as shown in FIG13 in conjunction with FIG12 , the communication apparatus 90 further includes a receiving module 92. The receiving module 92 is configured to receive a second message sent by the first communication device, where the second message includes a first event, and the first event includes at least one of the following:

[0383] Establish an event to independently guide DC;

[0384] Establish an event for independent application DC;

[0385] The event in which an independent IMS DC session becomes a normal IMS session;

[0386] The event in which a normal IMS session becomes an independent IMS DC session;

[0387] Events for establishing a local bootstrap DC;

[0388] Establishing remote bootstrap DC events;

[0389] The local terminal initiates the event of establishing an application DC;

[0390] The peer terminal initiates the establishment of an application DC.

[0391] In one possible implementation, as shown in FIG13 in combination with FIG12 , the communication apparatus 90 further includes a receiving module 92. The receiving module 92 is configured to receive a third message sent by the first communication device, where the third message includes the second event and first indication information, where the first indication information is used to indicate relevant information about the second event.

[0392] In a possible implementation, the second event includes at least one of the following: an event of establishing a bootstrap DC, an event of establishing an application DC, an event of establishing a DC, and an event of establishing an IMS session;

[0393] The first indication information is used to indicate at least one of the following:

[0394] The DC is an independent boot DC or a dependent boot DC;

[0395] The DC is an independent application DC or a dependent application DC;

[0396] A DC is either an independent DC or a dependent DC.

[0397] In a possible implementation, the second event includes at least one of the following: an event of establishing or modifying a normal IMS session, an event of establishing an IMS session;

[0398] The first indication information is used to indicate at least one of the following:

[0399] The IMS session is obtained by change or not;

[0400] The IMS session is derived from an independent IMS DC session, or is not derived from an independent IMS DC session;

[0401] In a possible implementation, the second event includes at least one of the following: an event of establishing or modifying an independent IMS DC session, an event of establishing an IMS session;

[0402] The first indication information is used to indicate at least one of the following:

[0403] The IMS DC session is obtained by change or not;

[0404] The IMS DC session is derived from a normal IMS session or is not derived from a normal IMS session.

[0405] In a possible implementation, the second event includes at least one of the following: an event of establishing a bootstrap DC, an event of establishing an IMS session;

[0406] The first indication information is used to indicate at least one of the following:

[0407] DC is local or not local;

[0408] The DC is either remote or not remote.

[0409] In a possible implementation, the second event includes at least one of the following: an event of establishing an application DC, an event of establishing an IMS DC application, and an event of establishing an IMS session;

[0410] The first indication information is used to indicate at least one of the following:

[0411] DC is initiated by the local terminal or not;

[0412] DC is initiated by the peer terminal or not.

[0413] In a possible implementation, the second event includes an event of establishing an application DC;

[0414] The first indication information is used to indicate at least one of the following:

[0415] Application information corresponding to the application DC;

[0416] Information about the boot DC corresponding to the application DC.

[0417] In a possible implementation, the application information includes at least one of the following: application type, application identifier, and application binding information.

[0418] In one possible implementation, as shown in FIG13 in combination with FIG12 , the communication apparatus 90 further includes a receiving module 92. The receiving module 92 is configured to receive a fourth message sent by the first communication device, where the fourth message includes a second event and second indication information, where the second indication information is used to obtain at least one of the following:

[0419] Information corresponding to the guide DC;

[0420] Information corresponding to the application DC;

[0421] Information corresponding to the IMS session;

[0422] Information corresponding to the IMS DC session.

[0423] An embodiment of the present application provides a communication device that can send a notification message to a first communication device to notify relevant information of an event that has occurred, that is, first information related to the terminal. Through this solution, the terminal status is more comprehensively opened to the first communication device, allowing the first communication device to obtain more terminal status, such as content related to an independent DC, whether the DC is related to the terminal on the local end or the terminal on the opposite end, etc., thereby more accurately determining the terminal status when the terminal uses a DC application.

[0424] The communication device provided in the embodiment of the present application can implement the various processes implemented in the above-mentioned communication method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0425] As shown in Figure 14, an embodiment of the present application further provides a communication device 5000, including a processor 5001 and a memory 5002. The memory 5002 stores a program or instruction that can be run on the processor 5001. For example, when the communication device 5000 is a first communication device, the program or instruction is executed by the processor 5001 to implement the various steps of the above-mentioned first communication device side method embodiment, and can achieve the same technical effect. To avoid repetition, it is not repeated here. When the communication device 5000 is a second communication device, the program or instruction is executed by the processor 5001 to implement the various steps of the above-mentioned second communication device side method embodiment, and can achieve the same technical effect. To avoid repetition, it is not repeated here.

[0426] It should be noted that in the embodiment of the present application, the first communication device may be a terminal or a network-side device, and the network-side device may be an access network device or a core network device. The second communication device may be a terminal or a network-side device, and the network-side device may be an access network device or a core network device.

[0427] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps in the above-described communication method embodiment. This terminal embodiment corresponds to the above-described first communication device side or second communication device side method embodiment. Each implementation process and implementation method of the above-described method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 15 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0428] The terminal 7000 includes but is not limited to: a radio frequency unit 7001, a network module 7002, an audio output unit 7003, an input unit 7004, a sensor 7005, a display unit 7006, a user input unit 7007, an interface unit 7008, a memory 7009 and at least some of the components of the processor 7010.

[0429] Those skilled in the art will appreciate that the terminal 7000 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 7010 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG15 does not limit the terminal. The terminal may include more or fewer components than shown, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0430] It should be understood that in an embodiment of the present application, the input unit 7004 may include a graphics processing unit (GPU) 70041 and a microphone 70042, and the graphics processor 70041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 7006 may include a display panel 70061, and the display panel 70061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 7007 includes a touch panel 70071 and at least one of other input devices 70072. The touch panel 70071 is also called a touch screen. The touch panel 70071 may include two parts: a touch detection device and a touch controller. Other input devices 70072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0431] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 7001 may transmit the data to the processor 7010 for processing. Furthermore, the RF unit 7001 may send uplink data to the network-side device. Typically, the RF unit 7001 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0432] The memory 7009 can be used to store software programs or instructions and various data. The memory 7009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 7009 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may 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 may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 7009 in the embodiment of the present application includes, but is not limited to, these and any other suitable types of memory.

[0433] The processor 7010 may include one or more processing units. Optionally, the processor 7010 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into the processor 7010.

[0434] The terminal provided in the embodiment of the present application can implement the various processes implemented in the above-mentioned method embodiment and achieve the same technical effect. The implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above-mentioned communication method embodiment. To avoid repetition, it will not be repeated here.

[0435] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the above-mentioned communication method embodiment. This network-side device embodiment corresponds to the above-mentioned first communication device-side or second communication device-side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this network-side device embodiment and can achieve the same technical effects.

[0436] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 16, the network-side device 600 includes an antenna 601, a radio frequency device 602, a baseband device 603, a processor 604, and a memory 605. Antenna 601 is connected to radio frequency device 602. In the uplink direction, radio frequency device 602 receives information via antenna 601 and sends the received information to baseband device 603 for processing. In the downlink direction, baseband device 603 processes the information to be transmitted and sends it to radio frequency device 602. Radio frequency device 602 processes the received information and then sends it through antenna 601.

[0437] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 603 , which includes a baseband processor.

[0438] The baseband device 603 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 16, one of which is, for example, a baseband processor, which is connected to the memory 605 through a bus interface to call the program in the memory 605 and execute the network device operations shown in the above method embodiment.

[0439] The network side device may further include a network interface 606, which is, for example, a Common Public Radio Interface (CPRI).

[0440] Specifically, the network side device 600 of an embodiment of the present invention also includes: instructions or programs stored in the memory 605 and executable on the processor 604. The processor 604 calls the instructions or programs in the memory 605 to execute the methods executed by the modules shown in the above embodiment and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0441] The network side device provided in the embodiment of the present application can implement the various processes implemented in the above method embodiment and achieve the same technical effect. The implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above communication method embodiment. To avoid repetition, it will not be repeated here.

[0442] Specifically, the embodiment of the present application further provides a network side device. As shown in FIG17 , the network side device 1700 includes: a processor 1701, a network interface 1702, and a memory 1703. The network interface 1702 is, for example, a common public radio interface (CPRI).

[0443] Specifically, the network side device 1700 of the embodiment of the present application also includes: instructions or programs stored in the memory 1703 and executable on the processor 1701. The processor 1701 calls the instructions or programs in the memory 1703 to execute the methods executed by the modules shown in the above embodiment and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0444] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned communication method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0445] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0446] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned communication method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

[0448] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned communication method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0449] An embodiment of the present application also provides a communication system, including: a first communication device and a second communication device, wherein the first communication device can be used to execute the steps of the communication method described above, and the second communication device can be used to execute the steps of the communication method described above.

[0450] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0451] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0452] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A communication method, comprising: A first communication device receives a first message sent by a second communication device, where the first message is used to notify a terminal of related first information, where the first information is used to indicate at least one of the following: An independent boot data channel DC has been established; An independent application DC has been established; The independent Internet Protocol Multimedia Subsystem IMSDC session becomes a normal IMS session; Normal IMS sessions become independent IMSDC sessions; A local bootstrap DC has been established; A remote boot DC has been established; The local terminal initiates the establishment of the application DC; The peer terminal initiates the establishment of an application DC; Application information corresponding to the established application DC; Information about the boot DC corresponding to the established application DC.

2. The method according to claim 1, wherein The method further comprises: The first communication device sends a second message to the second communication device, where the second message includes a first event, and the first event includes at least one of the following: Establish an event to independently guide DC; Establish an event for independent application DC; The event in which an independent IMSDC session becomes a normal IMS session; The event in which a normal IMS session becomes an independent IMSDC session; Events for establishing a local bootstrap DC; Establishing remote bootstrap DC events; The local terminal initiates the event of establishing an application DC; The peer terminal initiates the establishment of an application DC.

3. The method according to claim 1, wherein The method further comprises: The first communication device sends a third message to the second communication device, where the third message includes a second event and first indication information, and the first indication information is used to indicate relevant information of the second event.

4. The method according to claim 3, wherein: The second event includes at least one of the following: an event of establishing a bootstrap DC, an event of establishing an application DC, an event of establishing a DC, and an event of establishing an IMS session; The first indication information is used to indicate at least one of the following: The DC is an independent boot DC or a dependent boot DC; The DC is an independent application DC or a dependent application DC; A DC is either an independent DC or a dependent DC.

5. The method according to claim 3, wherein The second event includes at least one of the following: an event of establishing or modifying a normal IMS session, an event of establishing an IMS session; The first indication information is used to indicate at least one of the following: The IMS session is obtained by change or not; The IMS session is derived from an independent IMSDC session or is not derived from an independent IMSDC session.

6. The method according to claim 3, wherein: The second event includes at least one of the following: an event of establishing or modifying an independent IMS DC session, an event of establishing an IMS session; The first indication information is used to indicate at least one of the following: The IMSDC session is obtained by change or not; The IMSDC session is derived from a normal IMS session or is not derived from a normal IMS session.

7. The method according to claim 3, wherein: The second event includes at least one of the following: an event of establishing a bootstrap DC, an event of establishing an IMS session; The first indication information is used to indicate at least one of the following: DC is local or not local; The DC is either remote or not remote.

8. The method according to claim 3, wherein: The second event includes at least one of the following: an event of establishing an application DC, an event of establishing an IMSDC application, and an event of establishing an IMS session; The first indication information is used to indicate at least one of the following: DC is initiated by the local terminal or not; DC is initiated by the peer terminal or not.

9. The method according to claim 3, wherein: The second event includes an event of establishing an application DC; The first indication information is used to indicate at least one of the following: Application information corresponding to the application DC; Information about the boot DC corresponding to the application DC.

10. The method according to any one of claims 1 to 9, wherein The application information includes at least one of the following: application type, application identifier, and application binding information.

11. The method according to claim 1, wherein The method further comprises: The first communication device sends a fourth message to the second communication device, where the fourth message includes a second event and second indication information, where the second indication information is used to obtain at least one of the following: Information corresponding to the guide DC; Information corresponding to the application DC; Information corresponding to the IMS session; Information corresponding to the IMSDC session.

12. A communication method, comprising: The second communication device sends a first message to the first communication device, where the first message is used to notify the terminal of related first information, where the first information is used to indicate at least one of the following: An independent boot DC has been established; An independent application DC has been established; The independent IMSDC session becomes a normal IMS session; Normal IMS sessions become independent IMSDC sessions; A local bootstrap DC has been established; A remote boot DC has been established; The local terminal initiates the establishment of the application DC; The peer terminal initiates the establishment of an application DC; Application information corresponding to the established application DC; Information about the boot DC corresponding to the established application DC.

13. The method according to claim 12, wherein: The method further comprises: The second communication device receives a second message sent by the first communication device, where the second message includes a first event, and the first event includes at least one of the following: Establish an event to independently guide DC; Establish an event for independent application DC; The event in which an independent IMSDC session becomes a normal IMS session; The event in which a normal IMS session becomes an independent IMSDC session; Events for establishing a local bootstrap DC; Establishing remote bootstrap DC events; The local terminal initiates the event of establishing an application DC; The peer terminal initiates the establishment of an application DC.

14. The method according to claim 12, wherein: The method further comprises: The second communication device receives a third message sent by the first communication device, where the third message includes a second event and first indication information, and the first indication information is used to indicate relevant information of the second event.

15. The method according to claim 14, wherein The second event includes at least one of the following: an event of establishing a bootstrap DC, an event of establishing an application DC, an event of establishing a DC, and an event of establishing an IMS session; The first indication information is used to indicate at least one of the following: The DC is an independent boot DC or a dependent boot DC; The DC is an independent application DC or a dependent application DC; A DC is either an independent DC or a dependent DC.

16. The method according to claim 14, wherein The second event includes at least one of the following: an event of establishing or modifying a normal IMS session, an event of establishing an IMS session; The first indication information is used to indicate at least one of the following: The IMS session is obtained by change or not; The IMS session is derived from an independent IMSDC session or is not derived from an independent IMSDC session.

17. The method according to claim 14, wherein: The second event includes at least one of the following: an event of establishing or modifying an independent IMSDC session, an event of establishing an IMS session; The first indication information is used to indicate at least one of the following: The IMSDC session is obtained by change or not; The IMSDC session is derived from a normal IMS session or is not derived from a normal IMS session.

18. The method according to claim 14, wherein The second event includes at least one of the following: an event of establishing a bootstrap DC, an event of establishing an IMS session; The first indication information is used to indicate at least one of the following: DC is local or not local; The DC is either remote or not remote.

19. The method according to claim 14, wherein The second event includes at least one of the following: an event of establishing an application DC, an event of establishing an IMSDC application, and an event of establishing an IMS session; The first indication information is used to indicate at least one of the following: DC is initiated by the local terminal or not; DC is initiated by the peer terminal or not.

20. The method according to claim 14, wherein The second event includes an event of establishing an application DC; The first indication information is used to indicate at least one of the following: Application information corresponding to the application DC; Information about the boot DC corresponding to the application DC.

21. The method according to any one of claims 12 to 20, wherein The application information includes at least one of the following: application type, application identifier, and application binding information.

22. The method according to claim 12, wherein The method further comprises: The second communication device receives a fourth message sent by the first communication device, where the fourth message includes a second event and second indication information, where the second indication information is used to obtain at least one of the following: Information corresponding to the guide DC; Information corresponding to the application DC; Information corresponding to the IMS session; Information corresponding to the IMSDC session.

23. A communication device comprising: Receiver module; The receiving module is configured to receive a first message sent by a second communication device, where the first message is used to notify the terminal of related first information, where the first information is used to indicate at least one of the following: An independent boot DC has been established; An independent application DC has been established; The independent IMSDC session becomes a normal IMS session; Normal IMS sessions become independent IMSDC sessions; A local bootstrap DC has been established; A remote boot DC has been established; The local terminal initiates the establishment of the application DC; The peer terminal initiates the establishment of an application DC; Application information corresponding to the established application DC; Information about the boot DC corresponding to the established application DC.

24. The device according to claim 23, wherein The device further includes: a sending module; The sending module is configured to send a second message to the second communication device, where the second message includes a first event, and the first event includes at least one of the following: Establish an event to independently guide DC; Establish an event for independent application DC; The event in which an independent IMSDC session becomes a normal IMS session; The event in which a normal IMS session becomes an independent IMSDC session; Events for establishing a local bootstrap DC; Establishing remote bootstrap DC events; The local terminal initiates the event of establishing an application DC; The peer terminal initiates the establishment of an application DC.

25. The apparatus according to claim 23, wherein The device further includes: a sending module; The sending module is used to send a third message to the second communication device, where the third message includes a second event and first indication information, and the first indication information is used to indicate relevant information of the second event.

26. The apparatus according to claim 23, wherein The device further includes: a sending module; The sending module is configured to send a fourth message to the second communication device, where the fourth message includes a second event and second indication information, where the second indication information is used to obtain at least one of the following: Information corresponding to the guide DC; Information corresponding to the application DC; Information corresponding to the IMS session; Information corresponding to the IMSDC session.

27. A communication device comprising: Sending module; The sending module is configured to send a first message to the first communication device, where the first message is used to notify the terminal of related first information, where the first information is used to indicate at least one of the following: An independent boot DC has been established; An independent application DC has been established; The independent IMSDC session becomes a normal IMS session; Normal IMS sessions become independent IMSDC sessions; A local bootstrap DC has been established; A remote boot DC has been established; The local terminal initiates the establishment of the application DC; The peer terminal initiates the establishment of an application DC; Application information corresponding to the established application DC; Information about the boot DC corresponding to the established application DC.

28. The apparatus according to claim 27, wherein The device further includes: a receiving module; The receiving module is configured to receive a second message sent by the first communication device, where the second message includes a first event, and the first event includes at least one of the following: Establish an event to independently guide DC; Establish an event for independent application DC; The event in which an independent IMSDC session becomes a normal IMS session; The event in which a normal IMS session becomes an independent IMSDC session; Events for establishing a local bootstrap DC; Establishing remote bootstrap DC events; The local terminal initiates the event of establishing an application DC; The peer terminal initiates the establishment of an application DC.

29. The apparatus according to claim 27, wherein The device further includes: a receiving module; The receiving module is configured to receive a third message sent by the first communication device, where the third message includes a second event and first indication information, and the first indication information is used to indicate relevant information of the second event.

30. The apparatus of claim 27, wherein: The device further includes: a receiving module; The receiving module is configured to receive a fourth message sent by the first communication device, where the fourth message includes a second event and second indication information, where the second indication information is used to obtain at least one of the following: Information corresponding to the guide DC; Information corresponding to the application DC; Information corresponding to the IMS session; Information corresponding to the IMSDC session.

31. A communication device comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, implements the steps of the communication method according to any one of claims 1 to 11, or implements the steps of the communication method according to any one of claims 12 to 22.

32. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the communication method according to any one of claims 1 to 11, or implements the steps of the communication method according to any one of claims 12 to 22.

33. A computer program, wherein the computer program is stored in a storage medium, and when the program is executed by at least one processor, implements the communication method according to any one of claims 1 to 11, or implements the steps of the communication method according to any one of claims 12 to 22.

Images