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: exchanging first data with a terminal, the first data corresponding to first information, and the first information comprising one of the following: first identifier information and second identifier information, the first identifier information indicating that the first data is IMS signaling, and the second identifier information indicating that the first data is IMS data. An access type used by the terminal is NB-IoT. By means of the solution of the present disclosure, the requirements of an IMS service can be met, and system performance can be enhanced.

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, Narrow Band Internet of Things (NB-IoT) has been proposed as an access technology to meet the access needs of low-power, low-cost terminals. Terminals can connect to the evolved packet core (EPC) network via 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: interacting with a terminal to exchange first data, wherein the first data corresponds to first information; wherein the first information includes one of the following: first identification information and second identification information; the first identification information indicates that the first data is IMS signaling, and the second identification information indicates that the first data is IMS data; wherein the access type used by the terminal is NB-IoT.

[0006] According to a second 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 to exchange first data, wherein the first data corresponds to first information; wherein the first information includes one of the following: first identification information and second identification information; the first identification information indicates that the first data is IMS signaling, and the second identification information indicates that the first data is IMS data; wherein the access type used by the terminal is NB-IoT.

[0007] According to a third 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 terminal. The method includes: the first network element and the terminal interacting with first data, wherein the first data corresponds to first information; wherein the first information includes one of the following: first identification information and second identification information; the first identification information indicates that the first data is IMS signaling, and the second identification information indicates that the first data is IMS data; wherein the access type used by the terminal is NB-IoT.

[0008] According to a fourth aspect of the present disclosure, a communication device is provided. This communication device is used to perform the communication method as described in the first or second aspect.

[0009] According to a fifth 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, and a terminal. The first network element is configured to perform the communication method as described in the first aspect. The terminal is configured to perform the communication method as described in the second aspect. The second network element is configured to perform the communication method as described in the third aspect.

[0010] According to a sixth 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 third aspects.

[0011] According to a seventh 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 third aspects.

[0012] According to an eighth aspect of the present disclosure, a computer program is provided. When this computer program is run on a computer, it causes the computer to perform the communication method as described in any one of the first to third aspects.

[0013] According to a ninth 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 third aspects.

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

[0015] 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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0029] In a first aspect, embodiments of this disclosure provide a communication method. The method is executed by a first network element. The method includes: interacting with a terminal to exchange first data, wherein the first data corresponds to first information; wherein the first information includes one of the following: first identification information and second identification information; the first identification information indicates that the first data is IMS signaling, and the second identification information indicates that the first data is IMS data; wherein the access type used by the terminal is NB-IoT.

[0030] In this embodiment, the first data exchanged between the first network element and the terminal can correspond to first information. The first information includes first identification information indicating that the first data is IMS signaling. The first information includes second identification information indicating that the first data is IMS data. Thus, based on whether the first information corresponding to the first data contains first identification information or second identification information, it can be determined that the first data is IMS signaling or IMS data, thereby enabling different processing of IMS signaling and IMS data, meeting the different service requirements of different types of data in IMS services, and enhancing system performance.

[0031] In conjunction with some embodiments of the first aspect, in some embodiments, interacting with the terminal to exchange first data includes: sending first data and first information.

[0032] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is used by the access network device to map the first data to an SRB; wherein, the first information includes first identification information, and the first data is mapped to a first SRB according to the first identification information; or, the first information includes second identification information, and the first data is mapped to a second SRB according to the second identification information, wherein the first SRB and the second SRB are different.

[0033] In conjunction with some embodiments of the first aspect, in some embodiments, interacting with the terminal to receive first data includes: receiving first data and first information.

[0034] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is used by the terminal to map the first data to an SRB; wherein, the first information includes first identification information, and the first data is mapped to a first SRB according to the first identification information; or, the first information includes second identification information, and the first data is mapped to a second SRB according to the second identification information, wherein the first SRB and the second SRB are different.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the first data and the first information are carried in the control plane message of the EPS.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes a field, wherein the field has a first value indicating first identification information; or, the field has a second value indicating second identification information.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes: sending first identification information and / or second identification information, wherein the first identification information and / or second identification information are sent to at least one of the following: a terminal, an access network device; wherein the first identification information and the second identification information are determined by a first network element.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the first identification information and the second identification information are determined by the first network element based on at least one of the following: the terminal and the first network's ability to support IMS services in a control plane CIoT EPS optimized manner; the terminal and the first network's ability to support IMS services through NB-IoT access; and the terminal and the first network's ability to support the establishment of multiple bearers through NB-IoT access; wherein the first network element is located in the first network.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the first identification information and the second identification information are determined when establishing a PDN connection for IMS services.

[0040] In a second 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 data, wherein the first data corresponds to first information; wherein the first information includes one of the following: first identification information and second identification information; the first identification information indicates that the first data is IMS signaling, and the second identification information indicates that the first data is IMS data; wherein the access type used by the terminal is NB-IoT.

[0041] In this embodiment, the first data exchanged between the first network element and the terminal can correspond to first information. The first information includes first identification information indicating that the first data is IMS signaling. The first information includes second identification information indicating that the first data is IMS data. Thus, based on whether the first information corresponding to the first data contains first identification information or second identification information, it can be determined that the first data is IMS signaling or IMS data, thereby enabling different processing of IMS signaling and IMS data, meeting the different service requirements of different types of data in IMS services, and enhancing system performance.

[0042] In conjunction with some embodiments of the second aspect, in some embodiments, the interaction with the first network element for first data includes: receiving first data and first information.

[0043] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is used by the access network device to map the first data to the SRB; wherein, the first information includes first identification information, and the first data is mapped to the first SRB according to the first identification information; or, the first information includes second identification information, and the first data is mapped to the second SRB according to the second identification information, wherein the first SRB and the second SRB are different.

[0044] In conjunction with some embodiments of the second aspect, in some embodiments, the interaction with the first network element for first data includes: sending first data and first information.

[0045] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is used by the terminal to map the first data to an SRB; wherein, the first information includes first identification information, and the first data is mapped to a first SRB according to the first identification information; or, the first information includes second identification information, and the first data is mapped to a second SRB according to the second identification information, wherein the first SRB and the second SRB are different.

[0046] In conjunction with some embodiments of the second aspect, in some embodiments, the first data and the first information are carried in the control plane message of the EPS.

