WO2025195331A1 - 通信方法、装置、设备及存储介质 - Google Patents

通信方法、装置、设备及存储介质

Info

Publication number
WO2025195331A1
WO2025195331A1 PCT/CN2025/082962 CN2025082962W WO2025195331A1 WO 2025195331 A1 WO2025195331 A1 WO 2025195331A1 CN 2025082962 W CN2025082962 W CN 2025082962W WO 2025195331 A1 WO2025195331 A1 WO 2025195331A1
Authority
WO
WIPO (PCT)
Prior art keywords
event
application
session
independent
establishing
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2025/082962
Other languages
English (en)
French (fr)
Inventor
金辉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2025195331A1 publication Critical patent/WO2025195331A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Definitions

  • the present application belongs to the field of communication technology, and specifically relates to a communication method, apparatus, device and storage medium.
  • the communication standard introduces a mechanism for establishing a Data Channel (DC) during a call.
  • DC Data Channel
  • This 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 experience.
  • IMS Internet Protocol Multimedia Subsystem
  • IMS session status changes IMS session status changes
  • 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.
  • a communication method comprising: a first communication device receiving 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.
  • IMS Internet Protocol Multimedia Subsystem
  • a communication method 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 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.
  • a communication device comprising: a receiving module.
  • the receiving module is 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.
  • a communication device comprising: a sending module, configured to send a first message to a first communication device, the first message being configured to notify a terminal of first information related thereto, the first information being configured 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.
  • a communication device 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.
  • a communication device 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.
  • a communication device 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.
  • a communication device 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.
  • a readable storage medium on which a program or instruction is stored.
  • 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.
  • a wireless communication system 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.
  • 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 method as described in the first aspect, or to implement the method as described in the second 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.
  • 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.
  • 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.
  • FIG1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application.
  • FIG2 is a flow chart of a communication method according to an embodiment of the present application.
  • FIG3 is a second flow chart of a communication method provided in an embodiment of the present application.
  • FIG4 is a third flow chart of a communication method provided in an embodiment of the present application.
  • FIG5 is a fourth flow chart of a communication method provided in an embodiment of the present application.
  • FIG6 is a fifth flow chart of a communication method provided in an embodiment of the present application.
  • FIG7 is a sixth flowchart of a communication method provided in an embodiment of the present application.
  • FIG8 is a seventh flowchart of a communication method provided in an embodiment of the present application.
  • FIG9 is a flowchart of an eighth embodiment of a communication method provided by the present application.
  • FIG10 is a schematic diagram of a structure of a communication device according to an embodiment of the present application.
  • FIG11 is a second structural diagram of a communication device provided in an embodiment of the present application.
  • FIG12 is a third structural diagram of a communication device provided in an embodiment of the present application.
  • FIG13 is a fourth structural diagram of a communication device provided in an embodiment of the present application.
  • FIG14 is a schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application.
  • FIG15 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application.
  • FIG16 is a schematic diagram of a hardware structure of a network side device according to an embodiment of the present application.
  • FIG17 is a second schematic diagram of the hardware structure of a network-side device provided in an embodiment of the present application.
  • 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.
  • “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.
  • 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.
  • 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.
  • 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.
  • at least two means two or more, and its meaning is similar to "at least one”.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR New Radio
  • 6G 6th Generation
  • FIG1 shows a block diagram of a wireless communication system applicable to embodiments of the present application.
  • the wireless communication system includes a terminal 11 and a network-side device 12 .
  • the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (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 (Wearable Device), a flight vehicle, a vehicle user equipment (VUE), a ship-borne equipment, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (PC), an ATM or a self-service machine and other terminal-side devices.
  • PC personal computer
  • ATM an ATM or a self-service machine and other terminal
  • 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.
  • a chip in the terminal such as a modem chip or a system-on-chip (SoC).
  • SoC system-on-chip
  • 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.
  • WLAN wireless local area network
  • AS wireless local area network
  • WiFi wireless fidelity
  • the base station can be called 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, base The Basic Service Set (BSS), Extended Service Set (ESS), home Node B (HNB), 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 embodiments of the present application, only the base station in the NR system is introduced as an example, and the specific type of the base station is not limited.
  • 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 (PCRF), Edge Application Server Discovery Function (Edge Application Server Discovery Function), and so on.
  • EASDF Unified Data Management
  • UDM Unified Data Repository
  • HSS Home Subscriber Server
  • CNC Centralized Network Configuration
  • NRF Network Repository Function
  • NEF Network Exposure Function
  • L-NEF Binding Support Function
  • BSF Binding Support Function
  • AF Application Function
  • 3GPP 3rd Generation Partnership Project
  • IMS DC application event When a specific user downloads an IMS DC application, the producer reports the corresponding event to the consumer;
  • IMS session events When the session status or media of a specific IMS session changes, the producer reports the corresponding event to the consumer;
  • Supplementary service events When a supplementary service is activated for a specific IMS session, the producer reports the corresponding event to the consumer.
  • 3rd Party registration event When the producer receives a 3rd party registration request, the producer reports the corresponding event to the consumer.
  • 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.
  • 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.
  • 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.
  • 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.
  • the 3GPP standard introduces a mechanism for establishing DC during a call.
  • 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, making it easier for users to use.
  • Bootstrap DC used to download DC applications from the data channel server (e.g. Data Channel Signaling Function (DCSF));
  • DCSF Data Channel Signaling Function
  • Application DC used to transmit DC application data.
  • 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.
  • the bootstrap DC is usually established by the terminal.
  • 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).
  • Application DC can be established by the terminal or by the network server.
  • 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.
  • the present invention provides a communication method
  • Figure 2 shows a flow chart of the communication method provided by the present invention.
  • the communication method provided by the present invention may include the following steps 201 and 202.
  • Step 201 A second communication device sends a first message to a first communication device.
  • Step 202 The first communication device receives a first message sent by the second communication device.
  • the first message is used to notify the terminal of related first information
  • the first information is used to indicate at least one of the following:
  • a standalone bootstrap data channel has been established.
  • a standalone application data channel (DC) has been established.
  • the independent IMS DC session becomes a normal IMS session
  • the local terminal initiates the establishment of the application DC;
  • the peer terminal initiates the establishment of an application DC
  • 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.
  • MMTEL Multimedia Telephony
  • the above-mentioned independent IMS DC session may include at least one of the following: independent boot DC, independent application DC.
  • IMS DC session can be understood as DC session.
  • voice, video or messaging media is added to an independent IMS DC session, and the independent IMS DC session can be converted into a normal IMS session.
  • 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.
  • the local bootstrap DC may also be referred to as the bootstrap DC connected to the local DCSF or the originating bootstrap DC
  • the remote bootstrap DC may also be referred to as the bootstrap DC connected to the remote DCSF or the terminating bootstrap DC.
  • 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.
  • the above-mentioned consumer may be a network function (NF) service consumer.
  • NF network function
  • 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.
  • the above-mentioned consumer may be a DCSF
  • the above-mentioned producer may be an IMS AS or HSS.
  • the first message may be a notification message, such as Notify_Request.
  • the communication method provided in the embodiment of the present application also includes the following steps 301 and 302.
  • Step 301 A first communication device sends a second message to a second communication device.
  • Step 302 The second communication device receives a second message sent by the first communication device.
  • the second message includes a first event
  • the first event includes at least one of the following:
  • the local terminal initiates the event of establishing an application DC
  • the peer terminal initiates the establishment of an application DC.
  • the second message may be a subscription message (or subscription request) for requesting to subscribe to the first information related to the terminal.
  • the second message may be a Subscribe_Request.
  • 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.
  • the intermediate NF when the consumer is AF, NEF or DC AS, the intermediate NF may be HSS, and the producer may be DCSF or IMS AS.
  • the intermediate NF when the above-mentioned consumer is DCSF or NEF, the intermediate NF may be HSS and the producer may be IMS AS.
  • the intermediate NF when the above-mentioned consumer is AF, NEF or DC AS, the intermediate NF can be DCSF and the producer can be IMS AS.
  • the intermediate NF can be DCSF or NEF
  • the producer can be IMS AS.
  • the first information is used to indicate at least one of the following:
  • the independent IMS DC session becomes a normal IMS session
  • the local terminal initiates the establishment of the application DC;
  • the peer terminal initiates the establishment of an 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).
  • 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.
  • 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.
  • the terminal has established an application DC can be understood or replaced by: the terminal has completed the establishment of the application DC, or the application DC has been established between the terminal and the opposite end (the opposite end UE or DC AS), or the network side has established an application DC for the terminal. The following will be omitted for clarity.
  • Example 1-2 For event 1-2: a standalone IMS DC session becomes a normal IMS session.
  • the consumer subscribes to the producer for the event that the standalone IMS DC session becomes a normal IMS session (i.e., the consumer sends a second message to the producer).
  • the producer determines that the terminal's standalone IMS DC session has become a normal IMS session, it sends a notification message (i.e., a first message) to the consumer, notifying them of the change (i.e., the first message).
  • the second message includes the first event (event 1-2), which is the event that the standalone IMS DC session becomes a normal IMS session.
  • 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 of a normal IMS session becoming an independent IMS DC session (i.e., the consumer sends a second message to the producer).
  • the producer determines that the terminal's normal IMS session has become an independent IMS DC session, it sends a notification message (i.e., a first message) to the consumer, notifying them of the change (i.e., the first message).
  • the second message includes the first event (event 1-3), which is the change from a normal IMS session to an independent IMS DC session.
  • 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).
  • 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.
  • 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).
  • 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).
  • event 1-5 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).
  • the consumer subscribes to a specific event (i.e., the first event) from the producer.
  • a specific event i.e., the first event
  • 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.
  • 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.
  • the communication method provided in the embodiment of the present application also includes the following steps 401 and 402.
  • Step 401 A first communication device sends a third message to a second communication device.
  • Step 402 The second communication device receives a third message sent by the first communication device.
  • 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.
  • the third message may be a subscription message, used to request subscription of the first information related to the terminal.
  • the third message may be Subscribe_Request.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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
  • 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
  • the second event is an event of establishing an application DC
  • 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
  • the second event is an event of establishing a DC
  • 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.
  • the second event is an event of establishing an IMS session
  • 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.
  • the DC refers to the DC already established by the terminal, including the bootstrap DC or the application 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.
  • the first indication information may be 1-bit information.
  • a value of 1 for the first indication information indicates that the system is in standalone mode
  • 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).
  • a value of 0 for the first indication information indicates that the system is in standalone mode
  • a value of 1 for the first indication information indicates that the system is not in standalone mode.
  • 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.
  • the above-mentioned indication information a and indication information b may be the same parameter, which may be implemented through multi-bit encoding, where the first bit is 1 to indicate a standalone bootstrap DC, and the first bit is 0 to indicate a non-standalone bootstrap DC; the second bit is 1 to indicate a standalone application DC, and the second bit is 0 to indicate a non-standalone application DC.
  • 11 indicates both a standalone bootstrap DC and a standalone application DC
  • 10 indicates both a standalone bootstrap DC and a non-standalone application DC
  • 01 indicates both a standalone application DC and a non-standalone bootstrap DC;
  • 00 indicates both a standalone bootstrap DC and a non-standalone application DC.
  • 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 IMS DC session or is not derived from an independent IMS DC session.
  • the first communications device sends the second event (general event) and the first indication information to the second communications device, causing the second communications device to send a notification message upon determining that the IMS session established by the terminal has changed, or that the terminal's independent IMS DC session has become a normal IMS session.
  • the second event occurs and the IMS session at the time of the second event is the result of a change indicated by the first indication information, or is a change from an independent IMS DC session
  • the specific event is considered to have occurred. That is, the second event and the first indication information, taken together, correspond to the specific event.
  • Example 2-2 For event 2-2 + first indication information (corresponding to event 1-2 above), the consumer subscribes to the producer for the event that an independent IMS DC session becomes a normal IMS session (i.e., the consumer sends a third message to the producer).
  • the producer determines that the IMS session established by the terminal has been changed, or that the terminal's independent IMS DC session has become a normal IMS session, it sends a notification message (i.e., the first message) to the consumer to notify the independent IMS DC session of the change to a normal IMS session (i.e., the first message).
  • 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.
  • the first indication information may be 1-bit information.
  • 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 an independent IMS DC 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 an independent IMS DC session.
  • 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 an independent IMS DC 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 an independent IMS DC session.
  • 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:
  • the IMS DC session is obtained or not;
  • An IMS DC session is derived from a normal IMS session or is not derived from a normal IMS session.
  • the first communications device sends the second event (general event) and the first indication information to the second communications device, causing the second communications device to send a notification message when it determines that the IMS session established by the terminal has changed, or that the terminal's normal IMS session has become an independent IMS DC session.
  • the second event occurs and the IMS session at the time of the second event is a change indicated by the first indication information or a change from a normal IMS session, then it is considered that a specific event has occurred. That is, the second event and the first indication information, taken together, correspond to a specific event.
  • Example 2-3 For event 2-3 + first indication information (corresponding to events 1-3 above), the consumer subscribes to the producer for the event that a normal IMS session is transformed into an independent IMS DC session (i.e., the consumer sends a third message to the producer).
  • the producer determines that the IMS session established by the terminal has been modified, or that the terminal's normal IMS session has been transformed into an independent IMS DC session, it sends a notification message (i.e., the first message) to the consumer to notify them of the transformation of the normal IMS session into an independent IMS DC session (i.e., the first message).
  • the third message includes the second event (event 2-3) and the first indication information.
  • the second event is the event of establishing or modifying an independent IMS DC session, or the event of establishing an IMS session.
  • the first indication information may be 1-bit information.
  • 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.
  • 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.
  • 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.
  • the first indication information corresponding to events 2-2 and 2-3 can be the same parameter, which can be implemented through joint coding.
  • 1 indicates that the IMS session is derived from an independent IMS DC session, and 0 indicates that the IMS session is derived from a normal IMS session.
  • 0 indicates that the IMS session is derived from an independent IMS DC session, and 1 indicates that the IMS session is derived from a normal IMS session.
  • 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.
  • 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.
  • 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.
  • the first indication information may be 1-bit information.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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:
  • DC is initiated by the peer terminal or not.
  • 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.
  • 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.
  • Example 2-5 for event 2-5 + first indication information (corresponding to the above events 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 (i.e., the consumer sends a third message to the producer).
  • 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 third message includes the second event (event 2-5) and the first indication information.
  • the second event is an event of establishing an application DC, or an event of establishing an IMS DC application, or an event of establishing an IMS session.
  • the first indication information may be 1-bit information.
  • 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.
  • 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.
  • the first indication information may be 1-bit information.
  • 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.
  • 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.
  • 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:
  • 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.
  • 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.
  • 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).
  • 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.
  • the consumer subscribes to the producer for an event that the terminal uses a screen sharing app.
  • the application corresponding to the application DC is the screen sharing app
  • the producer sends a notification message to the consumer.
  • 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.
  • 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).
  • 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 was downloaded.
  • the above-mentioned information about the bootstrap DC may be the stream ID of the bootstrap DC.
  • the consumer subscribes to a specific event (i.e., the second event + the first indication information) from the producer.
  • a specific event i.e., the second event + the first indication information
  • 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.
  • 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.
  • the communication method provided in the embodiment of the present application also includes the following steps 501 and 502.
  • Step 501 A first communication device sends a fourth message to a second communication device.
  • Step 502 The second communication device receives a fourth message sent by the first communication device.
  • 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.
  • the fourth message 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.
  • 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.
  • the consumer subscribes to a general event (i.e., the second event) from the producer.
  • a general event i.e., the second event
  • 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.
  • 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.
  • 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.
  • the communication method provided in the embodiment of the present application includes the following steps 20 to 25 .
  • 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.
  • the subscription message may be Subscribe_Request.
  • Step 21 The producer creates a new event subscription resource and starts detecting subscribed events.
  • Step 22 The producer sends a response message to the NF service consumer.
  • the response message can be Subscribe_Request response.
  • Step 23 The producer determines that the subscribed event occurs.
  • Step 24 The producer sends a notification message to the NF service consumer to notify the terminal of the first information.
  • the notification message may be Notify_Request.
  • Step 25 The NF service consumer sends a response message to the producer.
  • the response message can be Notify_Request response.
  • step 20 is specifically step 20a: the consumer subscribes to the producer for the 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).
  • 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.
  • 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.
  • 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:
  • 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.
  • step 20 is specifically step 20b: the consumer subscribes to the producer for the event that the independent IMS DC session becomes a normal IMS session (that is, the consumer sends a subscription message to the producer).
  • step 24 is specifically step 24b: when the producer determines that the terminal's independent IMS DC session becomes a normal IMS session, it sends a notification message to the consumer.
  • the subscription message includes a first event (event 1-2), which is an event in which an independent IMS DC session becomes a normal IMS session.
  • 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:
  • the IMS session is obtained by change or not;
  • the IMS session is derived from an independent IMS DC session or is not derived from an independent IMS DC session.
  • step 20 is specifically step 20c: the consumer subscribes to the producer for the event that the normal IMS session becomes an independent IMS DC session (that is, the consumer sends a subscription message to the producer).
  • step 24 is specifically step 24c: when the producer determines that the normal IMS session of the terminal has become an independent IMS DC session, it sends a notification message to the consumer.
  • the subscription message includes the first event (event 1-3), which is the event in which a normal IMS session becomes an independent IMS DC session.
  • 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:
  • the IMS DC session is obtained or not;
  • An IMS DC session is derived from a normal IMS session or is not derived from a normal IMS session.
  • 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).
  • 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.
  • 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.
  • 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:
  • DC is local or not local
  • the DC is either remote or not remote.
  • 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).
  • 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.
  • 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 originating application DC event), or the event of the peer terminal initiating the establishment of the application DC (also called terminating application DC event).
  • event 1-5 is the event of the local terminal initiating the establishment of the application DC (also called originating application DC event), or the event of the peer terminal initiating the establishment of the application DC (also called terminating application DC event).
  • 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:
  • DC is initiated by the peer terminal or not.
  • 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).
  • 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.
  • 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:
  • 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.
  • the communication method provided in the embodiment of the present application includes the following steps 30 to 42 .
  • 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.
  • Step 31 The intermediate NF determines the producer.
  • 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.
  • the subscription message in step 30 and the subscription message in step 32 may be the same or different.
  • the subscription message may be Subscribe_Request.
  • Step 33 The producer creates a new event subscription resource and starts detecting subscribed events.
  • Step 34 The producer sends a response message to the intermediate NF.
  • Step 35 The intermediate NF sends a response message to the NF service consumer.
  • the response message in step 34 and the response message in step 35 may be the same or different.
  • the response message in step 34 may be Subscribe_Request response
  • the response message in step 35 may be Ndcsf_EE_Subscribe_Request response.
  • Step 36 The producer determines that the subscribed event occurs.
  • Step 37 The producer sends a notification message to the intermediate NF to notify the terminal of the first information.
  • Step 38 The intermediate NF sends a notification message to the NF service consumer to notify the terminal of the first information.
  • notification message in step 37 and the notification message in step 38 may be the same or different.
  • the notification message may be Notify_Request.
  • Step 39 The NF service consumer sends a response message to the intermediate NF.
  • Step 40 The intermediate NF sends a response message to the producer.
  • response message in step 39 and the response message in step 40 may be the same or different.
  • the response message may be Notify_Request response.
  • Step 41 The producer directly sends a notification message to the NF service consumer to notify the terminal of the first information.
  • the notification message may be Notify_Request.
  • Step 42 The NF service consumer sends a response message directly to the producer.
  • the response message can be Notify_Request response.
  • 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.
  • 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.
  • the communication method provided in the embodiment of the present application includes the following steps 50 to 55 .
  • Step 50 The NF service consumer sends a subscription message to the producer, where the subscription message includes the second event.
  • the subscription message may be Subscribe_Request.
  • the above subscription message also includes second indication information.
  • Step 51 The producer creates a new event subscription resource and starts detecting subscribed events.
  • Step 52 The producer sends a response message to the NF service consumer.
  • the response message can be Subscribe_Request response.
  • Step 53 The producer determines that the subscribed event occurs.
  • 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.
  • the notification message may be Notify_Request.
  • Step 55 The NF service consumer sends a response message to the producer.
  • the response message can be Notify_Request response.
  • the second event 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:
  • 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.
  • 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:
  • 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.
  • the second event 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:
  • the second indication information is used to obtain information corresponding to the IMS session.
  • 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:
  • the IMS session is obtained by change or not;
  • the IMS session is derived from an independent IMS DC session or is not derived from an independent IMS DC session.
  • the second event 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:
  • the above second indication information is used to obtain information corresponding to the IMS DC session.
  • 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:
  • the IMS DC session is obtained or not;
  • An IMS DC session is derived from a normal IMS session or is not derived from a normal IMS session.
  • the second event 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:
  • the above-mentioned second indication information is used to obtain information corresponding to the boot DC.
  • 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:
  • DC is local or not local
  • the DC is either remote or not remote.
  • the second event 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, or an event of establishing an IMS session:
  • the above-mentioned second indication information is used to obtain information corresponding to the application DC.
  • 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:
  • DC is initiated by the peer terminal or not.
  • the second event 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:
  • the above-mentioned second indication information is used to obtain information corresponding to the application DC.
  • 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:
  • 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.
  • the communication method provided in the embodiment of the present application includes the following steps 60 to 72 .
  • Step 60 The NF service consumer sends a subscription message to the intermediate NF, where the subscription message includes the second event.
  • the above subscription message also includes second indication information.
  • Step 61 The intermediate NF determines the producer.
  • Step 62 The intermediate NF sends a subscription message to the producer, where the subscription message includes the second event.
  • the subscription message in step 60 and the subscription message in step 62 may be the same or different.
  • the subscription message may be Subscribe_Request.
  • Step 63 The producer creates a new event subscription resource and starts detecting subscribed events.
  • Step 64 The producer sends a response message to the intermediate NF.
  • Step 65 The intermediate NF sends a response message to the producer.
  • the response message in step 64 and the response message in step 65 may be the same or different.
  • the response message in step 64 may be Subscribe_Request response
  • the response message in step 65 may be Ndcsf_EE_Subscribe_Request response.
  • Step 66 The producer determines that the subscribed event occurs.
  • 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.
  • 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.
  • the notification message in step 67 and the notification message in step 68 may be the same or different.
  • the notification message may be Notify_Request.
  • Step 69 The NF service consumer sends a response message to the intermediate NF.
  • Step 70 The intermediate NF sends a response message to the producer.
  • the response message in step 69 and the response message in step 70 may be the same or different.
  • the response message may be Notify_Request response.
  • 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.
  • the notification message may be Notify_Request.
  • Step 72 The NF service consumer sends a response message directly to the producer.
  • the response message can be Notify_Request response.
  • 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.
  • 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.
  • 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.
  • 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.
  • the communication method provided in the embodiment of the present application can be executed by a communication device.
  • 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.
  • FIG10 shows a possible structural diagram of a communication device involved in an embodiment of the present application.
  • the communication device 80 may include: a receiving module 81 .
  • 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.
  • 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:
  • the local terminal initiates the event of establishing an application DC
  • the peer terminal initiates the establishment of an application DC.
  • 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.
  • 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.
  • 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 a standalone IMS DC session, or is not derived from a standalone IMS DC session;
  • 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:
  • the IMS DC session is obtained or not;
  • An IMS DC session is derived from a normal IMS session or is not derived from a normal IMS session.
  • 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.
  • 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:
  • DC is initiated by the peer terminal or not.
  • 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:
  • the application information includes at least one of the following: application type, application identifier, and application binding information.
  • 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:
  • 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.
  • 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.
  • the communication device in the embodiments of the present application may 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 a chip.
  • the electronic device may be a terminal, or may be another device other than a terminal.
  • the terminal may include but is not limited to the types of terminal 11 listed above, and the other devices may be a server, a network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.
  • FIG12 shows a possible structural diagram of a communication device involved in an embodiment of the present application.
  • a communication device 90 may include: a sending module 91 .
  • 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 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.
  • 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:
  • the local terminal initiates the event of establishing an application DC
  • the peer terminal initiates the establishment of an application DC.
  • 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.
  • 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.
  • 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 a standalone IMS DC session, or is not derived from a standalone IMS DC session;
  • 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:
  • the IMS DC session is obtained or not;
  • An IMS DC session is derived from a normal IMS session or is not derived from a normal IMS session.
  • 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.
  • 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:
  • DC is initiated by the peer terminal or not.
  • 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:
  • the application information includes at least one of the following: application type, application identifier, and application binding information.
  • 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:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Figure 15 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.
  • 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.
  • 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.
  • 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 the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the 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 the 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 a joystick, which will not be repeated here.
  • 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.
  • 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.
  • 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.
  • 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.).
  • the memory 7009 may include volatile memory or non-volatile memory.
  • 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 random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM (DRRAM).
  • RAM random access memory
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDRSDRAM double data rate synchronous DRAM
  • ESDRAM enhanced SDRAM
  • SLDRAM synchronous link DRAM
  • DRRAM direct RAM
  • the memory 7009 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.
  • the processor 7010 may include one or more processing units.
  • 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.
  • 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.
  • 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.
  • 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.
  • radio frequency device 602 receives information via antenna 601 and sends the received information to baseband device 603 for processing.
  • 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.
  • 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.
  • 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.
  • the network side device may also include a network interface 606, which is, for example, a Common Public Radio Interface (CPRI).
  • CPRI Common Public Radio Interface
  • 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.
  • 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.
  • an embodiment of the present application further provides a network-side device.
  • 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).
  • CPRI common public radio interface
  • 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.
  • An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored.
  • a program or instruction is stored.
  • 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.
  • 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.
  • ROM computer read-only memory
  • RAM random access memory
  • magnetic disk such as a hard disk, a hard disk, or a magnetic disk.
  • optical disk such as a hard disk, a hard disk, or an optical disk.
  • the readable storage medium may be a non-transitory readable storage medium.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a storage medium such as ROM, RAM, magnetic disk, optical disk, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Databases & Information Systems (AREA)
  • Computer And Data Communications (AREA)
  • Communication Control (AREA)

