Communication method, communication device, communication system, storage medium, and program product

Abstract

The present disclosure relates to a communication method, a communication device, a communication system, a storage medium, and a program product. The method is executed by a first network element, and comprises: determining to allocate a first bearer and a second bearer to a first service, wherein the first service is an IMS service accessed by using NB-IoT, the first bearer is used for carrying IMS signaling of the first service, and the second bearer is used for carrying IMS data of the first service. The solution of the present disclosure can meet the requirements on IMS services, and enhances the system performance.

Description

Communication methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of wireless communication, and more particularly to a communication method, communication device, communication system, storage medium, and program product. Background Technology

[0002] The Internet Protocol (IP) Multimedia Subsystem (IMS) is a new form of multimedia service. It can meet the needs of end users for voice calls, video calls, and more innovative and diverse multimedia services.

[0003] With the development of IoT technology, narrowband Internet of Things (NB-IoT) access technology has been proposed to meet the access needs of low-power, low-cost IoT terminals. Terminals can connect to the evolved packet core (EPC) network through NB-IoT access. Summary of the Invention

[0004] This disclosure provides a communication method, communication device, communication system, storage medium, and program product for conducting IMS services via NB-IoT access.

[0005] According to a first aspect of the present disclosure, a communication method is provided. The method is executed by a first network element. The method includes: determining to allocate a first bearer and a second bearer for a first service, wherein the first service is an IMS service accessed using NB-IoT; wherein the first bearer is used to carry IMS signaling for the first service, and the second bearer is used to carry IMS data for the first service.

[0006] According to a second aspect of the present disclosure, a communication method is provided. The method is executed by a second network element. The method includes: interacting with a first network element with IMS signaling or IMS data for a first service, wherein the first service is an IMS service accessed using NB-IoT, the IMS signaling is carried in a first bearer, and the IMS data is carried in a second bearer.

[0007] According to a third aspect of the present disclosure, a communication method is provided. The method is executed by a third network element. The method includes: interacting with a second network element with IMS signaling or IMS data for a first service, wherein the first service is an IMS service accessed using NB-IoT, the IMS signaling is carried in a first bearer, and the IMS data is carried in a second bearer.

[0008] According to a fourth aspect of the present disclosure, a communication method is provided. The method is executed by a terminal. The method includes: interacting with a first network element with first information, wherein the first information includes one of the following: IMS signaling and a first identifier of a first service, IMS data of the first service, and a second identifier; the first service is an IMS service accessed using NB-IoT; the first identifier indicates a first bearer; and the second identifier indicates a second bearer; wherein the first bearer is used to carry the IMS signaling of the first service, and the second bearer is used to carry the IMS data of the first service.

[0009] According to a fifth aspect of the present disclosure, a communication method is provided. The method is executed by a communication system. The communication system includes a first network element and a second network element. The method includes: the first network element determining to allocate a first bearer and a second bearer for a first service; the first network element and the second network element interacting with IMS signaling or IMS data of the first service, wherein the IMS signaling is carried in the first bearer and the IMS data is carried in the second bearer; wherein the first service is an IMS service accessed using NB-IoT.

[0010] According to a sixth aspect of the present disclosure, a communication device is provided. This communication device is used to perform the communication methods described in any of the first to fourth aspects.

[0011] According to a seventh aspect of the present disclosure, a communication device is provided. This communication device is used to perform the communication methods as described in any of the first to fourth aspects.

[0012] According to an eighth aspect of the present disclosure, a communication system is provided. The communication system includes at least one of the following: a first network element, a second network element, a third network element, and a terminal. The first network element is configured to perform the communication method as described in the first aspect. The second network element is configured to perform the communication method as described in the second aspect. The third network element is configured to perform the communication method as described in the third aspect. The terminal is configured to perform the communication method as described in the fourth aspect.

[0013] According to a ninth aspect of the present disclosure, a storage medium is provided. The storage medium stores instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in any one of the first to fifth aspects.

[0014] According to a tenth aspect of the present disclosure, a program product is provided. The program product includes at least one of a program and instructions. When executed by a communication device, the program or instructions implement the steps of the communication method as described in any one of the first to fifth aspects.

[0015] According to an eleventh aspect of the present disclosure, a computer program is provided. When run on a computer, the computer program causes the computer to perform the communication method as described in any one of the first to fifth aspects.

[0016] According to a twelfth aspect of the present disclosure, a chip or chip system is provided. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication method as described in any one of the first to fifth aspects.

[0017] According to the embodiments of this disclosure, the requirements of IMS services can be met and system performance can be enhanced.

[0018] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not constitute a limitation on the embodiments of this disclosure. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the embodiments of the invention.

[0020] Figure 1 is a schematic diagram of an exemplary architecture of a communication system provided according to an embodiment of the present disclosure.

[0021] Figure 2A is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0022] Figure 2B is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0023] Figure 3A is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0024] Figure 3B is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0025] Figure 4A is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0026] Figure 4B is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0027] Figure 5A is a schematic diagram of the bearer of IMS services provided according to an embodiment of the present disclosure.

[0028] Figure 5B is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure.

[0029] Figure 5C is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure.

[0030] Figure 6 is an exemplary schematic diagram of a communication device provided according to an embodiment of the present disclosure.

[0031] Figure 7A is an exemplary structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0032] Figure 7B is an exemplary structural diagram of a chip provided according to an embodiment of the present disclosure. Detailed Implementation

[0033] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0034] In a first aspect, embodiments of this disclosure provide a communication method. The method is executed by a first network element. The method includes: determining to allocate a first bearer and a second bearer for a first service, wherein the first service is an IMS service accessed using NB-IoT; wherein the first bearer is used to carry IMS signaling for the first service, and the second bearer is used to carry IMS data for the first service.

[0035] In this embodiment, the first network element allocates a first bearer and a second bearer for the IMS service accessed via NB-IoT, to carry the IMS signaling and IMS data of the IMS service, respectively. Thus, by carrying the IMS signaling and IMS data in different bearers, the different transmission requirements of IMS signaling and IMS data, such as QoS, can be met. In this way, different processing of IMS signaling and IMS data can be implemented in the EPS, satisfying the different service requirements of different types of data in the IMS service and enhancing system performance.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the first bearer and the second bearer are allocated when both the terminal and the first network support the first service, the first network element is located in the first network, and the access type used by the terminal is NB-IoT.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the first bearer is a default bearer or a dedicated bearer, and the second bearer is a dedicated bearer; the first bearer and the second bearer are different.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes at least one of the following: establishing or modifying a first bearer according to a first strategy, wherein the first strategy is used for the QoS requirements of a first service for the first bearer; and establishing or modifying a second bearer according to a second strategy, wherein the second strategy is used for the QoS requirements of the first service for the second bearer.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, establishing or modifying the first bearer includes: establishing or modifying the first S11-U bearer, wherein the first S11-U bearer is located between the first network element and the service gateway.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, establishing or modifying the second bearer includes: establishing or modifying the second S11-U bearer, wherein the second S11-U bearer is located between the first network element and the service gateway.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes: receiving first information sent by a terminal, wherein the first information includes one of the following: IMS signaling and a first identifier, IMS data and a second identifier; wherein the first identifier indicates a first bearer and the second identifier indicates a second bearer.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes: sending a first message to a second network element, wherein the first message carries IMS signaling or IMS data, the first message carrying IMS signaling is carried in a first bearer, and the first message carrying IMS signaling is carried in a second bearer.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes: receiving a second message sent by a second network element, wherein the second message carries IMS signaling or IMS data, the second message carrying IMS signaling is sent by the second network element through a first bearer, the second message carrying IMS data is sent by the second network element through a second bearer, the first bearer is indicated by a first identifier, and the second bearer is indicated by a second identifier; sending first information to a terminal, wherein the first information includes one of the following: IMS signaling and a first identifier, IMS data, and a second identifier.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments, the first bearer includes a first S11-U bearer, and the second bearer includes a second S11-U bearer; wherein, the IMS signaling bearer is in the first S11-U bearer, and the IMS data bearer is in the second S11-U bearer.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes: sending a first identifier and a second identifier to the terminal.

[0046] In conjunction with some embodiments of the first aspect, in some embodiments, the first bearer and the second bearer are used for a data transmission process initiated by the terminal, and the first bearer and the second bearer are in response to IMS signaling or IMS data allocation from the terminal; or, the first bearer and the second bearer are used for a data transmission process terminated at the terminal, and the first bearer and the second bearer are in response to IMS signaling or IMS data allocation from the first network.

[0047] In a second aspect, embodiments of this disclosure provide a communication method. This method is executed by a second network element. The method includes: interacting with a first network element for IMS signaling or IMS data of a first service, wherein the first service is an IMS service accessed using NB-IoT, the IMS signaling is carried in a first bearer, and the IMS data is carried in a second bearer.

[0048] In this embodiment, by carrying IMS signaling and IMS data in different bearers, the differences in transmission requirements such as QoS between IMS signaling and IMS data can be met, thus accurately transmitting IMS signaling and IMS data in different bearers. In this way, different processing of IMS signaling and IMS data can be implemented in EPS, meeting the different requirements of different types of data in IMS services and enhancing system performance.

[0049] In conjunction with some embodiments of the second aspect, in some embodiments, the first bearer and the second bearer are allocated when both the terminal and the first network support the first service, the first network element is located in the first network, and the access type used by the terminal is NB-IoT.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the first bearer is a default bearer or a dedicated bearer, and the second bearer is a dedicated bearer; the first bearer and the second bearer are different.

[0051] In conjunction with some embodiments of the second aspect, in some embodiments, the interaction of IMS signaling or IMS data with the first network element for the first service includes: sending a second message to the first network element, wherein the second message carries IMS signaling or IMS data, the second message carrying IMS signaling is carried in a first bearer, the second message carrying IMS data is carried in a second bearer, the first bearer is indicated by a first identifier, and the second bearer is indicated by a second identifier.

[0052] In conjunction with some embodiments of the second aspect, in some embodiments, the interaction of IMS signaling or IMS data with the first network element for the first service includes: receiving a first message sent by the first network element, wherein the first message carries IMS signaling or IMS data, the first message carrying IMS signaling is sent by the first network element through a first bearer, the first message carrying IMS data is sent by the first network element through a second bearer, the first bearer is indicated by a first identifier, and the second bearer is indicated by a second identifier.

[0053] In conjunction with some embodiments of the second aspect, in some embodiments, the first bearer includes a first S11-U bearer located between the first network element and the second network element, and the second bearer includes a second S11-U bearer located between the first network element and the second network element; wherein, the IMS signaling bearer is in the first S11-U bearer, or the IMS data bearer is in the second S11-U bearer.

[0054] In conjunction with some embodiments of the second aspect, in some embodiments, the above method further includes: interacting with a third network element using IMS signaling or IMS data.

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the first bearer and the second bearer are used for a data transmission process initiated by the terminal, and the first bearer and the second bearer are in response to IMS signaling or IMS data allocation from the terminal; or, the first bearer and the second bearer are used for a data transmission process terminated at the terminal, and the first bearer and the second bearer are in response to IMS signaling or IMS data allocation from the first network.

[0056] In a third aspect, embodiments of this disclosure provide a communication method. This method is executed by a third network element. The method includes: interacting with a second network element for IMS signaling or IMS data of a first service, wherein the first service is an IMS service accessed using NB-IoT, the IMS signaling is carried in a first bearer, and the IMS data is carried in a second bearer.

[0057] In this embodiment, by carrying IMS signaling and IMS data on different bearers, the differences in transmission requirements such as QoS between IMS signaling and IMS data can be met, thus accurately transmitting IMS signaling and IMS data on different bearers. In this way, different processing of IMS signaling and IMS data can be implemented in EPS, meeting the different requirements of different types of data in IMS services and enhancing system performance.

[0058] In conjunction with some embodiments of the third aspect, in some embodiments, the first bearer and the second bearer are allocated when both the terminal and the first network support the first service, the first network element is located in the first network, and the access type used by the terminal is NB-IoT.

[0059] In conjunction with some embodiments of the third aspect, in some embodiments, the first bearer is a default bearer or a dedicated bearer, and the second bearer is a dedicated bearer; the first bearer and the second bearer are different.

[0060] In conjunction with some embodiments of the third aspect, in some embodiments, the interaction of IMS signaling or IMS data with the second network element for the first service includes: sending a third message to the second network element, wherein the third message carries IMS signaling or IMS data, the third message carrying IMS signaling is carried in a first bearer, the third message carrying IMS data is carried in a second bearer, the first bearer is indicated by a first identifier, and the second bearer is indicated by a second identifier.

[0061] In conjunction with some embodiments of the third aspect, in some embodiments, the interaction with the second network element for IMS signaling or IMS data of the first service includes: receiving a fourth message sent by the second network element, wherein the fourth message carries IMS signaling or IMS data, the fourth message carrying IMS signaling is sent by the second network element through a first bearer, the fourth message carrying IMS data is sent by the second network element through a second bearer, the first bearer is indicated by a first identifier, and the second bearer is indicated by a second identifier.

[0062] In conjunction with some embodiments of the third aspect, in some embodiments, the first bearer and the second bearer are used for a data transmission process initiated by the terminal, and the first bearer and the second bearer are in response to IMS signaling or IMS data allocation from the terminal; or, the first bearer and the second bearer are used for a data transmission process terminated at the terminal, and the first bearer and the second bearer are in response to IMS signaling or IMS data allocation from the first network.

[0063] In a fourth aspect, embodiments of this disclosure provide a communication method. This method is executed by a terminal. The method includes: interacting with a first network element to exchange first information, wherein the first information includes one of the following: IMS signaling and a first identifier for a first service, IMS data for the first service, and a second identifier; the first service is an IMS service accessed using NB-IoT; the first identifier indicates a first bearer; and the second identifier indicates a second bearer; wherein the first bearer is used to carry the IMS signaling of the first service, and the second bearer is used to carry the IMS data of the first service.

[0064] In this embodiment, by transmitting IMS signaling and IMS data on different bearers, the differences in transmission requirements such as QoS between IMS signaling and IMS data can be met, thus accurately transmitting IMS signaling and IMS data on different bearers. In this way, different processing of IMS signaling and IMS data can be implemented in EPS, meeting the different requirements of different types of data in IMS services and enhancing system performance.

[0065] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first bearer and the second bearer are allocated when both the terminal and the first network support the first service, the first network element is located in the first network, and the access type used by the terminal is NB-IoT.

[0066] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first bearer is a default bearer or a dedicated bearer, and the second bearer is a dedicated bearer; the first bearer and the second bearer are different.

[0067] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above method further includes: receiving a first identifier and a second identifier sent by a first network element.

[0068] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first bearer and the second bearer are used for a data transmission process initiated by the terminal, and the first bearer and the second bearer are in response to IMS signaling or IMS data allocation from the terminal; or, the first bearer and the second bearer are used for a data transmission process terminated at the terminal, and the first bearer and the second bearer are in response to IMS signaling or IMS data allocation from the first network.

[0069] In a fifth aspect, embodiments of this disclosure provide a communication method. The method is executed by a communication system. The communication system includes a first network element and a second network element. The method includes: the first network element determining to allocate a first bearer and a second bearer for a first service; the first network element and the second network element interacting with each other regarding IMS signaling or IMS data for the first service, wherein the IMS signaling is carried in the first bearer and the IMS data is carried in the second bearer; wherein the first service is an IMS service accessed using NB-IoT.

[0070] In conjunction with some embodiments of the fifth aspect, in some embodiments, the communication system further includes a third network element. The method also includes: the third network element interacting with the second network element using IMS signaling or IMS data.