[0047] In conjunction with some embodiments of the second aspect, in some embodiments, the first information includes a field, wherein the field has a first value indicating first identification information; or, the field has a second value indicating second identification information.

[0048] In conjunction with some embodiments of the second aspect, in some embodiments, the above method further includes: receiving first identification information and / or second identification information sent by the first network element, wherein the first identification information and the second identification information are determined by the first network element.

[0049] In conjunction with some embodiments of the second aspect, in some embodiments, the first identification information and the second identification information are determined by the first network element based on at least one of the following: the terminal and the first network's ability to support IMS services in a control plane CIoT EPS optimized manner; the terminal and the first network's ability to support IMS services through NB-IoT access; and the terminal and the first network's ability to support the establishment of multiple bearers through NB-IoT access; wherein the first network element is located in the first network.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the first identification information and the second identification information are determined when establishing a PDN connection for IMS services.

[0051] In a third 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 terminal. The method includes: the first network element and the terminal interacting with first data, wherein the first data corresponds to first information; wherein the first information includes one of the following: first identification information and second identification information; the first identification information indicates that the first data is IMS signaling, and the second identification information indicates that the first data is IMS data; wherein the access type used by the terminal is NB-IoT.

[0052] In a fourth aspect, embodiments of this disclosure provide a communication device. The communication device is a first network element. The communication device includes a transceiver module. The transceiver module is configured to interact with a terminal to exchange first data, wherein the first data corresponds to first information; wherein the first information includes one of the following: first identification information and second identification information; the first identification information indicates that the first data is IMS signaling, and the second identification information indicates that the first data is IMS data; wherein the access type used by the terminal is NB-IoT.

[0053] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is configured to send first data and first information.

[0054] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information is used by the access network device to map the first data to the SRB; wherein, the first information includes first identification information, and the first data is mapped to the first SRB according to the first identification information; or, the first information includes second identification information, and the first data is mapped to the second SRB according to the second identification information, wherein the first SRB and the second SRB are different.

[0055] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is configured to receive first data and first information.

[0056] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information is used by the terminal to map the first data to an SRB; wherein, the first information includes first identification information, and the first data is mapped to a first SRB according to the first identification information; or, the first information includes second identification information, and the first data is mapped to a second SRB according to the second identification information, wherein the first SRB and the second SRB are different.

[0057] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first data and the first information are carried in the control plane message of the EPS.

[0058] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information includes a field, wherein the field has a first value indicating first identification information; or, the field has a second value indicating second identification information.

[0059] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured to: send first identification information and / or second identification information, wherein the first identification information and / or second identification information are sent to at least one of the following: a terminal, an access network device; wherein the first identification information and the second identification information are determined by a first network element.

[0060] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first identification information and the second identification information are determined by the first network element based on at least one of the following: the terminal and the first network's ability to support IMS services in a control plane CIoT EPS optimized manner; the terminal and the first network's ability to support IMS services through NB-IoT access; and the terminal and the first network's ability to support the establishment of multiple bearers through NB-IoT access; wherein the first network element is located in the first network.

[0061] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first identification information and the second identification information are determined when establishing a PDN connection for IMS services.

[0062] In a fifth 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 data, wherein the first data corresponds to first information; wherein the first information includes one of the following: first identification information and second identification information; the first identification information indicates that the first data is IMS signaling, and the second identification information indicates that the first data is IMS data; wherein the access type used by the terminal is NB-IoT.

[0063] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module is configured to receive first data and first information.

[0064] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first information is used by the access network device to map the first data to the SRB; wherein, the first information includes first identification information, and the first data is mapped to the first SRB according to the first identification information; or, the first information includes second identification information, and the first data is mapped to the second SRB according to the second identification information, wherein the first SRB and the second SRB are different.

[0065] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module is configured to send first data and first information.

[0066] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first information is used by the terminal to map the first data to an SRB; wherein the first information includes first identification information, and the first data is mapped to a first SRB according to the first identification information; or, the first information includes second identification information, and the first data is mapped to a second SRB according to the second identification information, wherein the first SRB and the second SRB are different.

[0067] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first data and the first information are carried in the control plane message of the EPS.

[0068] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first information includes a field, wherein the field has a first value indicating first identification information; or, the field has a second value indicating second identification information.

[0069] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module is further configured to: receive first identification information and / or second identification information sent by the first network element, wherein the first identification information and the second identification information are determined by the first network element.

[0070] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first identification information and the second identification information are determined by the first network element based on at least one of the following: the terminal and the first network's ability to support IMS services in a control plane CIoT EPS optimized manner; the terminal and the first network's ability to support IMS services through NB-IoT access; and the terminal and the first network's ability to support the establishment of multiple bearers through NB-IoT access; wherein the first network element is located in the first network.

[0071] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first identification information and the second identification information are determined when establishing a PDN connection for IMS services.

[0072] In a sixth 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 third aspects and their possible implementations.

[0073] In a seventh aspect, embodiments of this disclosure provide a communication system. The communication system includes a first 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 terminal is configured to perform the communication method as described in any of the second aspect and its possible embodiments.

[0074] In an eighth 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 third aspects and their possible implementations.

[0075] In a ninth 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 third aspects and their possible embodiments.

[0076] In a tenth aspect, this disclosure provides 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 third aspects and their possible implementations.

[0077] In an eleventh 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 third aspects and their possible implementations.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0107] 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).

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

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

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

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

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

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

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

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

[0116] 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).

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

[0118] 1. IMS (IP Multimedia Subsystem)

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

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

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

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

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