Abstract

本申请公开了一种通信方法、装置、设备及存储介质，属于通信技术领域，本申请实施例的通信方法包括：第一通信设备接收第二通信设备发送的第一消息，第一消息用于通知终端相关的第一信息，第一信息用于指示以下至少一项：已建立独立引导DC；已建立独立应用DC；独立IMS DC会话变为正常IMS会话；正常IMS会话变为独立IMS DC会话；已建立本地引导DC；已建立远端引导DC；本地终端发起应用DC的建立；对端终端发起应用DC的建立；建立的应用DC对应的应用信息；建立的应用DC对应的引导DC的信息。

Description

通信方法、装置、设备及存储介质
相关申请的交叉引用
本申请主张在2024年03月22日在中国提交的申请号为202410337065.9的中国专利的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种通信方法、装置、设备及存储介质。
背景技术
在通信标准中，引入了在通话过程中建立数据通道(Data Channel，DC)的机制，通过DC可以在通话过程中进行额外的业务，例如进行屏幕共享，位置共享，文件传输等，从而给用户带来更好的体验。不同的业务对应不同的DC应用(application)，该DC应用可以在通话过程中动态下载到终端，不需要终端提前安装，方便用户使用。
目前，通信标准定义了开放终端状态的方法，consumer(例如第三方服务器)可以向producer(例如客户端)发送订阅请求，该订阅请求中包括请求订阅的事件，例如互联网协议多媒体子系统(Internet Protocol Multimedia Subsystem，IMS)DC应用事件、IMS会话事件(IMS会话状态发生变化)等，以便于获知终端使用DC应用时的终端状态。
然而，目前仅考虑了上述IMS DC应用下载、IMS会话状态变化等IMS业务，producer向第三方服务器开放的终端状态不够全面，因此会导致无法准确地判断终端使用DC时的终端状态。
发明内容
本申请实施例提供一种通信方法、装置、设备及存储介质，能够解决无法准确地判断终端使用DC时的终端状态的问题。
第一方面，提供了一种通信方法，该方法包括：第一通信设备接收第二通信设备发送的第一消息，第一消息用于通知终端相关的第一信息，第一信息用于指示以下至少一项：已建立独立引导DC；已建立独立应用DC；独立互联网协议多媒体子系统(Internet Protocol Multimedia Subsystem，IMS)DC会话变为正常IMS会话；正常IMS会话变为独立IMS DC会话；已建立本地引导DC；已建立远端引导DC；本地终端发起应用DC的建立；对端终端发起应用DC的建立；建立的应用DC对应的应用信息；建立的应用DC对应的引导DC的信息。
第二方面，提供了一种通信方法，该方法包括：第二通信设备向第一通信设备发送第一消息，第一消息用于通知终端相关的第一信息，第一信息用于指示以下至少一项：已建立独立引导DC；已建立独立应用DC；独立IMS DC会话变为正常IMS会话；正常IMS会话变为独立IMS DC会话；已建立本地引导DC；已建立远端引导DC；本地终端发起应用DC的建立；对端终端发起应用DC的建立；建立的应用DC对应的应用信息；建立的应用DC对应的引导DC的信息。
第三方面，提供了一种通信装置，该通信装置包括：接收模块。接收模块，用于接收第二通信设备发送的第一消息，第一消息用于通知终端相关的第一信息，第一信息用于指示以下至少一项：已建立独立引导DC；已建立独立应用DC；独立IMS DC会话变为正常IMS会话；正常IMS会话变为独立IMS DC会话；已建立本地引导DC；已建立远端引导DC；本地终端发起应用DC的建立；对端终端发起应用DC的建立；建立的应用DC对应的应用信息；建立的应用DC对应的引导DC的信息。
第四方面，提供了一种通信装置，该通信装置包括：发送模块。发送模块，用于向第一通信设备发送第一消息，第一消息用于通知终端相关的第一信息，第一信息用于指示以下至少一项：已建立独立引导DC；已建立独立应用DC；独立IMS DC会话变为正常IMS会话；正常IMS会话变为独立IMS DC会话；已建立本地引导DC；已建立远端引导DC；本地终端发起应用DC的建立；对端终端发起应用DC的建立；建立的应用DC对应的应用信息；建立的应用DC对应的引导DC的信息。
第五方面，提供了一种通信设备，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种通信设备，包括处理器及通信接口，其中，所述通信接口用于接收第二通信设备发送的第一消息，第一消息用于通知终端相关的第一信息，第一信息用于指示以下至少一项：已建立独立引导DC；已建立独立应用DC；独立IMS DC会话变为正常IMS会话；正常IMS会话变为独立IMS DC会话；已建立本地引导DC；已建立远端引导DC；本地终端发起应用DC的建立；对端终端发起应用DC的建立；建立的应用DC对应的应用信息；建立的应用DC对应的引导DC的信息。
第七方面，提供了一种通信设备，该网络侧设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第八方面，提供了一种通信设备，包括处理器及通信接口，其中，所述通信接口用于向第一通信设备发送第一消息，第一消息用于通知终端相关的第一信息，第一信息用于指示以下至少一项：已建立独立引导DC；已建立独立应用DC；独立IMS DC会话变为正常IMS会话；正常IMS会话变为独立IMS DC会话；已建立本地引导DC；已建立远端引导DC；本地终端发起应用DC的建立；对端终端发起应用DC的建立；建立的应用DC对应的应用信息；建立的应用DC对应的引导DC的信息。
第九方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第十方面，提供了一种无线通信系统，包括：第一通信设备及第二通信设备，所述第一通信设备可用于执行如第一方面所述的方法的步骤，所述第二通信设备可用于执行如第二方面所述的方法的步骤。
第十一方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法，或实现如第二方面所述的方法。
第十二方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述程序/程序产品被至少一个处理器执行以实现如第一方面所述的通信方法的步骤，或者实现如第二方面所述的通信方法的步骤。
在本申请实施例中，第一通信设备可以接收第二通信设备发送的通知消息，以获知发生的事件的相关信息，即终端相关的第一信息。如此，通过本方案较为全面地向第一通信设备开放了终端状态，使得第一通信设备能够获知更多的终端状态，例如独立DC相关的内容、DC是与本端终端相关的还是与对端终端相关的等内容，从而更加准确地判断出终端使用DC应用时的终端状态。
附图说明
图1是本申请实施例提供的一种无线通信系统的架构示意图；
图2是本申请实施例提供的一种通信方法的流程图之一；
图3是本申请实施例提供的一种通信方法的流程图之二；
图4是本申请实施例提供的一种通信方法的流程图之三；
图5是本申请实施例提供的一种通信方法的流程图之四；
图6是本申请实施例提供的一种通信方法的流程图之五；
图7是本申请实施例提供的一种通信方法的流程图之六；
图8是本申请实施例提供的一种通信方法的流程图之七；
图9是本申请实施例提供的一种通信方法的流程图之八；
图10是本申请实施例提供的一种通信装置的结构示意图之一；
图11是本申请实施例提供的一种通信装置的结构示意图之二；
图12是本申请实施例提供的一种通信装置的结构示意图之三；
图13是本申请实施例提供的一种通信装置的结构示意图之四；
图14是本申请实施例提供的一种通信设备的硬件结构示意图；
图15是本申请实施例提供的一种终端的硬件结构示意图；
图16是本申请实施例提供的一种网络侧设备的硬件结构示意图之一；
图17是本申请实施例提供的一种网络侧设备的硬件结构示意图之二。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，本申请中的“或”表示所连接对象的至少其中之一。例如“A或B”涵盖三种方案，即，方案一：包括A且不包括B；方案二：包括B且不包括A；方案三：既包括A又包括B。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请的术语“指示”既可以是一个直接的指示(或者说显式的指示)，也可以是一个间接的指示(或者说隐含的指示)。其中，直接的指示可以理解为，发送方在发送的指示中明确告知了接收方具体的信息、需要执行的操作或请求结果等内容；间接的指示可以理解为，接收方根据发送方发送的指示确定对应的信息，或者进行判断并根据判断结果确定需要执行的操作或请求结果等。
本申请的术语“至少一个(项)”、“至少之一”等指其包含对象中的任意一个、任意两个或两个以上的组合。例如，a、b、c中的至少一个(项)，可以表示：“a”、“b”、“c”、“a和b”、“a和c”、“b和c”以及“a、b和c”，其中a，b，c可以是单个，也可以是多个。同理，“至少两个(项)”是指两个或两个以上，其表达的含义与“至少一个(项)”类似。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(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)或其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统以外的系统，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(Ultra-mobile Personal Computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(Augmented Reality，AR)、虚拟现实(Virtual Reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、飞行器(flight vehicle)、车载设备(Vehicle User Equipment，VUE)、船载设备、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(Personal Computer，PC)、柜员机或者自助机等终端侧设备。可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。其中，车载设备也可以称为车载终端、车载控制器、车载模块、车载部件、车载芯片或车载单元等。除了上述终端设备，也可以是终端内的芯片，例如调制解调器(Modem)芯片，系统级芯片(System on Chip，SoC)。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备也可以称为无线接入网(Radio Access Network,RAN)设备、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点(Access Point，AS)或无线保真(Wireless Fidelity，WiFi)节点等。其中，基站可被称为节点B(Node B，NB)、演进节点B(Evolved Node B，eNB)、下一代节点B(the next generation Node B，gNB)、新空口节点B(New Radio Node B，NR Node B)、接入点、中继站(Relay Base Station，RBS)、服务基站(Serving Base Station，SBS)、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点(home Node B，HNB)、家用演进型B节点(home evolved Node B)、发送接收点(Transmission Reception Point，TRP)或所属领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。
核心网设备可以包含但不限于如下至少一项：核心网节点、核心网功能、移动管理实体(Mobility Management Entity，MME)、接入移动管理功能(Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)、用户平面功能(User Plane Function，UPF)、策略控制功能(Policy Control Function，PCF)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)、边缘应用服务发现功能(Edge Application Server Discovery Function，EASDF)、统一数据管理(Unified Data Management，UDM)、统一数据仓储(Unified Data Repository，UDR)、归属用户服务器(Home Subscriber Server，HSS)、集中式网络配置(Centralized network configuration，CNC)、网络存储功能(Network Repository Function，NRF)、网络开放功能(Network Exposure Function，NEF)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)等。需要说明的是，在本申请实施例中仅以NR系统中的核心网设备为例进行介绍，并不限定核心网设备的具体类型。
目前，3GPP标准定义了开放(expose)终端状态的方法，consumer(例如，第三方服务器)可以向producer订阅如下信息：
IMS DC应用(application)事件(event)：当特定用户下载IMS DC application时，producer向consumer报告对应的事件；
IMS会话(session)事件：当特定IMS会话的会话状态(session status)或媒体发生变化时，producer向consumer报告对应的事件；
补充业务(Supplementary service)事件：当特定IMS会话的补充服务被激活时，producer向consumer报告对应的事件；
三方注册(3rd Party registration)事件：当producer接收到三方注册请求，producer向consumer报告对应的事件。
现有技术仅考虑了IMS DC application下载，IMS会话状态变化等IMS业务，producer向第三方服务器开放的终端状态不够全面，因此会导致无法准确地判断终端使用DC时的终端状态，无法更好的为用户提供服务。
本申请实施例提供一种通信方法，第一通信设备可以接收第二通信设备发送的通知消息，以获知发生的事件的相关信息，即终端相关的第一信息。如此，通过本方案较为全面地向第一通信设备开放了终端状态，使得第一通信设备能够获知更多的终端状态，例如独立DC相关的内容、DC是与本端终端相关的还是与对端终端相关的等内容，从而更加准确地判断出终端使用DC应用时的终端状态。
需要说明的是，producer向consumer报告对应的事件，也可以理解或替换为：producer向consumer发送事件对应的信息，或者，producer向consumer发送事件的相关信息，或者，producer向consumer发送对应的信息。
下面对本申请实施例提供的一种通信方法、装置、设备及存储介质中涉及的一些概念和/或术语做一下解释说明。
3GPP标准引入了在通话过程中建立DC的机制，通过DC可以在通话过程中进行额外的业务，例如进行屏幕共享，位置共享，文件传输等，从而给用户带来更好的体验。不同的业务对应不同的DC application(应用)，该DC application可以在通话过程中动态下载到终端，不需要终端提前安装，方便用户使用。DC分为两种：
引导(bootstrap)DC：用于从数据通道服务器(例如数据通道信令功能(Data Channel Signaling Function，DCSF))下载DC应用；
应用(application)DC：用于传输DC应用的数据。
DC可以伴随着语音通话、视频通话或短信等业务的建立而建立的；也可以不伴随语音通话、视频通话或短信等业务建立。对于后者，称为独立(standalone)DC。
bootstrap DC通常是由终端发起建立的，例如，终端-1和终端-2之间进行通信时，终端-1可以请求建立与本端DCSF(为终端-1提供服务的DCSF)间的bootstrap DC，或者，请求建立与对端DCSF(为终端-2提供服务的DCSF)间的bootstrap DC。
Application DC可以由终端发起建立，也可以有网络侧服务器发起建立请求，例如，终端-1和终端-2之间进行通信时，终端-1可以请求建立application DC；或者，对端终端也可以请求建立application DC；或者，终端-1可以请求与网络侧服务器建立application DC；或者，网络侧服务器请求与终端-1建立application DC。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的通信方法进行详细地说明。
本申请实施例提供一种通信方法，图2示出了本申请实施例提供的通信方法的流程图。如图2所示，本申请实施例提供的通信方法可以包括下述的步骤201和步骤202。
步骤201、第二通信设备向第一通信设备发送第一消息。
步骤202、第一通信设备接收第二通信设备发送的第一消息。
本申请实施例中，上述第一消息用于通知终端相关的第一信息，该第一信息用于指示以下至少一项：
已建立独立引导DC(Standalone bootstrap data channel)；
已建立独立应用DC(standalone application data channel)；
独立IMS DC会话变为正常IMS会话；
正常IMS会话变为独立IMS DC会话；
已建立本地(local)引导DC；
已建立远端(remote)引导DC；
本地终端发起应用DC的建立；
对端终端发起应用DC的建立；
建立的应用DC对应的应用信息；
建立的应用DC对应的引导DC的信息。
需要说明的是，正常IMS会话(normal IMS session)可以理解为非独立IMS会话。正常IMS会话也可以称为多媒体电话(Multimedia telephony，MMTEL)IMS会话，或MMTEL会话。
可选地，本申请实施例中，上述独立IMS DC会话可以包括以下至少一项：独立引导DC、独立应用DC。
需要说明的是，IMS DC会话可以理解为DC会话。
可选地，本申请实施例中，在独立IMS DC会话的基础上，添加语音、视频或消息(messaging)媒体，则该独立IMS DC会话可变成正常IMS会话。
可选地，本申请实施例中，在正常IMS会话的基础上，删除语音、视频或messaging媒体，则该正常IMS会话变成独立IMS DC会话。
需要说明的是，本地引导DC也可以称为连接到本端DCSF的引导DC或发起(originating)引导DC。远端引导DC也可以称为连接到对端DCSF的引导DC或终结(terminating)引导DC。
本申请实施例中，上述第一通信设备可以为consumer(消费者)设备，例如第三方服务器。上述第二通信设备可以为producer(客户端)设备。
可选地，本申请实施例中，上述consumer可以为网络功能(Network Function，NF)服务consumer。
可选地，本申请实施例中，上述consumer可以为以下任一项：应用功能(Application Function，AF)服务器、网络开放功能(Network Exposure Function，NEF)服务器、DC应用服务器(Application Server，AS)、归属用户服务器(Home Subscriber Server，HSS)。上述producer可以为DCSF或IMS AS。
可选地，本申请实施例中，上述consumer可以为DCSF，上述producer可以为IMS AS或HSS。
可选地，本申请实施例中，上述第一消息可以为通知消息，例如Notify_Request。
可选地，本申请实施例中，结合图2，如图3所示，在上述步骤201之前，本申请实施例提供的通信方法还包括下述的步骤301和步骤302。
步骤301、第一通信设备向第二通信设备发送第二消息。
步骤302、第二通信设备接收第一通信设备发送的第二消息。
本申请实施例中，上述第二消息中包括第一事件，该第一事件包括以下至少一项：
建立独立引导DC的事件；
建立独立应用DC的事件；
独立IMS DC会话变为正常IMS会话的事件；
正常IMS会话变为独立IMS DC会话的事件；
建立本地引导DC的事件；
建立远端引导DC的事件；
本地终端发起应用DC的建立的事件；
对端终端发起应用DC的建立的事件。
可选地，本申请实施例中，上述第二消息可以为订阅消息(或订阅请求)，用于请求订阅终端相关的第一信息。例如第二消息可以为Subscribe_Request。
可选地，本申请实施例中，第一通信设备可以经由中间(intermediate)NF向第二通信设备发送第二消息。具体的交互过程参见下述实施例中的描述，此处不予赘述。
可选地，本申请实施例中，在consumer为AF或NEF或DC AS的情况下，intermediate NF可以为HSS，producer可以为DCSF或IMS AS。
可选地，本申请实施例中，在上述consumer为DCSF或NEF的情况下，intermediate NF可以为HSS，producer可以为IMS AS。
可选地，本申请实施例中，在上述consumer为AF或NEF或DC AS的情况下，intermediate NF可以为DCSF，producer可以为IMS AS。
可选地，本申请实施例中，在上述consumer为AF或DC AS的情况下，intermediate NF可以是DCSF或NEF，producer可以是IMS AS。
可选地，本申请实施例中，在上述第二消息中包括第一事件的情况下，上述第一信息用于指示以下至少一项：
已建立独立引导DC；
已建立独立应用DC；
独立IMS DC会话变为正常IMS会话；
正常IMS会话变为独立IMS DC会话；
已建立本地引导DC；
已建立远端引导DC；
本地终端发起应用DC的建立；
对端终端发起应用DC的建立。
示例1-1、对于事件1-1：建立独立引导DC或独立应用DC。consumer向producer订阅终端的建立独立引导DC或独立应用DC的事件(即consumer向producer发送第二消息)。当producer确定终端已建立独立引导DC或独立应用DC时，向consumer发送通知消息(即第一消息)，以通知已建立独立引导数据通道DC或已建立独立应用DC(即第一信息)。其中，第二消息中包括第一事件(事件1-1)，该第一事件为建立独立引导DC的事件或建立独立应用DC的事件。
需要说的是，终端已建立引导DC可以理解或替换为：终端完成了引导DC的建立或终端与DCSF之间已建立引导DC或网络侧为终端已建立引导DC，后续相同不再赘述。
需要说的是，终端已建立应用DC可以理解或替换为：终端完成了应用DC的建立或终端与对端(对端UE或DC AS)之间已建立应用DC或网络侧为终端已建立应用DC，后续相同不再赘述。
示例1-2、对于事件1-2：独立IMS DC会话变为正常IMS会话。consumer向producer订阅独立IMS DC会话变为正常IMS会话的事件(即consumer向producer发送第二消息)。当producer确定终端的独立IMS DC会话变为正常IMS会话时，向consumer发生通知消息(即第一消息)，以通知独立IMS DC会话变为正常IMS会话(即第一信息)。其中，第二消息中包括第一事件(事件1-2)，该第一事件为独立IMS DC会话变为正常IMS会话的事件。
示例1-3、对于事件1-3：正常IMS会话变为独立IMS DC会话。consumer向producer订阅正常IMS会话变为独立IMS DC会话的事件(即consumer向producer发送第二消息)。当producer确定终端的正常IMS会话变为独立IMS DC会话时，向consumer发生通知消息(即第一消息)，以通知正常IMS会话变为独立IMS DC会话(即第一信息)。其中，第二消息中包括第一事件(事件1-3)，该第一事件为正常IMS会话变为独立IMS DC会话的事件。
示例1-4、对于事件1-4：建立本地引导DC或远端引导DC。consumer向producer订阅终端建立本地引导DC或远端引导DC的事件(即consumer向producer发送第二消息)。当producer确定终端已建立本地引导DC，或已建立远端引导DC时，向consumer发生通知消息(即第一消息)，以通知已建立本地引导DC，或已建立远端引导DC(即第一信息)。其中，第二消息中包括第一事件(事件1-4)，该第一事件为建立本地引导DC的事件，或建立远端引导DC的事件。
示例1-5、对于事件1-5：本地终端发起应用DC建立请求，或对端终端发起应用DC建立请求。consumer向producer订阅本地终端发起应用DC建立请求，或对端终端发起应用DC建立请求的事件(即consumer向producer发送第二消息)。当producer确定终端发起应用DC建立请求，或接收到对端终端发起的应用DC建立请求时，向consumer发生通知消息(即第一消息)，以通知本地终端发起应用DC的建立，或对端终端发起应用DC的建立(即第一信息)。其中，第二消息中包括第一事件(事件1-5)，该第一事件为本地终端发起应用DC的建立的事件(也可以称为originating application DC event)，或对端终端发起应用DC的建立的事件(也可以称为terminating application DC event)。
本申请实施例中，consumer向producer订阅特定事件(即第一事件)，producer是在满足特定事件时，向consumer发送通知消息，以通知发生的第一事件的信息，即终端相关的第一信息。如此，通过本方案较为全面地向consumer开放了终端状态，使得consumer能够获知更多的终端状态，例如独立DC相关的内容、DC是与本端终端相关的还是与对端终端相关的等内容，从而更加准确地判断出终端使用DC应用时的终端状态。
可选地，本申请实施例中，结合图2，如图4所示，在上述步骤201之前，本申请实施例提供的通信方法还包括下述的步骤401和步骤402。
步骤401、第一通信设备向第二通信设备发送第三消息。
步骤402、第二通信设备接收第一通信设备发送的第三消息。
本申请实施例中，上述第三消息中包括第二事件和第一指示信息，该第一指示信息用于指示第二事件的相关信息。
可选地，本申请实施例中，上述第三消息可以为订阅消息，用于请求订阅终端相关的第一信息。例如第三消息可以为Subscribe_Request。
可选地，本申请实施例中，上述第二事件包括以下至少一项：建立引导DC的事件；建立应用DC的事件；建立DC的事件；建立IMS会话的事件；建立或修改正常IMS会话的事件；建立或修改独立IMS DC会话的事件；建立IMS DC应用的事件。
可选地，本申请实施例中，上述第二事件包括以下至少一项：建立引导DC的事件、建立应用DC的事件、建立DC的事件、建立IMS会话的事件。上述第一指示信息用于指示以下至少一项：
DC是独立引导DC或非独立引导DC；
DC是独立应用DC或非独立应用DC；
DC是独立DC或非独立DC。
可以理解，在这种情况下，第一通信设备通过向第二通信设备发送第二事件(通用事件)和第一指示信息，以使得第二通信设备在确定终端已建立独立引导DC或独立应用DC时发送通知消息，即在发生了特定事件时发送通知消息。换言之，在发生了第二事件、且发生第二事件时的DC是第一指示信息指示的独立引导DC或独立应用DC或独立DC，则认为发生了特定事件，即第二事件和第一指示信息结合在一起对应的是特定事件。
示例2-1、对于事件2-1+第一指示信息(对应于上述事件1-1)。consumer向producer订阅终端的建立独立引导DC或独立应用DC或独立DC的事件(即consumer向producer发送第三消息)。当producer确定终端已建立独立引导DC或独立应用DC或独立DC时，向consumer发送通知消息(即第一消息)，以通知已建立独立引导数据通道DC或已建立独立应用DC(即第一信息)。其中，第三消息中包括第二事件(事件2-1)和第一指示信息。第二事件为建立引导DC的事件，第一指示信息用于指示DC是独立引导DC或非独立引导DC，或用于指示DC是独立DC或非独立DC；或者，第二事件为建立应用DC的事件，第一指示信息用于指示DC是独立应用DC或非独立应用DC，或用于指示DC是独立DC或非独立DC；或者，第二事件为建立DC的事件，第一指示信息(以下称为指示信息a)用于指示以下至少一项：DC是独立引导DC或非独立引导DC、DC是独立应用DC或非独立应用DC、DC是独立DC或非独立DC。或者，第二事件为建立IMS会话的事件，第一指示信息(以下称为指示信息b)用于指示以下至少一项：DC是独立引导DC或非独立引导DC、DC是独立应用DC或非独立应用DC、DC是独立DC或非独立DC。
需要说明的是，在第二事件为建立IMS会话的事件的情况下，DC是指终端已建立的DC，包括引导DC或应用DC。例如，当终端完成了引导DC建立时，该DC是指已建立的引导DC；当终端完成了应用DC建立时，该DC是指已建立的应用DC。
示例性地，上述第一指示信息可以为1比特信息。例如，第一指示信息的取值为1代表是standalone，第一指示信息的取值为0代表不是standalone(不是standalone也可以称为normal)。或者，第一指示信息的取值为0代表是standalone，第一指示信息的取值为1代表不是standalone。
示例性地，上述指示信息a和指示信息b可以是不同的参数，分别通过1比特指示是standalone或不是standalone。
或者，上述指示信息a和指示信息b可以是相同的参数，可以通过多个比特的编码实现，其中第一比特取值为1代表是standalone bootstrap DC，第一比特取值为0代表不是standalone bootstrap DC；第二比特取值为1代表时代表是standalone application DC，第二比特取值为0代表不是standalone application DC。例如，11代表既是standalone bootstrap DC，又是standalone application DC；10代表是standalone bootstrap DC，不是standalone application DC；01代表不是standalone bootstrap DC，是standalone application DC；00代表不是standalone bootstrap DC，不是standalone application DC。
可选地，本申请实施例中，上述第二事件包括以下至少一项：建立(establish)或修改(modify)正常IMS会话的事件、建立IMS会话的事件。上述第一指示信息用于指示以下至少一项：
IMS会话是变化得到的或不是变化得到的；
IMS会话是从独立IMS DC会话变化得到的，或不是从独立IMS DC会话变化得到的。
可以理解，在这种情况下，第一通信设备通过向第二通信设备发送第二事件(通用事件)和第一指示信息，以使得第二通信设备在确定终端建立的IMS会话是变化得到的，或终端的独立IMS DC会话变为正常IMS会话时发送通知消息，即在发生了特定事件时发送通知消息。换言之，在发生了第二事件、且发生第二事件时的IMS会话是第一指示信息指示的变化得到的或从独立IMS DC会话变化得到的，则认为发生了特定事件，即第二事件和第一指示信息结合在一起对应的是特定事件。
示例2-2、对于事件2-2+第一指示信息(对应于上述事件1-2)。consumer向producer订阅独立IMS DC会话变为正常IMS会话的事件(即consumer向producer发送第三消息)。当producer确定终端建立的IMS会话是变化得到的，或终端的独立IMS DC会话变为正常IMS会话时，向consumer发生通知消息(即第一消息)，以通知独立IMS DC会话变为正常IMS会话(即第一信息)。其中，第三消息中包括第二事件(事件2-2)和第一指示信息，该第二事件为建立或修改正常IMS会话的事件，或者建立IMS会话的事件。
示例性地，上述第一指示信息可以为1比特信息。例如，第一指示信息的取值为1代表IMS会话是变化得到的，或IMS会话是从独立IMS DC会话变化得到的；第一指示信息的取值为0代表IMS会话不是变化得到的，或IMS会话不是从独立IMS DC会话变化得到的。或者，第一指示信息的取值为0代表IMS会话是变化得到的，或IMS会话是从独立IMS DC会话变化得到的；第一指示信息的取值为1代表IMS会话不是变化得到的，或IMS会话不是从独立IMS DC会话变化得到的。
可选地，本申请实施例中，上述第二事件包括以下至少一项：建立或修改独立IMS DC会话的事件、建立IMS会话的事件。上述第一指示信息用于指示以下至少一项：
IMS DC会话是变化得到的或不是变化得到的；
IMS DC会话是从正常IMS会话变化得到的，或不是从正常IMS会话变化得到的。
可以理解，在这种情况下，第一通信设备通过向第二通信设备发送第二事件(通用事件)和第一指示信息，以使得第二通信设备在确定终端建立的IMS会话是变化得到的，或终端的正常IMS会话变为独立IMS DC会话时发送通知消息，即在发生了特定事件时发送通知消息。换言之，在发生了第二事件、且发生第二事件时的IMS会话是第一指示信息指示的变化得到的或从正常IMS会话变化得到的，则认为发生了特定事件，即第二事件和第一指示信息结合在一起对应的是特定事件。
示例2-3、对于事件2-3+第一指示信息(对应于上述事件1-3)。consumer向producer订阅正常IMS会话变为独立IMS DC会话的事件(即consumer向producer发送第三消息)。当producer确定终端建立的IMS会话是变化得到的，或终端的正常IMS会话变为独立IMS DC会话时，向consumer发生通知消息(即第一消息)，以通知正常IMS会话变为独立IMS DC会话(即第一信息)。其中，第三消息中包括第二事件(事件2-3)和第一指示信息，该第二事件为建立或修改独立IMS DC会话的事件，或者建立IMS会话的事件。
示例性地，上述第一指示信息可以为1比特信息。例如，第一指示信息的取值为1代表IMS会话是变化得到的，或IMS会话是从正常IMS会话变化得到的；第一指示信息的取值为0代表IMS会话不是变化得到的，或IMS会话不是从正常IMS会话变化得到的。或者，第一指示信息的取值为0代表IMS会话是变化得到的，或IMS会话是从正常IMS会话变化得到的；第一指示信息的取值为1代表IMS会话不是变化得到的，或IMS会话不是从正常IMS会话变化得到的。
需要说明的是，上述事件2-2和事件2-3对应的第一指示信息可以是不同的参数，分别通过1比特代表不同的含义。
或者，上述事件2-2和事件2-3对应的第一指示信息可以是相同的参数，可以通过联合编码实现。例如，1代表IMS会话是从独立IMS DC会话变化得到的，0代表IMS会话是从正常IMS会话变化得到的。或者，0代表IMS会话是从独立IMS DC会话变化得到的，1代表IMS会话是从正常IMS会话变化得到的。
可选地，本申请实施例中，上述第二事件包括以下至少一项：建立引导DC的事件、建立IMS会话的事件。上述第一指示信息用于指示以下至少一项：
DC是本地的或不是本地的；
DC是远端的或不是远端的。
可以理解，在这种情况下，第一通信设备通过向第二通信设备发送第二事件(通用事件)和第一指示信息，以使得第二通信设备在确定终端已建立本地引导DC，或已建立远端引导DC，即在发生了特定事件时发送通知消息。换言之，在发生了第二事件、且发生第二事件时的DC是第一指示信息指示的DC是本地的或DC是远端的，则认为发生了特定事件，即第二事件和第一指示信息结合在一起对应的是特定事件。
示例2-4、对于事件2-4+第一指示信息(对应于上述事件1-4)。consumer向producer订阅终端建立本地引导DC或远端引导DC的事件(即consumer向producer发送第三消息)。当producer确定终端已建立本地引导DC，或已建立远端引导DC时，向consumer发送通知消息(即第一消息)，以通知已建立本地引导DC，或已建立远端引导DC(即第一信息)。其中，第三消息中包括第二事件(事件2-4)和第一指示信息，该第二事件为建立引导DC的事件或建立IMS会话的事件。
示例性地，上述第一指示信息可以为1比特信息。例如，第一指示信息的取值为1代表DC是本地的，第一指示信息的取值为0代表DC不是本地的。或者，第一指示信息的取值为0代表DC是本地的，第一指示信息的取值为1代表DC不是本地的。
示例性地，上述第一指示信息可以为1比特信息。例如，第一指示信息的取值为1代表DC是远端的，第一指示信息的取值为0代表DC不是远端的。或者，第一指示信息的取值为0代表DC是远端的，第一指示信息的取值为1代表DC不是远端的。
示例性地，上述第一指示信息用于指示DC是本地引导DC或远端引导DC。例如，第一指示信息的取值为1代表DC是本地引导DC，第一指示信息的取值为0代表DC是远端引导DC。或者，第一指示信息的取值为0代表DC是本地引导DC，第一指示信息的取值为1代表DC是远端引导DC。
可选地，本申请实施例中，上述第二事件包括以下至少一项：建立应用DC的事件、建立IMS DC应用的事件、建立IMS会话的事件。上述第一指示信息用于指示以下至少一项：
DC是本地终端发起的，或不是本地终端发起的；
DC是对端终端发起的，或不是对端终端发起的。
可以理解，在这种情况下，第一通信设备通过向第二通信设备发送第二事件(通用事件)和第一指示信息，以使得第二通信设备在确定终端发起应用DC建立请求，或接收到对端终端发起的应用DC建立请求，即在发生了特定事件时发送通知消息。换言之，在发生了第二事件、且发生第二事件时的DC是第一指示信息指示的DC是本地终端发起的或DC是对端终端发起的，则认为发生了特定事件，即第二事件和第一指示信息结合在一起对应的是特定事件。
示例2-5、对于事件2-5+第一指示信息(对应于上述事件1-5)。consumer向producer订阅本地终端发起应用DC建立请求，或对端终端发起应用DC建立请求的事件(即consumer向producer发送第三消息)。当producer确定终端发起应用DC建立请求，或接收到对端终端发起的应用DC建立请求时，向consumer发送通知消息(即第一消息)，以通知本地终端发起应用DC的建立，或对端终端发起应用DC的建立(即第一信息)。其中，第三消息中包括第二事件(事件2-5)和第一指示信息，该第二事件为建立应用DC的事件，或者建立IMS DC应用的事件，或者建立IMS会话的事件。
示例性地，上述第一指示信息可以是1比特信息。例如，第一指示信息的取值为1代表DC是本地终端发起的，第一指示信息的取值为0代表DC不是本地终端发起的。或者，第一指示信息的取值为0代表DC是本地终端发起的，第一指示信息的取值为1代表DC不是本地终端发起的。
示例性地，上述第一指示信息可以是1比特信息。例如，第一指示信息的取值为1代表DC是对端终端发起的，第一指示信息的取值为0代表DC不是对端终端发起的。或者，第一指示信息的取值为0代表DC是对端终端发起的，第一指示信息的取值为1代表DC不是对端终端发起的。
可选地，本申请实施例中，上述第二事件包括建立应用DC的事件。上述第一指示信息用于指示以下至少一项：
应用DC对应的应用信息；
应用DC对应的引导DC的信息。
可以理解，在这种情况下，第一通信设备通过向第二通信设备发送第二事件(通用事件)和第一指示信息，以使得第二通信设备在确定终端建立的应用DC对应的信息满足consumer提供的特定信息，即在发生了特定事件时发送通知消息。换言之，在发生了第二事件、且发生第二事件时第一指示信息指示的应用DC对应的应用信息或对应的引导DC的信息满足特定信息时，则认为发生了特定事件，即第二事件和第一指示信息结合在一起对应的是特定事件。
示例2-6、对于事件2-6+第一指示信息。consumer向producer订阅终端的符合特定信息的应用DC建立的事件(即consumer向producer发送第三消息)。当producer确定终端建立的应用DC对应的信息满足consumer提供的特定信息时，向consumer发送通知消息(即第一消息)，以通知建立的应用DC对应的应用信息，或建立的应用DC对应的引导DC的信息(即第一信息)。其中，第三消息中包括第二事件(事件2-6)和第一指示信息，该第二事件为建立应用DC的事件。
例如，consumer向producer订阅终端使用屏幕共享APP的事件，则当应用DC对应的应用是屏幕共享APP时，producer向consumer发送通知消息。
示例性地，上述第一指示信息可以是上述应用信息或引导DC的信息，即在producer确定建立的应用DC符合consumer提供的特定信息时，向consumer发送通知消息。
可选地，本申请实施例中，上述应用信息包括以下至少一项：应用类型(application type)、应用标识(application ID)、应用绑定信息(application binding information)。
需要说明的是，上述引导DC的信息为应用DC关联的引导DC的信息，例如，该应用DC对应的应用是通过哪个引导DC下载的。可选地，上述引导DC的信息可以是引导DC的流标识(stream id)。
本申请实施例中，consumer向producer订阅特定事件(即第二事件+第一指示信息)，producer是在满足特定事件时，向consumer发送通知消息，以通知发生的事件的信息，即终端相关的第一信息。如此，通过本方案较为全面地向consumer开放了终端状态，使得consumer能够获知更多的终端状态，例如独立DC相关的内容、DC是与本端终端相关的还是与对端终端相关的等内容，从而更加准确地判断出终端使用DC应用时的终端状态。
可选地，本申请实施例中，结合图2，如图5所示，在上述步骤201之前，本申请实施例提供的通信方法还包括下述的步骤501和步骤502。
步骤501、第一通信设备向第二通信设备发送第四消息。
步骤502、第二通信设备接收第一通信设备发送的第四消息。
本申请实施例中，上述第四消息中包括第二事件和第二指示信息，该第二指示信息用于获取以下至少一项：引导DC对应的信息；应用DC对应的信息；IMS会话对应的信息；IMS DC会话对应的信息。
可选地，本申请实施例中，在上述第四消息中包括第二事件，或者包括第二事件和第二指示信息的情况下，上述第一信息包括第二事件和第三指示信息，该第三指示信息用于指示第二事件的相关信息。即第二通信设备在确定发生了第二事件后，向第一通信设备发送发生的第二事件和第三指示信息，即第一信息是第二事件和第三指示信息结合在一起得到的。
需要说明的是，针对第二事件和第三指示信息的方案，与第二事件和第一指示信息的方案类似，可以参见上述实施例中对于第二事件和第一指示信息的描述，此处不再赘述。
本申请实施例中，consumer向producer订阅通用事件(即第二事件)，producer在consumer发送通知消息时，以通知发生的事件的信息，即终端相关的第一信息。如此，通过本方案较为全面地向consumer开放了终端状态，使得consumer能够获知更多的终端状态，例如独立DC相关的内容、DC是与本端终端相关的还是与对端终端相关的等内容，从而更加准确地判断出终端使用DC应用时的终端状态。
示例性地，下面通过具体实施方式，对本申请实施例提供的通信方法的交互过程进行描述。
实施方式一：consumer向producer请求特定事件，在满足特定事件时producer向consumer发送通知消息。
如图6所示，本申请实施例提供的通信方法包括下述的步骤20至步骤25。
步骤20、NF服务consumer向producer发送订阅消息，该订阅消息中包括第一事件，或者包括第二事件和第一指示信息。
例如，订阅消息可以为Subscribe_Request。
步骤21、producer创建新的事件订阅资源，开始检测订阅的事件。
步骤22、producer向NF服务consumer发送响应消息。
例如，响应消息可以为Subscribe_Request response。
步骤23、producer确定订阅的事件发生。
步骤24、producer向NF服务consumer发送通知(notify)消息，用于通知终端相关的第一信息。
例如，通知消息可以为Notify_Request。
步骤25、NF服务consumer向producer发送响应消息。
例如，响应消息可以为Notify_Request response。
可选地，本申请实施例中，对于上述实施例所述的事件1-1：
上述步骤20具体为步骤20a：consumer向producer订阅终端的建立独立引导DC或独立应用DC的事件(即consumer向producer发送订阅消息)。
上述步骤24具体为步骤24a：当producer确定终端已建立独立引导DC或独立应用DC时，向consumer发送通知消息。
其中，在上述步骤20a中，订阅消息中包括第一事件(事件1-1)，该第一事件为建立独立引导DC的事件或建立独立应用DC的事件。
或者，在上述步骤20a中，订阅消息中包括第二事件(上述实施例所述的事件2-1)和第一指示信息。其中，该第二事件包括以下至少一项：建立引导DC的事件、建立应用DC的事件、建立DC的事件、建立IMS会话的事件。该第一指示信息用于指示以下至少一项：
DC是独立引导DC或非独立引导DC；
DC是独立应用DC或非独立应用DC；
DC是独立DC或非独立DC。
可选地，本申请实施例中，对于上述实施例所述的事件1-2：
上述步骤20具体为步骤20b：consumer向producer订阅独立IMS DC会话变为正常IMS会话的事件(即consumer向producer发送订阅消息)。
上述步骤24具体为步骤24b：当producer确定终端的独立IMS DC会话变为正常IMS会话时，向consumer发送通知消息。
其中，在上述步骤20b中，订阅消息中包括第一事件(事件1-2)，该第一事件为独立IMS DC会话变为正常IMS会话的事件。
或者，在上述步骤20b中，订阅消息中包括第二事件(上述实施例所述的事件2-2)和第一指示信息。其中，该第二事件包括以下至少一项：建立或修改正常IMS会话的事件、建立IMS会话的事件。该第一指示信息用于指示以下至少一项：
IMS会话是变化得到的或不是变化得到的；
IMS会话是从独立IMS DC会话变化得到的，或不是从独立IMS DC会话变化得到的。
可选地，本申请实施例中，对于上述实施例所述的事件1-3：
上述步骤20具体为步骤20c：consumer向producer订阅正常IMS会话变为独立IMS DC会话的事件(即consumer向producer发送订阅消息)。
上述步骤24具体为步骤24c：当producer确定终端的正常IMS会话变为独立IMS DC会话时，向consumer发送通知消息。
其中，在上述步骤20c中，订阅消息中包括第一事件(事件1-3)，该第一事件为正常IMS会话变为独立IMS DC会话的事件。
或者，在上述步骤20c中，订阅消息中包括第二事件(上述实施例所述的事件2-3)和第一指示信息。其中，该第二事件包括以下至少一项：建立或修改独立IMS DC会话的事件、建立IMS会话的事件。该第一指示信息用于指示以下至少一项：
IMS DC会话是变化得到的或不是变化得到的；
IMS DC会话是从正常IMS会话变化得到的，或不是从正常IMS会话变化得到的。
可选地，本申请实施例中，对于上述实施例所述的事件1-4：
上述步骤20具体为步骤20d：consumer向producer订阅终端建立本地引导DC或远端引导DC的事件(即consumer向producer发送订阅消息)。
上述步骤24具体为步骤24d：当producer确定终端已建立本地引导DC，或已建立远端引导DC时，向consumer发送通知消息。
其中，在上述步骤20d中，订阅消息中包括第一事件(事件1-4)，该第一事件为建立本地引导DC的事件，或建立远端引导DC的事件。
或者，在上述步骤20d中，订阅消息中包括第二事件(上述实施例所述的事件2-4)和第一指示信息。其中，该第二事件包括以下至少一项：建立引导DC的事件、建立IMS会话的事件。该第一指示信息用于指示以下至少一项：
DC是本地的或不是本地的；
DC是远端的或不是远端的。
可选地，本申请实施例中，对于上述实施例所述的事件1-5：
上述步骤20具体为步骤20e：consumer向producer订阅本地终端发起应用DC建立请求，或对端终端发起应用DC建立请求的事件(即consumer向producer发送订阅消息)。
上述步骤24具体为步骤24e：当producer确定终端发起应用DC建立请求，或接收到对端终端发起的应用DC建立请求时，向consumer发送通知消息。
其中，在上述步骤20e中，订阅消息中包括第一事件(事件1-5)，该第一事件为本地终端发起应用DC的建立的事件(也可以称为originating application DC event)，或对端终端发起应用DC的建立的事件(也可以称为terminating application DC event)。
或者，在上述步骤20e中，订阅消息中包括第二事件(上述实施例所述的事件2-5)和第一指示信息。其中，该第二事件包括以下至少一项：建立应用DC的事件、建立IMS DC应用的事件、建立IMS会话的事件。该第一指示信息用于指示以下至少一项：
DC是本地终端发起的，或不是本地终端发起的；
DC是对端终端发起的，或不是对端终端发起的。
可选地，本申请实施例中，对于上述实施例所述的事件2-6：
上述步骤20具体为步骤20f：consumer向producer订阅终端的符合特定信息的应用DC建立的事件(即consumer向producer发送订阅消息)。
上述步骤24具体为步骤24f：当producer确定终端建立的应用DC对应的信息满足consumer提供的特定信息时，向consumer发送通知消息。
其中，在上述步骤20f中，订阅消息中包括第二事件(上述实施例所述的事件2-6)和第一指示信息。其中，该第二事件包括建立应用DC的事件。该第一指示信息用于指示以下至少一项：
应用DC对应的应用信息；
应用DC对应的引导DC的信息。
需要说明的是，针对上述步骤20至步骤25以及相关方案的说明，参见上述实施例中的描述，此处不再赘述。
实施方式二：consumer经由中间(intermediate)NF向producer请求特定事件，在满足特定事件时producer向consumer发送通知消息。
如图7所示，本申请实施例提供的通信方法包括下述的步骤30至步骤42。
步骤30、NF服务consumer向中间NF发送订阅消息，该订阅消息中包括第一事件，或者包括第二事件和第一指示信息。
步骤31、中间NF确定producer。
步骤32、中间NF向producer发送订阅消息，该订阅消息中包括第一事件，或者包括第二事件和第一指示信息。
需要说明的是，上述步骤30中的订阅消息和步骤32中的订阅消息可以相同或不同。例如，订阅消息都可以为Subscribe_Request。
步骤33、producer创建新的事件订阅资源，开始检测订阅的事件。
步骤34、producer向中间NF发送响应消息。
步骤35、中间NF向NF服务consumer发送响应消息。
需要说明的是，上述步骤34中的响应消息和步骤35中的响应消息可以相同或不同。例如，步骤34中的响应消息可以为Subscribe_Request response，步骤35中的响应消息可以为Ndcsf_EE_Subscribe_Request response。
步骤36、producer确定订阅的事件发生。
步骤37、producer向中间NF发送通知消息，用于通知终端相关的第一信息。
步骤38、中间NF向NF服务consumer发送通知消息，用于通知终端相关的第一信息。
需要说明的是，上述步骤37中的通知消息和步骤38中的通知消息可以相同或不同。例如，通知消息都可以为Notify_Request。
步骤39、NF服务consumer向中间NF发送响应消息。
步骤40、中间NF向producer发送响应消息。
需要说明的是，上述步骤39中的响应消息和步骤40中的响应消息可以相同或不同。例如，响应消息都可以为Notify_Request response。
步骤41、producer直接向NF服务consumer发送通知消息，用于通知终端相关的第一信息。
例如，通知消息可以为Notify_Request。
步骤42、NF服务consumer直接向producer发送响应消息。
例如，响应消息可以为Notify_Request response。
需要说明的是，上述步骤37至步骤40，与步骤41至步骤42，执行关系为或者的关系，即在上述步骤36之后，可以执行上述步骤37至步骤40，或者也可以执行上述步骤41至步骤42。
需要说明的是，针对上述步骤30和步骤37(或步骤41)的具体实现方案，即第一事件分别包括事件1-1至事件1-5，第二事件分别包括事件2-1至事件2-6时，上述步骤30和步骤37(或步骤41)的具体实现步骤，可以参见上述实施方式一中的描述，此处不再赘述。
实施方式三：consumer向producer请求通用事件，producer在向consumer发送通知时，携带指示信息。
如图8所示，本申请实施例提供的通信方法包括下述的步骤50至步骤55。
步骤50、NF服务consumer向producer发送订阅消息，该订阅消息中包括第二事件。
例如，订阅消息可以为Subscribe_Request。
可选地，本申请实施例中，上述订阅消息中还包括第二指示信息。
步骤51、producer创建新的事件订阅资源，开始检测订阅的事件。
步骤52、producer向NF服务consumer发送响应消息。
例如，响应消息可以为Subscribe_Request response。
步骤53、producer确定订阅的事件发生。
步骤54、producer向NF服务consumer发送通知(notify)消息，用于通知终端相关的第一信息，该第一信息包括第二事件和第三指示信息。
例如，通知消息可以为Notify_Request。
步骤55、NF服务consumer向producer发送响应消息。
例如，响应消息可以为Notify_Request response。
可选地，本申请实施例中，在上述第二事件为上述实施例所述的事件2-1，即第二事件包括以下至少一项：建立引导DC的事件、建立应用DC的事件、建立DC的事件、建立IMS会话的事件的情况下：
上述第二指示信息用于获取以下至少一项：引导DC对应的信息、应用DC对应的信息。
上述步骤54具体为步骤54a：当producer确定终端已建立引导DC或应用DC时，向consumer发送通知消息，用于通知终端相关的第一信息，该第一信息包括第二事件和第三指示信息。其中，该第三指示信息用于指示以下至少一项：
DC是独立引导DC或非独立引导DC；
DC是独立应用DC或非独立应用DC；
DC是独立DC或非独立DC。
可选地，本申请实施例中，在上述第二事件为上述实施例所述的事件2-2，即第二事件包括以下至少一项：建立或修改正常IMS会话的事件、建立IMS会话的事件的情况下：
上述第二指示信息用于获取IMS会话对应的信息。
上述步骤54具体为步骤54b：当producer确定发生建立或修改正常IMS会话时，向consumer发送通知消息，用于通知终端相关的第一信息，该第一信息包括第二事件和第三指示信息。其中，该第三指示信息用于指示以下至少一项：
IMS会话是变化得到的或不是变化得到的；
IMS会话是从独立IMS DC会话变化得到的，或不是从独立IMS DC会话变化得到的。
可选地，本申请实施例中，在上述第二事件为上述实施例所述的事件2-3，即第二事件包括以下至少一项：建立或修改独立IMS DC会话的事件、建立IMS会话的事件的情况下：
上述第二指示信息用于获取IMS DC会话对应的信息。
上述步骤54具体为步骤54c：当producer确定发生建立或修改独立IMS DC会话或建立IMS DC会话时，向consumer发送通知消息，用于通知终端相关的第一信息，该第一信息包括第二事件和第三指示信息。其中，该第三指示信息用于指示以下至少一项：
IMS DC会话是变化得到的或不是变化得到的；
IMS DC会话是从正常IMS会话变化得到的，或不是从正常IMS会话变化得到的。
可选地，本申请实施例中，在上述第二事件为上述实施例所述的事件2-4，即第二事件包括以下至少一项：建立引导DC的事件、建立IMS会话的事件的情况下：
上述第二指示信息用于获取引导DC对应的信息。
上述步骤54具体为步骤54d：当producer确定终端已建立引导DC时，向consumer发送通知消息，用于通知终端相关的第一信息，该第一信息包括第二事件和第三指示信息。其中，该第三指示信息用于指示以下至少一项：
DC是本地的或不是本地的；
DC是远端的或不是远端的。
可选地，本申请实施例中，在上述第二事件为上述实施例所述的事件2-5，即第二事件包括以下至少一项：建立应用DC的事件、建立IMS DC应用的事件、建立IMS会话的事件的情况下：
上述第二指示信息用于获取应用DC对应的信息。
上述步骤54具体为步骤54e：当producer确定终端已建立应用DC时，向consumer发送通知消息，用于通知终端相关的第一信息，该第一信息包括第二事件和第三指示信息。其中，该第三指示信息用于指示以下至少一项：
DC是本地终端发起的，或不是本地终端发起的；
DC是对端终端发起的，或不是对端终端发起的。
可选地，本申请实施例中，在上述第二事件为上述实施例所述的事件2-6，即第二事件包括建立应用DC的事件的情况下：
上述第二指示信息用于获取应用DC对应的信息。
上述步骤54具体为步骤54f：当producer确定终端已建立应用DC时，向consumer发送通知消息，用于通知终端相关的第一信息，该第一信息包括第二事件和第三指示信息。其中，该第三指示信息用于指示以下至少一项：
应用DC对应的应用信息；
应用DC对应的引导DC的信息。
需要说明的是，针对上述步骤步骤50至步骤55以及相关方案的说明，参见上述实施例中的描述，此处不再赘述。
实施方式四：consumer经由中间(intermediate)NF向producer请求通用事件，producer在向consumer发送通知时，携带指示信息。
如图9所示，本申请实施例提供的通信方法包括下述的步骤60至步骤72。
步骤60、NF服务consumer向中间NF发送订阅消息，该订阅消息中包括第二事件。
可选地，本申请实施例中，上述订阅消息中还包括第二指示信息。
步骤61、中间NF确定producer。
步骤62、中间NF向producer发送订阅消息，该订阅消息中包括第二事件。
需要说明的是，上述步骤60中的订阅消息和步骤62中的订阅消息可以相同或不同。例如，订阅消息都可以为Subscribe_Request。
步骤63、producer创建新的事件订阅资源，开始检测订阅的事件。
步骤64、producer向中间NF发送响应消息。
步骤65、中间NF向producer发送响应消息。
需要说明的是，上述步骤64中的响应消息和步骤65中的响应消息可以相同或不同。例如，步骤64中的响应消息可以为Subscribe_Request response，步骤65中的响应消息可以为Ndcsf_EE_Subscribe_Request response。
步骤66、producer确定订阅的事件发生。
步骤67、producer向中间NF发送通知消息，用于通知终端相关的第一信息，该第一信息包括第二事件和第三指示信息。
步骤68、中间NF向NF服务consumer发送通知消息，用于通知终端相关的第一信息，该第一信息包括第二事件和第三指示信息。
需要说明的是，上述步骤67中的通知消息和步骤68中的通知消息可以相同或不同。例如，通知消息都可以为Notify_Request。
步骤69、NF服务consumer向中间NF发送响应消息。
步骤70、中间NF向producer发送响应消息。
需要说明的是，上述步骤69中的响应消息和步骤70中的响应消息可以相同或不同。例如，响应消息都可以为Notify_Request response。
步骤71、producer直接向NF服务consumer发送通知消息，用于通知终端相关的第一信息，该第一信息包括第二事件和第三指示信息。
例如，通知消息可以为Notify_Request。
步骤72、NF服务consumer直接向producer发送响应消息。
例如，响应消息可以为Notify_Request response。
需要说明的是，上述步骤67至步骤70，与步骤71至步骤72，执行关系为或者的关系，即在上述步骤66之后，可以执行上述步骤67至步骤70，或者也可以执行上述步骤71至步骤72。
需要说明的是，针对第二事件分别包括事件2-1至事件2-6时，第二指示信息、上述步骤67或步骤71的具体实现方案以及第三指示信息的说明，可以参见上述实施方式三中的描述，此处不再赘述。
本申请实施例提供一种通信方法，第一通信设备可以接收第二通信设备发送的通知消息，以获知发生的事件的相关信息，即终端相关的第一信息。如此，通过本方案较为全面地向第一通信设备开放了终端状态，使得第一通信设备能够获知更多的终端状态，例如独立DC相关的内容、DC是与本端终端相关的还是与对端终端相关的等内容，从而更加准确地判断出终端使用DC应用时的终端状态。
上述各个方法实施例，或者各个方法实施例中的各种可能的实现方式均可以单独执行，也可以任意两个或两个以上相互结合执行，具体可以根据实际使用需求确定，本申请实施例对此不做限制。
本申请实施例提供的通信方法，执行主体可以为通信装置。本申请实施例中以通信装置执行通信方法为例，说明本申请实施例提供的通信装置。
图10示出了本申请实施例中涉及的通信装置的一种可能的结构示意图。如图10所示，通信装置80可以包括：接收模块81。
其中，接收模块81，用于接收第二通信设备发送的第一消息，第一消息用于通知终端相关的第一信息，第一信息用于指示以下至少一项：已建立独立引导DC；已建立独立应用DC；独立IMS DC会话变为正常IMS会话；正常IMS会话变为独立IMS DC会话；已建立本地引导DC；已建立远端引导DC；本地终端发起应用DC的建立；对端终端发起应用DC的建立；建立的应用DC对应的应用信息；建立的应用DC对应的引导DC的信息。
在一种可能的实现方式中，结合图10，如图11所示，上述通信装置80还包括：发送模块82。发送模块82，用于向第二通信设备发送第二消息，第二消息中包括第一事件，第一事件包括以下至少一项：
建立独立引导DC的事件；
建立独立应用DC的事件；
独立IMS DC会话变为正常IMS会话的事件；
正常IMS会话变为独立IMS DC会话的事件；
建立本地引导DC的事件；
建立远端引导DC的事件；
本地终端发起应用DC的建立的事件；
对端终端发起应用DC的建立的事件。
在一种可能的实现方式中，结合图10，如图11所示，上述通信装置80还包括：发送模块82。发送模块82，用于向第二通信设备发送第三消息，第三消息中包括第二事件和第一指示信息，第一指示信息用于指示第二事件的相关信息。
在一种可能的实现方式中，上述第二事件包括以下至少一项：建立引导DC的事件、建立应用DC的事件、建立DC的事件、建立IMS会话的事件；
上述第一指示信息用于指示以下至少一项：
DC是独立引导DC或非独立引导DC；
DC是独立应用DC或非独立应用DC；
DC是独立DC或非独立DC。
在一种可能的实现方式中，上述第二事件包括以下至少一项：建立或修改正常IMS会话的事件、建立IMS会话的事件；
上述第一指示信息用于指示以下至少一项：
IMS会话是变化得到的或不是变化得到的；
IMS会话是从独立IMS DC会话变化得到的，或不是从独立IMS DC会话变化得到的；
在一种可能的实现方式中，上述第二事件包括以下至少一项：建立或修改独立IMS DC会话的事件、建立IMS会话的事件；
上述第一指示信息用于指示以下至少一项：
IMS DC会话是变化得到的或不是变化得到的；
IMS DC会话是从正常IMS会话变化得到的，或不是从正常IMS会话变化得到的。
在一种可能的实现方式中，上述第二事件包括以下至少一项：建立引导DC的事件、建立IMS会话的事件；
上述第一指示信息用于指示以下至少一项：
DC是本地的或不是本地的；
DC是远端的或不是远端的。
在一种可能的实现方式中，上述第二事件包括以下至少一项：建立应用DC的事件、建立IMS DC应用的事件、建立IMS会话的事件；
上述第一指示信息用于指示以下至少一项：
DC是本地终端发起的，或不是本地终端发起的；
DC是对端终端发起的，或不是对端终端发起的。
在一种可能的实现方式中，上述第二事件包括建立应用DC的事件；
上述第一指示信息用于指示以下至少一项：
应用DC对应的应用信息；
应用DC对应的引导DC的信息。
在一种可能的实现方式中，上述应用信息包括以下至少一项：应用类型、应用标识、应用绑定信息。
在一种可能的实现方式中，结合图10，如图11所示，上述通信装置80还包括：发送模块82。发送模块82，用于向第二通信设备发送第四消息，第四消息中包括第二事件和第二指示信息，第二指示信息用于获取以下至少一项：
引导DC对应的信息；
应用DC对应的信息；
IMS会话对应的信息；
IMS DC会话对应的信息。
本申请实施例提供一种通信装置，通信装置可以接收第二通信设备发送的通知消息，以获知发生的事件的相关信息，即终端相关的第一信息。通过本方案较为全面地向通信装置开放了终端状态，使得通信装置能够获知更多的终端状态，例如独立DC相关的内容、DC是与本端终端相关的还是与对端终端相关的等内容，从而更加准确地判断出终端使用DC应用时的终端状态。
本申请实施例提供的通信装置能够实现上述通信方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例中的通信装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于上述所列举的终端11的类型，其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例不作具体限定。
图12示出了本申请实施例中涉及的通信装置的一种可能的结构示意图。如图12所示，通信装置90可以包括：发送模块91。
其中，发送模块91，用于向第一通信设备发送第一消息，第一消息用于通知终端相关的第一信息，第一信息用于指示以下至少一项：已建立独立引导DC；已建立独立应用DC；独立IMS DC会话变为正常IMS会话；正常IMS会话变为独立IMS DC会话；已建立本地引导DC；已建立远端引导DC；本地终端发起应用DC的建立；对端终端发起应用DC的建立；建立的应用DC对应的应用信息；建立的应用DC对应的引导DC的信息。
在一种可能的实现方式中，结合图12，如图13所示，上述通信装置90还包括：接收模块92。接收模块92，用于接收第一通信设备发送的第二消息，第二消息中包括第一事件，第一事件包括以下至少一项：
建立独立引导DC的事件；
建立独立应用DC的事件；
独立IMS DC会话变为正常IMS会话的事件；
正常IMS会话变为独立IMS DC会话的事件；
建立本地引导DC的事件；
建立远端引导DC的事件；
本地终端发起应用DC的建立的事件；
对端终端发起应用DC的建立的事件。
在一种可能的实现方式中，结合图12，如图13所示，上述通信装置90还包括：接收模块92。接收模块92，用于接收第一通信设备发送的第三消息，第三消息中包括第二事件和第一指示信息，第一指示信息用于指示第二事件的相关信息。
在一种可能的实现方式中，上述第二事件包括以下至少一项：建立引导DC的事件、建立应用DC的事件、建立DC的事件、建立IMS会话的事件；
上述第一指示信息用于指示以下至少一项：
DC是独立引导DC或非独立引导DC；
DC是独立应用DC或非独立应用DC；
DC是独立DC或非独立DC。
在一种可能的实现方式中，上述第二事件包括以下至少一项：建立或修改正常IMS会话的事件、建立IMS会话的事件；
上述第一指示信息用于指示以下至少一项：
IMS会话是变化得到的或不是变化得到的；
IMS会话是从独立IMS DC会话变化得到的，或不是从独立IMS DC会话变化得到的；
在一种可能的实现方式中，上述第二事件包括以下至少一项：建立或修改独立IMS DC会话的事件、建立IMS会话的事件；
上述第一指示信息用于指示以下至少一项：
IMS DC会话是变化得到的或不是变化得到的；
IMS DC会话是从正常IMS会话变化得到的，或不是从正常IMS会话变化得到的。
在一种可能的实现方式中，上述第二事件包括以下至少一项：建立引导DC的事件、建立IMS会话的事件；
上述第一指示信息用于指示以下至少一项：
DC是本地的或不是本地的；
DC是远端的或不是远端的。
在一种可能的实现方式中，上述第二事件包括以下至少一项：建立应用DC的事件、建立IMS DC应用的事件、建立IMS会话的事件；
上述第一指示信息用于指示以下至少一项：
DC是本地终端发起的，或不是本地终端发起的；
DC是对端终端发起的，或不是对端终端发起的。
在一种可能的实现方式中，上述第二事件包括建立应用DC的事件；
上述第一指示信息用于指示以下至少一项：
应用DC对应的应用信息；
应用DC对应的引导DC的信息。
在一种可能的实现方式中，上述应用信息包括以下至少一项：应用类型、应用标识、应用绑定信息。
在一种可能的实现方式中，结合图12，如图13所示，上述通信装置90还包括：接收模块92。接收模块92，用于接收第一通信设备发送的第四消息，第四消息中包括第二事件和第二指示信息，第二指示信息用于获取以下至少一项：
引导DC对应的信息；
应用DC对应的信息；
IMS会话对应的信息；
IMS DC会话对应的信息。
本申请实施例提供一种通信装置，通信装置可以向第一通信设备发送通知消息，以通知发生的事件的相关信息，即终端相关的第一信息。通过本方案较为全面地向第一通信设备开放了终端状态，使得第一通信设备能够获知更多的终端状态，例如独立DC相关的内容、DC是与本端终端相关的还是与对端终端相关的等内容，从而更加准确地判断出终端使用DC应用时的终端状态。
本申请实施例提供的通信装置能够实现上述通信方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
如图14所示，本申请实施例还提供一种通信设备5000，包括处理器5001和存储器5002，存储器5002上存储有可在所述处理器5001上运行的程序或指令，例如，该通信设备5000为第一通信设备时，该程序或指令被处理器5001执行时实现上述第一通信设备侧方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。该通信设备5000为第二通信设备时，该程序或指令被处理器5001执行时实现上述第二通信设备侧方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，本申请实施例中，上述第一通信设备可以为终端或网络侧设备，该网络侧设备可以为接入网设备或核心网设备。上述第二通信设备可以为终端或网络侧设备，该网络侧设备可以为接入网设备或核心网设备。
本申请实施例还提供一种终端，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述通信方法实施例中的步骤。该终端实施例与上述第一通信设备侧或第二通信设备侧方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。具体地，图15为实现本申请实施例的一种终端的硬件结构示意图。
该终端7000包括但不限于：射频单元7001、网络模块7002、音频输出单元7003、输入单元7004、传感器7005、显示单元7006、用户输入单元7007、接口单元7008、存储器7009以及处理器7010等中的至少部分部件。
本领域技术人员可以理解，终端7000还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器7010逻辑相连，从而通过电源管理系统实现管理充电、放电以及功耗管理等功能。图15中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元7004可以包括图形处理单元(Graphics Processing Unit，GPU)70041和麦克风70042，图形处理器70041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元7006可包括显示面板70061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板70061。用户输入单元7007包括触控面板70071以及其他输入设备70072中的至少一种。触控面板70071，也称为触摸屏。触控面板70071可包括触摸检测装置和触摸控制器两个部分。其他输入设备70072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元7001接收来自网络侧设备的下行数据后，可以传输给处理器7010进行处理；另外，射频单元7001可以向网络侧设备发送上行数据。通常，射频单元7001包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器7009可用于存储软件程序或指令以及各种数据。存储器7009可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器7009可以包括易失性存储器或非易失性存储器。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器7009包括但不限于这些和任意其它适合类型的存储器。
处理器7010可包括一个或多个处理单元；可选的，处理器7010集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器7010中。
本申请实施例提供的终端能够实现上述方法实施例实现的各个过程，并达到相同的技术效果，本实施例中提及的各实现方式的实现过程可以参照上述通信方法实施例的相关描述，为避免重复，这里不再赘述。
本申请实施例还提供一种网络侧设备，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述通信方法实施例的步骤。该网络侧设备实施例与上述第一通信设备侧或第二通信设备侧方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中，且能达到相同的技术效果。
具体地，本申请实施例还提供了一种网络侧设备。如图16所示，该网络侧设备600包括：天线601、射频装置602、基带装置603、处理器604和存储器605。天线601与射频装置602连接。在上行方向上，射频装置602通过天线601接收信息，将接收的信息发送给基带装置603进行处理。在下行方向上，基带装置603对要发送的信息进行处理，并发送给射频装置602，射频装置602对收到的信息进行处理后经过天线601发送出去。
以上实施例中网络侧设备执行的方法可以在基带装置603中实现，该基带装置603包括基带处理器。
基带装置603例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图16所示，其中一个芯片例如为基带处理器，通过总线接口与存储器605连接，以调用存储器605中的程序，执行以上方法实施例中所示的网络设备操作。
该网络侧设备还可以包括网络接口606，该接口例如为通用公共无线接口(Common Public Radio Interface，CPRI)。
具体地，本发明实施例的网络侧设备600还包括：存储在存储器605上并可在处理器604上运行的指令或程序，处理器604调用存储器605中的指令或程序执行上述实施例所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例提供的网络侧设备能够实现上述方法实施例实现的各个过程，并达到相同的技术效果，本实施例中提及的各实现方式的实现过程可以参照上述通信方法实施例的相关描述，为避免重复，这里不再赘述。
具体地，本申请实施例还提供了一种网络侧设备。如图17所示，该网络侧设备1700包括：处理器1701、网络接口1702和存储器1703。其中，网络接口1702例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本申请实施例的网络侧设备1700还包括：存储在存储器1703上并可在处理器1701上运行的指令或程序，处理器1701调用存储器1703中的指令或程序执行上述实施例所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述通信方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。在一些示例中，可读存储介质可以是非瞬态的可读存储介质。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述通信方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述通信方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种通信系统，包括：第一通信设备及第二通信设备，所述第一通信设备可用于执行如上所述的通信方法的步骤，所述第二通信设备可用于执行如上所述的通信方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助计算机软件产品加必需的通用硬件平台的方式来实现，当然也可以通过硬件。该计算机软件产品存储在存储介质(如ROM、RAM、磁碟、光盘等)中，包括若干指令，用以使得终端或者网络侧设备执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式的实施方式，这些实施方式均属于本申请的保护之内。