[0071] In conjunction with some embodiments of the fifth aspect, in some embodiments, the communication system further includes a terminal. The method further includes: the terminal interacting with a first network element to exchange first information, wherein the first information includes one of the following: Internet Protocol Multimedia Subsystem (IMS) signaling and a first identifier for the first service, and IMS data and a second identifier for the first service.

[0072] In a sixth aspect, embodiments of this disclosure provide a communication device. The communication device is a first network element. The communication device includes a processing module. The processing module is configured to: determine and allocate a first bearer and a second bearer for a first service, wherein the first service is an IMS service accessed using NB-IoT; wherein the first bearer is used to carry IMS signaling for the first service, and the second bearer is used to carry IMS data for the first service.

[0073] In conjunction with some embodiments of the sixth aspect, in some embodiments, the first bearer and the second bearer are allocated when both the terminal and the first network support the first service, the first network element is located in the first network, and the access type used by the terminal is NB-IoT.

[0074] In conjunction with some embodiments of the sixth aspect, in some embodiments, the first bearer is a default bearer or a dedicated bearer, and the second bearer is a dedicated bearer; the first bearer and the second bearer are different.

[0075] In conjunction with some embodiments of the sixth aspect, in some embodiments, the processing module is further configured to perform at least one of the following: establishing or modifying a first bearer according to a first policy, wherein the first policy is used for the QoS requirements of a first service for the first bearer; and establishing or modifying a second bearer according to a second policy, wherein the second policy is used for the QoS requirements of the first service for the second bearer.

[0076] In conjunction with some embodiments of the sixth aspect, in some embodiments, the processing module is configured to: establish or modify a first S11-U bearer, wherein the first S11-U bearer is located between a first network element and a service gateway.

[0077] In conjunction with some embodiments of the sixth aspect, in some embodiments, the processing module is configured to: establish or modify a second S11-U bearer, wherein the second S11-U bearer is located between the first network element and the service gateway.

[0078] In conjunction with some embodiments of the sixth aspect, in some embodiments, the above-mentioned communication device further includes a transceiver module, which is configured to receive first information sent by a terminal, wherein the first information includes one of the following: IMS signaling and a first identifier, IMS data and a second identifier; wherein the first identifier indicates a first bearer and the second identifier indicates a second bearer.

[0079] In conjunction with some embodiments of the sixth aspect, in some embodiments, the transceiver module is further configured to: send a first message to the second network element, wherein the first message carries IMS signaling or IMS data, the first message carrying IMS signaling is carried in a first bearer, and the first message carrying IMS signaling is carried in a second bearer.

[0080] In conjunction with some embodiments of the sixth aspect, in some embodiments, the transceiver module is further configured to: receive a second message sent by a second network element, wherein the second message carries IMS signaling or IMS data, the second message carrying IMS signaling is sent by the second network element through a first bearer, the second message carrying IMS data is sent by the second network element through a second bearer, the first bearer is indicated by a first identifier, and the second bearer is indicated by a second identifier; and send first information to the terminal, wherein the first information includes the following six: IMS signaling and the first identifier, IMS data, and the second identifier.

[0081] In conjunction with some embodiments of the sixth aspect, in some embodiments, the first bearer includes a first S11-U bearer, and the second bearer includes a second S11-U bearer; wherein, the IMS signaling bearer is in the first S11-U bearer, and the IMS data bearer is in the second S11-U bearer.

[0082] In conjunction with some embodiments of the sixth aspect, in some embodiments, the transceiver module is further configured to send a first identifier and a second identifier to the terminal.

[0083] In conjunction with some embodiments of the sixth aspect, in some embodiments, the first bearer and the second bearer are used for a data transmission process initiated by the terminal, and the first bearer and the second bearer are in response to IMS signaling or IMS data allocation from the terminal; or, the first bearer and the second bearer are used for a data transmission process terminated at the terminal, and the first bearer and the second bearer are in response to IMS signaling or IMS data allocation from the first network.

[0084] In a seventh aspect, embodiments of this disclosure provide a communication device. The communication device is a second network element. The communication device includes a transceiver module. The transceiver module is configured to interact with a first network element for IMS signaling or IMS data of a first service, wherein the first service is an IMS service accessed using NB-IoT, the IMS signaling is carried in a first bearer, and the IMS data is carried in a second bearer.

[0085] In conjunction with some embodiments of the seventh aspect, in some embodiments, the first bearer and the second bearer are allocated when both the terminal and the first network support the first service, the first network element is located in the first network, and the access type used by the terminal is NB-IoT.

[0086] In conjunction with some embodiments of the seventh aspect, in some embodiments, the first bearer is a default bearer or a dedicated bearer, and the second bearer is a dedicated bearer; the first bearer and the second bearer are different.

[0087] In conjunction with some embodiments of the seventh aspect, in some embodiments, the transceiver module is configured to: send a second message to a first network element, wherein the second message carries IMS signaling or IMS data, the second message carrying IMS signaling is carried in a first bearer, the second message carrying IMS data is carried in a second bearer, the first bearer is indicated by a first identifier, and the second bearer is indicated by a second identifier.

[0088] In conjunction with some embodiments of the seventh aspect, in some embodiments, the transceiver module is configured to: receive a first message sent by a first network element, wherein the first message carries IMS signaling or IMS data, the first message carrying IMS signaling is sent by the first network element through a first bearer, the first message carrying IMS data is sent by the first network element through a second bearer, the first bearer is indicated by a first identifier, and the second bearer is indicated by a second identifier.

[0089] In conjunction with some embodiments of the seventh aspect, in some embodiments, the first bearer includes a first S11-U bearer located between the first network element and the second network element, and the second bearer includes a second S11-U bearer located between the first network element and the second network element; wherein, the IMS signaling bearer is in the first S11-U bearer, or the IMS data bearer is in the second S11-U bearer.

[0090] In conjunction with some embodiments of the seventh aspect, in some embodiments, the transceiver module is further configured to: interact with a third network element for IMS signaling or IMS data.

[0091] In conjunction with some embodiments of the seventh aspect, in some embodiments, the first bearer and the second bearer are used for a data transmission process initiated by the terminal, and the first bearer and the second bearer are in response to IMS signaling or IMS data allocation from the terminal; or, the first bearer and the second bearer are used for a data transmission process terminated at the terminal, and the first bearer and the second bearer are in response to IMS signaling or IMS data allocation from the first network.

[0092] In an eighth aspect, embodiments of this disclosure provide a communication device. The communication device is a third network element. The communication device includes a transceiver module. The transceiver module is configured to interact with a second network element for IMS signaling or IMS data of a first service, wherein the first service is an IMS service accessed using NB-IoT, the IMS signaling is carried in a first bearer, and the IMS data is carried in a second bearer.

[0093] In conjunction with some embodiments of the eighth aspect, in some embodiments, the first bearer and the second bearer are allocated when both the terminal and the first network support the first service, the first network element is located in the first network, and the access type used by the terminal is NB-IoT.

[0094] In conjunction with some embodiments of the eighth aspect, in some embodiments, the first bearer is a default bearer or a dedicated bearer, and the second bearer is a dedicated bearer; the first bearer and the second bearer are different.

[0095] In conjunction with some embodiments of the eighth aspect, in some embodiments, the transceiver module is configured to: send a third message to a second network element, wherein the third message carries IMS signaling or IMS data, the third message carrying IMS signaling is carried in a first bearer, the third message carrying IMS data is carried in a second bearer, the first bearer is indicated by a first identifier, and the second bearer is indicated by a second identifier.

[0096] In conjunction with some embodiments of the eighth aspect, in some embodiments, the transceiver module is configured to: receive a fourth message sent by a second network element, wherein the fourth message carries IMS signaling or IMS data, the fourth message carrying IMS signaling is sent by the second network element through a first bearer, the fourth message carrying IMS data is sent by the second network element through a second bearer, the first bearer is indicated by a first identifier, and the second bearer is indicated by a second identifier.

[0097] In conjunction with some embodiments of the eighth aspect, in some embodiments, the first bearer and the second bearer are used for a data transmission process initiated by the terminal, the first bearer and the second bearer being in response to IMS signaling or IMS data allocation from the terminal; or, the first bearer and the second bearer are used for a data transmission process terminated at the terminal, the first bearer and the second bearer being in response to IMS signaling or IMS data allocation from the first network.

[0098] In a ninth aspect, embodiments of this disclosure provide a communication device. The communication device is a terminal. The communication device includes a transceiver module. The transceiver module is configured to interact with a first network element to exchange first information, wherein the first information includes one of the following: IMS signaling and a first identifier for a first service, IMS data for the first service, and a second identifier; the first service is an IMS service accessed using NB-IoT; the first identifier indicates a first bearer; and the second identifier indicates a second bearer; wherein the first bearer is used to carry the IMS signaling of the first service, and the second bearer is used to carry the IMS data of the first service.

[0099] In conjunction with some embodiments of the ninth aspect, in some embodiments, the first bearer and the second bearer are allocated when both the terminal and the first network support the first service, the first network element is located in the first network, and the access type used by the terminal is NB-IoT.

[0100] In conjunction with some embodiments of the ninth aspect, in some embodiments, the first bearer is a default bearer or a dedicated bearer, and the second bearer is a dedicated bearer; the first bearer and the second bearer are different.

[0101] In conjunction with some embodiments of the ninth aspect, in some embodiments, the transceiver module is further configured to receive a first identifier and a second identifier sent by the first network element.

[0102] In conjunction with some embodiments of the ninth aspect, in some embodiments, the first bearer and the second bearer are used for a data transmission process initiated by the terminal, the first bearer and the second bearer being in response to IMS signaling or IMS data allocation from the terminal; or, the first bearer and the second bearer are used for a data transmission process terminated at the terminal, the first bearer and the second bearer being in response to IMS signaling or IMS data allocation from the first network.

[0103] In a tenth aspect, embodiments of this disclosure provide a communication device. This communication device is used to perform the communication methods described in any of the first to fourth aspects and their possible implementations.

[0104] In an eleventh aspect, embodiments of this disclosure provide a communication system. The communication system includes at least one of the following: a first network element, a second network element, a third network element, and a terminal. The first network element is configured to perform the communication method as described in any of the first aspect and its possible embodiments. The second network element is configured to perform the communication method as described in any of the second aspect and its possible embodiments. The third network element is configured to perform the communication method as described in any of the third aspect and its possible embodiments. The terminal is configured to perform the communication method as described in any of the fourth aspect and its possible embodiments.

[0105] In an eleventh aspect, embodiments of this disclosure provide a storage medium storing instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in any of the first to fifth aspects and their possible implementations.

[0106] In a twelfth aspect, embodiments of this disclosure provide a program product. The program product includes at least one of a program and instructions. When executed by a communication device, the program or instructions implement the steps of the communication method as described in any of the first to fifth aspects and their possible embodiments.

[0107] In a thirteenth aspect, embodiments of this disclosure provide a computer program. When run on a computer, the computer program causes the computer to perform the communication methods described in any of the first to fifth aspects and their possible implementations.

[0108] In a fourteenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication methods described in any of the first to fifth aspects and their possible implementations.

[0109] It is understood that the aforementioned communication devices, communication systems, storage media, program products, computer programs, chips, and chip systems are all used to execute the methods provided in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0110] This disclosure provides a communication method, a communication device, a communication system, a storage medium, and a program product. In some embodiments, terms such as communication method, information processing method, and information transmission method can be used interchangeably; terms such as communication device, communication equipment, network equipment, network function, and network entity can be used interchangeably; and terms such as communication system and information processing system can be used interchangeably.

[0111] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0112] In the embodiments disclosed herein, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the various embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0113] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0114] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0115] In the embodiments of this disclosure, "a plurality of" means two or more.

[0116] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0117] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0118] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0119] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0120] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0121] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0122] In some embodiments, terms such as “greater than,” “more than,” “higher than,” and “exceeding” can be used interchangeably; terms such as “greater than or equal to,” “not less than,” “more than or equal to,” “not less than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably; terms such as “less than,” “less than,” and “lower than” can be used interchangeably; and terms such as “less than or equal to,” “not greater than,” “less than or equal to,” “not more than,” “lower than or equal to,” “not higher than,” and “below” can be used interchangeably.

[0123] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0124] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0125] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0126] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0127] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0128] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0129] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0130] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0131] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0132] Figure 1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 includes a terminal 101, an access network device 102, and a core network device 103.

[0133] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.

[0134] In some embodiments, terminal 101 may be an Internet of Things (IoT) device. In some embodiments, terminal 101 may be a device that supports NB-IoT access. For example, terminal 101 may be an NB-IoT device. For example, terminal 101 may have NB-IoT access capability.

[0135] In some embodiments, the access network device 102 may be a node or device that connects the terminal 101 to the wireless network. The access network device may include at least one of the following in a 5G communication system: evolved Node B (eNB), next generation eNB (ng-eNB), next generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system, but is not limited thereto.

[0136] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0137] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0138] In some embodiments, the core network device 103 may be a single device including a first network element 1031, a second network element 1032, a third network element 1033, etc., or it may be multiple devices or a group of devices, each encompassing all or part of the first network element 1031, the second network element 1032, the third network element 1033, etc. Core network elements may be virtual or physical. The core network may include, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

[0139] In some embodiments, the first network element 1031 is, for example, a mobility management entity (MME).

[0140] In some embodiments, the first network element 1031 may be responsible for UE registration, authentication and mobility management, handle UE attach, detach and handover requests, and provide non-access stratum (NAS) signaling security and access stratum security control, etc., and the name is not limited thereto.

[0141] In some embodiments, the second network element 1032 is, for example, a serving gateway (SGW).

[0142] In some embodiments, the second network element 1032 may be responsible for routing and forwarding user plane data, and its name is not limited thereto.

[0143] In some embodiments, the third network element 1033 is, for example, a packet data network (PDN) gateway (PGW).

[0144] In some embodiments, the third network element 1033 may be responsible for routing and forwarding user data, supporting UE mobility between different base stations, providing quality of service (QoS) control and billing functions, etc., and the name is not limited thereto.

[0145] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0146] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0147] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0148] Here, important concepts and terms involved in the embodiments of this disclosure are explained.

[0149] 1. IMS (IP Multimedia Subsystem)

[0150] IMS is a brand-new form of multimedia service. It can meet the needs of end users for voice communication, video calls, and newer, more diverse multimedia services. As an IP-based network architecture, IMS aims to provide a wide variety of multimedia communication services, such as voice, video, messaging, and data.

[0151] In some embodiments, IMS can be deployed in conjunction with a mobile communication system. For example, IMS can be deployed within or connected to a communication system. In some embodiments, when IMS is integrated with a mobile communication system, IMS can provide mobile multimedia services.

[0152] 2. NB-IoT (Narrowband Internet of Things)

[0153] NB-IoT is a low-power wide-area network (LPWAN) technology based on cellular networks, designed specifically for IoT devices. It supports low-power devices to connect to cellular data over wide-area networks. It aims to provide low-power, wide-coverage, and low-cost connectivity for IoT devices, supporting the deployment and application of large-scale IoT devices.

[0154] In some embodiments, NB-IoT may have the following characteristics:

[0155] (1) Low power consumption: Ultra-low power consumption is achieved through smaller transmission bandwidth and power-saving features during inactive transmission cycles, such as power saving mode (PSM) and extended discontinuous reception (eDRX). This supports longer battery life, which is crucial for remote devices with limited power access.

[0156] (2) Enhanced coverage: NB-IoT uses narrowband signals and data packet retransmission to achieve reliable indoor and underground connectivity. The range can reach about 1 kilometer in urban areas and about 10 kilometers in rural areas, making it ideal for remote devices.