[0124] (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.

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

[0126] (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.

[0127] (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.

[0128] In some embodiments, NB-IoT can be deployed as an access technology in the EPS. In this case, terminals can connect to the EPC in 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).

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

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

[0131] (1) It does not support inter-RAT mobility, i.e., switching across RATs, from NB-IoT to other access methods, or from other access methods to NB-IoT access.

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

[0133] (3) Dedicated bearers are not supported via NB-IoT. 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.

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

[0135] In some embodiments, in order to support IMS voice communication in the EPS system and enable the UE to initiate IMS services through the EPS system, the EPS may notify the UE of "Instruction to provide IMS voice support on PS session". Here, PS session may refer to a packet-switched (PS) session.

[0136] In some embodiments, if IMS voice service is supported over a PS session, 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 it can establish a voice-enabled bearer to successfully conduct IMS service over the PS session.

[0137] 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 on PS session, the UE can consider the above-mentioned instructions from EPS.

[0138] 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).

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

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

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

[0142] 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 S2118.

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

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

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

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

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

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

[0149] In some embodiments, the satellite on which the access network device 102 is deployed may have various orbit types. In some embodiments, the satellite on which the access network device 102 is deployed may be a geostationary orbit (GEO) satellite, a low earth orbit (LEO) satellite, a geosynchronous orbit (GSO) satellite, a polar satellite, or a highly elliptical orbit (HEO) satellite.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0163] In some embodiments, the APN can be associated with IMS services. In some embodiments, the APN can be used to establish a PDN connection for IMS services.

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

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

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

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

[0168] In some embodiments, the connection acceptance message may include first identification information and second identification information.

[0169] In some embodiments, the first identification information may indicate IMS signaling in an IMS service. In some embodiments, the first identification information may indicate that the associated data is IMS signaling. In some embodiments, the first identification information may be used to indicate that the data carried in the control plane message containing the first identification information is IMS signaling.

[0170] In some embodiments, the second identification information may indicate IMS data in an IMS service. In some embodiments, the second identification information may indicate that the associated data is IMS data. In some embodiments, the second identification information may be used to indicate that the data carried in the control plane message containing the first identification information is IMS data.

[0171] In some embodiments, the first identification information and the second identification information may be determined by the first network element 1031. In some embodiments, the first identification information and the second identification information may be allocated by the first network element 1031 for the data transmission of IMS services. In one example, the first network element 1031 may allocate the first identification information for the transmission of IMS signaling. In one example, the first network element 1031 may allocate the second identification information for the transmission of IMS data.

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

[0173] In some embodiments, the first identification information and the second identification information may be determined 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 the 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.

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

[0175] In some embodiments, the first network element 1031 may determine, based on the first capability information, that the terminal 101 supports IMS services delivered via NB-IoT access in a control plane CIoT EPS optimized manner. In some embodiments, the first network element 1031 may determine, based on the 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.

[0176] 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. 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, the support capabilities of the first network can be determined by the first network element 1031 based on at least one of operator policies, local configuration, and operations administration and maintenance (OAM) configuration.

[0177] In some embodiments, when it is determined that both terminal 101 and the first network support IMS services delivered via NB-IoT access in a control plane CIoT EPS optimized manner, the first network element 1031 can determine the first identification information and the second identification information. In some embodiments, when it is determined that both terminal 101 and the first network support IMS services delivered via NB-IoT access in a control plane CIoT EPS optimized manner, and support the establishment of multiple bearers via NB-IoT access, the first network element 1031 can determine the first identification information and the second identification information.

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

[0179] In step S2103, terminal 101 sends first data to access network device 102.

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

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

[0182] In some embodiments, the first data may be IMS service data. In some embodiments, the first data may be IMS signaling or IMS data.

[0183] In some embodiments, step S2103 may include: terminal 101 sending first data and first information to access network device 102. In some embodiments, the first data may be one of the following: IMS signaling in IMS service, or IMS data in IMS service.

[0184] Optionally, the first information indicates that the first data is IMS signaling or indicates that the first data is IMS data.

[0185] In some embodiments, the first data and the first information may be carried in the same message and sent together, or carried in different messages and sent separately.

[0186] In some embodiments, the first information may indicate the type of the first data. For example, the first information may indicate that the first data is IMS signaling or IMS data.

[0187] In some embodiments, the first information may include first identification information or second identification information. For example, if the first information includes first identification information, then the first identification information indicates that the first data is IMS signaling. For example, if the first information includes second identification information, then the second identification information indicates that the first data is IMS data.

[0188] In some embodiments, step S2103 may include mapping the first data to the SRB.

[0189] In some embodiments, the first information can be used by terminal 101 to perform the mapping of first data to an SRB. In some embodiments, the SRB between terminal 101 and access network device 102 may include a first SRB and a second SRB. In some embodiments, the first SRB may be used to carry IMS signaling. In some embodiments, the second SRB may be used to carry IMS data.

[0190] In some embodiments, the first SRB and the second SRB can be different. In one example, the first SRB and the second SRB can correspond to different Quality of Service (QoS) requirements. For example, the QoS requirement corresponding to the first SRB can be higher than that corresponding to the second SRB. Alternatively, the QoS requirement corresponding to the first SRB can be lower than that corresponding to the second SRB. In one example, the first SRB and the second SRB can correspond to different priorities. For example, the priority of the first SRB can be higher than that of the second SRB. Alternatively, the priority of the first SRB can be lower than that of the second SRB.

[0191] In some embodiments, the number of first SRBs can be one or more. In some embodiments, the number of second SRBs can be one or more.

[0192] In some embodiments, when the first information includes first identification information, the terminal 101 can map the first data to the first SRB based on the first identification information. In some embodiments, when the first information includes first identification information, the first data can be mapped to the first SRB. In other words, the first data can be carried in the first SRB. For example, a message carrying the first data can be carried in the first SRB.

[0193] In some embodiments, when the first information includes second identification information, the terminal 101 can map the first data to a second SRB based on the second identification information. In other words, the first data can be carried in the second SRB. For example, a message carrying the first data can be carried in the second SRB.

[0194] In some embodiments, the first information may include at least one field, wherein one or more fields are used to indicate first identification information or second identification information. For example, when one field is used, the field value of 1 indicates the first identification information and the value of 0 indicates the second identification information, or the field value of 0 indicates the first identification information and the value of 1 indicates the second identification information. When two fields are used, the two fields can correspond one-to-one with the two identification information. The first field value of 1 indicates the first identification information and the second field value of 1 indicates the second identification information. For example, 10 indicates the first identification information and 01 indicates the second identification information. The reverse is also possible. When multiple fields are used, the same principle applies, which will not be elaborated here.