Claims (33)

  1. 一种通信方法，包括：
    第一通信设备接收第二通信设备发送的第一消息，所述第一消息用于通知终端相关的第一信息，所述第一信息用于指示以下至少一项：
    已建立独立引导数据通道DC；
    已建立独立应用DC；
    独立互联网协议多媒体子系统IMSDC会话变为正常IMS会话；
    正常IMS会话变为独立IMSDC会话；
    已建立本地引导DC；
    已建立远端引导DC；
    本地终端发起应用DC的建立；
    对端终端发起应用DC的建立；
    建立的应用DC对应的应用信息；
    建立的应用DC对应的引导DC的信息。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述第一通信设备向所述第二通信设备发送第二消息，所述第二消息中包括第一事件，所述第一事件包括以下至少一项：
    建立独立引导DC的事件；
    建立独立应用DC的事件；
    独立IMSDC会话变为正常IMS会话的事件；
    正常IMS会话变为独立IMSDC会话的事件；
    建立本地引导DC的事件；
    建立远端引导DC的事件；
    本地终端发起应用DC的建立的事件；
    对端终端发起应用DC的建立的事件。
  3. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述第一通信设备向所述第二通信设备发送第三消息，所述第三消息中包括第二事件和第一指示信息，所述第一指示信息用于指示所述第二事件的相关信息。
  4. 根据权利要求3所述的方法，其中，所述第二事件包括以下至少一项：建立引导DC的事件、建立应用DC的事件、建立DC的事件、建立IMS会话的事件；
    所述第一指示信息用于指示以下至少一项：
    DC是独立引导DC或非独立引导DC；
    DC是独立应用DC或非独立应用DC；
    DC是独立DC或非独立DC。
  5. 根据权利要求3所述的方法，其中，所述第二事件包括以下至少一项：建立或修改正常IMS会话的事件、建立IMS会话的事件；
    所述第一指示信息用于指示以下至少一项：
    IMS会话是变化得到的或不是变化得到的；
    IMS会话是从独立IMSDC会话变化得到的，或不是从独立IMSDC会话变化得到的。
  6. 根据权利要求3所述的方法，其中，所述第二事件包括以下至少一项：建立或修改独立IMS DC会话的事件、建立IMS会话的事件；
    所述第一指示信息用于指示以下至少一项：
    IMSDC会话是变化得到的或不是变化得到的；
    IMSDC会话是从正常IMS会话变化得到的，或不是从正常IMS会话变化得到的。
  7. 根据权利要求3所述的方法，其中，所述第二事件包括以下至少一项：建立引导DC的事件、建立IMS会话的事件；
    所述第一指示信息用于指示以下至少一项：
    DC是本地的或不是本地的；
    DC是远端的或不是远端的。
  8. 根据权利要求3所述的方法，其中，所述第二事件包括以下至少一项：建立应用DC的事件、建立IMSDC应用的事件、建立IMS会话的事件；
    所述第一指示信息用于指示以下至少一项：
    DC是本地终端发起的，或不是本地终端发起的；
    DC是对端终端发起的，或不是对端终端发起的。
  9. 根据权利要求3所述的方法，其中，所述第二事件包括建立应用DC的事件；
    所述第一指示信息用于指示以下至少一项：
    应用DC对应的应用信息；
    应用DC对应的引导DC的信息。
  10. 根据权利要求1至9中任一项所述的方法，其中，所述应用信息包括以下至少一项：应用类型、应用标识、应用绑定信息。
  11. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述第一通信设备向所述第二通信设备发送第四消息，所述第四消息中包括第二事件和第二指示信息，所述第二指示信息用于获取以下至少一项：
    引导DC对应的信息；
    应用DC对应的信息；
    IMS会话对应的信息；
    IMSDC会话对应的信息。
  12. 一种通信方法，包括：
    第二通信设备向第一通信设备发送第一消息，所述第一消息用于通知终端相关的第一信息，所述第一信息用于指示以下至少一项：
    已建立独立引导DC；
    已建立独立应用DC；
    独立IMSDC会话变为正常IMS会话；
    正常IMS会话变为独立IMSDC会话；
    已建立本地引导DC；
    已建立远端引导DC；
    本地终端发起应用DC的建立；
    对端终端发起应用DC的建立；
    建立的应用DC对应的应用信息；
    建立的应用DC对应的引导DC的信息。
  13. 根据权利要求12所述的方法，其中，所述方法还包括：
    所述第二通信设备接收所述第一通信设备发送的第二消息，所述第二消息中包括第一事件，所述第一事件包括以下至少一项：
    建立独立引导DC的事件；
    建立独立应用DC的事件；
    独立IMSDC会话变为正常IMS会话的事件；
    正常IMS会话变为独立IMSDC会话的事件；
    建立本地引导DC的事件；
    建立远端引导DC的事件；
    本地终端发起应用DC的建立的事件；
    对端终端发起应用DC的建立的事件。
  14. 根据权利要求12所述的方法，其中，所述方法还包括：
    所述第二通信设备接收所述第一通信设备发送的第三消息，所述第三消息中包括第二事件和第一指示信息，所述第一指示信息用于指示所述第二事件的相关信息。
  15. 根据权利要求14所述的方法，其中，所述第二事件包括以下至少一项：建立引导DC的事件、建立应用DC的事件、建立DC的事件、建立IMS会话的事件；
    所述第一指示信息用于指示以下至少一项：
    DC是独立引导DC或非独立引导DC；
    DC是独立应用DC或非独立应用DC；
    DC是独立DC或非独立DC。
  16. 根据权利要求14所述的方法，其中，所述第二事件包括以下至少一项：建立或修改正常IMS会话的事件、建立IMS会话的事件；
    所述第一指示信息用于指示以下至少一项：
    IMS会话是变化得到的或不是变化得到的；
    IMS会话是从独立IMSDC会话变化得到的，或不是从独立IMSDC会话变化得到的。
  17. 根据权利要求14所述的方法，其中，所述第二事件包括以下至少一项：建立或修改独立IMSDC会话的事件、建立IMS会话的事件；
    所述第一指示信息用于指示以下至少一项：
    IMSDC会话是变化得到的或不是变化得到的；
    IMSDC会话是从正常IMS会话变化得到的，或不是从正常IMS会话变化得到的。
  18. 根据权利要求14所述的方法，其中，所述第二事件包括以下至少一项：建立引导DC的事件、建立IMS会话的事件；
    所述第一指示信息用于指示以下至少一项：
    DC是本地的或不是本地的；
    DC是远端的或不是远端的。
  19. 根据权利要求14所述的方法，其中，所述第二事件包括以下至少一项：建立应用DC的事件、建立IMSDC应用的事件、建立IMS会话的事件；
    所述第一指示信息用于指示以下至少一项：
    DC是本地终端发起的，或不是本地终端发起的；
    DC是对端终端发起的，或不是对端终端发起的。
  20. 根据权利要求14所述的方法，其中，所述第二事件包括建立应用DC的事件；
    所述第一指示信息用于指示以下至少一项：
    应用DC对应的应用信息；
    应用DC对应的引导DC的信息。
  21. 根据权利要求12至20中任一项所述的方法，其中，所述应用信息包括以下至少一项：应用类型、应用标识、应用绑定信息。
  22. 根据权利要求12所述的方法，其中，所述方法还包括：
    所述第二通信设备接收所述第一通信设备发送的第四消息，所述第四消息中包括第二事件和第二指示信息，所述第二指示信息用于获取以下至少一项：
    引导DC对应的信息；
    应用DC对应的信息；
    IMS会话对应的信息；
    IMSDC会话对应的信息。
  23. 一种通信装置，包括：接收模块；
    所述接收模块，用于接收第二通信设备发送的第一消息，所述第一消息用于通知终端相关的第一信息，所述第一信息用于指示以下至少一项：
    已建立独立引导DC；
    已建立独立应用DC；
    独立IMSDC会话变为正常IMS会话；
    正常IMS会话变为独立IMSDC会话；
    已建立本地引导DC；
    已建立远端引导DC；
    本地终端发起应用DC的建立；
    对端终端发起应用DC的建立；
    建立的应用DC对应的应用信息；
    建立的应用DC对应的引导DC的信息。
  24. 根据权利要求23所述的装置，其中，所述装置还包括：发送模块；
    所述发送模块，用于向所述第二通信设备发送第二消息，所述第二消息中包括第一事件，所述第一事件包括以下至少一项：
    建立独立引导DC的事件；
    建立独立应用DC的事件；
    独立IMSDC会话变为正常IMS会话的事件；
    正常IMS会话变为独立IMSDC会话的事件；
    建立本地引导DC的事件；
    建立远端引导DC的事件；
    本地终端发起应用DC的建立的事件；
    对端终端发起应用DC的建立的事件。
  25. 根据权利要求23所述的装置，其中，所述装置还包括：发送模块；
    所述发送模块，用于向所述第二通信设备发送第三消息，所述第三消息中包括第二事件和第一指示信息，所述第一指示信息用于指示所述第二事件的相关信息。
  26. 根据权利要求23所述的装置，其中，所述装置还包括：发送模块；
    所述发送模块，用于向所述第二通信设备发送第四消息，所述第四消息中包括第二事件和第二指示信息，所述第二指示信息用于获取以下至少一项：
    引导DC对应的信息；
    应用DC对应的信息；
    IMS会话对应的信息；
    IMSDC会话对应的信息。
  27. 一种通信装置，包括：发送模块；
    所述发送模块，用于向第一通信设备发送第一消息，所述第一消息用于通知终端相关的第一信息，所述第一信息用于指示以下至少一项：
    已建立独立引导DC；
    已建立独立应用DC；
    独立IMSDC会话变为正常IMS会话；
    正常IMS会话变为独立IMSDC会话；
    已建立本地引导DC；
    已建立远端引导DC；
    本地终端发起应用DC的建立；
    对端终端发起应用DC的建立；
    建立的应用DC对应的应用信息；
    建立的应用DC对应的引导DC的信息。
  28. 根据权利要求27所述的装置，其中，所述装置还包括：接收模块；
    所述接收模块，用于接收所述第一通信设备发送的第二消息，所述第二消息中包括第一事件，所述第一事件包括以下至少一项：
    建立独立引导DC的事件；
    建立独立应用DC的事件；
    独立IMSDC会话变为正常IMS会话的事件；
    正常IMS会话变为独立IMSDC会话的事件；
    建立本地引导DC的事件；
    建立远端引导DC的事件；
    本地终端发起应用DC的建立的事件；
    对端终端发起应用DC的建立的事件。
  29. 根据权利要求27所述的装置，其中，所述装置还包括：接收模块；
    所述接收模块，用于接收所述第一通信设备发送的第三消息，所述第三消息中包括第二事件和第一指示信息，所述第一指示信息用于指示所述第二事件的相关信息。
  30. 根据权利要求27所述的装置，其中，所述装置还包括：接收模块；
    所述接收模块，用于接收所述第一通信设备发送的第四消息，所述第四消息中包括第二事件和第二指示信息，所述第二指示信息用于获取以下至少一项：
    引导DC对应的信息；
    应用DC对应的信息；
    IMS会话对应的信息；
    IMSDC会话对应的信息。
  31. 一种通信设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至11中任一项所述的通信方法的步骤，或者实现如权利要求12至22中任一项所述的通信方法的步骤。
  32. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至11中任一项所述的通信方法，或者实现如权利要求12至22中任一项所述的通信方法的步骤。
  33. 一种计算机程序，所述计算机程序被存储在存储介质中，所述程序被至少一个处理器执行时实现如权利要求1至11中任一项所述的通信方法，或者实现如权利要求12至22中任一项所述的通信方法的步骤。