[0157] (3) Massive connectivity: By effectively scheduling transmission and sleep windows, NB-IoT base stations can support more than 50,000 devices simultaneously. This scalability enables large-scale deployment and is crucial for large-scale IoT networks across infrastructure.

[0158] (4) Low equipment and deployment costs: By minimizing equipment complexity and providing only the necessary connectivity, NB-IoT hardware costs only a fraction of a 4G / 5G modem. Small data plans are also less expensive. Deployment is significantly cheaper than building a dedicated LPWAN network, as it eliminates the need for gateways and utilizes existing frequency bands.

[0159] In some embodiments, NB-IoT can be deployed as an access technology within the EPS. In this case, terminals can connect to the EPC within the EPS via NB-IoT access. In some embodiments, NB-IoT access can be considered an access type or access technology, namely NB-IoT radio access technology (RAT).

[0160] In some embodiments, to optimize support for small data transmission, NB-IoT defines Cellular IoT (CIoT) EPS optimization for EPC. CIoT EPS optimization provides optimized support for small data transmission. In some embodiments, one optimization is based on user plane (UP) transmission of user data and is referred to as user plane CIoT EPS optimization; another optimization, known as control plane (CP) CIoT EPS optimization, reduces the total number of control plane messages by encapsulating user data or SMS messages in NAS messages when processing short messages and small data transactions, and uses the MME to transmit user data or SMS messages.

[0161] In some embodiments, NB-IoT access has the following limitations compared to other access types such as E-UTRAN:

[0162] (1) It does not support mobility between RATs, that is, it does not support handover across RATs, such as handover from NB-IoT to other access or handover from other access to NB-IoT.

[0163] (2) In NB-IoT RAT, guaranteed bit rate (GBR) bearer is not supported.

[0164] (3) NB-IoT does not support dedicated bearers. For example, when a UE accesses the network via NB-IoT, the PGW uses the RAT type to ensure that there is no active dedicated bearer.

[0165] (4) Only the default bearer is supported in NB-IoT RAT. The default bearer is a non-GBR bearer.

[0166] In some embodiments, the EPS system supports IMS voice services and enables the UE to initiate IMS services through the EPS system. The EPS can notify the UE of "IMS voice support instruction on PS session". Here, PS session can refer to packet-switched (PS) session.

[0167] In some embodiments, if IMS voice over a PS session is supported, the serving public land mobile network (PLMN) may send this indication to the UE during the attach procedure or during a tracking area update (TAU). The serving PLMN may use this indication to tell the UE whether the UE can establish a voice-enabled bearer to conduct IMS services over the PS session.

[0168] In some embodiments, a UE with the capability to "conduct IMS voice over PS session" can support "IMS voice over PS session". During the process of establishing a voice bearer over PS session, the UE can consider the aforementioned instructions from EPS.

[0169] In some embodiments, the serving PLMN may provide the indication based on at least one of the following: local policy, home PLMN (HPLMN), voice support matching indication, the network's single radio voice call continuity (SRVCC) capability, the UE's SRVCC capability, and the coverage of the Universal Mobile Telecommunication System (UMTS) terrestrial radio access network (UTRAN) / evolved UTRAN (E-UTRAN).

[0170] In some embodiments, if the UE uses NB-IoT as the access point, the feature "conducting IMS voice over PS session" is not supported by the EPS system.

[0171] In one example, the access network serving the PLMN can extend its network coverage area using satellites. For instance, the access network can be deployed on geostationary orbit satellites, or satellites can be used as the wireless coverage function of the access network. In this case, supporting IMS voice services could be considered for the network to connect to NB-IoT and the EPC via geostationary orbit satellites.

[0172] Therefore, how to meet the business requirements of IMS services is an urgent problem to be solved.

[0173] Figure 2A is an exemplary interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. The communication method involved in this embodiment can be applied to a communication system 100. As shown in Figure 2A, the communication method of this embodiment includes steps S2101 to S2119.

[0174] In step S2101, terminal 101 sends a connection request message to the first network element 1031.

[0175] In some embodiments, terminal 101 may send a connection request message. In some embodiments, the connection request message may be sent by terminal 101, but is not limited to this, and may also be sent by other entities.

[0176] In some embodiments, the first network element 1031 can receive a connection request message. In some embodiments, the connection request message can be received by the first network element 1031, but is not limited thereto, and can also be received by other entities.

[0177] In some embodiments, terminal 101 requests the establishment of a PDN connection for a first service by sending a connection request message. In some embodiments, the first service may be an IMS service conducted via NB-IoT access. It is understood that an IMS service conducted via NB-IoT access may also be referred to as an IMS service over NB-IoT access.

[0178] In some embodiments, the types of IMS services may include IMS voice, IMS video, IMS messaging, IMS data, etc. It is understood that IMS services may also have other types, and this disclosure does not specifically limit these types.

[0179] In some embodiments, terminal 101 may have the capability to support IMS services via NB-IoT access. In this case, terminal 101 can provide IMS services via NB-IoT access. For example, terminal 101 can connect to core network device 103 via NB-IoT access.

[0180] In some embodiments, terminal 101 can send a connection request message to first network element 1031 through access network device 102. In some embodiments, NB-IoT access can be provided by access network device 102. In some embodiments, access network device 102 can support NB-IoT access. In some embodiments, terminal 101 can connect to core network device 103 through NB-IoT access provided by access network device 102.

[0181] In some embodiments, access network device 102 may be deployed in a terrestrial network. In one example, access network device 102 may be a terrestrial base station. In some embodiments, access network device 102 may be deployed in a non-terrestrial network (NTN). In one example, access network device 102 may be a satellite-based base station. For example, access network device 102 may include an eNB deployed on a satellite.

[0182] In some embodiments, the satellites on which the access network equipment 102 is deployed can have various orbit types. In some embodiments, the satellites on which the access network equipment 102 is deployed can be geostationary orbit (GEO) satellites, low earth orbit (LEO) satellites, medium earth orbit (MEO) satellites, polar satellites, and highly elliptical orbit (HEO) satellites.

[0183] In some embodiments, a satellite equipped with access network device 102 may operate in transparent transmission mode or regenerative mode.

[0184] In some embodiments, the connection request message may be a PDN connection request message. In some embodiments, by sending a PDN connection request message, terminal 101 can initiate a PDN connection process. In some embodiments, a PDN connection can be established for IMS services before starting IMS services. Then terminal 101 can initiate a PDN connection process. In some embodiments, the PDN connection process may be part of the attach process or may be a separate process.

[0185] In some embodiments, upon determining that a first service needs to be initiated, terminal 101 may send a connection request message. In some embodiments, the connection request message may be sent before the first service begins.

[0186] In some embodiments, the connection request message may include first capability information. The first capability information may indicate the capabilities of terminal 101.

[0187] In some embodiments, the first capability information may indicate at least one of the following: the terminal 101's ability to support IMS services in a control plane CIoT EPS optimized manner; the terminal 101's ability to support IMS services through NB-IoT access; and the terminal 101's ability to establish multiple bearers through NB-IoT access.

[0188] In some embodiments, the first capability information may indicate whether the terminal 101 supports IMS services in a control plane CIoT EPS optimized manner. In some embodiments, the first capability information may include a first field. The first field may have one or more values. In one example, the first field may have a first value. The first value indicates that the terminal 101 supports IMS services in a control plane CIoT EPS optimized manner. In one example, the first field may have a second value. The second value indicates that the terminal 101 does not support IMS services in a control plane CIoT EPS optimized manner. In some embodiments, the first field includes 1 bit. For example, the first value of the first field is 1, and the second value of the first field is 0. For example, the first value of the first field is 0, and the second value of the first field is 1. In some embodiments, the presence of the first field may be used to indicate that the terminal 101 supports IMS services in a control plane CIoT EPS optimized manner. For example, if the first capability information includes the first field and the first field has a first value, it indicates that the terminal 101 supports IMS services in a control plane CIoT EPS optimized manner. For example, if the first capability information does not include the first field, it indicates that the terminal 101 does not support IMS services in a control plane CIoT EPS optimized manner.

[0189] In some embodiments, the first capability information may indicate the terminal 101's ability to support IMS services via NB-IoT access. In some embodiments, the first capability information may include a second field. The second field may have one or more values. In one example, the second field may have a first value. The first value indicates that the terminal 101 supports IMS services via NB-IoT access. In another example, the second field may have a second value. The second value indicates that the terminal 101 does not support IMS services via NB-IoT access. In some embodiments, the second field includes 1 bit. For example, the first value of the second field is 1, and the second value of the second field is 0. For example, the first value of the second field is 0, and the second value of the second field is 1. In some embodiments, the presence of the second field may be used to indicate that the terminal 101 supports IMS services via NB-IoT access. For example, if the first capability information includes the second field and the second field has a first value, it indicates that the terminal 101 supports IMS services via NB-IoT access. For example, if the first capability information does not include the second field, it indicates that the terminal 101 does not support IMS services via NB-IoT access.

[0190] In some embodiments, the first field and the second field in the first capability information can be independent. In this case, the first capability information can indicate the terminal 101's support capability for IMS services delivered in a control plane CIoT EPS optimized manner and the terminal 101's support capability for IMS services delivered via NB-IoT access through the first field and the second field, respectively.

[0191] In some embodiments, the first and second fields in the first capability information may be combined. In this case, the first capability information may jointly indicate the terminal 101's support capability for IMS services delivered in a control plane CIoT EPS optimized manner and the terminal 101's support capability for IMS services delivered via NB-IoT access. In some embodiments, the first capability information may include first indication information. The first indication information may indicate the network behaviors (or preferred network behaviors) supported and preferred by the terminal 101. In some embodiments, the first indication information may include a preferred network behavior indication.

[0192] In some embodiments, the preferred network behavior of terminal 101 indicated by the first indication information may include at least one of the following: whether it supports IMS services delivered via NB-IoT access in a control plane CIoT EPS optimized manner, and whether it prefers to deliver IMS services via NB-IoT access in a control plane CIoT EPS optimized manner. It is understood that preferring to deliver IMS services via NB-IoT access in a control plane CIoT EPS optimized manner means supporting IMS services delivered via NB-IoT access in a control plane CIoT EPS optimized manner.

[0193] In some embodiments, the first capability information may indicate the terminal 101's ability to establish multiple bearers via NB-IoT access. In some embodiments, the first capability information may include a third field. The third field may have one or more values. In one example, the third field may have a first value. The first value indicates that the terminal 101 supports establishing multiple bearers via NB-IoT access. In one example, the third field may have a second value. The second value indicates that the terminal 101 does not support establishing multiple bearers via NB-IoT access. In some embodiments, the third field includes 1 bit. For example, the first value of the third field is 1, and the second value of the second field is 0. For example, the first value of the second field is 0, and the second value of the second field is 1. In some embodiments, the presence of the third field may be used to indicate that the terminal 101 supports establishing multiple bearers via NB-IoT access. For example, if the first capability information includes a third field and the third field has a first value, it indicates that the terminal 101 supports establishing multiple bearers via NB-IoT access. For example, if the first capability information does not include a third field, it indicates that the terminal 101 does not support establishing multiple bearers via NB-IoT access.

[0194] In some embodiments, the bearer may include a control plane bearer and / or a user plane bearer. In some embodiments, the bearer may include at least one of the following: a bearer between terminal 101 and access network device 102, a bearer between the first network element 1031 and the second network element 1032, and a bearer between the second network element 1032 and the third network element 1033. In some embodiments, the bearer between terminal 101 and access network device 102 may include a signaling radio bearer (SRB). In some embodiments, the bearer between the first network element 1031 and the second network element 1032 may include an S11-U bearer. In some embodiments, the bearer between the second network element 1032 and the third network element 1033 may include a user plane GPRS tunneling protocol (GTP-U) bearer.

[0195] In some embodiments, terminal 101 may support the establishment of one or more SRBs via NB-IoT access. In some embodiments, terminal 101 may support the establishment of one or more S11-U bearers via NB-IoT access. In some embodiments, terminal 101 may support the establishment of one or more GTP-U bearers via NB-IoT access.

[0196] In some embodiments, the connection request message may include an access point name (APN).

[0197] In some embodiments, the APN can be associated with IMS services. In some embodiments, the APN can be used by terminal 101 to establish a PDN connection for IMS services and connect to the network.

[0198] In step S2102, the first network element 1031 determines the allocation of the first bearer and the second bearer.

[0199] In some embodiments, upon receiving a connection request message, the first network element 1031 may determine to allocate a first bearer and a second bearer. In some embodiments, each of the first bearer and the second bearer may be used to carry first data of a first service.

[0200] In some embodiments, the first bearer and the second bearer are allocated when both the terminal and the first network support the first service. It is understood that supporting the first service can be referred to as supporting the first service.

[0201] In some embodiments, the first bearer and the second bearer may be determined and allocated by the first network element 1031 based on at least one of the following: the ability of the terminal 101 and the first network to support IMS services in a control plane CIoT EPS optimized manner; the ability of the terminal 101 and the first network to support IMS services through NB-IoT access; and the ability of the terminal 101 and the first network to support the establishment of multiple bearers through NB-IoT access.

[0202] In some embodiments, the first network may be the network where the first network element 1031 is located. For example, the first network may be the PLMN where the first network element 1031 is located. In one example, in a roaming scenario, the first network may be a visited network. In one example, in a non-roaming scenario, the first network may be a local network.

[0203] In some embodiments, the first network element 1031 may determine, based on first capability information, that the terminal 101 supports access via NB-IoT to conduct IMS services. In some embodiments, the first network element 1031 may determine that the first network supports access via NB-IoT to conduct IMS services. In some embodiments, if it is determined that both the terminal 101 and the first network support access via NB-IoT to conduct IMS services, the first network element 1031 may determine to allocate a first bearer and a second bearer.

[0204] In some embodiments, the first network element 1031 may determine, based on first capability information, that the terminal 101 supports IMS services via NB-IoT access in a control plane CIoT EPS optimized manner. In some embodiments, the first network element 1031 may determine that the first network supports IMS services via NB-IoT access in a control plane CIoT EPS optimized manner. In some embodiments, if it is determined that both the terminal 101 and the first network support IMS services via NB-IoT access in a control plane CIoT EPS optimized manner, the first network element 1031 may determine to allocate a first bearer and a second bearer.

[0205] In some embodiments, the first network element 1031 may determine, based on first capability information, that the terminal 101 supports IMS services via NB-IoT access and supports establishing multiple bearers via NB-IoT access. In some embodiments, the first network element 1031 may determine that the first network supports IMS services via NB-IoT access and supports establishing multiple bearers via NB-IoT access. In some embodiments, if it is determined that both the terminal 101 and the first network support IMS services via NB-IoT access and support establishing multiple bearers via NB-IoT access, the first network element 1031 may determine to allocate a first bearer and a second bearer.

[0206] In some embodiments, the first network element 1031 can determine, based on first capability information, that the terminal 101 supports IMS services delivered via NB-IoT access in a control plane CIoT EPS optimized manner and supports establishing multiple bearers via NB-IoT access. In some embodiments, the first network element 1031 can determine that the first network supports IMS services delivered via NB-IoT access in a control plane CIoT EPS optimized manner and supports establishing multiple bearers via NB-IoT access. In some embodiments, if it is determined that both the terminal 101 and the first network support IMS services delivered via NB-IoT access in a control plane CIoT EPS optimized manner and support establishing multiple bearers via NB-IoT access, the first network element 1031 can determine to allocate a first bearer and a second bearer.