[0195] In some embodiments, the first identification information and the second identification information can be represented by the same field. In one example, the first information may include a field. This field may include one or more bits. Different values ​​of this field indicate the first identification information and the second identification information, respectively. For example, the first value of the field may be the first identification information, and the second value of the field may be the second identification information. In one example, the field may include 1 bit. For example, the first value of this bit may be 1, and the second value may be 0. For example, the first value of this bit may be 0, and the second value may be 1.

[0196] In some embodiments, the first identification information and the second identification information can be represented by different fields. In one example, the first information may include a bitmap. The bitmap may include two bits. Different bits in the bitmap indicate the first identification information and the second identification information, respectively. In other words, one bit indicates the first identification information, and the other bit indicates the second identification information. For example, a bitmap value of 10 indicates the first identification information; a bitmap value of 01 indicates the second identification information, and vice versa. It is understood that the values ​​of the two bits in the bitmap are different, and this disclosure does not specifically limit this.

[0197] In some embodiments, terminal 101 can establish a radio resource control (RRC) connection. For example, terminal 101 can send an RRC connection request message. In some embodiments, the RRC connection request message may include first data and first information. In some embodiments, the RRC connection request message may include first data but not first information. In this case, the first information may be provided to access network device 102 by other means.

[0198] In some embodiments, the RRC connection request message may include: first information and a NAS packet data unit (PDU). In some embodiments, the NAS PDU may carry an EPS bearer identifier (EBI) and first data. In some embodiments, the first data carried in the RRC connection request message may be encrypted uplink data.

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

[0200] In some embodiments, access network device 102 may receive first data. In some embodiments, access network device 102 may receive IMS signaling via a first SRB. For example, access network device 102 may receive first data on a first SRB. In some embodiments, access network device 102 may receive IMS data via a second SRB.

[0201] In step S2104, the access network device 102 sends the first data to the first network element 1031.

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

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

[0204] In some embodiments, the first data and the first information may be carried in the same message and sent together, or carried in different messages and sent separately.

[0205] In some embodiments, access network device 102 may send first information and first data to first network element 1031. In some embodiments, access network device 102 may send an S1-AP initial UE message to first network element 1031. In some embodiments, the S1-AP initial UE message may include first data and first information. In some embodiments, the S1-AP initial UE message may include first data but not first information. In this case, the first information may be provided to the first network element in other ways.

[0206] In some embodiments, the access network device 102 can send the received first data to the first network element 1031.

[0207] In some embodiments, after receiving the RRC connection request message, the access network device 102 can transmit the NAS PDU relay to the first network element 1031 via the S1-AP initial UE message.

[0208] In some embodiments, the S1-AP initial UE message may include first information and NAS PDU.

[0209] In some embodiments, before sending the first data, 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.

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

[0211] In some embodiments, for the two cases where the first data is IMS signaling and the first data is IMS data, the processing of the first data between the access network device 102 and the first network element 1031 may be different depending on whether the first information includes first identification information or second identification information.

[0212] In step S2105, the first network element 1031 processes the first data.

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

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

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

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

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

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

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

[0220] In some embodiments, the Modify 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, and RAT type. In some embodiments, the DL TEID of the first network element 1031 may be MME TEID DL. The 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0236] In some embodiments, the modified bearer response message sent by the second network element 1032 may include at least one of the following: the address information of the second network element 1032 and the TEID of the second network element 1032. The address information and the 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 an SGW TEID UL. The SGW TEID UL can be used to identify the uplink tunnel from the UE to the SGW.

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

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

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

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

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

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

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

[0244] In some embodiments, the first data can travel from the first network element 1031 to the third network element 1033 via a default bearer. In one example, the same bearer, i.e., the default bearer, can be used for both IMS signaling and IMS data.

[0245] In some embodiments, the first data can reach the third network element 1033 from the first network element 1031 via multiple bearers. In some embodiments, both the terminal 101 and the first network can support the establishment of multiple bearers via NB-IoT access. In this case, multiple bearers can be established through steps S2106 to S2109. In one example, the bearer used to transmit the first data may include an established default bearer and / or a dedicated bearer. In one example, different bearers are used for IMS signaling and IMS data respectively. For example, the default bearer can be used for IMS signaling, and the dedicated bearer can be used for IMS data. For example, the default bearer can be used for IMS data, and the dedicated bearer can be used for IMS signaling. For example, different dedicated bearers can be used for IMS signaling and IMS data respectively.

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

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

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

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

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

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

[0252] In some embodiments, the first data can travel from the third network element 1033 to the first network element 1031 via a default bearer. In one example, the same bearer, i.e., the default bearer, can be used for both IMS signaling and IMS data.

[0253] In some embodiments, first data can reach first network element 1031 from third network element 1033 via multiple bearers. In one example, the bearer used to transmit the first data may include an established default bearer and / or a dedicated bearer. In one example, different bearers are used for IMS signaling and IMS data respectively. For example, a default bearer may be used for IMS signaling, and a dedicated bearer may be used for IMS data. For example, a default bearer may be used for IMS data, and a dedicated bearer may be used for IMS signaling. For example, different dedicated bearers may be used for IMS signaling and IMS data respectively.

[0254] In step S2112, the first network element 1031 processes the first data.

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

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

[0257] In step S2113, the first network element 1031 sends the first data to the access network device 102.

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

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

[0260] In some embodiments, step S2113 may include: the first network element 1031 sending first data and first information to the access network device 102. In some embodiments, the first data may be one of the following: IMS signaling in IMS service, or IMS data in IMS service.

[0261] In some embodiments, the first data and the first information may be carried in the same message and sent together, or carried in different messages and sent separately.

[0262] In some embodiments, the first information may indicate the type of the first data. For example, the first information may indicate that the first data is IMS signaling or IMS data.

[0263] In some embodiments, the first information may include first identification information or second identification information. For example, if the first information includes first identification information, then the first identification information indicates that the first data is IMS signaling. For example, if the first information includes second identification information, then the second identification information indicates that the first data is IMS data.

[0264] In some embodiments, the first identification information and the second identification information can be represented by the same field. In one example, the first information may include a field. This field may include one or more bits. Different values ​​of this field indicate the first identification information and the second identification information, respectively. For example, the first value of the field may be the first identification information, and the second value of the field may be the second identification information. In one example, the field may include 1 bit. For example, the first value of this bit may be 1, and the second value may be 0. For example, the first value of this bit may be 0, and the second value may be 1.