PCT/CN2025/082962 2024-03-22 2025-03-17 通信方法、装置、设备及存储介质 Pending WO2025195331A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410337065.9A CN120692686A (zh) 2024-03-22 2024-03-22 通信方法、装置、设备及存储介质
CN202410337065.9 2024-03-22

Publications (1)

Publication Number Publication Date
WO2025195331A1 true WO2025195331A1 (zh) 2025-09-25

Family

ID=97083878

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/082962 Pending WO2025195331A1 (zh) 2024-03-22 2025-03-17 通信方法、装置、设备及存储介质

Country Status (2)

Country Link
CN (1) CN120692686A (zh)
WO (1) WO2025195331A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101068199A (zh) * 2007-06-04 2007-11-07 华为技术有限公司 实现融合业务的方法、系统、业务代理及终端
CN104579914A (zh) * 2013-10-17 2015-04-29 中兴通讯股份有限公司 一种系统之间订阅状态的方法及装置
CN105282730A (zh) * 2014-05-26 2016-01-27 中国电信股份有限公司 Ims网络中终端通信状态获取方法与系统和应用服务器

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101068199A (zh) * 2007-06-04 2007-11-07 华为技术有限公司 实现融合业务的方法、系统、业务代理及终端
CN104579914A (zh) * 2013-10-17 2015-04-29 中兴通讯股份有限公司 一种系统之间订阅状态的方法及装置
CN105282730A (zh) * 2014-05-26 2016-01-27 中国电信股份有限公司 Ims网络中终端通信状态获取方法与系统和应用服务器

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on system architecture for next generation real time communication services Phase 2 (Release 19)", 3GPP DRAFT; 23700-77-030, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 2 February 2024 (2024-02-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052597521 *