[0207] In some embodiments, the support capabilities of the first network may be determined by the first network element 1031 based on at least one of operator policy, local configuration, and operations administration and maintenance (OAM) configuration.

[0208] In some embodiments, the first bearer may be used to carry IMS signaling for a first service.

[0209] In some implementations, the number of first bearers can be one or more. In one example, the number of first bearers can be one. For example, the first bearer can be a default bearer. For example, the first bearer can be a dedicated bearer. In one example, the number of first bearers can be multiple. For example, one of the multiple first bearers can be a default bearer, and the others can be dedicated bearers. For example, each of the multiple first bearers can be a dedicated bearer.

[0210] In some embodiments, the second bearer can be used to carry IMS data of the first service. In some embodiments, the first bearer can be a bearer used to carry IMS data of the first service.

[0211] In some embodiments, the number of second bearers can be one or more. In some embodiments, each first bearer can be a dedicated bearer.

[0212] In some embodiments, both the first and second bearers can be EPS bearers. EPS bearers are a granular level of QoS control used at the bearer level in EPC / E-UTRAN. In some embodiments, all traffic mapped to the same EPS bearer can be processed with the same bearer-level packet forwarding.

[0213] In some embodiments, the first bearer and the second bearer are different. In some embodiments, the first bearer and the second bearer may have different QoS requirements. In one example, the QoS requirement of the first bearer may be higher than the QoS requirement of the second bearer. In another example, the QoS requirement of the first bearer may be lower than the QoS requirement of the second bearer. In some embodiments, the first bearer and the second bearer may have different priorities. In one example, the priority of the first bearer may be higher than the priority of the second bearer. In yet another example, the priority of the first bearer may be lower than the priority of the second bearer.

[0214] In some embodiments, the first bearer may include at least one of the following: a first S11-U bearer and a first GTP-U bearer. In some embodiments, the first bearer may include at least one of the following: a second S11-U bearer and a second GTP-U bearer.

[0215] In some embodiments, the first S11-U bearer and the first GTP-U bearer in the first bearer and the second S11-U bearer and the second GTP-U bearer in the second bearer may all be different. For example, the first S11-U bearer and the second S11-U bearer may be different, and the first GTP-U bearer and the second GTP-U bearer may be different. In some embodiments, the first S11-U bearer and the first GTP-U bearer are associated with each other. In some embodiments, the second S11-U bearer and the second GTP-U bearer are associated with each other.

[0216] In some embodiments, the first S11-U bearer and the first GTP-U bearer in the first bearer and the second S11-U bearer and the second GTP-U bearer in the second bearer may each be partially different. For example, the first S11-U bearer and the second S11-U bearer may be different, and the first GTP-U bearer and the second GTP-U bearer may be the same. For example, the first S11-U bearer and the second S11-U bearer may be the same, and the first GTP-U bearer and the second GTP-U bearer may be different.

[0217] In some embodiments, the first bearer may further include a first SRB, and the second bearer may further include a second SRB. In some embodiments, the first SRB and the second SRB may be the same or different.

[0218] In some embodiments, step S2102 may include: determining first identification information and second identification information. In some embodiments, when determining the allocation of a first bearer and a second bearer, the first network element 1031 may allocate the first identification information and the second identification information for the first bearer and the second bearer, respectively.

[0219] It should be noted that, in this embodiment of the disclosure, the first identification information may also be referred to as the first identifier, and the second identification information may also be referred to as the second identifier.

[0220] In some embodiments, the first identification information may indicate a first bearer. In some embodiments, the first identification information may be used to identify the first bearer. In some embodiments, the first identification information may be associated with the first bearer. In some embodiments, each of the first SRB, the first S11-U bearer, and the first GTP-U bearer in the first bearer may be associated with the first identification information.

[0221] In some embodiments, the second identification information may indicate a second bearer. In some embodiments, the second identification information may be used to identify a second bearer. In some embodiments, the second identification information may be associated with a second bearer. In some embodiments, each of the second SRB, the second S11-U bearer, and the second GTP-U bearer in the second bearer may be associated with the second identification information.

[0222] In some embodiments, when the first bearer and the second bearer are EPS bearers, the first identification information may include a first EPS bearer identifier (EBI), and the second identification information may include a second EPS bearer identifier.

[0223] In step S2103, the first network element 1031 sends a connection acceptance message to the terminal 101.

[0224] In some embodiments, the first network element 1031 may send a connection acceptance message. In some embodiments, the connection acceptance message may be sent by the first network element 1031, but is not limited to this, and may also be sent by other entities.

[0225] In some embodiments, terminal 101 may receive a connection acceptance message. In some embodiments, the connection acceptance message may be received by terminal 101, but is not limited thereto, and may also be received by other entities.

[0226] In some embodiments, the connection acceptance message may be sent by the first network element 1031 upon accepting the PDN connection request message. In some embodiments, the connection acceptance message may be a PDN connection acceptance message.

[0227] In some embodiments, the connection acceptance message may include first identification information and second identification information. In some embodiments, the first identification information and second identification information may be provided to terminal 101 and / or access network device 102.

[0228] In step S2104, terminal 101 sends first information to access network device 102.

[0229] In some embodiments, terminal 101 can send information. In some embodiments, the first information can be sent by terminal 101, but is not limited thereto, and can also be sent by other entities.

[0230] In some embodiments, the access network device 102 may receive the first information. In some embodiments, the first information may be received by the access network device 102, but is not limited thereto, and may also be received by other entities.

[0231] In some embodiments, the first information may include first data and first identification information or second identification information.

[0232] In some embodiments, the first data may be IMS service data. In some embodiments, the first data may be IMS signaling or IMS data. In one example, the first data may be IMS signaling, in which case the first information may include first identification information. In one example, the first data may be IMS data, in which case the first information may include second identification information.

[0233] In some embodiments, terminal 101 may establish a radio resource control (RRC) connection. For example, terminal 101 may send an RRC connection request message. In some embodiments, first information may be carried in the RRC connection request message.

[0234] In some embodiments, the RRC connection request message may include a NAS packet data unit (PDU). In some embodiments, the NAS PDU may carry first information. For example, first identification information or second identification information, and first data may be included in the NAS PDU. In some embodiments, the first data carried in the RRC connection request message may be encrypted uplink data.

[0235] In some embodiments, for a PDN connection of type IP PDN configured to support header compression, terminal 101 should use header compression before encapsulating the first data in the NAS message. In some embodiments, the UE may indicate expected downlink data transmission in the NAS release auxiliary information in the NAS PDU.

[0236] In step S2105, the access network device 102 sends the first information to the first network element 1031.

[0237] In some embodiments, the access network device 102 may send first information. In some embodiments, the first information may be sent by the access network device 102, but is not limited thereto, and may also be sent by other entities.

[0238] In some embodiments, the first network element 1031 can receive the first information. In some embodiments, the first information can be received by the first network element 1031, but is not limited thereto, and can also be received by other entities.

[0239] In some embodiments, the access network device 102 may send an S1-AP initial UE message to the first network element 1031. In some embodiments, the first information may be carried in the S1-AP initial UE message.

[0240] In some embodiments, the access network device 102 can send the received first information to the first network element 1031. In some embodiments, after receiving the RRC connection request message, the access network device 102 can send a NAS PDU carrying the first information to the first network element 1031 via an S1-AP initial UE message.

[0241] In some embodiments, before sending the first information, the access network device 102 may obtain the EPS negotiated QoS profile from the first network element 1031 based on configuration information. In some embodiments, the access network device 102 may receive the QoS profile sent by the first network element 1031.

[0242] In some embodiments, the access network device 102 can apply different priorities to requests from different terminals. Thus, requests from different terminals can have different priorities.

[0243] In step S2106, the first network element 1031 processes the first data.

[0244] In some embodiments, the first network element 1031 can process the first data. In some embodiments, the processing performed by the first network element 1031 may include: integrity verification and decryption.

[0245] In some embodiments, the first network element 1031 may perform integrity verification on the NAS PDU and / or decrypt the first data contained in the NAS PDU after receiving the NAS PDU from the access network device 102.

[0246] In some embodiments, robust header compression (ROHC) can be applied. When ROHC is configured and used, and header compression is used for PDN connections, the first network element 1031 can decompress the IP header.

[0247] In step S2107, the first network element 1031 sends a modify bearer request message to the second network element 1032.

[0248] In some embodiments, the first network element 1031 may send a modify bearer request message. In some embodiments, the modify bearer request message may be sent by the first network element 1031, but is not limited thereto, and may also be sent by other entities.

[0249] In some embodiments, the second network element 1032 may receive a modify bearer request message. In some embodiments, the modify bearer request message may be received by the second network element 1032, but is not limited thereto, and may also be received by other entities.

[0250] In some embodiments, the bearer between the first network element 1031 and the second network element 1032 may not yet be established. In this case, the first network element 1031 may send a modify bearer request message to the second network element 1032. In some embodiments, the modify bearer request message may be sent for each PDN connection.

[0251] In some embodiments, if the allocation of the first bearer and the second bearer is determined in step S2102, the first network element 1031 may establish or modify the first bearer and / or the second bearer.

[0252] In some embodiments, the first network element 1031 can determine whether a first bearer exists. In some embodiments, the first information received by the first network element 1031 may include first identification information, then the first network element 1031 can determine whether the first bearer corresponding to the first identification information exists. If it is determined that the first bearer does not exist, the first network element 1031 can establish or modify the first bearer.

[0253] In some embodiments, the first network element 1031 may establish or modify the first bearer according to a first policy. In some embodiments, the first policy may indicate the QoS requirements of the first service for the first bearer. In some embodiments, the first policy may be used for the QoS requirements of the first service for the first bearer. In some embodiments, if the first service has specific requirements for the transmission of IMS signaling in the first network, then the first service has corresponding QoS requirements for the first bearer used to carry IMS signaling.

[0254] In some embodiments, the first bearer may be a dedicated bearer. In some embodiments, the first network element 1031 may receive a dedicated bearer establishment request from the second network element 1032 or the third network element 1033. The dedicated bearer establishment request may indicate a request to establish the first bearer. In response to the dedicated bearer establishment request, the first network element 1031 may perform a dedicated bearer establishment or modification process to obtain the first bearer.

[0255] In some embodiments, the first network element 1031 can determine whether the second bearer exists. In some embodiments, the first information received by the first network element 1031 may include second identification information, then the first network element 1031 can determine whether the first bearer corresponding to the second identification information exists. If it is determined that the second bearer does not exist, the first network element 1031 can establish or modify the second bearer.

[0256] In some embodiments, the dedicated bearer establishment request may be sent by the second network element 1032 or the third network element 1033. In some embodiments, the second network element 1032 or the third network element 1033 may be triggered to send a dedicated bearer establishment request for the first bearer upon receiving the first policy. In some embodiments, the dedicated bearer establishment request may be sent by the PCRF or other network elements.

[0257] In some embodiments, the first network element 1031 may establish or modify the second bearer according to a second policy. In some embodiments, the second policy may indicate the QoS requirements of the first service for the second bearer. In some embodiments, the second policy may be used for the QoS requirements of the first service for the second bearer. In some embodiments, if the first service has specific requirements for the transmission of IMS terminals in the first network, then the first service has corresponding QoS requirements for the second bearer used to carry the IMS terminals.

[0258] In some embodiments, the second bearer may be a dedicated bearer. In some embodiments, the first network element 1031 may receive a dedicated bearer establishment request from the second network element 1032 or the third network element 1033. The dedicated bearer establishment request may indicate a request to establish a second bearer. In response to the dedicated bearer establishment request, the first network element 1031 may perform a dedicated bearer establishment or modification process to obtain the second bearer.

[0259] In some embodiments, the dedicated bearer establishment request may be sent by the second network element 1032 or the third network element 1033. In some embodiments, the second network element 1032 or the third network element 1033 may be triggered to send a dedicated bearer establishment request for the second bearer upon receiving the second policy. In some embodiments, the dedicated bearer establishment request may be sent by the PCRF or other network elements.

[0260] In some embodiments, in order to establish or modify the first bearer and / or the second bearer, the first network element 1031 may send a modify bearer request message.

[0261] In some embodiments, the first bearer may include a first S11-U bearer. If the first network element 1031 determines that the first S11-U bearer has not been established based on the first identification information included in the first information, the first network element 1031 may send a modify bearer request message to establish or modify the first S11-U bearer. In some embodiments, the second bearer may include a second S11-U bearer. If the first network element 1031 determines that the second S11-U bearer has not been established based on the second identification information included in the first information, the first network element 1031 may send a modify bearer request message to establish or modify the second S11-U bearer.

[0262] In some embodiments, the modified bearer request message may include at least one of the following: address information of the first network element 1031, downlink tunnel endpoint identifier (DL TEID) of the first network element 1031, RAT type, and S11-U bearer identifier. In some embodiments, the DL TEID of the first network element 1031 may be MME TEID DL. MME TEID DL can be used to identify the downlink tunnel from the MME to the SGW. In some embodiments, the RAT type may be NB-IoT access (or NB-IoT).

[0263] In some embodiments, the S11-U bearer identifier can be used to indicate the S11-U bearer to be established. For example, in the case of requesting the establishment of a first S11-U bearer, the S11-U bearer identifier can indicate the first S11-U bearer. For example, in the case of requesting the establishment of a second S11-U bearer, the S11-U bearer identifier can indicate the second S11-U bearer. It is understood that the S11-U bearer identifier of the first S11-U bearer can be associated with the first identification information, or the first identification information can be used as the S11-U bearer identifier of the first S11-U bearer; similarly, the S11-U bearer identifier of the second S11-U bearer can be associated with the second identification information, or the second identification information can be used as the S11-U bearer identifier of the second S11-U bearer. This disclosure does not specifically limit this aspect.

[0264] In some embodiments, the second network element 1032 can send downlink data to the terminal 101.

[0265] In some embodiments, the first network element 1031 may indicate the S11-U tunnel for NAS user data and use the S11-U IP address and DL TEID of the first network element for the second network element 1032 to forward downlink data.

[0266] In step S2108, the second network element 1032 sends a modify bearer request message to the third network element 1033.

[0267] In some embodiments, the second network element 1032 may send a modify bearer request message. In some embodiments, the modify bearer request message may be sent by the second network element 1032, but is not limited thereto, and may also be sent by other entities.

[0268] In some embodiments, the third network element 1033 may receive a modify bearer request message. In some embodiments, the modify bearer request message may be received by the third network element 1033, but is not limited thereto, and may also be received by other entities.

[0269] In some embodiments, upon receiving a modify bearer request message from the first network element 1031, the second network element 1032 may send a modify bearer request message to the third network element 1033.

[0270] In some embodiments, the Modify Bearer Request message sent by the second network element 1032 may include a RAT type.

[0271] In step S2109, the third network element 1033 sends a modified bearer response message to the second network element 1032.

[0272] In some embodiments, the third network element 1033 may send a modified bearer response message. In some embodiments, the modified bearer response message may be sent by the third network element 1033, but is not limited thereto, and may also be sent by other entities.

[0273] In some embodiments, the second network element 1032 may receive a modified bearer response message. In some embodiments, the modified bearer response message may be received by the second network element 1032, but is not limited thereto, and may also be received by other entities.

[0274] In some embodiments, the Modify Bearer Response Message may be sent by the third network element 1033 in response to the Modify Bearer Request Message.

[0275] In step S2110, the second network element 1032 sends a modified bearer response message to the first network element 1031.

[0276] In some embodiments, the second network element 1032 may send a modified bearer response message. In some embodiments, the modified bearer response message may be sent by the second network element 1032, but is not limited thereto, and may also be sent by other entities.