[0265] In some embodiments, the first identification information and the second identification information can be represented by different fields. In one example, the first information may include a bitmap. The bitmap may include two bits. Different bits in the bitmap indicate the first identification information and the second identification information, respectively. In other words, one bit indicates the first identification information, and the other bit indicates the second identification information. For example, a bitmap value of 10 indicates the first identification information; a bitmap value of 01 indicates the second identification information. It is understood that the values ​​of the two bits in the bitmap are different.

[0266] 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 S1-AP downlink NAS message may include first data and first information. In some embodiments, the S1-AP downlink NAS message may include first data but not first information. In this case, the first information may be provided to the access network device 102 in other ways.

[0267] In some embodiments, the S1-AP downlink NAS message may include: first information and NAS PDU.

[0268] In some embodiments, step S2113 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.

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

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

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

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

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

[0274] In some embodiments, the context release command may 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 exchanged at the application layer. In this case, the first network element 1031 may send the S1UE context release command immediately after the S1-AP downlink NAS message.

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

[0276] In step S2115, the access network device 102 sends the first data to the terminal 101.

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

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

[0279] In some embodiments, the access network device 102 may send first information and first data to the terminal 101.

[0280] In some embodiments, the first data and the first information may be carried in the same message and sent together, or carried in different messages and sent separately.

[0281] In some embodiments, access network device 102 may send RRC downlink data messages to terminal 101. In some embodiments, the RRC downlink data message may include first data and first information. In some embodiments, the RRC downlink data message may include first data but not first information. In this case, the first information may be provided to terminal 101 by other means.

[0282] In some embodiments, access network device 102 can send the received first data to terminal 101. In some embodiments, after receiving the S1-AP downlink NAS message, access network device 102 can send the NAS PDU to terminal 101 via RRC downlink data message.

[0283] In some embodiments, the RRC downlink data message may include first information and NAS PDU.

[0284] In some embodiments, step S2115 may include mapping the first data to the SRB.

[0285] In some embodiments, the first information can be used by the access network device 102 to perform the mapping of first data to SRB.

[0286] In some embodiments, when the first information includes first identification information, the access network device 102 can map the first data to the first SRB based on the first identification information. In some embodiments, when the first information includes first identification information, the first data can be mapped to the first SRB. In other words, the first data can be carried in the first SRB. For example, a message carrying the first data can be carried in the first SRB.

[0287] In some embodiments, when the first information includes second identification information, the access network device 102 can map the first data to a second SRB based on the second identification information. In other words, the first data can be carried in the second SRB. For example, a message carrying the first data can be carried in the second SRB.

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

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

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

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

[0292] In step S2117, the access network device 102 determines to perform the release.

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

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

[0295] In step S2118, the access network device 102 performs a release process.

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

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

[0298] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2118. 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 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 S2113 and S2115 may be implemented as a standalone embodiment. For example, a combination of steps S2102, S2103, and S2104 may be implemented as a standalone embodiment. For example, a combination of steps S2102, S2113, and S2115 may be implemented as a standalone embodiment. It should be noted that the possible independent embodiments consisting of one or more steps in steps S2101 to S2118 are not limited thereto.

[0299] In some embodiments, steps S2101, S2103 to S2118 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 S2118 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 S2118 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2101 to S2112, S2114 to S2118 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2101 to S2114, S2116 to S2118 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0317] 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, and can also be sent by other entities.

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

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

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

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

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

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

[0324] In step S2207, terminal 101 initiates RRC connection establishment.

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

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

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

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

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

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

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

[0332] The optional implementation of step S2209 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.

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

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

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

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

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

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

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

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

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

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

[0343] 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 S2204 to S2212, and the cached first data is sent to the first network element 1031 through the established bearer.

[0344] In some embodiments, through steps S2203 and S2213, first data can travel from the third network element 1033 to the first network element 1031. In some embodiments, first data can travel from the first network element 1031 to the third network element 1033 via a default bearer. In one example, the same bearer, i.e., the default bearer, can be used for both IMS signaling and IMS data. In some embodiments, first data can travel from the first network element 1031 to the third network element 1033 via multiple bearers. In some embodiments, both the terminal 101 and the first network can support the establishment of multiple bearers through NB-IoT access. In this case, multiple bearers can be established through steps S2106 to S2109. In one example, the bearer used to transmit the first data may include the established default bearer and / or a dedicated bearer. In one example, different bearers are used for IMS signaling and IMS data respectively. For example, the default bearer can be used for IMS signaling, and the dedicated bearer can be used for IMS data. For example, the default bearer can be used for IMS data, and the dedicated bearer can be used for IMS signaling. For example, different dedicated bearers can be used for IMS signaling and IMS data respectively.

[0345] In step S2214, the first network element 1031 processes the first data.

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

[0347] In step S2215, the first network element 1031 sends the first data to the access network device 102.

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

[0349] In some embodiments, step S2215 may include: the first network element 1031 determining the type of the first data. In some embodiments, the first network element 1031 may determine that the first data is IMS signaling or IMS data of an IMS service.

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

[0351] In some embodiments, step S2215 may include: the first network element 1031 sending first data and first information to the access network device 102.

[0352] In some embodiments, when it is determined that the first data is IMS signaling, the first information may include first identification information.

[0353] In some embodiments, if it is determined that the first data is IMS data, the first information may include second identification information.

[0354] In step S2216, the access network device 102 sends the first data to the terminal 101.

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

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

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

[0358] In step S2218, terminal 101 sends first data to access network device 102.

[0359] The optional implementation of step S2218 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.

[0360] In some embodiments, terminal 101 may send an RRC uplink data message to access network device 102. In some embodiments, the RRC uplink data message may include first data and first information.

[0361] In some embodiments, the first data and the first information may be carried in the same message and sent together, or carried in different messages and sent separately.

[0362] In some embodiments, the RRC uplink data message may include: first information, NAS PDU.

[0363] In step S2219, the access network device 102 sends the first data to the first network element 1031.

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

[0365] In step S2220, the first network element 1031 processes the first data.

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

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

[0368] The optional implementation of step S2221 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.

[0369] In step S2222, the access network device 102 determines to perform the release.

[0370] The optional implementation of step S2222 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.

[0371] In step S2223, the access network device 102 performs a release process.

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

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