Also Published As

Publication number Publication date
CN120692686A (zh) 2025-09-23

Similar Documents

Publication Publication Date Title
US20250203677A1 (en) Communication establishment method and apparatus, terminal device, and network side device
WO2024120282A1 (zh) 信息发送、信息接收方法、装置、终端及网络侧设备
WO2023179595A1 (zh) 非3gpp设备的会话通道建立方法、装置及设备
US20250071178A1 (en) Method and Apparatus for Processing Data Channel Application List, and Device
WO2025026192A1 (zh) Ai业务的处理方法、装置、设备及可读存储介质
WO2024120285A1 (zh) 信息传输方法、装置、终端及网络侧设备
WO2025195331A1 (zh) 通信方法、装置、设备及存储介质
WO2024164877A1 (zh) 数据通道处理方法、装置、通信设备及可读存储介质
WO2024078400A1 (zh) 模型请求方法、装置、通信设备及可读存储介质
WO2024061143A1 (zh) 应用程序确定方法、装置、终端及服务器
WO2024104149A1 (zh) 信息传输方法、装置、终端、网络侧设备及存储介质
WO2023005898A1 (zh) 多终端联合会话管理方法、网络侧设备及终端
WO2024051663A1 (zh) 数据通道建立方法、第一终端及第二终端
WO2025130941A1 (zh) 数据交互方法及设备
WO2025130939A1 (zh) 数据面连接建立的方法及设备
WO2025055800A1 (zh) 网络注册处理方法、装置、系统及通信设备
WO2025167902A1 (zh) 数据发送方法、用户设备及网络功能
WO2025195234A1 (zh) 终端能力注册方法、获取方法、装置、终端及设备
WO2025148874A1 (zh) 终端控制方法、终端及网络侧设备
JP2025525123A (ja) ホスティングネットワークのネットワーク選択情報の取得方法、端末およびネットワーク側機器
WO2022268012A1 (zh) 资源处理方法、装置、电子设备及存储介质
WO2025195235A1 (zh) 任务处理方法、装置及通信设备
WO2024078589A1 (zh) 信息上报方法、装置、通信设备及存储介质
WO2024120286A1 (zh) 传输方法、装置、终端及网络侧设备
WO2025130841A1 (zh) 终端能力上报或获取方法、装置及网元

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25773030

Country of ref document: EP

Kind code of ref document: A1