[0277] In some embodiments, the first network element 1031 may receive a modified bearer response message. In some embodiments, the modified bearer response message may be received by the first network element 1031, but is not limited thereto, and may also be received by other entities.

[0278] In some embodiments, as a response to a modify bearer request message, the second network element 1032 may send a modify bearer response message to the first network element 1031.

[0279] In some embodiments, the modified bearer response message sent by the second network element 1032 may include at least one of the following: address information of the second network element 1032, TEID of the second network element 1032, and S11-U bearer identifier. The address information and TEID of the second network element 1032 can be used for uplink transmission. In some embodiments, the TEID of the second network element 1032 carried in the modified bearer response message may be SGW TEID UL. SGW TEID UL can be used to identify the uplink tunnel from the UE to the SGW.

[0280] In some embodiments, the second network element 1032 is used for the address of the S11-U user plane, and the TEID is used by the first network element 1031 to forward uplink data to the second network element 1032.

[0281] It should be noted that, through steps S2107 to S2110, a first bearer and a second bearer can be established between the first network element 1031 and the second network element 1032 for the transmission of the first data.

[0282] In step S2111, the first network element 1031 sends the first data to the third network element 1033.

[0283] In some embodiments, the first network element 1031 can transmit first data. In some embodiments, the first data can be transmitted by the first network element 1031, but is not limited thereto, and can also be transmitted by other entities.

[0284] In some embodiments, the third network element 1033 can receive the first data. In some embodiments, the first data can be received by the third network element 1033, but is not limited thereto, and can also be received by other entities.

[0285] In some embodiments, the first network element 1031 can send the first data from the terminal 101 to the third network element 1033. In some embodiments, the first network element 1031 can send the first data to the third network element 1033 through the second network element 1032.

[0286] In some embodiments, the first network element 1031 can send the first data to the third network element 1033 via control plane messages.

[0287] In some embodiments, when the first information includes first identification information, the first network element 1031 can send the first data to the third network element 1033 via the first bearer. In other words, the first data can be carried in the first bearer indicated by the first identification information. In some embodiments, the first network element 1031 can send the first data to the third network element 1033 via the first S11-U bearer and the first GTP-U bearer. The first data transmitted via the first bearer can be IMS signaling.

[0288] In some embodiments, when the first information includes second identification information, the first network element 1031 can send the first data to the third network element 1033 via the second bearer. In other words, the first data can be carried in the second bearer indicated by the second identification information. In some embodiments, the first network element 1031 can send the first data to the third network element 1033 via the second S11-U bearer and the second GTP-U bearer. The first data transmitted via the second bearer can be IMS data.

[0289] In step S2112, the third network element 1033 sends the first data to the first network element 1031.

[0290] In some embodiments, the third network element 1033 can transmit the first data. In some embodiments, the first data can be transmitted by the third network element 1033, but is not limited to this, and can also be transmitted by other entities.

[0291] In some embodiments, the first network element 1031 can receive the first data. In some embodiments, the first data can be received by the first network element 1031, but is not limited thereto, and can also be received by other entities.

[0292] In some embodiments, based on NAS release auxiliary information from terminal 101, downlink first data can be expected. This means that downlink first data transmission may occur after uplink first data transmission.

[0293] In some embodiments, the first data sent by the third network element 1033 to the first network element 1031 may be downlink data. In some embodiments, the first data may be IMS signaling or IMS data.

[0294] In some embodiments, when the downlink first data arrives at the third network element 1033, the third network element 1033 can send the first data to the first network element 1031 through the second network element 1032.

[0295] In some embodiments, before sending the first data, the third network element 1033 can detect whether the first data is IMS signaling or IMS data. For example, the third network element 1033 can determine whether the first data is IMS signaling or IMS data based on the header of the first data packet. For example, the first network element 1031 can determine whether the first data is IMS signaling or IMS data based on the payload content of the first data packet.

[0296] In some embodiments, if it is determined that the first data is IMS signaling, the third network element 1033 can send the first data to the first network element 1031 via the first bearer. In other words, the first data can be carried in the first bearer. In some embodiments, the third network element 1033 can send the first data to the first network element 1031 via the first S11-U bearer and the first GTP-U bearer.

[0297] In some embodiments, if it is determined that the first data is IMS data, the third network element 1033 can send the first data to the first network element 1031 via the second bearer. In other words, the first data can be carried in the second bearer. In some embodiments, the third network element 1033 can send the first data to the first network element 1031 via the second S11-U bearer and the second GTP-U bearer.

[0298] In some embodiments, step S2112 may include: the second network element 1032 receiving first data sent by the third network element 1033; the second network element 1032 sending the first data to the first network element 1031.

[0299] In some embodiments, the first data may include IMS signaling. In this case, the second network element 1032 can receive the first data from the third network element 1033 via the first bearer and send the first data to the first network element 1031. In some embodiments, the first identification information may be transmitted together with the first data. For example, the second network element 1032 can receive the first data and the first identification information from the third network element 1033 via the first bearer and send the first data and the first identification information to the first network element 1031.

[0300] In some embodiments, the first data may include IMS data. In this case, the second network element 1032 can receive the first data from the third network element 1033 via the second bearer and send the first data to the first network element 1031. In some embodiments, the second identification information can be transmitted together with the first data. For example, the second network element 1032 can receive the first data and the second identification information from the third network element 1033 via the second bearer and send the first data and the second identification information to the first network element 1031.

[0301] In step S2113, the first network element 1031 processes the first data.

[0302] In some embodiments, the first network element 1031 may process the received first data. The processing of the first data by the first network element 1031 may include at least one of the following: integrity protection and encryption.

[0303] In some embodiments, the first network element 1031 may encrypt the first data and then perform integrity protection on the encrypted first data.

[0304] In step S2114, the first network element 1031 sends the first information to the access network device 102.

[0305] In some embodiments, the first network element 1031 can send first information. In some embodiments, the first information can be sent by the first network element 1031, but is not limited to this, and can also be sent by other entities.

[0306] In some embodiments, the access network device 102 may receive the first information. In some embodiments, the first information may be received by the access network device 102, but is not limited thereto, and may also be received by other entities.

[0307] In some embodiments, the first information may include first data and first identification information or second identification information.

[0308] In some embodiments, step S2114 may include: the first network element 1031 determining that the first information includes first identification information or second identification information.

[0309] In some embodiments, the first data may be IMS service data. In some embodiments, the first data may be IMS signaling or IMS data. In one example, the first data may be IMS signaling, in which case the first information may include first identification information. In one example, the first data may be IMS data, in which case the first information may include second identification information.

[0310] In some embodiments, the first network element 1031 receives only first data from the third network element 1033. In this case, the first network element 1031 can detect that the first data is IMS signaling or IMS data. For example, the first network element 1031 can determine that the first data is IMS signaling or IMS data based on the header of the first data packet. For example, the first network element 1031 can determine that the first data is IMS signaling or IMS data based on the payload content of the first data packet. For example, the first network element 1031 can determine that the first data is IMS signaling based on the first data bearer in the first bearer, or determine that the first data is IMS data based on the first data bearer in the first bearer.

[0311] In some embodiments, the first network element 1031 may determine whether to carry first identification information or second identification information in the first information based on the bearer that receives the first data. For example, if the first network element 1031 receives the first data through a first bearer, then the first information includes the first identification information. For example, if the first network element 1031 receives the first data through a second bearer, then the first information includes the second identification information.

[0312] In some embodiments, the first network element 1031 receives first data and either first identification information or second identification information from the third network element 1033. In this case, the first network element 1031 can determine that the first data is IMS signaling based on the first identification information, or determine that the first data is IMS data based on the second identification information.

[0313] In some embodiments, the first network element 1031 may send an S1-AP downlink NAS message to the access network device 102. In some embodiments, the first information may be carried in the S1-AP downlink NAS message.

[0314] In some embodiments, the S1-AP downlink NAS message may include a NAS PDU. In some embodiments, the NAS PDU may carry first information. For example, first identification information or second identification information, and first data may be included in the NAS PDU.

[0315] In some embodiments, step S2114 may include: the first network element 1031 encapsulating the first data in a NAS PDU. In some embodiments, the NAS PDU may carry an EBI and the first data. It is understood that the first data carried in the S1-AP downlink NAS message may be encrypted downlink data.

[0316] In some embodiments, the first network element 1031 may indicate a request for acknowledgment from the access network device 102 in an S1-AP downlink NAS message.

[0317] In some embodiments, for a PDN connection of type IP PDN configured to support header compression, the first network element 1031 should use header compression before encapsulating the first data in the NAS message.

[0318] In step S2115, the first network element 1031 sends a context release command to the access network device 102.

[0319] In some embodiments, the first network element 1031 may send a context release command. In some embodiments, the context release command may be sent by the first network element 1031, but is not limited to this, and may also be sent by other entities.

[0320] In some embodiments, the access network device 102 may receive a context release command. In some embodiments, the context release command may be received by the access network device 102, but is not limited thereto, and may also be received by other entities.

[0321] In some embodiments, the context release command can be an S1UE context release command. In some embodiments, when the first data received along with the uplink receives NAS release assistance information, and the NAS release assistance information indicates that downlink data is expected, this means that the next downlink data packet after the transmission of the NAS release assistance information is the last data packet of the application layer data exchange. In this case, the first network element 1031 can send the S1UE context release command immediately after the S1-AP downlink NAS message.

[0322] In some embodiments, the context release command may instruct the RRC connection to be released immediately after the first data is successfully sent to terminal 101.

[0323] In step S2116, the access network device 102 sends the first information to the terminal 101.

[0324] In some embodiments, the access network device 102 may send first information. In some embodiments, the first information may be sent by the access network device 102, but is not limited thereto, and may also be sent by other entities.

[0325] In some embodiments, terminal 101 may receive first information. In some embodiments, the first information may be received by terminal 101, but is not limited thereto, and may also be received by other entities.

[0326] In some embodiments, access network device 102 may send the received first information to terminal 101. In some embodiments, access network device 102 may send an RRC downlink data message to terminal 101. In some embodiments, the first information may be carried in the RRC downlink data message.

[0327] In some embodiments, the RRC downlink data message may include a NAS PDU. The NAS PDU may carry first information.

[0328] In step S2117, the access network device 102 sends a NAS transmission instruction to the first network element 1031.

[0329] In some embodiments, the access network device 102 may send a NAS transmission indication. In some embodiments, the NAS transmission indication may be sent by the access network device 102, but is not limited thereto, and may also be sent by other entities.

[0330] In some embodiments, the first network element 1031 may receive a NAS transmission instruction. In some embodiments, the NAS transmission instruction may be received by the first network element 1031, but is not limited thereto, and may also be received by other entities.

[0331] In some embodiments, the access network device 102 may send a NAS transmission instruction to the first network element 1031 upon request.

[0332] In step S2118, the access network device 102 determines to perform the release.

[0333] In some embodiments, in the absence of NAS PDU activity, access network device 102 may determine to perform S1 release.

[0334] In some embodiments, if there is no NAS PDU activity within a first duration, the access network device 102 may determine to perform S1 release.

[0335] In step S2119, the access network device 102 performs a release process.

[0336] In some embodiments, when it is determined that S1 release should be performed, access network device 102 or first network element 1031 may trigger the S1 release process. In this case, access network device 102 may perform the S1 release process.

[0337] The communication method of this embodiment can be implemented through steps S2101 to S2119.

[0338] In some embodiments, the embodiment shown in FIG2A can be applied to a mobile-originated data transport process.

[0339] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2119. For example, step S2102 may be implemented as a standalone embodiment. For example, step S2103 may be implemented as a standalone embodiment. For example, step S2104 may be implemented as a standalone embodiment. For example, step S2105 may be implemented as a standalone embodiment. For example, step S2113 may be implemented as a standalone embodiment. For example, step S2115 may be implemented as a standalone embodiment. For example, a combination of steps S2102 and S2103 may be implemented as a standalone embodiment. For example, a combination of steps S2103 and S2104 may be implemented as a standalone embodiment. For example, a combination of steps S2104 and S2105 may be implemented as a standalone embodiment. For example, a combination of steps S2114 and S2116 may be implemented as a standalone embodiment. For example, a combination of steps S2103, S2104, and S2105 may be implemented as a standalone embodiment. For example, a combination of steps S2103, S2114, and S2116 can be implemented as an independent embodiment. It should be noted that possible independent embodiments consisting of one or more steps from S2101 to S2119 are not limited thereto.

[0340] In some embodiments, steps S2101, S2103 to S2119 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2101 to S2102, S2104 to S2119 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2101 to S2103, S2105 to S2119 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2101 to S2104, S2106 to S2119 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2101 to S2113, S2115 to S2119 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2101 to S2115 and S2117 to S2119 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0341] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0342] Figure 2B is an exemplary interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. The communication method involved in this embodiment can be applied to a communication system 100. As shown in Figure 2B, the communication method of this embodiment includes steps S2201 to S2224.

[0343] In step S2201, terminal 101 sends a connection request message to the first network element 1031.

[0344] The optional implementation of step S2201 can be found in the optional implementation of step S2101 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0345] In step S2202, the first network element 1031 determines the allocation of the first bearer and the second bearer.

[0346] The optional implementation of step S2202 can be found in the optional implementation of step S2102 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0347] In step S2203, the first network element 1031 sends a connection acceptance message to the terminal 101.

[0348] The optional implementation of step S2203 can be found in the optional implementation of step S2103 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0349] In step S2204, the third network element 1033 sends the first data to the second network element 1032.

[0350] The optional implementation of step S2204 can be found in the optional implementation of step S2112 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0351] In some embodiments, the third network element 1033 can transmit the first data. In some embodiments, the first data can be transmitted by the third network element 1033, but is not limited to this, and can also be transmitted by other entities.

[0352] In some embodiments, the second network element 1032 can receive the first data. In some embodiments, the first data can be received by the second network element 1032, but is not limited thereto, and can also be received by other entities.

[0353] In some embodiments, the first data sent by the third network element 1033 to the first network element 1031 may be downlink data. In some embodiments, the first data may include IMS signaling or IMS data of IMS services.

[0354] In some embodiments, the context data of the second network element 1032 may indicate that there is no downlink user plane TEID pointing to the first network element 1031, in which case the second network element 1032 cannot send the first data to the first network element 1031. In this case, the received first data can be cached in the second network element 1032. Furthermore, the second network element 1032 can determine the first network element 1031 used to provide services to the terminal 101 targeted by the first data.

[0355] In step S2205, the second network element 1032 sends a notification message to the first network element 1031.

[0356] In some embodiments, the second network element 1032 can send a notification message. In some embodiments, the notification message can be sent by the second network element 1032, but is not limited to this; it can also be sent by other entities.

[0357] In some embodiments, the first network element 1031 can receive notification messages. In some embodiments, the notification message can be received by the first network element 1031, but is not limited thereto; it can also be received by other entities.

[0358] In some embodiments, while or after the second network element 1032 caches the first data, the second network element 1032 may send a notification message. This notification message indicates the presence of downlink first data. In some embodiments, the notification message may be a downlink data notification message.

[0359] In some embodiments, in response to a notification message, the first network element 1031 may send an acknowledgment message to the second network element 1032. In some embodiments, the acknowledgment message may be a downlink data notification acknowledgment message.

[0360] In step S2206, the first network element 1031 sends a paging message to the access network device 102.

[0361] In some embodiments, the first network element 1031 can send a paging message. In some embodiments, the paging message can be sent by the first network element 1031, but is not limited to this; it can also be sent by other entities.

[0362] In some embodiments, the access network device 102 may receive paging messages. In some embodiments, the paging message may be received by the access network device 102, but is not limited thereto, and may also be received by other entities.