[0374] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2223. For example, step S2202 may be implemented as a standalone embodiment; step S2215 may be implemented as a standalone embodiment; step S2216 may be implemented as a standalone embodiment; step S2218 may be implemented as a standalone embodiment; step S2219 may be implemented as a standalone embodiment; a combination of steps S2202 and S2215 may be implemented as a standalone embodiment; a combination of steps S2215 and S2216 may be implemented as a standalone embodiment; a combination of steps S2202 and S2218 may be implemented as a standalone embodiment; a combination of steps S2218 and S2219 may be implemented as a standalone embodiment; a combination of steps S2202, S2215, and S2216 may be implemented as a standalone embodiment; a combination of steps S2202, S2218, and S2219 may be implemented as a standalone embodiment. It should be noted that the possible independent embodiments consisting of one or more steps in steps S2201 to S2223 are not limited thereto.

[0375] In some embodiments, steps S2201, S2203 to S2223 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2201 to S2214, S2216 to S2223 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 S2223 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2201 to S2217, S2219 to S2223 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2201 to S2218, S2220 to S2223 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

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

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

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

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

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

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

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

[0383] 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, S2102, S2110, S2111, S2201, S2202, and S2221.

[0384] 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 S3103.

[0385] In step S3101, the first network element 1031 sends the first identification information and / or the second identification information.

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

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

[0388] In some embodiments, the first identification information and the second identification information may be carried in the same message and sent together, or carried in different messages and sent separately.

[0389] In step S3102, terminal 101 sends first data and first information to access network device 102.

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

[0391] In some embodiments, the first information may include first identification information or second identification information.

[0392] In some embodiments, when the first information includes first identification information, the terminal 101 maps the first data to the first SRB based on the first identification information.

[0393] In some embodiments, when the first information includes second identification information, the terminal 101 maps the first data to the second SRB based on the second identification information.

[0394] In step S3103, the access network device 102 sends first data and first information to the first network element 1031.

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

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

[0397] 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 S3203.

[0398] In step S3201, the first network element 1031 sends the first identification information and / or the second identification information.

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

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

[0401] In step S3202, the first network element 1031 sends first data and first information to the access network device 102.

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

[0403] In some embodiments, the first information may include first identification information or second identification information.

[0404] In step S3203, the access network device 102 sends the first data and the first information to the terminal 101.

[0405] The optional implementation of step S3203 can be found in the optional implementation of step S2115 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.

[0406] In some embodiments, when the first information includes first identification information, the access network device 102 maps the first data to the first SRB based on the first identification information.

[0407] In some embodiments, when the first information includes second identification information, the access network device 102 maps the first data to the second SRB according to the second identification information.

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

[0409] Figure 4 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 4, the method includes step S401.

[0410] In step S401, the first network element 1031 and the terminal 101 exchange first data.

[0411] The optional implementations of step S401 can be found in the optional implementations of steps S2103, S2104, S2113, and S2115 in Figure 2A, steps S2215, S2216, S2218, and S2219 in Figure 2B, as well as other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0412] In some embodiments, step S401 may include: the first network element 1031 sending first data and first information to the terminal 101.

[0413] In some embodiments, step S401 may include: terminal 101 sending first data and first information to first network element 1031.

[0414] In some embodiments, the first information may include first identification information or second identification information.

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

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

[0417] In some embodiments, IMS signaling is identified by a first identification information and IMS data is identified by a second identification information. The UE (i.e., the terminal), eNodeB (i.e., the access network device), and MME (i.e., the first network element) distinguish between IMS signaling and IMS data based on the first and second identification information, and process the transmission of IMS signaling and IMS data differently based on the first and second identification information during transmission.

[0418] In some embodiments, the first identification information and the second identification information are applied to the case of transmitting IMS services using the EPS control plane.

[0419] In some embodiments, the first identification information and the second identification information may be the same identification, but with different values. Different values ​​are assigned to IMS signaling and IMS data to indicate that they are distinguished.

[0420] In some embodiments, the first identification information and the second identification information may correspond to different QoS values, indicating that different QoS processing is performed on IMS signaling and IMS data when they are transmitted through the control plane.

[0421] In some embodiments, on the UE and eNodeB, the IMS signaling corresponding to the first identification information is transmitted using the first SRB (signalling radio bearer), and the IMS data corresponding to the second identification information is transmitted using the second SRB, wherein the first SRB is different from the second SRB.

[0422] In some embodiments, the transmission of IMS signaling and IMS data is differentiated based on the first identification information and the second identification information during transmission, including using different SRBs for IMS signaling and IMS data on the control plane, or using different QoS processing on the control plane.

[0423] In some embodiments, the first identification information and the second identification information are generated by the MME and sent to at least one of the UE and the eNodeB.

[0424] In some embodiments, when a PDN connection for conducting IMS services is successfully established, the MME sends the first identification information and the second identification information to the UE or eNodeB.

[0425] In some embodiments, the first identification information and the second identification information are generated by the MME based on the IMS support capability of both the UE and the network to support control plane CIoT EPS optimization.

[0426] In some embodiments, the first identification information and the second identification information are also generated by the MME based on the UE's use of NB-IoT access to carry out IMS services.

[0427] In some embodiments, when the UE sends uplink IMS signaling or IMS data, it includes IMS signaling and first identification information in the uplink signaling message, or includes IMS data and second identification information.

[0428] In some embodiments, the UE maps uplink signaling messages to a first SRB or a second SRB based on first identification information and / or second identification information.

[0429] In some embodiments, when the MME sends downlink IMS signaling or data, it includes IMS signaling and first identification information in the downlink signaling message, or includes IMS data and second identification information.

[0430] In some embodiments, the eNodeB maps downlink messages carrying IMS signaling or IMS data to a first SRB or a second SRB based on first identification information and / or second identification information.

[0431] Figure 5A 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 5A includes steps S5101 to S5118.

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

[0433] In step S5102, if the MME determines that the network (i.e., the first network) supports IMS voice over NB-IoT, and the control plane CIoT EPS optimization is used to support IMS voice services, then the MME allocates an IMS signaling identifier (i.e., first identifier information) and an IMS data identifier (i.e., second identifier information) for the IMS service transmission. The IMS signaling identifier indicates that the NAS PDU is used to transmit IMS signaling. The IMS data identifier indicates that the NAS PDU is used to transmit IMS data. The eNodeB and MME can distinguish whether the data transmission is IMS signaling or IMS data based on the IMS signaling identifier and the IMS data identifier.