[0363] In some embodiments, if a terminal 101 is registered in the first network element 1031, the terminal 101 can be considered reachable. In this case, the first network element 1031 can send a paging message to the access network device 102 to page the terminal 101.

[0364] In step S2207, the access network device 102 sends a paging message to the terminal 101.

[0365] In some embodiments, the access network device 102 may send a paging message. In some embodiments, the paging message may be sent by the access network device 102, but is not limited thereto, and may also be sent by other entities.

[0366] In some embodiments, terminal 101 may receive paging messages. In some embodiments, paging messages may be received by terminal 101, but are not limited thereto, and may also be received by other entities.

[0367] In some embodiments, upon receiving a paging message from the first network element 1031, the access network device 102 may send a paging message to the terminal 101 to page the terminal 101.

[0368] In step S2208, terminal 101 initiates RRC connection establishment.

[0369] In some embodiments, upon receiving a paging message, terminal 101 may send an RRC connection request message. In some embodiments, the RRC connection request message may include a Control Plane Service Request (NAS) message.

[0370] In step S2209, the access network device 102 sends the S1-AP initial UE message to the first network element 1031.

[0371] In some embodiments, the access network device 102 may send an S1-AP initial UE message. In some embodiments, the access network device 102 may carry a Control Plane Service Request (NAS) message in the S1-AP initial UE message and send it to the first network element 1031.

[0372] In some embodiments, when using control plane CIoT PES optimization, the first network element 1031 will not trigger the establishment of a data radio bearer (DRB) based on the control plane service request NAS message. Meanwhile, the first network element 1031 can transmit the first data.

[0373] In some embodiments, the access network device 102 may obtain the QoS configuration negotiated by EPS from the first network element 1031 based on configuration information. In some embodiments, the access network device 102 may receive the QoS configuration sent by the first network element 1031.

[0374] In some embodiments, the access network device 102 can apply different priorities to requests from different terminals. Thus, requests from different terminals can have different priorities.

[0375] In step S2210, the first network element 1031 sends a modify bearer request message to the second network element 1032.

[0376] The optional implementation of step S2210 can be found in the optional implementation of step S2107 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0377] In step S2211, the second network element 1032 sends a modify bearer request message to the third network element 1033.

[0378] The optional implementation of step S2211 can be found in the optional implementation of step S2108 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0379] In step S2212, the third network element 1033 sends a modified bearer response message to the second network element 1032.

[0380] The optional implementation of step S2212 can be found in the optional implementation of step S2109 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0381] In step S2213, the second network element 1032 sends a modified bearer response message to the first network element 1031.

[0382] The optional implementation of step S2213 can be found in the optional implementation of step S2110 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0383] In step S2214, the second network element 1032 sends the first data to the first network element 1031.

[0384] The optional implementation of step S2214 can be found in the optional implementation of step S2112 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0385] In some embodiments, the second network element 1032 can transmit the first data. In some embodiments, the first data can be transmitted by the second network element 1032, but is not limited thereto, and can also be transmitted by other entities.

[0386] In some embodiments, the first network element 1031 can receive the first data. In some embodiments, the first data can be received by the first network element 1031, but is not limited thereto, and can also be received by other entities.

[0387] In some embodiments, when there is a bearer between the first network element 1031 and the second network element 1032, the second network element 1032 can directly send the first data from the third network element 1033 to the first network element 1031.

[0388] In some embodiments, if there is no bearer between the first network element 1031 and the second network element 1032, the second network element 1032 may first cache the first data. Then, a bearer is established through the above steps S2205 to S2213, and the cached first data is sent to the first network element 1031 through the established bearer.

[0389] In step S2215, the first network element 1031 processes the first data.

[0390] The optional implementation of step S2215 can be found in the optional implementation of step S2113 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0391] In step S2216, the first network element 1031 sends the first information to the access network device 102.

[0392] The optional implementation of step S2216 can be found in the optional implementation of step S2114 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0393] In some embodiments, the first information may include first data and first identification information or second identification information.

[0394] In some embodiments, step S2216 may include: the first network element 1031 determining that the first information includes first identification information or second identification information.

[0395] In some embodiments, the first network element 1031 can determine whether the first data is IMS signaling or IMS data based on the header of the first data packet. In some embodiments, the first network element 1031 can determine whether the first data is IMS signaling or IMS data based on the payload content of the first data.

[0396] In step S2217, the access network device 102 sends the first information to the terminal 101.

[0397] The optional implementation of step S2217 can be found in the optional implementation of step S2116 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0398] In step S2218, the access network device 102 sends a NAS transmission instruction to the first network element 1031.

[0399] The optional implementation of step S2218 can be found in the optional implementation of step S2117 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0400] In step S2219, terminal 101 sends first information to access network device 102.

[0401] The optional implementation of step S2219 can be found in the optional implementation of step S2104 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0402] In some embodiments, terminal 101 may send an RRC uplink data message to access network device 102. In some embodiments, first information may be carried in the RRC uplink data message.

[0403] In step S2220, the access network device 102 sends the first information to the first network element 1031.

[0404] The optional implementation of step S2220 can be found in the optional implementation of step S2105 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0405] In step S2221, the first network element 1031 processes the first data.

[0406] The optional implementation of step S2221 can be found in the optional implementation of step S2106 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0407] In step S2222, the first network element 1031 sends the first data to the third network element 1033.

[0408] The optional implementation of step S2222 can be found in the optional implementation of step S2111 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0409] In step S2223, the access network device 102 determines to perform the release.

[0410] The optional implementation of step S2223 can be found in the optional implementation of step S2118 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0411] In step S2224, the access network device 102 performs a release process.

[0412] The optional implementation of step S2224 can be found in the optional implementation of step S2119 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0413] The communication method of this embodiment can be implemented through steps S2201 to S2224.

[0414] In some embodiments, the embodiment shown in FIG2B can be applied to a mobile terminated data transport process.

[0415] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2224. For example, step S2202 may be implemented as a standalone embodiment. For example, step S2203 may be implemented as a standalone embodiment. For example, step S2214 may be implemented as a standalone embodiment. Step S2216 may be implemented as a standalone embodiment. For example, step S2217 may be implemented as a standalone embodiment. For example, step S2219 may be implemented as a standalone embodiment. For example, step S2220 may be implemented as a standalone embodiment. For example, step S2222 may be implemented as a standalone embodiment. For example, step S2202 and S2203 may be implemented as a standalone embodiment. For example, step S2202 and S2214 may be implemented as a standalone embodiment. For example, step S2202 and S2216 may be implemented as a standalone embodiment. For example, step S2216 and S2217 may be implemented as a standalone embodiment. For example, a combination of steps S2202 and S2219 can be implemented as an independent embodiment. For example, a combination of steps S2219 and S2220 can be implemented as an independent embodiment. For example, a combination of steps S2202, S2216, and S2217 can be implemented as an independent embodiment. For example, a combination of steps S2202, S2203, S2219, and S2220 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from S2201 to S2224 are not limited thereto.

[0416] In some embodiments, steps S2201, S2203 to S2224 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2201 to S2202, S2204 to S2224 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2201 to S2213, S2215 to S2224 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2201 to S2215, S2217 to S2224 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2201 to S2216, S2218 to S2224 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2201 to S2218 and S2220 to S2224 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2201 to S2219 and S2221 to S2224 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0417] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0418] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0419] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0420] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0421] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0422] In some embodiments, terms such as "certain", "preset", "default", "set", "indicated", "a certain", "any", and "first" can be used interchangeably. "Certain A", "preset A", "default A", "set A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0423] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0424] In some embodiments, if the arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another subject via other subjects, or it can be interpreted as the information being sent from one subject to another subject without passing through other subjects, for example, steps S2101, S2103, S2111, S2112, S2201, S2203, and S2222.

[0425] Figure 3A is an exemplary interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. As shown in Figure 3A, the method includes steps S3101 to S3107.

[0426] In step S3101, the first network element 1031 determines the allocation of the first bearer and the second bearer.

[0427] The optional implementation of step S3101 can be found in the optional implementation of step S2102 in Figure 2A, step S2202 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0428] In step S3102, the first network element 1031 sends the second information.

[0429] The optional implementation of step S3102 can be found in the optional implementation of step S2103 in Figure 2A, step S2203 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0430] In some embodiments, the second information may include first identification information and second identification information.

[0431] In some embodiments, the second information may be sent to terminal 101 and / or access network device 102.

[0432] In step S3103, terminal 101 sends first information to access network device 102.

[0433] The optional implementation of step S3103 can be found in the optional implementation of step S2104 in Figure 2A, step S2219 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0434] In some embodiments, the first information may include first data and first identification information or second identification information.

[0435] In step S3104, the access network device 102 sends the first information to the first network element 1031.

[0436] The optional implementation of step S3104 can be found in the optional implementation of step S2105 in Figure 2A, step S2220 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0437] In step S3105, the first network element 1031 establishes or modifies the bearer.

[0438] The optional implementation of step S3105 can be found in the optional implementation of step S2107 in Figure 2A, step S2210 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0439] In some embodiments, the first network element 1031 may establish or modify a first bearer. In some embodiments, the first bearer may include a first S11-U bearer.

[0440] In some embodiments, the first network element 1031 may establish or modify a second bearer. In some embodiments, the second bearer may include a second S11-U bearer.

[0441] In step S3106, the first network element 1031 sends the first data to the second network element 1032.

[0442] The optional implementations of step S3106 can be found in the optional implementations of step S2111 in Figure 2A, step S2222 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0443] In some embodiments, if the first information includes first identification information, then the first data is carried in the first S11-U carrier indicated by the first identification information.

[0444] In some embodiments, if the first information includes second identification information, then the first data is carried in the second S11-U carrier indicated by the second identification information.

[0445] In some embodiments, the first data may be carried in a first message and sent by the first network element 1031 to the second network element 1032. It is understood that the first message may be any message sent by the first network element 1031 to the second network element 1032, and this disclosure does not specifically limit it.

[0446] In step S3107, the second network element 1032 sends the first data to the third network element 1033.

[0447] The optional implementation of step S3107 can be found in the optional implementation of step S2111 in Figure 2A, step S2222 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0448] In some embodiments, the first data may be carried in a fourth message and sent by the second network element 1032 to the third network element 1033. It is understood that the fourth message may be any message sent by the second network element 1032 to the third network element 1033, and this disclosure does not specifically limit it.

[0449] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0450] Figure 3B is an exemplary interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. As shown in Figure 3B, the method includes steps S3201 to S3207.

[0451] In step S3201, the first network element 1031 determines the allocation of the first bearer and the second bearer.

[0452] The optional implementation of step S3201 can be found in the optional implementation of step S2102 in Figure 2A, step S2202 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0453] In step S3202, the first network element 1031 sends the second information.

[0454] The optional implementation of step S3202 can be found in the optional implementation of step S2103 in Figure 2A, step S2203 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0455] In some embodiments, the second information may include first identification information and second identification information.

[0456] In some embodiments, the second information may be sent to terminal 101 and / or access network device 102.

[0457] In step S3203, the first network element 1031 establishes or modifies the bearer.

[0458] The optional implementation of step S3203 can be found in the optional implementation of step S2107 in Figure 2A, step S2210 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0459] In some embodiments, the first network element 1031 may establish or modify a first bearer. In some embodiments, the first bearer may include a first S11-U bearer.

[0460] In some embodiments, the first network element 1031 may establish or modify a second bearer. In some embodiments, the second bearer may include a second S11-U bearer.

[0461] In step S3204, the third network element 1033 sends the first data to the second network element 1032.

[0462] Optional implementations of step S3204 can be found in step S2112 of Figure 2A, optional implementations of step S2204 of Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0463] In some embodiments, the first data may be carried in a third message and sent by the third network element 1033 to the second network element 1032. It is understood that the third message may be any message sent by the third network element 1033 to the second network element 1032, and this disclosure does not specifically limit it.

[0464] In step S3205, the second network element 1032 sends the first data to the first network element 1031.

[0465] The optional implementation of step S3205 can be found in the optional implementation of step S2112 in Figure 2A, step S2214 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0466] In some embodiments, the first data may be carried in a second message and sent by the second network element 1032 to the first network element 1031. It is understood that the second message may be any message sent by the second network element 1032 to the first network element 1031, and this disclosure does not specifically limit it.

[0467] In step S3206, the first network element 1031 sends the first information to the access network device 102.

[0468] The optional implementation of step S3206 can be found in the optional implementation of step S2114 in Figure 2A, step S2216 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0469] In some embodiments, the first information may include first data and first identification information or second identification information.

[0470] In step S3207, the access network device 102 sends the first information to the terminal 101.

[0471] The optional implementation of step S3207 can be found in the optional implementation of step S2116 in Figure 2A, step S2217 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0472] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0473] Figure 4A is an exemplary interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. As shown in Figure 4A, the method includes steps S4101 and S4102.

[0474] In step S4101, the first network element 1031 determines the allocation of the first bearer and the second bearer.

[0475] The optional implementation of step S4101 can be found in the optional implementation of step S2102 in Figure 2A, step S2202 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0476] In step S4102, the first network element 1031 and the terminal 101 exchange first information.

[0477] The optional implementations of step S4102 can be found in the optional implementations of steps S2104, S2105, S2114, and S2116 in Figure 2A, steps S2216, S2217, S2219, and S2220 in Figure 2B, as well as other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0478] In some embodiments, step S4102 may include: the first network element 1031 sending first information to the terminal 101.

[0479] In some embodiments, step S4102 may include: terminal 101 sending first information to first network element 1031.

[0480] In some embodiments, the first information may include first data and first identification information or second identification information.

[0481] In step S4103, the first network element 1031 and the second network element 1032 interact with the first data.

[0482] The optional implementations of step S4103 can be found in the optional implementations of steps S2111 and S2112 in Figure 2A, steps S2214 and S2222 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0483] In some embodiments, step S4103 may include: the first network element 1031 sending first data to the second network element 1032. In some embodiments, the first network element 1031 may also send first identification information or second identification information to the second network element 1032.

[0484] In some embodiments, step S4103 may include: the second network element 1032 sending first data to the first network element 1031. In some embodiments, the second network element 1032 may also send first identification information or second identification information to the first network element 1031.

[0485] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0486] Figure 4B is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. As shown in Figure 4B, the method includes step S4201.

[0487] In step S4201, the second network element 1032 and the third network element 1033 exchange the first data.

[0488] The optional implementations of step S4201 can be found in the optional implementations of steps S2111 and S2112 in Figure 2A, steps S2204 and S2222 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0489] In some embodiments, step S4201 may include: the second network element 1032 sending first data to the third network element 1033. In some embodiments, the second network element 1032 may also send first identification information or second identification information to the third network element 1033.

[0490] In some embodiments, step S4201 may include: the third network element 1033 sending first data to the second network element 1032. In some embodiments, the third network element 1033 may also send first identification information or second identification information to the second network element 1032.

[0491] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0492] In the following, the technical solutions of the embodiments of this disclosure will be described by way of specific implementation.

[0493] Figure 5A is a schematic diagram of the bearer of IMS service provided according to an embodiment of the present disclosure. As shown in Figure 5A, for example, the IMS service includes IMS signaling and IMS data. According to requirements, the bearer establishment process under NB-IoT access is extended (originally only one default bearer was supported), and multiple bearers (e.g., one default bearer and one dedicated bearer) can be established to carry IMS signaling and IMS data respectively. The corresponding S11-U bearer is also extended to allow the establishment of multiple S11-U bearers.

[0494] In some embodiments, the MME allocates a second bearer for IMS services using NB-IoT, wherein the second bearer is a dedicated bearer, different from the first bearer, which is the default bearer, and the first and second bearers are respectively represented by bearer identifiers.

[0495] In some embodiments, the MME allocates a second bearer when both the UE and the network support using NB-IoT to carry out IMS services.

[0496] In some embodiments, after receiving a dedicated bearer establishment request from a second network element (S-GW or PGW), the MME establishes a second bearer, wherein the second network element receives a triggering dedicated bearer establishment request from a third network element (PCRF) to trigger a strategy for establishing a dedicated bearer.

[0497] In some embodiments, the MME also allocates a third bearer for the use of NB-IoT services, wherein the third bearer is a dedicated bearer, different from the second bearer, and is identified by a third bearer identifier.

[0498] In some embodiments, the MME allocates a first S11-U bearer for IMS services using NB-IoT, wherein the first S11-U bearer corresponds to a first default bearer and is identified by a first S11-U bearer identifier.

[0499] In some embodiments, the MME allocates a second S11-U bearer for IMS services using NB-IoT, wherein the second S11-U bearer corresponds to a second dedicated bearer and is identified by a second S11-U bearer identifier.

[0500] In some embodiments, when both the UE and the network support using NB-IoT to carry out IMS services, the MME allocates a first S11-U bearer / a second S11-U bearer.

[0501] In some embodiments, IMS signaling and IMS data of IMS services are transmitted using different bearers, i.e., IMS signaling uses a first bearer and IMS data uses a second bearer; or IMS signaling uses a second bearer and IMS data uses a third bearer.

[0502] In some embodiments, IMS signaling and IMS data of IMS services are transmitted using different S11-U bearers, i.e., IMS signaling uses a first S11-U bearer and IMS data uses a second S11-U bearer; or IMS signaling uses a second bearer and IMS data uses a third bearer.

[0503] In some embodiments, when the UE sends uplink signaling, it includes IMS signaling or IMS data and the corresponding bearer identifier (first / second / third bearer identifier).

[0504] In some embodiments, when the MME receives uplink signaling, it places the IMS signaling or IMS data on different bearers based on the bearer identifier.

[0505] In some embodiments, when the MME receives uplink signaling, it places the IMS signaling or IMS data in different S11-U bearers according to the correspondence between the bearer identifier and the S11-U bearer identifier.

[0506] In some embodiments, when the PGW sends downlink IMS signaling or IMS data, it places the IMS signaling or IMS data on different bearers (first / second / third bearer) and sends it to the SGW.

[0507] In some embodiments, the SGW places IMS signaling or IMS data from different bearers on the same or different S11-U bearers and sends them to the MME.

[0508] In some embodiments, the MME sends IMS signaling or IMS data and the corresponding bearer identifier to the UE via downlink signaling.

[0509] Figure 5B is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure. The communication method in Figure 5B includes steps S5101 to S5118.

[0510] In step S5101, a PDN connection should be established for the IMS voice service before starting the service. The UE uses the APN corresponding to the IMS service to establish the PDN connection. The PDN connection process can be implemented during the attach process or as a separate process. The UE sends a PDN connection request to the MME to indicate that the UE supports IMS voice via NB-IoT.

[0511] In step S5102, if the MME determines that the network (i.e., the first network) supports IMS voice over NB-IoT, and control plane CIoT EPS optimization is used to support IMS voice services, then to provide different processing for IMS signaling and IMS data (e.g., providing different QoS for IMS signaling and IMS data), the PDN connection for IMS services may include two bearers: a default bearer and a dedicated bearer. The default bearer is identified by EPS bearer identifier 1 (EBI-1) and is used to carry IMS signaling. The dedicated bearer is identified by EBI-2 and is used to carry IMS data. EBI-1 and EBI-2, allocated by the MME, are used to receive messages and provide them to the UE through the PDN connection.

[0512] In step S5103, the UE establishes an RRC connection and, as part of it, sends an integrity-protected NAS PDU. The NAS PDU carries EBI-1 and encrypted IMS signaling. For PDN connections configured to support header compression of the IP PDN type, the UE should apply header compression before encapsulating the data in the NAS message. The UE may also indicate expected downlink data transmission in the NAS release auxiliary information within the NAS PDU.

[0513] Step S5104 includes steps S5104a and S5104b.

[0514] In some embodiments, in step S5104a, the eNodeB can obtain the EPS-negotiated QoS configuration from the MME based on its configuration. Before triggering step S5104b, the eNodeB can apply prioritization among requests from different UEs.

[0515] In some embodiments, in step S5104b, the NAS PDU sent in step S5103 can be relayed to the MME by the eNodeB via the S1-AP Initial UE message.

[0516] In step S5105, the MME verifies the integrity of the incoming NAS PDU and decrypts the data in the NAS PDU. When ROHC is configured for use, if header compression is applied to the PDN connection, the MME should decompress the IP header.

[0517] In step S5106, based on EBI-1, if the S11-U connection is not established, the MME sends a Modify Bearer Request message (MME address, MME DL TEID, RAT type, S11-U bearer identifier 1) to establish S11-U bearer 1 (i.e., the first S11-U bearer) corresponding to EBI-1. The SGW can then send downlink data to the UE. The MME should indicate the S11-U tunnel for NAS user data and send its own S11-U IP address and MME DL TEID for downlink data forwarding by the SGW. In some embodiments, for IMS data transmission, S11-U bearer 2 (i.e., the second S11-U bearer) corresponding to EBI-2 can be established.

[0518] In step S5107, the SGW should send a Modify Bearer Request message (RAT type) to the PDN GW (i.e., the third network element).

[0519] In step S5108, the PGW sends a modified bearer response to the SGW.

[0520] In step S5109, the SGW should return a Modify Bearer response (using the SGW address and TEID for uplink traffic) to the MME as a response to the Modify Bearer Request message. The SGW address and SGW TEID for the S11-U user plane are used by the MME to forward uplink data to the SGW. In this step, two EPS bearers are established for IMS services: EPS bearer 1 (i.e., the first bearer) and EPS bearer 2 (i.e., the second bearer).

[0521] In step S5110, the MME sends uplink data (IMS signaling) to the PGW via the SGW and using S11-U bearer 1 and EPS bearer 1.

[0522] In step S5111, if downlink data is expected based on the NAS release auxiliary information from the UE in step S5103, it means that downlink data transmission may occur after uplink data transmission. The downlink data (IMS signaling) can reach the PGW, and the PGW sends the downlink data to the MME through the SGW and using EPS bearer 1.

[0523] In step S5112, the MME encrypts and protects the integrity of the downlink data (IMS signaling).

[0524] In step S5113, the downlink data (IMS signaling along with EBI-1) is encapsulated in a NAS PDU and sent to the eNodeB in an S1-AP downlink NAS message. The MME may also indicate a request for acknowledgment from the eNodeB in the S1-AP downlink NAS message. For PDN connections of the IP PDN type configured to support header compression, the MME should apply header compression before encapsulating the data in the NAS message.

[0525] In step S5114, if NAS release assistance information is received along with uplink data, and the NAS release assistance information indicates that downlink data is expected, it means that the next downlink data packet after the transmission of the NAS release assistance information is the last data packet of the application layer data exchange. Then, in this case, after the S1-AP message containing downlink data encapsulated in the NAS PDU, the MME can immediately send an S1UE context release command to instruct the eNodeB to release the RRC connection immediately after successfully sending the data to the UE.

[0526] In step S5115, the eNodeB sends an RRC downlink data message, which includes downlink data (IMS signaling) encapsulated in a NAS PDU. If, in step S5114, the S1-AP with the NASDATA PDU carrying IMS signaling is followed by an S1UE context release command, then step S5118 is completed immediately after the eNodeB completes the downlink data transmission of the NAS PDU to the UE and the confirmation to the MME in step S16 is completed, and there is no need to proceed to step S5117. If header compression is applied to the PDN, the UE can perform header decompression to reconstruct the IP header.

[0527] In step S5116, the eNodeB sends a NAS delivery indication to the MME upon request. If the eNodeB reports a failed delivery via an S1-AP NAS non-delivery indication, the MME should wait for a period of time until the UE may change cells and re-establish contact with the MME; in this way, the MME should resend the downlink S1-AP message to the eNodeB.

[0528] In step S5117, if there is no NAS PDU activity for a period of time, the eNodeB begins the S1 release in step S5118.

[0529] In step S5118, the S1 release process is triggered by the eNodeB or MME.

[0530] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0531] Figure 5C is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure. The communication method in Figure 5C includes steps S5201 to S5223.

[0532] In step S5201, a PDN connection should be established for the IMS voice service before starting the service. The UE uses the APN corresponding to the IMS service to establish the PDN connection. The PDN connection process can be implemented during the attach process or as a separate process. The UE sends a PDN connection request to the MME to indicate that the UE supports IMS voice via NB-IoT.

[0533] In step S5202, if the MME determines that the network supports IMS voice over NB-IoT, and control plane CIoT EPS optimization is used to support IMS voice services, then to provide different processing for IMS signaling and IMS data (e.g., providing different QoS for IMS signaling and IMS data), the PDN connection for IMS services may include two bearers: a default bearer and a dedicated bearer. The default bearer is identified by EPS bearer identifier 1 (EBI-1) and is used to carry IMS signaling. The dedicated bearer is identified by EBI-2 and is used to carry IMS data. EBI-1 and EBI-2, allocated by the MME, are used to receive messages and provide them to the UE through the PDN connection.

[0534] In step S5203, when the SGW receives downlink data (IMS signaling) for the UE, if the SGW context data indicates that there is no downlink user plane TEID pointing to the MME, the SGW buffers the downlink data packet and identifies the MME providing services to the UE.

[0535] In step S5204, if the SGW cached data in step S5203, the SGW sends a downlink data notification message to the MME, which has a control plane connection with the given UE. The MME sends a downlink data notification confirmation message to the SGW in response.

[0536] In step S5205, if the UE is registered with the MME and is considered reachable, the MME sends a paging message to the eNodeB.

[0537] In step S5206, if the eNodeB receives a paging message from the MME, the eNodeB will paging the UE.

[0538] In step S5207, upon receiving a paging indication, the UE sends a Control Plane Service Request (NAS) message via an RRC connection request (step S5207) and an S1-AP initialization message (step S5208b). In the context of Control Plane CIoT EPS optimization applications, the NAS message does not trigger the establishment of a data radio bearer by the MME, and the MME can immediately send the downlink data received via the NAS PDU to the eNodeB.

[0539] Step S5208 includes steps S5208a and S5208b.

[0540] In some embodiments, in step S5208a, the eNodeB can obtain the EPS-negotiated QoS configuration from the MME based on its configuration. Before triggering step S5208b, the eNodeB can apply priorities among requests from different UEs.

[0541] In some embodiments, in step S5208b, the eNodeB sends a Control Plane Service Request (NAS) message to the MME via the S1-AP initial message.

[0542] In step S5209, based on EBI-1 and EBI-2, if the S11-U connection is not established, the MME sends a Modify Bearer Request message (MME address, MME DL TEID, RAT type, S11-U bearer identifier) ​​to establish S11-U bearer 1 corresponding to each EPS bearer. The MME should indicate the S11-U tunnel for NAS user data and send its own S11-U IP address and MME DL TEID for downlink data forwarding by the SGW.

[0543] In this step, the establishment of S11-U bearer 1 corresponds to EPS bearer 1 and is used to carry IMS signaling. The establishment of S11-U bearer 2 corresponds to EPS bearer 2 and is used to carry IMS data.

[0544] In step S5210, the SGW should send a Modify Bearer Request message (RAT type) to the PDN GW.

[0545] In step S5211, the PGW sends a modified bearer response to the SGW.

[0546] In step S5212, the SGW should return a Modify Bearer response (using the SGW address and TEID for uplink traffic) to the MME as a response to the Modify Bearer Request message. The SGW address and SGW TEID for the S11-U user plane are used by the MME to forward uplink data to the SGW.

[0547] In step S5213, (if S11-U is not established) the cached downlink data is sent from the SGW to the MME.

[0548] In step S5214, the MME encrypts and protects the integrity of the downlink data (IMS signaling).

[0549] In step S5215, the MME detects that the downlink data is IMS signaling. The downlink data (IMS signaling along with EBI-1) is encapsulated in a NAS PDU and sent to the eNodeB in an S1-AP downlink NAS message. The MME may also indicate a request for acknowledgment from the eNodeB in the S1-AP downlink NAS message. For PDN connections configured to support header compression of the IP PDN type, the MME should apply header compression before encapsulating the data in the NAS message.

[0550] In step S5216, the eNodeB sends an RRC downlink data message, which includes downlink data (IMS signaling along with EBI-1) encapsulated in a NAS PDU. This is interpreted by the UE as an implicit acknowledgment of the service request message sent in step S5207. If header compression is applied to the PDN, the UE can perform header decompression to reconstruct the IP header.

[0551] In step S5217, the eNodeB sends a NAS delivery indication to the MME upon request. If the eNodeB reports a failed delivery via the S1-AP NAS non-delivery indication, the MME should wait for a period of time until the UE may change cells and re-establish contact with the MME; in this way, the MME should resend the downlink S1-AP message to the eNodeB.

[0552] In step S5218, more uplink and downlink data can be transmitted via the NAS PDU. If IMS voice data exchange begins, this step shows uplink data transmission using an uplink RRC message encapsulating the NAS PDU with IMS data, and the EBI-2 can be included in the uplink RRC message. Based on this, different processing can be provided at the MME, SGW, and PGW. For PDN connections of the IP PDN type configured to support header compression, the UE should apply header compression before encapsulating the IMS data in the NAS message.

[0553] In step S5219, the NAS PDU containing IMS data, along with EBI-2, is sent to the MME in the uplink S1-AP message.

[0554] In step S5220, data integrity is verified and decrypted. If header compression is applied to the PDN, the MME should perform header decompression to reconstruct the IP header.

[0555] In step S5221, the MME sends uplink data to the PGW via the SGW and using S11-U bearer 2 and EPS bearer 2.

[0556] In step S5222, if there is no NAS activity for a period of time, the eNodeB detects inactivity and executes step S5223.

[0557] In step S5223, the eNodeB begins the S1 release process triggered by the eNodeB.

[0558] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0559] This disclosure also proposes apparatus (also referred to as communication equipment, etc.) for implementing any of the above methods. For example, this disclosure proposes an apparatus including units or modules for implementing the steps performed by the first network element in any of the above methods. For example, this disclosure proposes another apparatus including units or modules for implementing the steps performed by the second network element in any of the above methods. For example, this disclosure proposes another apparatus including units or modules for implementing the steps performed by the third network element in any of the above methods. For example, this disclosure proposes another apparatus including units or modules for implementing the steps performed by the terminal in any of the above methods.

[0560] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0561] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a central processing unit, microprocessor, graphics processing unit (GPU) (which can be understood as a type of microprocessor), or digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), tensor processing unit (TPU), deep learning processing unit (DPU), etc.

[0562] Figure 6 is an exemplary schematic diagram of a communication device provided according to an embodiment of the present disclosure. As shown in Figure 6, the communication device 600 may include at least one of the following: a transceiver module 601 and a processing module 602.