[0434] In step S5103, the UE establishes an RRC connection and, as part of it, sends an IMS signaling identifier and an integrity-protected NAS PDU. The NAS PDU carries an EPS bearer identifier 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. Based on the IMS signaling identifier, the NAS PDU carrying IMS signaling is transmitted between the UE and the eNodeB. For example, based on the identifier, SRB-1 (i.e., the first SRB) is designated to carry IMS signaling; SRB-2 (i.e., the second SRB) is designated to carry IMS data.

[0435] Step S5104 includes steps S5104a and S5104b.

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

[0437] 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. The eNodeB includes an IMS signaling identifier in the S1-AP Initial UE message.

[0438] In some embodiments, based on the identifier, NASDATA PDUs carrying IMS signaling and NASDATA PDUs carrying IMS data are processed differently between the eNodeB and the MME.

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

[0440] In step S5106, if the S11-U connection is not established, the MME sends a Modify Bearer Request message (MME address, MME DL TEID, RAT type) to the SGW (i.e., the second network element) for each PDN connection. The SGW can then send downlink data to the UE. The MME should instruct the S11-U tunnel for NAS user data and send its own S11-U IP address and MME DL TEID for use by the SGW for downlink data forwarding.

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

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

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

[0444] In step S5110, the MME sends uplink data (IMS signaling) to the PGW via the SGW. In the NB-IoT case, only a default bearer is established to carry uplink data between the MME and the PGW. IMS signaling and IMS data share the same default bearer.

[0445] 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 uses the default bearer and sends the downlink data to the MME through the SGW.

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

[0447] In step S5113, downlink data (IMS signaling) is encapsulated in a NAS PDU and sent to the eNodeB in an S1-AP downlink NAS message. Additionally, the IMS signaling identifier is included in this 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.

[0448] 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 which includes 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.

[0449] In step S5115, the eNodeB sends an RRC downlink data message. The RRC downlink data includes downlink data (IMS signaling) encapsulated in a NAS PDU and an IMS signaling identifier. 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. Based on the IMS signaling identifier, the eNodeB sends the NAS PDU carrying IMS signaling to the UE using SRB-1.

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

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

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

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

[0454] 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 S5201 to S5223.

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

[0456] In step S5202, if the MME determines that the network supports IMS voice transmission via NB-IoT, and the control plane CIoT EPS optimization is used to support IMS voice services, then the MME allocates an IMS signaling identifier (i.e., first identifier information) and an IMS data identifier (i.e., second identifier information) for the IMS service transmission. The IMS signaling identifier indicates that the NAS PDU is used to transmit IMS signaling. The IMS data identifier indicates that the NAS PDU is used to transmit IMS data. The eNodeB and MME can distinguish whether the data transmission is IMS signaling or IMS data based on the IMS signaling identifier and the IMS data identifier.

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

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

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

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

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

[0462] Step S5208 includes steps S5208a and S5208b.

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

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

[0465] In step S5209, if the S11-U connection is not established, the MME sends a Modify Bearer Request message (MME address, MME DL TEID, RAT type) to the SGW for each PDN connection. The SGW can then send downlink data to the UE. The MME should instruct the S11-U tunnel for NAS user data and send its own S11-U IP address and MME DL TEID for use by the SGW for downlink data forwarding.

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

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

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

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

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

[0471] In step S5215, the MME detects that the downlink data is IMS signaling. The downlink data (IMS signaling) is encapsulated in a NAS PDU and sent to the eNodeB in an S1-AP downlink NAS message. Furthermore, this message includes an IMS signaling identifier. 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.

[0472] In step S5216, the eNodeB sends an RRC downlink data message. The RRC downlink data includes downlink data (IMS signaling) encapsulated in a NAS PDU, and an IMS signaling identifier. 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. Based on the IMS signaling identifier, the eNodeB sends a NAS PDU carrying the IMS signaling to the UE using SRB-1.

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

[0474] 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 that encapsulates the NAS PDU with IMS data, and the IMS data identifier can be included in the uplink RRC message. Based on this, different processing can be provided at the UE, eNodeB, and MME. For example, based on the IMS data ID, the NAS PDU carrying IMS data is transmitted using SRB-2. For PDN connections configured to support header compression of the IP PDN type, the UE should apply header compression before encapsulating the IMS data in the NAS message.

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

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

[0477] In step S5221, the MME sends uplink data to the PGW via the SGW and using the default bearer.

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

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

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

[0481] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, this disclosure proposes an apparatus including a unit or module for implementing the steps performed by the first network element in any of the above methods. For example, this disclosure proposes another apparatus including a unit or module for implementing the steps performed by the terminal in any of the above methods.

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

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

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

[0485] In some embodiments, the communication device 600 may be a first network element. In some embodiments, the transceiver module 601 may be configured to: interact with the terminal to exchange first data, wherein the first data and first information correspond; wherein the first information includes one of the following: first identification information and second identification information; the first identification information indicates that the first data is IMS signaling, and the second identification information indicates that the first data is IMS data; wherein the access type used by the terminal is NB-IoT. 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, S2102, S2104, S2106, S2109, S2110, S2111, S2113, S2114, S2116, S2201, S2202, S2204, S2205, S2208, S2209, S2212, S2213, S2215, S2217, S2219, S2221, 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 S2105, S2112, S2214, S2220, but not limited thereto).

[0486] In some embodiments, the communication device 600 may be a terminal. In some embodiments, the transceiver module 601 may be configured to receive first information sent by a first network element, wherein the first information indicates that the first network supports IMS services via NB-IoT, the first network element is located in the first network, and the access type used by the terminal is NB-IoT. 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, S2102, S2103, S2115, S2201, S2202, S2206, S2207, S2216, S2218, but not limited thereto), which will not be elaborated here.

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

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

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

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

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