[0563] In some embodiments, the communication device 600 may be a first network element. In some embodiments, the processing module 602 may be configured to: determine to allocate a first bearer and a second bearer for a first service, wherein the first service is an IMS service accessed using NB-IoT; wherein the first bearer is used to carry the IMS signaling of the first service, and the second bearer is used to carry the IMS data of the first service. Optionally, the transceiver module 601 can be configured to perform at least one of the communication steps such as sending and / or receiving performed by the first network element in any of the above methods (e.g., steps S2101, S2103, S2105, S2107, S2110, S2111, S2112, S2114, S2115, S2117, S2201, S2203, S2205, S2206, S2209, S2210, S2213, S2214, S2216, S2218, S2220, S2222, but not limited thereto), which will not be elaborated here. Optionally, the processing module 602 may be configured to perform at least one of the steps performed by the first network element in any of the above methods, other than communication steps such as sending and receiving (e.g., steps S2102, S2106, S2113, S2202, S2215, S2221, but not limited thereto).

[0564] In some embodiments, the communication device 600 may be a second network element. In some embodiments, the processing module 602 may be configured to interact with the first network element for IMS signaling or IMS data of a first service, wherein the first service is an IMS service accessed using NB-IoT, the IMS signaling is carried in a first bearer, and the IMS data is carried in a second bearer. Optionally, the transceiver module 601 may be configured to perform at least one of the communication steps (e.g., steps S2107, S2108, S2109, S2110, S2111, S2112, S2204, S2205, S2210, S2211, S2212, S2213, S2214, S2222, but not limited thereto) performed by the second network element in any of the above methods, which will not be elaborated here.

[0565] In some embodiments, the communication device 600 may be a third network element. In some embodiments, the processing module 602 may be configured to interact with the second network element to exchange IMS signaling or IMS data of a first service, wherein the first service is an IMS service accessed using NB-IoT, the IMS signaling is carried in a first bearer, and the IMS data is carried in a second bearer. Optionally, the transceiver module 601 may be configured to perform at least one of the communication steps (e.g., steps S2108, S2109, S2111, S2112, S2204, S2211, S2212, S2222, but not limited thereto) performed by the third network element in any of the above methods, which will not be elaborated here.

[0566] In some embodiments, the communication device 600 may be a terminal. In some embodiments, the transceiver module 601 may be configured to: interact with a first network element to exchange first information, wherein the first information includes one of the following: IMS signaling and a first identifier of a first service, IMS data of the first service and a second identifier, wherein the first service is an IMS service accessed using NB-IoT, the first identifier information indicates a first bearer, and the second identifier information indicates a second bearer; wherein the first bearer is used to carry the IMS signaling of the first service, and the second bearer is used to carry the IMS data of the first service. Optionally, the transceiver module 601 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the terminal in any of the above methods (e.g., steps S2101, S2103, S2104, S2116, S2201, S2203, S2207, S2208, S2217, S2219, but not limited thereto), which will not be elaborated here.

[0567] In some embodiments, the communication device shown in FIG6 can be implemented as a communication equipment.

[0568] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module. The transmitting and receiving modules may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0569] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0570] Figure 7A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. The communication device 7100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 7100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0571] As shown in Figure 7A, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal device, terminal device chip, DU or CU, etc.), execute programs, and process program data. Optionally, the communication device 7100 can be used to execute any of the above methods. Optionally, one or more processors 7101 can be used to invoke instructions to cause the communication device 7100 to execute any of the above methods.

[0572] In some embodiments, the communication device 7100 further includes one or more transceivers 7102. When the communication device 7100 includes one or more transceivers 7102, the transceivers 7102 perform communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2103, S2104, S2105, S2107, S2108, S2109, S2110, S2111, S2112, S2114, S2115, S2116, S2117, S2119, S2201, S2203, S2204, S2205, S2206, S2...). At least one of S2207, S2208, S2209, S2210, S2211, S2212, S2213, S2214, S2216, S2217, S2218, S2219, S2220, S2222, S2224 (but not limited thereto) is performed by the processor 7101, while at least one of other steps (e.g., steps S2102, S2106, S2113, S2118, S2202, S2215, S2221, S2223, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be used interchangeably; terms such as transmitter, transmitting unit, transmitter, and transmitting circuit can be used interchangeably; and terms such as receiver, receiving unit, receiver, and receiving circuit can be used interchangeably.

[0573] In some embodiments, the communication device 7100 further includes one or more memories 7103 for storing data. Optionally, all or part of the memories 7103 may be located outside the communication device 7100. In optional embodiments, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuits 7104 are connected to the memories 7103 and can be used to receive data from the memories 7103 or other devices, and to send data to the memories 7103 or other devices. For example, the interface circuits 7104 can read data stored in the memories 7103 and send the data to the processor 7101.

[0574] The communication device 7100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 7100 described in this disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0575] Figure 7B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. For cases where the communication device 7100 can be a chip or a chip system, please refer to the schematic diagram of the chip 7200 shown in Figure 7B, but it is not limited thereto.

[0576] Chip 7200 includes one or more processors 7201. Chip 7200 is used to perform any of the above methods.

[0577] In some embodiments, chip 7200 further includes one or more interface circuits 7202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 7200 further includes one or more memories 7203 for storing data. Optionally, all or part of the memories 7203 may be located outside chip 7200. Optionally, interface circuit 7202 is connected to memory 7203, and interface circuit 7202 can be used to receive data from memory 7203 or other devices, and interface circuit 7202 can be used to send data to memory 7203 or other devices. For example, interface circuit 7202 can read data stored in memory 7203 and send the data to processor 7201.

[0578] In some embodiments, the interface circuit 7202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2103, S2104, S2105, S2107, S2108, S2109, S2110, S2111, S2112, S2114, S2115, S2116, S2117, S2119, S2201, S2203, S2204, S2205, S2206, S2207, S2208, S2209, S2210, S2211, S2212, S2213, S2214, S2216, S2217, S2218, S2219, S2220, S2222, S2224, but not limited thereto). The interface circuit 7202 performing the communication steps such as sending and / or receiving in the above method refers to, for example, the interface circuit 7202 performing data interaction between the processor 7201, the chip 7200, the memory 7203, or the transceiver device. In some embodiments, the processor 7201 performs at least one of other steps (e.g., steps S2102, S2106, S2113, S2118, S2202, S2215, S2221, S2223, but is not limited thereto).

[0579] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0580] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 7100, cause the communication device 7100 to perform any of the methods described above. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0581] This disclosure also proposes a program product that, when executed by a communication device 7100, causes the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0582] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method, executed by a first network element, wherein, The method includes: The first service is determined to be allocated a first bearer and a second bearer, wherein the first service is the Internet Protocol Multimedia Subsystem (IMS) service accessed using narrowband Internet of Things (NB-IoT). The first bearer is used to carry the IMS signaling of the first service, and the second bearer is used to carry the IMS data of the first service.

2. The method according to claim 1, wherein, The first bearer and the second bearer are allocated when both the terminal and the first network support the first service. The first network element is located in the first network, and the access type used by the terminal is NB-IoT.

3. The method according to claim 1 or 2, wherein, The first bearer is either a default bearer or a dedicated bearer, and the second bearer is a dedicated bearer; the first bearer and the second bearer are different.

4. The method according to any one of claims 1 to 3, wherein, The method further includes at least one of the following: According to the first policy, the first bearer is established or modified, wherein the first policy is used for the QoS requirements of the first service for the first bearer; According to the second strategy, the second bearer is established or modified, wherein the second strategy is used for the QoS requirements of the first service for the second bearer.

5. The method according to claim 4, wherein, The establishment or modification of the first bearer includes: Establish or modify a first S11-U bearer, wherein the first S11-U bearer is located between the first network element and the service gateway.

6. The method according to claim 4 or 5, wherein, The establishment or modification of the second bearer includes: Establish or modify a second S11-U bearer, wherein the second S11-U bearer is located between the first network element and the service gateway.

7. The method according to any one of claims 1 to 6, wherein, The method further includes: Receive first information sent by the terminal, wherein the first information includes one of the following: The IMS signaling and the first identifier; The IMS data and the second identifier; Wherein, the first identifier indicates the first carrier, and the second identifier indicates the second carrier.

8. The method according to claim 7, wherein, The method further includes: Send a first message to the second network element, wherein the first message carries the IMS signaling or the IMS data, the first message carrying the IMS signaling is carried in the first bearer, and the first message carrying the IMS signaling is carried in the second bearer.

9. The method according to any one of claims 1 to 6, wherein, The method further includes: Receive a second message sent by a second network element, wherein the second message carries the IMS signaling or the IMS data, the second message carrying the IMS signaling is sent by the second network element through the first bearer, the second message carrying the IMS data is sent by the second network element through the second bearer, the first bearer is indicated by a first identifier, and the second bearer is indicated by a second identifier; Send first information to the terminal, wherein the first information includes one of the following: The IMS signaling and the first identifier; The IMS data and the second identifier.

10. The method according to claim 8 or 9, wherein, The first bearer includes a first S11-U bearer, and the second bearer includes a second S11-U bearer; The IMS signaling is carried in the first S11-U bearer, and the IMS data is carried in the second S11-U bearer.

11. The method according to any one of claims 1 to 10, wherein, The method further includes: Send the first identifier and the second identifier to the terminal.

12. The method according to any one of claims 1 to 11, wherein, The first bearer and the second bearer are used for data transmission processes initiated by the terminal, and the first bearer and the second bearer are in response to the IMS signaling or the IMS data allocation from the terminal; or, The first and second bearers are used to terminate the data transmission process at the terminal, and the first and second bearers are in response to the IMS signaling or the IMS data allocation from the first network.

13. A communication method, executed by a second network element, wherein, The method includes: The interaction of Internet Protocol Multimedia Subsystem (IMS) signaling or IMS data with the first network element for the first service, wherein the first service is an IMS service accessed using Narrowband Internet of Things (NB-IoT), the IMS signaling is carried in the first bearer, and the IMS is carried in the second bearer.

14. The method according to claim 13, wherein, The first bearer and the second bearer are allocated when both the terminal and the first network support the first service. The first network element is located in the first network, and the access type used by the terminal is NB-IoT.

15. The method according to claim 13 or 14, wherein, The first bearer is either a default bearer or a dedicated bearer, and the second bearer is a dedicated bearer; the first bearer and the second bearer are different.

16. The method according to any one of claims 13 to 15, wherein, The interaction of IMS signaling or IMS data with the first network element for the first service includes: Send a second message to the first network element, wherein the second message carries the IMS signaling or the IMS data, the second message carrying the IMS signaling is carried in the first bearer, the second message carrying the IMS data is carried in the second bearer, the first bearer is indicated by a first identifier, and the second bearer is indicated by a second identifier.

17. The method according to any one of claims 13 to 15, wherein, The interaction of IMS signaling or IMS data with the first network element for the first service includes: The first message sent by the first network element is received, wherein the first message carries the IMS signaling or the IMS data, the first message carrying the IMS signaling is sent by the first network element through the first bearer, and the first message carrying the IMS data is sent by the first network element through the second bearer, the first bearer is indicated by a first identifier, and the second bearer is indicated by a second identifier.

18. The method according to any one of claims 13 to 17, wherein, The first bearer includes a first S11-U bearer located between the first network element and the second network element, and the second bearer includes a second S11-U bearer located between the first network element and the second network element; The IMS signaling is carried in the first S11-U bearer, or the IMS data is carried in the second S11-U bearer.

19. The method according to any one of claims 13 to 18, wherein, The method further includes: Interact with the third network element to exchange the IMS signaling or the IMS data.

20. The method according to any one of claims 13 to 19, wherein, The first bearer and the second bearer are used for data transmission processes initiated by the terminal, and the first bearer and the second bearer are in response to the IMS signaling or the IMS data allocation from the terminal; or, The first and second bearers are used to terminate the data transmission process at the terminal, and the first and second bearers are in response to the IMS signaling or the IMS data allocation from the first network.

21. A communication method, executed by a third network element, wherein, The method includes: The interaction between the Internet Protocol Multimedia Subsystem (IMS) signaling or IMS service and the second network element for the first service, wherein the first service is an IMS service accessed using Narrowband Internet of Things (NB-IoT), the IMS signaling is carried in the first bearer, and the IMS data is carried in the second bearer.

22. The method according to claim 21, wherein, The first bearer and the second bearer are allocated when both the terminal and the first network support the first service. The first network element is located in the first network, and the access type used by the terminal is NB-IoT.

23. The method according to claim 21 or 22, wherein, The first bearer is either a default bearer or a dedicated bearer, and the second bearer is a dedicated bearer; the first bearer and the second bearer are different.

24. The method according to any one of claims 21 to 23, wherein, The interaction of IMS signaling or IMS data with the second network element for the first service includes: A third message is sent to the second network element, wherein the third message carries the IMS signaling or the IMS data, the third message carrying the IMS signaling is carried in the first bearer, and the third message carrying the IMS data is carried in the second bearer, the first bearer is indicated by a first identifier, and the second bearer is indicated by a second identifier.

25. The method according to any one of claims 21 to 23, wherein, The interaction of IMS signaling or IMS data with the second network element for the first service includes: The system receives a fourth message sent by the second network element, wherein the fourth message carries the IMS signaling or the IMS data. The fourth message carrying the IMS signaling is sent by the second network element through the first bearer, and the fourth message carrying the IMS data is sent by the second network element through the second bearer. The first bearer is indicated by a first identifier, and the second bearer is indicated by a second identifier.

26. The method according to any one of claims 21 to 25, wherein, The first bearer and the second bearer are used for data transmission processes initiated by the terminal, and the first bearer and the second bearer are in response to the IMS signaling or the IMS data allocation from the terminal; or, The first and second bearers are used to terminate the data transmission process at the terminal, and the first and second bearers are in response to the IMS signaling or the IMS data allocation from the first network.

27. A communication method, executed by a terminal, wherein, The method includes: The interaction with the first network element involves exchanging first information, wherein the first information includes one of the following: The first service's Internet Protocol Multimedia Subsystem (IMS) signaling and first identifier; The first service is an IMS service accessed using Narrowband Internet of Things (NB-IoT), where the first identifier indicates the first bearer and the second identifier indicates the second bearer. The first bearer is used to carry the IMS signaling of the first service, and the second bearer is used to carry the IMS data of the first service.

28. The method according to claim 27, wherein, The first bearer and the second bearer are allocated when both the terminal and the first network support the first service. The first network element is located in the first network, and the access type used by the terminal is NB-IoT.

29. The method according to claim 27 or 28, wherein, The first bearer is either a default bearer or a dedicated bearer, and the second bearer is a dedicated bearer; the first bearer and the second bearer are different.

30. The method according to any one of claims 27 to 29, wherein, The method further includes: Receive the first identifier and the second identifier sent by the first network element.

31. The method according to any one of claims 27 to 30, wherein, The first bearer and the second bearer are used for the data transmission process initiated by the terminal, and the first bearer and the second bearer are in response to the IMS signaling or the IMS data allocation from the terminal; or, The first and second bearers are used to terminate the data transmission process at the terminal, and the first and second bearers are in response to the IMS signaling or the IMS data allocation from the first network.

32. A communication device, wherein, The communication device is used to perform the communication method as described in any one of claims 1 to 12, 13 to 20, 21 to 26, and 27 to 31.

33. A communication system, wherein, The communication system includes at least one of the following: a first network element, a second network element, a third network element, and a terminal; Wherein, the first network element is configured to implement the communication method as described in any one of claims 1 to 12, the second network element is configured to implement the communication method as described in any one of claims 13 to 20, the third network element is configured to implement the communication method as described in any one of claims 21 to 26, and the terminal is configured to implement the communication method as described in any one of claims 27 to 31.

34. A storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication device performs the communication method as described in any one of claims 1 to 12, 13 to 20, 21 to 26, and 27 to 31.

35. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the steps of the communication method as described in any one of claims 1 to 12, 13 to 20, 21 to 26, and 27 to 31.

Images