[0492] 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, S2102, S2103, S2104, S2106, S2107, S2108, S2109, S2110, S2111, S2113, S2114, S2115, S2116, S2118, S2201, S2202, S2203, S2204, S2...). At least one of S2205, S2206, S2207, S2208, S2209, S2210, S2211, S2212, S2213, S2215, S2216, S2217, S2218, S2219, S2221, S2223 (but not limited thereto) is performed by the processor 7101, while at least one of other steps (e.g., steps S2105, S2112, S2117, S2214, S2220, S2222, 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.

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

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

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

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

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

[0498] 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, S2102, S2103, S2104, S2106, S2107, S2108, S2109, S2110, S2111, S2113, S2114, S2115, S2116, S2118, S2201, S2202, S2203, S2204, S2205, S2206, S2207, S2208, S2209, S2210, S2211, S2212, S2213, S2215, S2216, S2217, S2218, S2219, S2221, S2223, 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 S2105, S2112, S2117, S2214, S2220, S2222, but not limited thereto).

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

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

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

[0502] 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 performed by a first network element, wherein, The method includes: The terminal interacts with the first data, wherein the first data corresponds to the first information; The first information includes one of the following: first identification information and second identification information; the first identification information indicates that the first data is Internet Protocol Multimedia Subsystem (IMS) signaling, and the second identification information indicates that the first data is IMS data; The terminal uses Narrowband Internet of Things (NB-IoT) as its access type.

2. The method of claim 1, wherein, The interaction with the terminal to exchange the first data includes: Send the first data and the first information.

3. The method of claim 2, wherein, The first information is used by the access network device to map the first data to the signaling radio bearer (SRB). Wherein, the first information includes the first identification information, and the first data is mapped to a first SRB according to the first identification information; or, the first information includes the second identification information, and the first data is mapped to a second SRB according to the second identification information, wherein the first SRB and the second SRB are different.

4. The method of claim 1, wherein, The interaction with the terminal to exchange the first data includes: Receive the first data and the first information.

5. The method of claim 4, wherein, The first information is used by the terminal to map the first data to the SRB; Wherein, the first information includes the first identification information, and the first data is mapped to a first SRB according to the first identification information; or, the first information includes the second identification information, and the first data is mapped to a second SRB according to the second identification information, wherein the first SRB and the second SRB are different.

6. The method of any one of claims 2 to 5, wherein, The first data and the first information are carried in the control plane messages of the Evolved Packet System (EPS).

7. The method of any one of claims 1 to 6, wherein, The first information includes one field. Wherein, the field has a first value, the field indicating the first identification information; or, the field has a second value, the field indicating the second identification information.

8. The method of any one of claims 1 to 7, wherein, The method further includes: Send the first identification information and / or the second identification information, wherein the first identification information and / or the second identification information are sent to at least one of the following: the terminal, the access network device; The first identification information and the second identification information are determined by the first network element.

9. The method of claim 8, wherein, The first identification information and the second identification information are determined by the first network element based on at least one of the following: The terminal and the first network support IMS services delivered in the control plane cellular IoT EPS optimization mode. The terminal and the first network support IMS services via NB-IoT access; The terminal and the first network support the establishment of multiple bearers through NB-IoT access; The first network element is located in the first network.

10. The method of claim 8 or 9, wherein, The first identification information and the second identification information are determined when establishing a packet data network (PDN) connection for IMS services.

11. A communication method performed by a terminal, wherein, The method includes: The system interacts with the first network element to exchange first data, wherein the first data corresponds to the first information. The first information includes one of the following: first identification information and second identification information; the first identification information indicates that the first data is Internet Protocol Multimedia Subsystem (IMS) signaling, and the second identification information indicates that the first data is IMS data; The terminal uses Narrowband Internet of Things (NB-IoT) as its access type.

12. The method of claim 11, wherein, The interaction with the first network element to exchange first data includes: Receive the first data and the first information.

13. The method of claim 12, wherein, The first information is used by the access network device to map the first data to the signaling radio bearer (SRB). Wherein, the first information includes the first identification information, and the first data is mapped to a first SRB according to the first identification information; or, the first information includes the second identification information, and the first data is mapped to a second SRB according to the second identification information, wherein the first SRB and the second SRB are different.

14. The method of claim 11, wherein, The interaction with the first network element to exchange first data includes: Send the first data and the first information.

15. The method of claim 14, wherein, The first information is used by the terminal to map the first data to the SRB; Wherein, the first information includes the first identification information, and the first data is mapped to a first SRB according to the first identification information; or, the first information includes the second identification information, and the first data is mapped to a second SRB according to the second identification information, wherein the first SRB and the second SRB are different.

16. The method of any one of claims 12 to 15, wherein, The first data and the first information are carried in the control plane messages of the Evolved Packet System (EPS).

17. The method of any one of claims 11 to 16, wherein, The first information includes one field. Wherein, the field has a first value, the field indicating the first identification information; or, the field has a second value, the field indicating the second identification information.

18. The method of any one of claims 11 to 17, wherein, The method further includes: The first identification information and / or the second identification information are received, wherein the first identification information and the second identification information are determined by the first network element.

19. The method of claim 18, wherein, The first identification information and the second identification information are determined by the first network element based on at least one of the following: The terminal and the first network support IMS services delivered in the control plane cellular IoT EPS optimization mode. The terminal and the first network support IMS services via NB-IoT access; The terminal and the first network support the establishment of multiple bearers through NB-IoT access; The first network element is located in the first network.

20. The method of claim 18 or 19, wherein, The first identification information and the second identification information are determined when establishing a packet data network (PDN) connection for IMS services.

21. A communication method, performed by a communication system, wherein, The communication system includes a first network element and a terminal, and the method includes: The first network element and the terminal interact with each other to exchange first data, wherein the first data corresponds to first information; The first information includes one of the following: first identification information and second identification information; the first identification information indicates that the first data is Internet Protocol Multimedia Subsystem (IMS) signaling, and the second identification information indicates that the first data is IMS data; The terminal uses Narrowband Internet of Things (NB-IoT) as its access type.

22. A communications device, characterized by The communication device is used to perform the communication method as described in any one of claims 1 to 10, 11 to 20.

23. A communication system, characterized by The device includes a first 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 10, and the terminal is configured to implement the communication method as described in any one of claims 11 to 20.

24. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1 to 10, 11 to 20.

25. 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 10, 11 to 20.

Images