A communication method, apparatus, and system
Patent Information
- Application Number
- CN202510338922.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-18
- Publication Date
- 2026-09-18
AI Technical Summary
[0093] It should be understood that the beneficial effects of aspects five through sixteen above can be referenced from aspects one through four above and any possible implementation thereof, and will not be elaborated here.
Smart Images
Figure CN122783484A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and more specifically, to a communication method, apparatus, and system. Background Technology
[0002] Non-terrestrial networks (NTNs) include nodes such as satellite networks, high-altitude platforms, and drones. They have significant advantages such as global coverage, long-distance transmission, flexible networking, convenient deployment, and no geographical limitations. They have been widely used in fields such as maritime communication, positioning and navigation, disaster relief, scientific experiments, video broadcasting, voice telephony, and Earth observation.
[0003] Narrowband IoT devices offer advantages such as low cost and low power consumption. Connecting narrowband IoT devices to satellites helps reduce the cost of satellite phones while also effectively reducing terminal power consumption and extending communication time. Therefore, supporting voice services via satellite access has become an industry trend for narrowband IoT devices. However, how to effectively support voice services is a pressing issue that needs to be addressed for narrowband IoT devices. Summary of the Invention
[0004] This application provides a communication method, apparatus, and system capable of providing voice services for narrowband Internet of Things (IoT) devices.
[0005] Firstly, a communication method is provided that can be applied to the narrowband IoT device side (or terminal side). For example, it can be a narrowband IoT device or its communication and / or computing modules, or circuits or chips responsible for communication functions within the narrowband IoT device (such as modem chips, also known as baseband chips, or system-on-chip (SoC) chips or system-in-package (SIP) chips containing modem cores), or circuits or chips responsible for communication and / or computing functions within the narrowband IoT device (such as graphics processing units (GPUs), artificial intelligence (AI) processors, or application-specific integrated circuits (ASICs)). Alternatively, it can be a logic module or software capable of implementing all or part of the functions of a narrowband IoT device. The method is described using the application of this method to a narrowband IoT device as an example.
[0006] The method includes: a narrowband IoT device sending a first request message and receiving a first response message. The first request message requests the establishment of a first connection, which supports both user plane-based and control plane-based transmissions. The access point name (APN) carried in the first request message indicates the Internet Protocol (IP) Multimedia Subsystem (IMS). The first connection is a connection between the narrowband IoT device and a core network element. The first response message indicates that the first connection has been established.
[0007] Based on the above scheme, narrowband IoT devices can request the core network element to establish a first connection for APN-indicated IMS. This first connection can support both user plane-based and control plane-based transmissions. Specifically, the narrowband IoT device can transmit IMS session initiation protocol (SIP) signaling through the first bearer of the first connection, and transmit IMS voice data through the second bearer of the first connection. In other words, the core network element can create a first connection for the narrowband IoT device that simultaneously supports control plane (CP) cellular internet of things (CIoT) evolved packet system (EPS) optimized transmission and user plane (UP) CIoT EPS optimized transmission. That is, by creating a user plane bearer (e.g., the second bearer of the first connection) to transmit IMS voice data, the core network element can provide quality of service (QoS) guarantees for the narrowband IoT device's IMS voice data, thereby improving voice call quality.
[0008] In conjunction with the first aspect, in certain implementations of the first aspect, the narrowband IoT device sends a first request message, including: when the narrowband IoT device accesses the narrowband Internet of Things (NB-IoT) via satellite, the narrowband IoT device sends a first request message.
[0009] Based on the above scheme, when a narrowband IoT device determines that it is accessing the narrowband IoT via satellite, it requests to establish a first connection from the core network element. Therefore, the technical solution of this application is applicable to IoT scenarios.
[0010] In conjunction with the first aspect, in some implementations of the first aspect, the first request message includes indication information for indicating that the first connection supports both user plane-based and control plane-based transmissions.
[0011] Based on the above scheme, by carrying indication information in the first request message, the core network element can determine, after receiving the first request message, that the narrowband IoT device requests to establish a first connection that supports both user plane-based and control plane-based transmissions. That is, by creating a user plane bearer (e.g., the second bearer of the first connection) to transmit IMS voice data, QoS guarantees can be provided for the IMS voice data of the narrowband IoT device, thereby improving the quality of voice calls.
[0012] In conjunction with the first aspect, in some implementations of the first aspect, the first bearer of the first connection is used to transmit SIP signaling, and the method further includes: a narrowband IoT device receiving a second request message and sending a second response message. The second request message is used to request the establishment of a second bearer for the first connection, the second bearer of the first connection is used to transmit IMS voice data, and the second response message is used to indicate that the establishment of the second bearer of the first connection is complete.
[0013] Based on the above scheme, narrowband IoT devices can transmit SIP signaling through the first bearer of the first connection, and when the second bearer of the first connection is established, they can also transmit IMS voice data through the second bearer of the first connection. That is, by creating a user plane bearer, QoS guarantee can be provided for the IMS voice data of narrowband IoT devices, thereby improving the quality of voice calls.
[0014] In conjunction with the first aspect, in some implementations of the first aspect, the first bearer is a bearer corresponding to the transmission based on the control plane, and the second bearer is a bearer corresponding to the transmission based on the user plane; or, the first bearer is a bearer corresponding to the transmission based on the user plane, and the second bearer is a bearer corresponding to the transmission based on the control plane.
[0015] Based on the above scheme, this application does not specifically limit the control plane bearer or user plane bearer corresponding to the first bearer of the first connection, nor does it specifically limit the control plane bearer or user plane bearer corresponding to the second bearer of the first connection.
[0016] It is understood that the first or second bearer of the first connection refers to the logical connection between the narrowband IoT device and the core network element, and the bearer between the narrowband IoT device and the base station can be a signaling radio bearer (SRB) or a data radio bearer (DRB).
[0017] Secondly, a communication method is provided that can be applied to the core network element side (or the mobility management entity (MME) side). This includes, for example, core network elements or communication and / or computing modules within core network elements, or circuits or chips within core network elements responsible for communication functions (such as modem chips, also known as baseband chips, or SoC chips or SIP chips containing modem cores), or circuits or chips within core network elements responsible for communication and / or computing functions (such as GPUs, AI processors, or ASICs), or logic modules or software capable of implementing all or part of the core network element functions. The method is described using the application of this method to a core network element as an example.
[0018] The method includes: a core network element receiving a first request message and sending a first response message. The first request message requests the establishment of a first connection, which supports both user plane-based and control plane-based transmissions. The first request message carries an APN indicating IMS. The first connection is a connection between a narrowband IoT device and a core network element. The first response message indicates that the first connection has been established.
[0019] Based on the above scheme, after receiving the first request message, the core network element can establish a first connection for the narrowband IoT device that indicates IMS via APN. This first connection can support both user plane-based and control plane-based transmissions. In other words, the core network element can create a first connection for the narrowband IoT device that simultaneously supports CP CIoT EPS optimized transmission and UP CIoT EPS optimized transmission. This means that the narrowband IoT device can subsequently transmit SIP signaling through the first bearer of the first connection and transmit IMS voice data through the second bearer of the first connection. This implementation, by creating a user plane bearer to transmit IMS voice data, can provide QoS guarantees for the IMS voice data of the narrowband IoT device, thereby improving voice call quality.
[0020] In conjunction with the second aspect, in some implementations of the second aspect, the first request message includes indication information for indicating that the first connection supports both user plane-based and control plane-based transmissions.
[0021] In conjunction with the second aspect, in some implementations of the second aspect, before the core network element sends the first response message, the method further includes: the core network element determining the session corresponding to the establishment of the first connection based on the first information; wherein the first information includes at least one of the following: the radio access technology (RAT) type of the narrowband IoT device, the APN, the subscription information of the narrowband IoT device, or the location information of the narrowband IoT device.
[0022] In conjunction with the second aspect, in certain implementations of the second aspect, the core network element determines the session corresponding to the establishment of the first connection based on the first information, including: when the RAT type indicates that the narrowband IoT device accesses NB-IoT via satellite, and / or the APN indicates IMS, the core network element determines the session corresponding to the establishment of the first connection.
[0023] In conjunction with the second aspect, in some implementations of the second aspect, the core network element determines the session corresponding to the establishment of the first connection based on the first information, including: when the first request message carries indication information, the core network element determines the session corresponding to the establishment of the first connection based on the first information.
[0024] In conjunction with the second aspect, in some implementations of the second aspect, the first bearer of the first connection is used to transmit IMSSIP signaling, and the method further includes: sending a second request message, the second request message being used to request the establishment of a second bearer of the first connection, the second bearer of the first connection being used to transmit IMS voice data; and receiving a second response message, the second response message being used to indicate that the establishment of the second bearer of the first connection is complete.
[0025] In conjunction with the second aspect, in some implementations of the second aspect, the first bearer is a bearer corresponding to the transmission based on the control plane, and the second bearer is a bearer corresponding to the transmission based on the user plane; or, the first bearer is a bearer corresponding to the transmission based on the user plane, and the second bearer is a bearer corresponding to the transmission based on the control plane.
[0026] The technical solution of the second aspect corresponds to the technical solution of the first aspect and has the same technical effect as the first aspect. For the technical effect of the second aspect, please refer to the relevant description of the first aspect, which will not be repeated here.
[0027] Thirdly, a communication method is provided, which can be applied to the first core network element side (or MME side). For example, it can be the first core network element, or a communication module and / or computing module within the first core network element; or a circuit or chip responsible for communication functions within the first core network element (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core); or a circuit or chip responsible for communication and / or computing functions within the first core network element (such as a GPU, AI processor, or ASIC); or it can be a logic module or software capable of implementing all or part of the functions of the first core network element. The method is described using the application of this method to a first core network element as an example.
[0028] The method includes: a first core network element sending a first request message and receiving a first response message. The first request message requests the establishment of a session corresponding to a first connection. The first request message includes a first bearer identifier for a second connection. The first connection and the second connection are associated. The APN of both the first and second connections indicates IMS. Both the first and second connections are connections between narrowband IoT devices and a second core network element. The first response message indicates that the session corresponding to the first connection has been established.
[0029] In this application, the first connection and the second connection are associated, which can be understood as: the default bearer of the second connection (i.e., the first bearer of the second connection) and the default bearer of the first connection are associated. This association is used for the replacement of the dedicated bearer (used for transmitting IMS voice data) of the second connection by subsequent second core network elements (e.g., PGW), and / or the conversion of the transmission addresses of uplink and downlink voice data.
[0030] Based on the above scheme, the first core network element can request the second core network element to establish a session corresponding to the first connection indicating IMS via APN. This first connection supports user plane-based transmission and is associated with a second connection that supports control plane-based transmission. That is, subsequent narrowband IoT devices can transmit SIP signaling through the first connection and IMS voice data through the second connection. In other words, the core network element can create a second connection supporting CPCIoT EPS optimized transmission and a first connection supporting UP CIoT EPS optimized transmission for narrowband IoT devices. Specifically, by creating control plane bearers (e.g., the first bearer of the second connection) and user plane bearers (e.g., the second bearer of the first connection) to transmit SIP signaling and IMS voice data respectively, QoS guarantees can be provided for the IMS voice data of narrowband IoT devices, thereby improving voice call quality.
[0031] In conjunction with the third aspect, in some implementations of the third aspect, before the first core network element sends the first request message, the method further includes: the first core network element determining the session corresponding to the establishment of the first connection based on the first information; wherein the first information includes at least one of the following: the RAT type, APN, subscription information of the narrowband IoT device, or location information of the narrowband IoT device.
[0032] In conjunction with the third aspect, in certain implementations of the third aspect, the first core network element determines the session corresponding to the establishment of the first connection based on the first information, including: when the RAT type indicates that the narrowband IoT device accesses NB-IoT via satellite, and / or the APN indicates IMS, the first core network element determines the session corresponding to the establishment of the first connection.
[0033] Based on the above scheme, the first core network element can determine whether to establish a session corresponding to the first connection for the narrowband IoT device based on the first information. For example, if the narrowband IoT device accesses NB-IoT via satellite and / or the APN indicates IMS, the first core network element determines to establish a session corresponding to the first connection. Conversely, if the narrowband IoT device is not accessed by NB-IoT or does not access NB-IoT via satellite, or if the APN does not indicate IMS, the first core network element determines not to establish a session corresponding to the first connection. In other words, the session corresponding to the first connection is established for scenarios where the narrowband IoT device accesses the narrowband IoT via satellite and performs IMS voice services.
[0034] In conjunction with the third aspect, in some implementations of the third aspect, before the first core network element sends the first request message, the method further includes: the first core network element receiving a second request message and sending a second response message. The second request message is used to request the establishment of a first connection, includes a first bearer identifier for the second connection, and carries an APN indicating IMS. The second response message indicates that the first connection has been established.
[0035] In conjunction with the third aspect, in some implementations of the third aspect, the first bearer of the second connection is used to transmit IMSSIP signaling, and the method further includes: a first core network element sending a third request message and receiving a third response message. The third request message is used to request the establishment of a second bearer for the first connection, includes an identifier for the second bearer of the first connection, the second bearer of the first connection is used to transmit IMS voice data, and the third response message indicates that the establishment of the second bearer of the first connection is complete.
[0036] In conjunction with the third aspect, in some implementations of the third aspect, the first bearer is a bearer corresponding to the transmission based on the control plane, and the second bearer is a bearer corresponding to the transmission based on the user plane; or, the first bearer is a bearer corresponding to the transmission based on the user plane, and the second bearer is a bearer corresponding to the transmission based on the control plane.
[0037] The beneficial effects of the third aspect and some implementations of the third aspect can be referred to the description of the first aspect and related implementations of the first aspect, which will not be repeated here.
[0038] Fourthly, a communication method is provided that can be applied to the second core network element side (or, the packet data network gateway (PGW) side). For example, it can be a second core network element, or a communication module and / or computing module within a second core network element; or a circuit or chip within a second core network element responsible for communication functions (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core); or a circuit or chip within a second core network element responsible for communication and / or computing functions (such as a GPU, AI processor, or ASIC); or it can be a logic module or software capable of implementing all or part of the functions of the second core network element. The method is described using the application of this method to a second core network element as an example.
[0039] The method includes: a second core network element receiving a first request message and sending a first response message. The first request message requests the establishment of a session corresponding to a first connection. The first request message includes a first bearer identifier for a second connection. The first connection and the second connection are associated. Both the first connection and the second connection have an IMS APN. Both the first connection and the second connection are connections between a narrowband IoT device and the second core network element. The first response message indicates that the session corresponding to the first connection has been established.
[0040] Based on the above scheme, after receiving the first request message, the second core network element can establish a session corresponding to the first connection indicating IMS via APN. This first connection supports user plane-based transmission and is associated with a second connection that supports control plane-based transmission. That is, subsequent narrowband IoT devices can transmit SIP signaling through the first connection and IMS voice data through the second connection. In other words, the core network element can create a second connection supporting CP CIoT EPS optimized transmission and a first connection supporting UP CIoT EPS optimized transmission for narrowband IoT devices. Specifically, by creating control plane bearers and user plane bearers to transmit SIP signaling and IMS voice data respectively, QoS guarantees can be provided for the IMS voice data of narrowband IoT devices, thereby improving voice call quality.
[0041] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method also includes: the second core network element storing the association between the first connection and the second connection.
[0042] Based on the above scheme, the second core network element stores the association between the first connection and the second connection, which can be used for the replacement of operations (e.g., from the second connection to the first connection) when the second core network element receives a dedicated bearer for the second connection (used to transmit IMS voice data), and / or for the conversion of uplink and downlink voice data transmission addresses, so as to facilitate communication between narrowband IoT devices and the IMS network.
[0043] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first bearer of the second connection is used to transmit IMSSIP signaling, and the method further includes: a second core network element receiving a fourth request message, the fourth request message being used to request modification of the second connection to transmit IMS voice data; determining, based on the fourth request message and the association between the first connection and the second connection, a second bearer for establishing the first connection, the second bearer of the first connection being used to transmit IMS voice data; and sending a fifth request message, the fifth request message being used to request the establishment of the second bearer for the first connection.
[0044] Based on the above scheme, after receiving the fourth request message, the second core network element can replace the modification request for the second connection with the modification request for the first connection according to the saved association between the first connection and the second connection. That is, it can establish a second bearer for the first connection used to transmit IMS voice data, provide QoS guarantee for the IMS voice data of narrowband IoT devices, and thus improve the quality of voice calls.
[0045] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes: receiving first data from a narrowband IoT device via a second bearer of the first connection; replacing the source address of the first data with the address of the narrowband IoT device corresponding to the second connection according to the association between the first connection and the second connection; and sending the first data to the IMS network.
[0046] Based on the above scheme, after receiving the first data from the narrowband IoT device, the second core network element can modify the source address of the first data to a source address that the IMS network can resolve or recognize, which is the address of the narrowband IoT device corresponding to the second connection, according to the saved association between the first connection and the second connection. In this way, after receiving the first data, the IMS network determines that the sender of the first data is the narrowband IoT device. This implementation method can provide QoS guarantee for the transmission of IMS voice data between the narrowband IoT device and the IMS network.
[0047] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes: receiving second data from the IMS network; replacing the destination address of the second data with the address of the narrowband IoT device corresponding to the first connection according to the association between the first connection and the second connection; and sending the second data to the narrowband IoT device through the second bearer of the first connection.
[0048] Based on the above scheme, after receiving the second data from the IMS network, the second core network element can modify the destination address of the second data to a source address that the narrowband IoT device can parse or recognize, which is the address of the narrowband IoT device corresponding to the first connection, according to the saved association between the first connection and the second connection. In this way, the narrowband IoT device can receive the second data through the second bearer of the first connection. This implementation method can provide QoS guarantee for the transmission of IMS voice data between the narrowband IoT device and the IMS network.
[0049] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first bearer is a bearer corresponding to the transmission based on the control plane, and the second bearer is a bearer corresponding to the transmission based on the user plane; or, the first bearer is a bearer corresponding to the transmission based on the user plane, and the second bearer is a bearer corresponding to the transmission based on the control plane.
[0050] The technical solution in the fourth aspect corresponds to the technical solution in the third aspect and has the same technical effect as the third aspect. For details on the technical effect of the fourth aspect, please refer to the relevant description of the third aspect, which will not be repeated here.
[0051] Fifthly, a communication method is provided, which can be applied to both a first core network element and a second core network element. The first core network element can be a first core network element itself, or a communication module and / or computing module within a first core network element, or a circuit or chip within a first core network element responsible for communication functions, or a circuit or chip within a first core network element responsible for communication and / or computing functions, or it can be a logic module or software capable of implementing all or part of the functions of the first core network element. The second core network element can be a second core network element itself, or a communication module and / or computing module within a second core network element, or a circuit or chip within a second core network element responsible for communication functions, or a circuit or chip within a second core network element responsible for communication and / or computing functions, or it can be a logic module or software capable of implementing all or part of the functions of the second core network element. The method is described using the application of this method to both a first and a second core network element as an example.
[0052] The method includes: a first core network element sending a first request message to a second core network element, correspondingly, the second core network element receiving the first request message from the first core network element. The first request message is used to request the establishment of a session corresponding to a first connection. The first request message includes a first bearer identifier of the second connection. The first connection and the second connection are associated. The APN of both the first connection and the second connection indicates IMS. Both the first connection and the second connection are connections between a narrowband IoT device and the second core network element. The second core network element sending a first response message to the first core network element, correspondingly, the first core network element receiving the first response message from the second core network element. The first response message is used to indicate that the session corresponding to the first connection has been established.
[0053] In conjunction with the fifth aspect, in some implementations of the fifth aspect, before the first core network element sends the first request message to the second core network element, the method further includes: the first core network element determining the session corresponding to the establishment of the first connection based on the first information; wherein the first information includes at least one of the following: the RAT type, APN, subscription information of the narrowband IoT device, or location information of the narrowband IoT device.
[0054] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first core network element determines the session corresponding to the establishment of the first connection based on the first information, including: determining the session corresponding to the establishment of the first connection when the RAT type indicates that the narrowband IoT device accesses NB-IoT via satellite, and / or the APN indicates IMS.
[0055] In conjunction with the fifth aspect, in some implementations of the fifth aspect, before the first core network element sends the first request message, the method further includes: the narrowband IoT device sending a second request message to the first core network element, correspondingly, the first core network element receiving the second request message from the narrowband IoT device, the second request message being used to request the establishment of a first connection, the second request message including a first bearer identifier of the second connection, and an APN indicating IMS carried in the second request message; the first core network element sending a second response message to the narrowband IoT device, correspondingly, the narrowband IoT device receiving the second response message from the first core network element, the second response message being used to indicate that the first connection has been established.
[0056] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method also includes: the second core network element storing the association between the first connection and the second connection.
[0057] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first bearer of the second connection is used to transmit SIP signaling. The method further includes: the second core network element receiving a fourth request message, which requests modification of the second connection to transmit IMS voice data; the second core network element determining, based on the fourth request message and the association between the first connection and the second connection, the second bearer of the first connection is used to transmit IMS voice data; the second core network element sending a fifth request message to the first core network element, and correspondingly, the first core network element receiving the fifth request message from the second core network element, which requests the establishment of the second bearer of the first connection.
[0058] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: a first core network element sending a third request message to a narrowband IoT device; correspondingly, the narrowband IoT device receiving the third request message from the first core network element; the third request message being used to request the establishment of a second bearer for the first connection; the third request message including an identifier of the second bearer for the first connection; and the second bearer for the first connection being used to transmit IMS voice data; the narrowband IoT device sending a third response message to the first core network element; correspondingly, the first core network element sending a third response message to the narrowband IoT device; and the third response message being used to indicate that the establishment of the second bearer for the first connection is complete.
[0059] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first bearer is a bearer corresponding to the transmission based on the control plane, and the second bearer is a bearer corresponding to the transmission based on the user plane; or, the first bearer is a bearer corresponding to the transmission based on the user plane, and the second bearer is a bearer corresponding to the transmission based on the control plane.
[0060] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: a narrowband IoT device sending first data to a second core network element through a second bearer of a first connection; correspondingly, the second core network element receiving the first data from the narrowband IoT device through a second bearer of the first connection; the second core network element replacing the source address of the first data with the address of the narrowband IoT device corresponding to the second connection according to the association relationship between the first connection and the second connection; and the second core network element sending the first data to the IMS network; correspondingly, the IMS network receiving the first data from the second core network element.
[0061] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: the IMS network sending second data to the second core network element, correspondingly, the second core network element receiving the second data from the IMS network; the second core network element replacing the destination address of the second data with the address of the narrowband IoT device corresponding to the first connection according to the association relationship between the first connection and the second connection; the second core network element sending the second data to the narrowband IoT device through the second bearer of the first connection, correspondingly, the narrowband IoT device receiving the second data from the second core network element through the second bearer of the first connection.
[0062] Sixthly, a communication device is provided. This communication device has the functions described in the first aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the first aspect. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware.
[0063] In one possible design, the communication device includes: a communication unit for sending a first request message, the first request message being used to request the establishment of a first connection, the first connection supporting user plane-based transmission and control plane-based transmission, the first request message carrying an APN indicating IMS, and the first connection being a connection between a narrowband IoT device and a core network element; and a communication unit further for receiving a first response message, the first response message being used to indicate that the first connection has been established.
[0064] The communication unit can perform the receiving and transmitting processes described in the first aspect above, and the processing unit can perform other processes described in the first aspect above besides receiving and transmitting.
[0065] The aforementioned communication device may be a narrowband IoT device, or a communication module in a narrowband IoT device, or a chip in a narrowband IoT device that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module, or a logical node, logical module or software that can realize all or part of the functions of a narrowband IoT device.
[0066] In a seventh aspect, a communication device is provided. This communication device has the functions described in the second aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the second aspect above. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware.
[0067] In one possible design, the communication device includes: a communication unit for receiving a first request message, the first request message being used to request the establishment of a first connection, the first connection supporting user plane-based transmission and control plane-based transmission, the first request message carrying an APN indicating IMS, and the first connection being a connection between a narrowband IoT device and a core network element; and a communication unit further for sending a first response message, the first response message being used to indicate that the first connection has been established.
[0068] The communication unit can perform the receiving and transmitting processes described in the second aspect above, and the processing unit can perform other processes described in the second aspect above besides receiving and transmitting.
[0069] The aforementioned communication device may be a core network element, or a communication module in a core network element, or a chip in a core network element that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module, or a logical node, logical module, or software that can realize all or part of the functions of a core network element.
[0070] Eighthly, a communication device is provided. This communication device has the functions described in the third aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the third aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.
[0071] In one possible design, the communication device includes: a communication unit for sending a first request message, the first request message being used to request the establishment of a session corresponding to a first connection, the first request message including a first bearer identifier of a second connection, wherein the first connection and the second connection are associated, the APN of both the first connection and the second connection indicates IMS, and both the first connection and the second connection are connections between a narrowband IoT device and a second core network element; the communication unit is also used to receive a first response message, the first response message being used to indicate that the session corresponding to the first connection has been established.
[0072] The communication unit can perform the receiving and transmitting processes described in the third aspect above, and the processing unit can perform other processes described in the third aspect above besides receiving and transmitting.
[0073] The aforementioned communication device may be a first core network element, or a communication module in a first core network element, or a chip in a first core network element that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module, or a logical node, logical module or software that can realize all or part of the functions of the first core network element.
[0074] Ninthly, a communication device is provided. This communication device has the functions described in the fourth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the fourth aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.
[0075] In one possible design, the communication device includes: a communication unit for receiving a first request message, the first request message being used to request the establishment of a session corresponding to a first connection, the first request message including a first bearer identifier of a second connection, wherein the first connection and the second connection are associated, the APN of the first connection and the second connection are both IMS, and the first connection and the second connection are both connections between a narrowband IoT device and a second core network element; the communication unit is also used to send a first response message, the first response message being used to indicate that the session corresponding to the first connection has been established.
[0076] The communication unit can perform the receiving and transmitting processes in the fourth aspect mentioned above, and the processing unit can perform other processes in the fourth aspect mentioned above besides receiving and transmitting.
[0077] The aforementioned communication device may be a second core network element, or a communication module in a second core network element, or a chip in a second core network element that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module, or a logical node, logical module or software that can realize all or part of the functions of the second core network element.
[0078] A tenth aspect provides a communication device. The communication device includes at least one processor. The at least one processor is capable of executing a computer program or instructions, which, when executed, cause the communication device to implement the methods in any possible design or implementation of any of the first to fifth aspects described above.
[0079] In one possible design, the communication device may further include at least one interface circuit. This interface circuit is used to implement communication functions within the communication device and / or communication functions between the communication device and other devices or components.
[0080] In one possible design, the communication device may further include at least one interface circuit and / or at least one memory. The at least one processor is coupled to the at least one memory. The at least one memory is used to store part or all of the necessary computer programs or instructions for implementing the functions involved in any of the first to fifth aspects described above. The interface circuit is used to implement the communication functions within the communication device and / or the communication functions between the communication device and other devices or components.
[0081] In one possible design, the at least one processor is used to communicate with other devices or components through the at least one interface circuit.
[0082] The aforementioned communication device may be a narrowband IoT device, or a communication module in a narrowband IoT device, or a chip in a narrowband IoT device that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module, or a logical node, logical module or software that can realize all or part of the functions of a narrowband IoT device.
[0083] The aforementioned communication device may be a core network element (or a first core network element, or a second core network element), or a communication module in a core network element (or a first core network element, or a second core network element), or a chip in a core network element (or a first core network element, or a second core network element) that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module, or a logical node, logical module, or software that can realize all or part of the functions of a core network element (or a first core network element, or a second core network element).
[0084] Eleventhly, a communication system is provided. This communication system includes core network elements for performing the method described in the second aspect or any possible implementation thereof.
[0085] In one implementation, the communication system further includes a narrowband Internet of Things (IoT) device for performing the method of the first aspect or any possible implementation of the first aspect described above.
[0086] In a twelfth aspect, a communication system is provided. It includes: a first core network element and a second core network element, wherein the first core network element is used to execute the method of the third aspect or any possible implementation thereof, and the second core network element is used to execute the method of the fourth aspect or any possible implementation thereof.
[0087] In one implementation, the communication system further includes a narrowband Internet of Things (IoT) device for sending a second request message to a first core network element, the second request message being used to request the establishment of a first connection, the second request message including a first bearer identifier of the second connection, and an APN indicating IMS carried in the second request message; and receiving a second response message from the first core network element, the second response message being used to indicate that the first connection has been established.
[0088] In a thirteenth aspect, a chip or chip system is provided. The chip or chip system includes at least one processing circuitry for executing a computer program or instructions, causing the chip or chip system to perform the methods described in the first to fifth aspects and any possible implementation thereof.
[0089] The chip or chip system may include output circuits or interfaces for transmitting information or data, and input circuits or interfaces for receiving information or data.
[0090] In a fourteenth aspect, a computer-readable storage medium is provided. This computer-readable storage medium stores computer program code or instructions, which, when read and executed by a computer, cause the method in any of the possible implementations of the first to fifth aspects to be implemented.
[0091] In a fifteenth aspect, a computer program product is provided. The computer program product includes computer program code or instructions that, when read and executed by a computer, cause the methods in any of the possible implementations of the first to fifth aspects to be implemented.
[0092] In a sixteenth aspect, a computer program is provided. When the computer program is run, it causes the methods in any of the possible implementations of the first to fourth aspects to be implemented.
[0093] It should be understood that the beneficial effects of aspects five through sixteen above can be referenced from aspects one through four above and any possible implementation thereof, and will not be elaborated here. Attached Figure Description
[0094] Figure 1 and Figure 2 This is a schematic diagram of a communication system applicable to embodiments of this application;
[0095] Figure 3 This is a schematic diagram of the system architecture of EPS applicable to the embodiments of this application;
[0096] Figure 4 This is a schematic diagram of the application framework applicable to the embodiments of this application;
[0097] Figure 5 A flowchart illustrating a method for a UE to request the establishment of a packet data network (PDN) connection is shown.
[0098] Figures 6 to 11 This is a flowchart illustrating the communication method provided in an embodiment of this application;
[0099] Figure 12 This is a schematic structural block diagram of a communication device provided in an embodiment of this application;
[0100] Figure 13 This is a schematic structural block diagram of another communication device provided in the embodiments of this application. Detailed Implementation
[0101] The technical solutions in this application will now be described with reference to the accompanying drawings.
[0102] Before introducing the scheme of this application, the following points should be noted.
[0103] First, in this application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.
[0104] Second, in this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Here, a, b, and c can each be single or multiple.
[0105] Third, in this application, the terms "first," "second," "#1," and "#2," as well as various numerical designations, are used for ease of description and are not intended to limit the scope of the embodiments of this application. For example, they are used to distinguish different messages, rather than to describe a specific order or sequence. It should be understood that such descriptions can be interchanged where appropriate to describe solutions other than those in the embodiments of this application.
[0106] Fourth, in this application, "instruction" or "for instruction" can include both direct and indirect instruction. When describing instruction information as being used to instruct A, it can include whether the instruction information directly or indirectly instructs A, but does not necessarily mean that the instruction information carries A.
[0107] The indication methods involved in the embodiments of this application should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. Moreover, the sending period and / or sending time of these sub-information can be the same or different. This application does not limit the sending method, for example.
[0108] The "instruction information" in the embodiments of this application can be an explicit instruction, that is, a direct instruction through signaling, or an instruction obtained by combining other rules or parameters with the parameters indicated by the signaling, or by deduction. It can also be an implicit instruction, that is, an instruction obtained based on rules or relationships, or based on other parameters, or by deduction. This application does not specifically limit it in this regard.
[0109] Fifth, in this application, "protocol" can refer to a standard protocol in the field of communications, such as fifth-generation (5G) protocols. th This application does not limit the scope of network protocols such as generation (5G), New Radio (NR) protocols, and related protocols applied in future communication systems. "Predefined" may include predefined terms, such as protocol definitions. "Preconfiguration" can be achieved by pre-storing corresponding codes, tables, or other means of indicating relevant information in the device; this application does not limit the implementation method.
[0110] Sixth, in this application, terms such as "message," "information," "signal," or "information element (IE, which may be abbreviated as information element)" can be used interchangeably. There is no limitation on the name of the message or information, as long as it can achieve the corresponding function.
[0111] "Sending information to XX (device)" can be understood as the destination of the information being that device. This can include sending information to that device directly or indirectly. "Receiving information from XX (device), or receiving information from XX (device)" can be understood as the source of the information being that device. This can include receiving information from that device directly or indirectly. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly, and will not be elaborated further here.
[0112] "Communication" can also be described as data transmission, information transmission, data processing, etc. "Transmission" includes sending and / or receiving. "Transmission" can be described as output. "Sending" can also be understood as the output of a chip interface, and "receiving" can be understood as the input of a chip interface. In other words, "sending" or "receiving" can occur between devices, for example, device 1 and device 2 sending or receiving data via an air interface. "Sending" or "receiving" can also occur within a device, for example, sending or receiving data between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.
[0113] For example, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logic module within a device sending information to another logic module. For instance, "device 1 sending information" can be understood as device 1 sending information to device 2, or it can be understood as logic module 1 within device 1 sending information to logic module 2 within device 1. Similarly, "receiving information" can be understood as device 1 receiving information from device 2, or it can also be understood as logic module 1 within device 1 receiving information from logic module 2. For instance, "device 1 receiving information" can be understood as device 1 receiving information from device 2, or it can be understood as logic module 1 within device 1 receiving information from logic module 2 within device 1.
[0114] Seventh, in this application, the words "exemplarily," "for example," etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the word "example" is intended to present concepts in a concrete manner. In the embodiments of this application, "of," "corresponding, relevant," "corresponding," and "associate" may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinctions are emphasized.
[0115] The following describes the communication system to which this application applies.
[0116] The technical solutions of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, 5G systems, New Radio (NR) systems, and future communication systems. The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems.
[0117] In a communication system, a device can send signals to or receive signals from another device. These signals may include reference signals, information, signaling, or data. In this application, "device" can be replaced by an entity, network entity, communication equipment, communication module, node, or communication node.
[0118] Figure 1 This is a schematic diagram of a communication system applicable to an embodiment of this application. For example... Figure 1 As shown, the communication system 100 includes at least one terminal (such as...) Figure 1 The 120a-120j, collectively referred to as 120), radio access network (RAN), and core network (CN) 200. The RAN includes at least one RAN node (e.g., Figure 1 110a and 110b in the RAN are collectively referred to as 110. The RAN may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices. Figure 1 (Not shown in the image). Terminal 120 is connected to RAN node 110 wirelessly. RAN node 110 is connected to core network 200 wirelessly or via wired connection. The core network equipment in core network 200 and RAN node 110 in RAN can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.
[0119] RAN can be used for the third-generation partner program (3 rd Cellular systems related to the Generation Partnership Project (3GPP), such as fourth-generation (4G) cellular systems. th RAN can be a generation (4G) mobile communication system, a 5G mobile communication system, or a future-oriented evolution system. RAN can also be an open radio access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi / WIFI) system. RAN can also be a communication system that integrates two or more of the above systems.
[0120] RAN node 110, sometimes also referred to as network equipment, access network equipment, RAN entity, or access node, constitutes part of the communication system and is used to help terminals achieve wireless access. Multiple RAN nodes 110 in communication system 100 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative, for example... Figure 1 Network element 120i can be a helicopter or a drone, and it can be configured as a mobile base station. For terminals 120j that access the RAN through network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes referred to as communication devices, for example... Figure 1 Network elements 110a and 110b can be understood as communication devices with base station functions, while network elements 120a-120j can be understood as communication devices with terminal functions.
[0121] In one possible scenario, a RAN node can be a base station (BS), an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a base station in a future mobile communication system, or an access node in a WiFi system, etc. Figure 1 110a), micro base stations or indoor stations (such as Figure 1 In V2X technology, the access network equipment can be a relay node or donor node (e.g., 110b), or a wireless controller in a CRAN scenario. Optionally, the RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in V2X technology can be an RSU.
[0122] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be central units (CU), distributed units (DU), CU-control plane (CU-CP), CU-user plane (CU-UP), radio units (RU), or CU-radio units (CU-RU), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radioheads (RRHs).
[0123] In different systems, CU (including open CU-CP (O-CU-CP) and open CU-UP (O-CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called an open central unit (O-CU), DU can also be called an open distributed unit (O-DU), CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.
[0124] Terminal 120 can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. A terminal can also be referred to as user equipment (UE), user device, access terminal, user unit, user station, mobile station, mobile station (MS), remote station, remote terminal, mobile device, user terminal, terminal unit, terminal station, terminal device, wireless communication equipment, user agent, or user equipment. A terminal typically contains a communication module, circuit, or chip that performs the corresponding communication functions. The terminal may also be configured with program instructions for performing these communication functions.
[0125] For example, the terminal in this application embodiment may be a mobile phone, a personal digital assistant (PDA) computer, a laptop computer, a tablet computer, a drone, a computer with wireless transceiver capabilities, an MTC terminal, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an IoT terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home (such as a game console, smart TV, smart speaker, smart refrigerator, and fitness equipment), a transportation vehicle with wireless communication capabilities, a communication module, or a roadside unit (RSU) with terminal capabilities.
[0126] The RAN and terminal 120 can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenario in which the RAN and terminal 120 are located.
[0127] Communication between access network devices and terminal devices follows a specific protocol layer structure. This protocol layer may include a control plane protocol layer and a user plane protocol layer. The control plane protocol layer may include at least one of the following: Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, or Physical (PHY) layer, etc. The user plane protocol layer may include at least one of the following: Service Data Adaptation Protocol (SDAP) layer, PDCP layer, RLC layer, MAC layer, or Physical layer, etc.
[0128] The correspondence between network elements and their achievable protocol layer functions in the ORAN system can be found in Table 1 below.
[0129] Table 1
[0130] ORAN network elements 3GPP protocol layer functions O-CU-CP RRC+PDCP-Control Plane (PDCP-C) O-CU-UP SDAP+PDCP - User Plane (PDCP-U) O-DU RLC+MAC+PHY-high O-RU PHY-low
[0131] CN 200 can be a 5G core network or an evolved 5G core network. Taking a 5G core network as an example, CN 200 includes access and mobility management (AMF) network elements responsible for mobility management and access management services; session management (SMF) network elements responsible for session management; user plane (UPF) network elements responsible for user plane packet routing and QoS control; and policy control (PCF) network elements. These core network elements can work independently or be combined to implement certain control functions. For example, AMF, SMF, and PCF can be combined into a single core network device.
[0132] The communication system 100 provided in this application may further include AI network elements for implementing some or all AI-related operations. AI network elements may also be referred to as AI nodes, AI devices, AI entities, AI modules, AI models, or AI units, etc. The AI network elements may be built into the network elements of the communication system. For example, an AI network element may be an AI module built into: access network equipment, core network equipment, cloud server, or operation, administration, and maintenance (OAM) to implement AI-related functions. The OAM may act as the network management system for the core network equipment and / or the access network equipment. Alternatively, the AI network element may also be an independently configured network element in the communication system. Optionally, the terminal or its built-in chip may also include an AI entity for implementing AI-related functions.
[0133] Satellites can provide communication, navigation, and positioning services to terminal devices via multiple beams. In this scenario, satellites include low Earth orbit (LEO), medium Earth orbit (MEO), highly elliptical orbit (HEO), and geostationary or geostationary orbit (GEO) satellites. Satellites use multiple beams to cover the service area, and different beams can communicate via one or more of time-division, frequency-division, and space-division multiplexing. Satellites communicate wirelessly with terminal devices through broadcast communication signals and navigation signals, and can also communicate wirelessly with ground station equipment. The satellites mentioned in this application's embodiments can be satellite base stations or satellite stations, and may also include orbital receivers or repeaters for information relay, or network-side equipment mounted on the satellite. For ease of description, in this application's embodiments, satellites with access network capabilities are referred to as satellite access network equipment, or base stations deployed on satellites are referred to as satellite base stations or satellite stations.
[0134] Figure 2 This is a schematic diagram of a communication system applicable to an embodiment of this application. For example... Figure 2 As shown, this communication system uses an NTN as an example. As an example, system 200 may include terminal equipment, satellite stations (e.g., satellite stations 201 and 202), ground stations or gateways (GW), core network, data network (DN), 5G NR, Xn interface, NG interface, etc. The data network DN, also known as a packet data network (PDN), is typically a network located outside the operator's network, such as a third-party network. In some implementations, the DN may also be deployed by the operator, meaning the DN is part of the public land mobile network (PLMN). This application does not restrict whether the DN belongs to the PLMN. Various services can be deployed on the DN, providing data and / or voice services to terminal equipment.
[0135] For example, the data network can be an IMS network. Under this architecture, terminal devices can access the mobile network via satellite stations (e.g., satellite station 201 and satellite station 202) and then access the IMS network through the mobile network to enjoy voice services. IMS is a multimedia service that can meet users' needs for newer and more diverse multimedia services. IMS is considered a core technology of future networks and an important way to solve the convergence of mobile and fixed networks and introduce differentiated services such as the triple convergence of voice, data, and video.
[0136] For example, the terminal device communicates with the satellite station via a wireless link, and the satellite station communicates with the core network via a wireless link. For instance, the satellite station transmits downlink data to the terminal, where the data is encoded using channel coding, and the channel-coded data is then modulated by constellation before being transmitted to the terminal. The terminal device also transmits uplink data to the satellite station, which can also be encoded using channel coding, and the encoded data is then modulated by constellation before being transmitted to the satellite station. Simultaneously, a wireless link exists between the satellites to facilitate signaling interaction and user data transmission between satellite stations 201 and 202.
[0137] Ground stations provide functions similar to gateways in terrestrial communication systems, such as establishing connections with terminal devices and communicating with servers. Their primary responsibility is forwarding signaling and service data between satellite stations and the core network. Additionally, ground stations perform functions such as satellite station detection and fault diagnosis, packet switching of communication data, and interface protocol conversion. For example, satellite base station 201 connects to a ground station, which can also be referred to as a surface gateway station (such as an NTN Gateway), gateway station, signaling gateway station, or ground station equipment.
[0138] Taking 5G networks as an example, ground-based terminal equipment can communicate with satellite stations (e.g., satellite stations 201 and 202) using the 5G New Radio interface. Satellite stations can wirelessly communicate with terminal equipment via broadcast communication signals and navigation signals. The connection between the terminal equipment and the satellite station can be called a service link, and the connection between the satellite station and the ground station can be called a feeder link. Satellite stations can wirelessly communicate with ground stations via NG interfaces (e.g., for exchanging signaling such as non-access stratum (NAS) signals with the core network and user service data), and satellite stations can also communicate with the core network through ground stations. Simultaneously, inter-satellite links (ISLs) exist between satellites to facilitate signaling interaction and user data transmission between 5G access network devices. For example, satellite station 202 can wirelessly communicate with satellite station 201 via the Xn interface (e.g., for signaling interaction such as handover). Normally, the service link between the terminal equipment and the satellite station, as well as the feeder link between the satellite station and the ground station, are connected. That is, uplink and downlink messages between the terminal equipment and the core network can be transmitted through the satellite station and the ground station.
[0139] Figure 3 The diagram illustrates the system architecture of EPS. Under this architecture, the UE can access the mobile network via satellite, and then access the IMS network via the mobile network to enjoy voice services. Figure 3 As shown, the architecture may include the following network entities.
[0140] 1. Evolved Universal Terrestrial Radio Access Network (EUTRAN): A network composed of multiple evolved node Bs (eNodeBs) that implements radio physical layer functions, resource scheduling and radio resource management, radio access control, and mobility management functions. eNodeBs can connect to each other via the X2 interface, which can be used to transmit data during X2-based handover. eNodeBs connect to the user plane interface S1-U and the serving gateway (SGW), using the General Packet Radio System General Tunneling Protocol user plane (GTP-U) to transmit user data; they connect to the Mobility Management Entity (MME) via the control plane interface S1-MME, using the S1-application protocol (S1-AP) to implement radio access bearer control and other functions.
[0141] 2. MME: The key control node of the LTE access network, responsible for UE authentication, paging of idle mode UEs, and marking processes including retransmission. It is mainly responsible for all control plane functions of user session management, including NAS signaling and security, management of the tracking area list, and selection of packet data network gateways PGW and SGW.
[0142] 3. SGW: It has functions such as local mobility anchor point for inter-eNodeB handover, mobility anchor for inter-3GPP mobility, packet routing and forwarding, transport level packet marking, and consideration of inter-carrier billing. It is mainly responsible for data transmission, forwarding and routing handover of user equipment, and serves as the local mobility anchor point for user equipment when handover between eNodeBs (for each user equipment, there is one SGW serving it at each time).
[0143] 4. PGW: The connection between the UE and an external packet data network (PDN). A UE can connect to multiple PDN gateways simultaneously to access multiple packet data networks. The PDN gateway performs policy enforcement, packet filtering for each user, charging support, lawful interception, and packet masking. As the anchor point for PDN connections, it is responsible for UE IP address allocation, UE data packet filtering, rate control, and generating charging information.
[0144] 5. Serving GPRS Supporting Node (SGSN): This is the access node for the 2G access network GSM / EDGE radio access network (GERAN), the 3G access network universal terrestrial radio access network (UTRAN), and the EPS core network EPC. It is responsible for establishing bearers and forwarding data from GERAN and UTRAN to the EPC.
[0145] 6. Home subscriber server (HSS): Stores mobile subscriber subscription data.
[0146] 7. Policy and Charging Rules Function (PCRF): Responsible for charging management and policy control, including policy and charging control (PCC) rules and QoS rules.
[0147] In addition, the IMS network mainly involves the following network functional entities:
[0148] 8. The proxy-call session control function (P-CSCF) is the first access point in the IMS system. The P-CSCF behaves like a proxy, accepting requests and either serving them internally or forwarding them upwards.
[0149] 9. The serving-call session control function (S-CSCF) performs session control services for the UE. It maintains session state according to the network operator's needs to support services.
[0150] For example, the satellite station in this application may also be a CU, DU, or RU, or an O-RAN node mounted on a satellite, without limitation.
[0151] Figure 4 This is a schematic diagram of an application framework applicable to embodiments of this application. For example... Figure 4 As shown in (a), network elements in the communication system are connected via interfaces (e.g., NG, Xn) or air interfaces. These network element nodes, such as core network equipment, access network nodes (RAN nodes), terminals, or one or more devices in the OAM, are equipped with one or more AI modules (for clarity, ...). Figure 4(Only one is shown in (a)). The access network node can be a single RAN node or can include multiple RAN nodes, such as CU and DU. The CU and / or DU can also be equipped with one or more AI modules. Optionally, the CU can also be split into CU-CP and CU-UP. One or more AI models are set in CU-CP and / or CU-UP.
[0152] The AI module is used to implement corresponding AI functions. AI modules deployed in different network elements can be the same or different. Depending on the parameter configuration, the AI module can implement different functions. The AI module model can be configured based on one or more of the following parameters: structural parameters (e.g., at least one of the following: number of neural network layers, neural network width, inter-layer connections, neuron weights, neuron activation function, or bias in the activation function), input parameters (e.g., type and / or dimension of input parameters), or output parameters (e.g., type and / or dimension of output parameters). The bias in the activation function can also be referred to as the neural network bias.
[0153] An AI module can have one or more models. A model can infer an output, which includes one or more parameters. The learning, training, or inference processes of different models can be deployed on different nodes or devices, or they can be deployed on the same node or device.
[0154] Network devices can be network devices equipped with one or more AI modules. These network devices can include core network devices, RAN nodes, or one or more devices within the OAM (Operational Network Access Center). For example, an AI module can be... Figure 4 The RIC shown in (b) can be a near-real-time RIC (near-RT RIC) or a non-real-time RIC (Non-RTRIC). For example, a near-real-time RIC is set in a RAN node (e.g., in a CU or DU), while a non-real-time RIC is set in an OAM, a cloud server, a core network device, or other access network devices. The RIC can be reassembled into a dataset by obtaining subsets from multiple terminal devices from RAN nodes (e.g., CU, CU-CP, CU-UP, DU, and / or RU), and then trained based on the dataset. Exemplarily, near-real-time RICs and non-real-time RICs can also be set up separately as a network element, and the access network device can be either a near-real-time RIC or a non-real-time RIC.
[0155] like Figure 4As shown in (b), the communication system includes an access network node (CU, DU, and RU shown in the figure) and a terminal, as well as a RIC. For example, the RIC could be... Figure 4 The AI module shown in (a) can be used to implement AI-related functions. The RIC includes near real-time RIC and non-real-time RIC. The non-real-time RIC primarily processes non-real-time information, such as data that is not sensitive to latency, with latency in the order of seconds. The real-time RIC primarily processes near real-time information, such as data that is relatively sensitive to latency, with latency in the order of tens of milliseconds.
[0156] The near real-time RIC is used for model training and inference. For example, it can be used to train an AI model and then use that AI model for inference. The near real-time RIC can obtain network-side and / or terminal-side information from RAN nodes (e.g., CU, CU-CP, CU-UP, DU, and / or RU) and / or terminals. This information can be used as training data or inference data. Optionally, the near real-time RIC can deliver inference results to RAN nodes and / or terminals. Optionally, inference results can be exchanged between CU and DU, and / or between DU and RU. For example, the near real-time RIC delivers the inference result to the DU, and the DU sends it to the RU.
[0157] The non-real-time RIC is also used for model training and inference. For example, it can be used to train an AI model and then use that model for inference. The non-real-time RIC can obtain network-side and / or terminal-side information from RAN nodes (e.g., one or more of CU, CU-CP, CU-UP, DU, or RU) and / or terminals. This information can be used as training data or inference data, and the inference results can be delivered to the RAN nodes and / or terminals. Optionally, inference results can be exchanged between CU and DU, and / or between DU and RU; for example, the non-real-time RIC delivers the inference results to the DU, which then forwards them to the RU.
[0158] The near real-time RIC and non-real-time RIC can also be set up as separate network elements. Optionally, the near real-time RIC and non-real-time RIC can also be part of other devices. For example, the near real-time RIC can be set in the RAN node (e.g., in CU, DU), while the non-real-time RIC can be set in the OAM, cloud server, core network device, or other network device.
[0159] It should be understood that the above Figures 1 to 4The communication system or application framework illustrated uses a satellite communication system combined with a 5G system as an example. This is a simplified diagram for ease of understanding, and the satellite communication system may also include other devices, which are not shown in the diagram. Furthermore, when a satellite communication system is combined with other terrestrial communication systems, the network elements and interfaces involved may have other names, and this application embodiment does not specifically limit them.
[0160] Non-terrestrial networks, including satellite networks, high-altitude platforms, and drones, offer significant advantages such as global coverage, long-distance transmission, flexible networking, convenient deployment, and independence from geographical limitations. They have been widely applied in maritime communication, positioning and navigation, disaster relief, scientific experiments, video broadcasting, voice calls, and Earth observation. Thanks to their wide coverage and ease of deployment, satellite communication can compensate for the shortcomings of terrestrial cellular network coverage, allowing users in remote areas such as deserts and rainforests to access the network and enjoy services like voice calls. Narrowband IoT devices offer advantages in low cost and low power consumption. Connecting narrowband IoT devices to satellites helps reduce the cost of satellite phones while effectively reducing power consumption of terminal devices and extending communication time.
[0161] Figure 5 A flowchart illustrating a method for a UE to request the establishment of a Packet Data Network (PDN) connection is shown. Figure 5 As shown, the process includes several steps; for details not covered, please refer to existing protocols.
[0162] S501, the UE sends a PDN connection request to the mobility management entity (MME);
[0163] Correspondingly, the MME receives a PDN connection request from the UE.
[0164] Specifically, the PDN connection request is used to request the establishment of a PDN connection based on control plane optimized transport, or in other words, the PDN connection request is used to trigger the MME to create a session.
[0165] For example, for narrowband devices or narrowband IoT devices, the UE can carry indication information in the PDN connection request. This indication information is used to indicate that the UE supports CP CIoT EPS optimization. In other words, the UE can optimize the control plane of CIoT EPS.
[0166] As is understandable, the Cellular Internet of Things (CIoT) is an Internet of Things that enables CIoT terminals to access mobile communication networks through narrowband Internet of Things (NB-IoT) access technology or enhanced machine-type communication (eMTC) access technology. For example, a CIoT system could be an evolved packet system (EPS).
[0167] S502, the MME sends a session creation request to the serving gateway (SGW);
[0168] Correspondingly, the SGW receives a session creation request from the MME.
[0169] For example, the MME triggers the SGW to create a data transmission channel between the SGW and the PDN gateway.
[0170] S503 establishes a data transmission channel between SGW and PGW.
[0171] For example, the SGW sends a session creation request to the PGW to request the establishment of a data transmission channel; the PGW exchanges information with the PCRF (IP-CAN session) to determine whether to establish a data transmission channel. Correspondingly, the PGW sends a session creation response to the SGW.
[0172] S504, the SGW sends a session creation response to the MME; correspondingly, the MME receives the session creation response from the SGW.
[0173] For example, the session creation response includes IP address information. For instance, if it is user plane data transmission, the SGW sends the IP address information to the MME for the evolved NodeB (eNodeB / eNB) to transmit user data; or, if it is CP CIoT EPS optimized data transmission, the SGW sends the IP address information to the MME for the MME to transmit user data.
[0174] S505, the MME sends a bearer establishment request or a PDN connection acceptance message to the eNB;
[0175] Correspondingly, the eNB receives a bearer establishment request or a PDN connection acceptance message from the MME.
[0176] For example, if it is a user plane data transmission, the eNB obtains the user plane address information of the SGW.
[0177] At this point, the uplink data channel has been created.
[0178] S506, the eNB sends an RRC connection reconfiguration or RRC direct transmission to the UE;
[0179] Correspondingly, the UE receives RRC connection reconfiguration or RRC direct transmission from the eNB.
[0180] S507, the UE sends an RRC connection reconfiguration complete message to the eNB;
[0181] Correspondingly, the eNB receives an RRC connection reconfiguration complete message from the UE.
[0182] That is, the eNB and UE perform an RRC reconfiguration procedure to create a data bearer corresponding to the session.
[0183] It should be noted that if the data transmission is optimized for CP CIoT EPS, then skip the following steps S506-S507.
[0184] S508, the eNB sends a bearer establishment response to the MME; correspondingly, the MME receives the bearer establishment response from the eNB.
[0185] S509, the UE sends an RRC direct transmission to the eNB; correspondingly, the eNB receives the RRC direct transmission from the UE.
[0186] S510, the eNB sends a PDN connection completion message to the MME; correspondingly, the MME receives the PDN connection completion message from the eNB.
[0187] S511, the MME sends a bearer modification request to the SGW; correspondingly, the SGW receives the bearer modification request from the MME.
[0188] For example, if it is user plane data transmission, the MME sends the eNB's address information to the SGW.
[0189] At this point, the downlink data channel has been created.
[0190] Understandably, after a UE successfully requests to establish a PDN connection, the UE can transmit data with the corresponding data network through a specific PDN connection.
[0191] S512, SGW and PGW interact to carry modification requests / responses.
[0192] S513, the SGW sends a bearer modification response to the MME; correspondingly, the MME receives the bearer modification response from the SGW.
[0193] S514, the MME sends a notification request to the HSS; correspondingly, the HSS receives the notification request from the MME.
[0194] S515, the HSS sends a notification response to the MME; correspondingly, the MME receives the notification response from the HSS.
[0195] In this implementation, the example of a UE requesting a core network element (e.g., MME, SGW, PGW, etc.) to establish a PDN connection supporting control plane transmission is used for illustration. Optionally, the UE can request a core network element (e.g., MME, SGW, PGW, etc.) to establish a PDN connection supporting user plane transmission; this is not limited. Considering the advantages of low cost and low power consumption of narrowband IoT devices, accessing satellite via narrowband IoT devices helps reduce the cost of satellite phones and can also effectively reduce the power consumption of terminal devices and extend communication time. Therefore, supporting voice services via satellite access for narrowband IoT devices has become an industry trend. However, due to limitations in processing power, how to support narrowband IoT devices in obtaining voice services is a problem that needs to be solved.
[0196] In view of this, this application provides a communication method and a communication device that can provide voice services for narrowband Internet of Things (IoT) devices, thereby improving the voice call quality of the devices.
[0197] Below, in conjunction with the appendix Figures 6 to 10 The communication method provided in the embodiments of this application is described in detail. It is understood that this application uses a narrowband IoT device and a core network element (or a first core network element, or a second core network element) as examples to illustrate the execution subject of the interaction, but this application does not limit the execution subject of the interaction. For example, the method executed by the narrowband IoT device in this application can be executed by the narrowband IoT device or its communication module and / or computing module, or by circuits or chips in the narrowband IoT device responsible for communication functions (such as modem chips, also known as baseband chips, or SoC chips or SIP chips containing modem cores), or by circuits or chips in the narrowband IoT device responsible for communication and / or computing functions (such as GPUs, AI processors, or ASICs), or by logic nodes, logic modules, or software capable of implementing all or part of the functions of the narrowband IoT device. The method executed by the core network element in this application may be executed by the core network element or the communication module and / or computing module in the core network element, or the circuit or chip in the core network element responsible for communication functions, or the logic node, logic module or software that can realize all or part of the core network element functions, without limitation.
[0198] Figure 6This is a schematic flowchart of a communication method 600 provided in this application, mainly illustrating a narrowband IoT device requesting a core network element to establish a first connection supporting both user plane and control plane transmissions. Specifically, this first connection can be used for the transmission of IMS SIP signaling and IMS voice data. Figure 6 As shown, the method includes the following steps; for details not covered, please refer to existing protocols.
[0199] S610, narrowband IoT devices send a first request message (e.g., PDN connectivity request) to core network elements;
[0200] Correspondingly, the core network element receives the first request message from the narrowband IoT device.
[0201] The first request message is used to request the establishment of a first connection (e.g., a PDN connection). The first connection supports user plane-based transmission and control plane-based transmission. The APN carried in the first request message indicates IMS (e.g., APN = IMS). The first connection is a connection between a narrowband IoT device and a core network element (e.g., the second core network element hereinafter).
[0202] In other words, the first request message is used to request the establishment of the first connection as a connection that simultaneously supports CP CIoT EPS optimization and UP CIoT EPS optimization transmission. That is, the first connection is used to transmit signaling and / or data related to IMS services (e.g., voice services). The IMS services can be user plane-based transmissions (e.g., IMS voice data) or control plane-based transmissions (e.g., SIP signaling).
[0203] Understandably, this method is applicable to scenarios where narrowband IoT devices access the network via satellite and perform IMS voice services, especially in scenarios where access is via narrowband, high-orbit satellites (e.g., narrowband non-terrestrial networks (NB-NTN), or narrowband-geostationary earth orbit (NB-GEO), NB-IoT NTN, or NB-IoT(GEO)) to perform IMS voice services.
[0204] Optionally, the first bearer of the first connection (also referred to as the default bearer of the first connection) may be the same type as the bearer type for performing CPCIoT EPS optimization, or it may be the same type as the bearer type for UP CIoT EPS optimization, without limitation.
[0205] For example, the narrowband IoT device can be a UE, the core network element can be an MME, or the core network element can be a PGW, without limitation.
[0206] Optionally, the first request message may include indication information (e.g., CP+UP CIoT indication) to indicate that the first connection supports both user plane-based and control plane-based transmissions.
[0207] In other words, the first connection supports both user plane-based and control plane-based transmissions, and this can be indicated directly or indirectly, without limitation. For example, a narrowband IoT device can directly carry indication information in the first request message to instruct the narrowband IoT device to request the establishment of a first connection that supports both user plane-based and control plane-based transmissions; and / or, the first request message sent by the narrowband IoT device itself can indicate that the first connection supports both user plane-based and control plane-based transmissions.
[0208] For example, a narrowband IoT device sends a first request message to a core network element via a base station. For instance, the narrowband IoT device may send a first request message to the base station to request the establishment of the first connection. This first request message carries APN=IMS, and optionally, may also carry indication information. Correspondingly, the base station sends a first request message to the core network element to request the establishment of the first connection.
[0209] In one possible implementation, when a narrowband IoT device accesses NB-IoT via satellite (e.g., a geostationary orbit satellite), it sends a first request message. That is, after the narrowband IoT device accesses NB-IoT via satellite, it can initiate a request to the core network element to establish a first connection to support the transmission of SIP signaling and IMS voice data.
[0210] In S620, the core network element determines to establish the first connection based on the first information.
[0211] In other words, the core network element determines the session corresponding to the establishment of the first connection based on the first information. The first information includes at least one of the following: the RAT type, APN, subscription information of the narrowband IoT device, or location information of the narrowband IoT device.
[0212] Example 1: When the RAT type indicates that a narrowband IoT device accesses NB-IoT via satellite, the core network element determines the session corresponding to the first connection.
[0213] Example 2: When the APN indicates IMS (e.g., APN = IMS), the core network element determines to establish the session corresponding to the first connection.
[0214] Example 3: When the subscription information of a narrowband IoT device includes satellite voice communication service, the core network element determines to establish the session corresponding to the first connection. Here, satellite voice communication service can be understood as: the narrowband IoT device supports accessing IMS services via satellite, or in other words, the narrowband IoT device supports making voice / video calls or sending text messages via satellite.
[0215] Example 4: When the location information of a narrowband IoT device indicates that the current location of the narrowband IoT device is within the coverage area of a satellite or narrowband IoT network, or in other words, when the narrowband IoT device is allowed to initiate communication services at its current location, the core network element determines to establish a session corresponding to the first connection.
[0216] Understandably, the above examples are merely illustrative for ease of understanding and do not exclude other solutions. Furthermore, the various examples described above can be implemented independently or in combination, without limitation. For instance, when the RAT type indicates that the narrowband IoT device accesses NB-IoT via satellite, and the APN indicates IMS, i.e., when the narrowband IoT device accesses the narrowband IoT via satellite and requests IMS services, the core network element determines to establish the first connection; that is, the core network element determines to establish the session corresponding to the first connection.
[0217] In one possible implementation, if the first request message in step S610 carries indication information, the core network element determines whether to establish the session corresponding to the first connection based on the first information. That is, the core network element can determine whether to establish the session corresponding to the first connection based on the first information, or it can determine whether to establish the session corresponding to the first connection based on both the indication information and the first information; there is no limitation on this.
[0218] It is understood that the technical solution of this application is for situations where the core network element determines to establish a session corresponding to the first connection. Optionally, if the core network element determines not to establish a session corresponding to the first connection, for example, based on the first information, then subsequent steps do not need to be performed. Optionally, the core network element can send a reason value to the narrowband IoT device to indicate that the first connection cannot be established or to reject the connection establishment request of the narrowband IoT device. For example, the reason value may include at least one of the following: a RAT type indicating that the narrowband IoT device has not accessed NB-IoT or has not received NB-IoT via satellite; or, the subscription information of the narrowband IoT device indicating that the narrowband IoT device does not support voice communication; or, the current location of the narrowband IoT device is not allowed to initiate communication services, etc., without limitation.
[0219] For example, after determining to establish a first connection, a core network element can execute the session establishment process corresponding to that first connection. For instance, a core network element (e.g., MME) can initiate a session establishment request for the first connection to a first core network element (e.g., SGW). Correspondingly, a session corresponding to the first connection is established between the first core network element and the second core network element (e.g., PGW). The specific session establishment process is not limited. The session establishment request message (e.g., create session request) sent by the core network element (e.g., MME) can carry the aforementioned indication information. Optionally, the core network element (e.g., MME) can also carry the MME address and tunnel endpoint identifier (TEID) for S11-U, as well as the EPS bearer identity (EBI) assigned by the core network element to the first bearer (or default bearer) of the first connection, such as EBI#1, in the session creation request message. Optionally, the aforementioned indication information can also be carried during the information exchange process between the first and second core network elements, without limitation.
[0220] Optionally, the core network element, the first core network element, or the second core network element may store information that the first connection supports both user plane-based and control plane-based transmissions (which may be denoted as information #a).
[0221] It should be noted that the above step S620 is optional. That is, after receiving the first request message from the narrowband IoT device, the core network element can execute the above step S620, that is, determine whether to establish the first connection based on the first information; or, it can choose not to execute the above step S620, that is, establish the first connection by default, without any limitation.
[0222] S630, the core network element sends a first response message (e.g., PDN ConnectivityAccept) to the narrowband IoT device;
[0223] Correspondingly, narrowband IoT devices receive the first response message from the core network element.
[0224] The first response message is used to indicate acceptance of the first connection establishment, and the first response message may carry the aforementioned indication information.
[0225] For example, a core network element can send a first response message to a narrowband IoT device via a base station. For instance, a core network element can send a first response message to a base station to indicate acceptance of a first connection establishment; correspondingly, the base station sends a first response message to the narrowband IoT device.
[0226] Optionally, the first response message sent by the core network element may be carried in the initial context request message, and the first response message sent by the base station may be carried in the RRC reconfiguration message; there are no restrictions on this.
[0227] It should be noted that the process of establishing the first bearer of the first connection involved in this application can refer to existing relevant descriptions, such as the establishment of the first bearer of the first connection between the narrowband IoT device and the base station through information interaction. For the sake of brevity, it will not be described here.
[0228] Based on the above implementation, once the first connection (or the first bearer of the first connection) between the narrowband IoT device and the core network element is established, the narrowband IoT device can transmit SIP signaling through the first bearer (or default bearer) of the first connection. For example, the narrowband IoT device can initiate a registration process or a call setup process to the IMS network element by sending SIP signaling, without limitation. The SIP signaling may carry at least one of the following: user identifier, access network information, or call identifier.
[0229] In this application, assuming that the first bearer of the first connection is used to transmit IMS Session Initiation Protocol (SIP) signaling, when a narrowband physical network (NB-IoT) device initiates a call setup process, i.e., when the NB-IoT device has a need to transmit IMS voice data, the NB-IoT device and the core network element can initiate a process to establish a second bearer for the first connection to transmit IMS voice data. In other words, the NB-IoT device can transmit IMS SIP signaling through the first bearer of the first connection, and / or transmit IMS voice data through the second bearer of the first connection; that is, the first connection simultaneously supports both user plane-based and control plane-based transmissions. The second bearer of the first connection can be referred to as the dedicated bearer of the first connection. Optionally, the method may further include the following steps S640-S650.
[0230] S640, the core network element sends a second request message (e.g., bearer setup request) to the narrowband IoT device;
[0231] Correspondingly, the narrowband IoT device receives a second request message from the core network element.
[0232] The second request message is used to request the establishment of a second bearer for the first connection, and the second bearer of the first connection is used to transmit IMS voice data.
[0233] For example, the core network element accepts the second bearer for creating the first connection based on the information #a saved in step S620 above, and sends a second request message to the narrowband IoT device.
[0234] Optionally, before executing step S640, the Proxy-Call Session Control Function (P-CSCF) in the IMS network can send an Authentication Authorization Request (AAR) message to the Policy and Charging Rules Function (PCRF) to request the establishment of a second bearer (or dedicated bearer) for the first connection, used to transmit IMS voice data. The Authentication Authorization Request message includes at least one of the following: the user's signaling address, media bandwidth, media type, or media description information. Optionally, the PCRF can send an Authentication Authorization Answer (AAA) message to the P-CSCF.
[0235] Correspondingly, after receiving the authentication / authorization request message, the PCRF makes a policy decision, provides authorized QoS, and sends a re-authentication / authorization request (RAR) message to the second core network element (e.g., PGW). The re-authentication / authorization request message carries QoS and PCC rules.
[0236] Correspondingly, after receiving the re-authentication / authorization request message, the second core network element can, based on the information #a saved in step S620 above, accept the request to establish the second bearer for the first connection, and send a bearer creation request message to the first core network element (e.g., SGW) to request the establishment of the second bearer for the first connection. The linked EPS bearer (LBI) identifier carried in the bearer creation request message is set to EBI#1. Optionally, the second core network element can send a re-authentication / authorization answer (RAA) message to the PCRF.
[0237] Correspondingly, after receiving the bearer creation request message, the first core network element can accept the second bearer for creating the first connection for EBI#1 based on the information #a saved in step S620 above, and send a bearer creation request message to the core network element (e.g., MME) to request the establishment of the second bearer for the first connection, wherein the LBI carried in the bearer creation request message is set to EBI#1.
[0238] Correspondingly, after receiving the bearer setup request message, the core network element can, based on the information #a saved in step S620 above, accept the request to create a second bearer for the first connection of EBI#1, and send a bearer setup request message to the base station to request the establishment of the second bearer for the first connection. Further, the base station sends an RRC reconfiguration message to the narrowband IoT device to establish the second bearer for the first connection.
[0239] S650, narrowband IoT devices send a second response message (e.g., bearer setupresponse) to core network elements;
[0240] Correspondingly, the core network element receives a second response message from the narrowband IoT device.
[0241] The second response message is used to indicate that the second bearer of the first connection has been established.
[0242] For example, narrowband IoT devices can send a second response message to the core network via a base station.
[0243] Optionally, core network elements can also send a bearer creation response message to the first core network element, and the first core network element can also send a bearer creation response message to the second core network element. Optionally, the second core network element can also send a re-authentication / authorization request (RAR) message to the PCRF, and correspondingly, the PCRF sends a re-authentication / authorization response (RAA) message to the second core network element.
[0244] In this application, the first bearer of the first connection can be a bearer based on the control plane transmission, and the second bearer of the first connection can be a bearer based on the user plane transmission; or, the first bearer of the first connection is a bearer based on the user plane transmission, and the second bearer of the first connection is a bearer based on the control plane transmission. For example, a narrowband IoT device can transmit SIP signaling using CP CIoT EPS optimization based on this first connection, and / or transmit IMS voice data using UP CIoT EPS optimization.
[0245] In other words, the first bearer of the first connection in this application is used to transmit SIP signaling, which can be transmitted based on the control plane or the user plane. The second bearer of the first connection is used to transmit IMS voice data, which can be transmitted based on the control plane or the user plane, and there is no limitation on this.
[0246] Based on the above implementation, once the second bearer of the first connection between the narrowband IoT device and the core network element is established, the narrowband IoT device can transmit IMS voice data through the second bearer (or dedicated bearer) of the first connection.
[0247] Using the above method, the narrowband IoT device requests the core network element to establish a first connection for APN-indicated IMS. This first connection can support both user plane-based and control plane-based transmissions. Specifically, the narrowband IoT device can transmit SIP signaling through the first bearer of the first connection and IMS voice data through the second bearer of the first connection. In other words, the core network element creates a first connection for the narrowband IoT device that simultaneously supports CP CIoT EPS optimized transmission and UP CIoT EPS optimized transmission. That is, by creating a user plane bearer (e.g., the second bearer of the first connection) to transmit IMS voice data, QoS guarantees can be provided for the narrowband IoT device's IMS voice data, thereby improving voice call quality.
[0248] To facilitate understanding, the following will be combined with Figure 7 This document illustrates how a core network element creates a first connection for a narrowband IoT device that supports both user plane and control plane transmissions. Specifically, the narrowband IoT device can transmit SIP signaling and IMS voice data through different bearers on the same connection. In the examples below, the narrowband IoT device is represented by the UE, and the core network element by the MME. It is understood that the processes described below are merely illustrative, and the embodiments of this application are not limited thereto. Details not described below can be found above. Figure 6 The relevant descriptions in the text will not be repeated below.
[0249] Figure 7 This is a schematic flowchart of a communication method 700 provided in this application. Figure 7 As shown, the process mainly includes the following steps; for parts not described in detail, please refer to the existing agreement.
[0250] For example, assume the UE registers with the network via satellite (e.g., GEO) and is a narrowband device. In this implementation, the UE requests the MME to create a PDN connection (i.e., the first connection) using the APN as the IMS connection. It simultaneously supports CP CIoT EPS optimized transmission (i.e., control plane-based transmission) and UP CIoT EPS optimized transmission (i.e., user plane-based transmission), used for IMS Session Initiation Protocol (SIP) signaling and IMS voice data transmission, respectively. The default bearer of the PDN connection (i.e., the first bearer of the first connection) is used to transmit IMS SIP signaling, and the dedicated bearer of the PDN connection (i.e., the second bearer of the first connection) is used to transmit IMS voice data.
[0251] The following provides an example of establishing an IMS voice call for a UE, illustrating the PDN connection establishment process with steps S701-S708, and the voice call establishment process with steps S709-S719.
[0252] S701, the UE sends a PDN connection request (e.g., PDN connectivity request, i.e., the first request message) to the MME;
[0253] Correspondingly, the MME receives a PDN connection request from the UE.
[0254] For example, a PDN connection request is used to request the establishment of a PDN connection (i.e., the first connection). The PDN connection request includes an ESM message container, which carries APN=IMS. It can be understood that this PDN connection is a PDN connection between the UE and the PGW.
[0255] Optionally, the PDN connection request may include a CP+UP CIoT indication (i.e., indication information) to request that the PDN connection be established as a PDN connection that simultaneously supports CP CIoT EPS optimized transmission and UP CIoT EPS optimized transmission.
[0256] Optionally, the default bearer corresponding to the PDN connection (i.e., the first bearer of the first connection) can be the same as the bearer type for performing CPCIoT EPS optimized transmission, or it can be the same as the bearer type for performing UP CIoT EPS optimized transmission, without limitation.
[0257] S702, the MME determines that the UE accesses the network through GEO and that the UE is a narrowband device, with APN = IMS.
[0258] In other words, the MME determines to create a PDN connection for the UE, that is, the MME determines to create the session corresponding to the PDN connection for the UE.
[0259] In one implementation, the MME determines whether to create a PDN connection for the UE based on information #1 (i.e., the first information). Information #1 includes the UE's RAT and APN. Optionally, information #1 may also include at least one of the following: the UE's subscription information or the UE's location information. The specific interpretation of information #1 and the specific judgment criteria and implementation method of the MME can be found in the relevant description of step S620 of method 600 above; for brevity, it will not be elaborated here.
[0260] In another implementation, the MME determines whether to create a PDN connection for the UE based on information #1 and the CP+UP CIoTindication carried in the PDN connection request. For the specific implementation, please refer to the relevant description of step S620 of method 600 above. For the sake of brevity, it will not be described here.
[0261] In other words, this implementation method can be either the UE requesting the establishment of a PDN connection that simultaneously supports the transmission of SIP signaling and IMS voice data (i.e., the first connection), or the MME determining itself to establish a PDN connection that simultaneously supports the transmission of SIP signaling and IMS voice data for the UE (i.e., the first connection), without any limitation on the latter.
[0262] S703, the MME sends a create session request to the SGW;
[0263] Correspondingly, the SGW receives a session creation request from the MME.
[0264] For example, the session creation request includes a CP+UP CIoT indication.
[0265] For example, the session creation request may also include the MME address and TEID for S11-U, as well as the EBI assigned by the MME for the default bearer of the PDN connection (i.e., the first bearer of the first connection), such as EBI#1.
[0266] S704, the SGW and PGW perform a session creation process, or in other words, establish a data transmission channel.
[0267] For example, the SGW sends a session creation request to the PGW, requesting the establishment of a session corresponding to the PDN connection; correspondingly, when the session corresponding to the PDN connection is established, the PGW sends a session creation response to the SGW.
[0268] Optionally, the CP+UP CIoT indication can be carried in the session creation request or session creation response.
[0269] Optionally, the SGW and PGW record or store the PDN connection to support both CP CIoT-optimized and UP CIoT-optimized transmissions (e.g., referred to as message #a).
[0270] S705, SGW sends a create session response to MME;
[0271] Correspondingly, the MME receives a session creation response from the SGW.
[0272] For example, the session creation response may include the SGW address and TEID assigned by the SGW for S11-U.
[0273] S706, the MME sends an initial context setup request or an S1-AP downlink NAS transport message to the eNB;
[0274] Correspondingly, the eNB receives an initial context establishment request or an S1-AP downlink NAS transmission message from the MME.
[0275] For example, the initial context establishment request or the S1-AP downlink NAS transmission message may include a PDN connection acceptance (e.g., PDN Connectivity Accept, i.e., a first response message) to indicate acceptance of PDN connection establishment. This PDN connection acceptance may include a CP+UP CIoT indication.
[0276] S707, the eNB sends a PDN connection acceptance message to the UE.
[0277] Among them, the eNB can carry the PDN connection acceptance through RRC Connection Reconfiguration or RRC Direct Tranfer messages.
[0278] For example, UE and eNB can transmit SIP signaling through signaling radio bearer (SRB) or data radio bearer (DRB). For specific implementation methods, please refer to the relevant descriptions of existing bearer establishment methods. For the sake of brevity, they will not be described here.
[0279] S708, SIP signaling is transmitted between the UE and PGW via the first bearer of the PDN connection (also known as the default bearer of the first connection).
[0280] For example, the first bearer of the PDN connection is a CP-based bearer. After the PDN connection is established, when the UE needs to initiate a registration procedure or a call setup procedure, the UE can send a NAS packet data unit (PDU) to the MME through control. This PDU carries SIP signaling. The SIP signaling may include registration or call setup related information.
[0281] S709, PCRF receives authentication requests and sends authentication responses.
[0282] For example, the P-CSCF can send an AAR message to the PCRF to request the establishment of a dedicated bearer for a PDN connection (i.e., a first connection with a second bearer) to transmit IMS voice data. The AAR may include at least one of the following: the user's signaling address, media type, media description information, or media bandwidth, etc.
[0283] S710, PGW and PCRF initiate a recertification process.
[0284] For example, the PCRF makes policy decisions based on the media type and media description information carried in the received AAR message, provides authorized QoS, and sends a re-authentication request message, such as a RAR message, to the PGW. The RAR message carries QoS (e.g., QoS class identifier (QCI), allocation and retention priority (ARP), guaranteed bit rate (GBR), maximum bit rate (MBR), or aggregate maximum bit rate (AMBR)) and PCC rules. Correspondingly, the PGW returns a re-authentication response message to the PCRF, such as a re-authentication authorization answer (RAA).
[0285] S711, PGW sends a create bearer request to SGW;
[0286] Correspondingly, the SGW receives a bearer creation request from the PGW.
[0287] For example, the bearer creation request carries LBI=EBI#1.
[0288] For example, after receiving a request to establish a dedicated bearer for a PDN connection, the PGW can set the LBI to EBI#1, i.e., LBI = EBI#1, to establish a user plane channel for it and configure a bearer based on user plane transmission (i.e., the second bearer of the first connection). For example, the PGW can accept the creation of a bearer based on user plane transmission for the PDN connection corresponding to EBI#1 based on the record information #a saved in step S704.
[0289] S712, SGW sends a create bearer request to MME;
[0290] Correspondingly, the MME receives a bearer creation request from the SGW.
[0291] For example, the bearer creation request carries LBI=EBI#1.
[0292] For example, the SGW can accept the creation of a bearer based on user plane transport (i.e., the second bearer of the first connection) for the PDN connection corresponding to EBI#1 based on the record information #a saved in step S704.
[0293] S713, the MME sends a bearer setup request (e.g., the second request message) to the eNB;
[0294] Correspondingly, the eNB receives a bearer establishment request from the MME.
[0295] For example, the MME can accept the creation of a bearer based on user plane transport (i.e., the second bearer of the first connection) for the PDN connection corresponding to EBI#1 based on the record information #a saved in step S704.
[0296] S714, RRC reconfiguration is performed between the UE and the eNB.
[0297] For example, the eNB and UE perform RRC reconfiguration to create a data radio bearer corresponding to the dedicated bearer connected to the PDN (i.e., the second bearer of the first connection) for transmitting IMS voice data.
[0298] It is understandable that the first or second bearer of the PDN connection refers to the logical connection between the UE and the PGW, while the bearer between the UE and the eNB can be a signaling radio bearer (SRB) or a data radio bearer (DRB).
[0299] S715, the eNB sends a bearer setup response (e.g., the second response message) to the MME;
[0300] Correspondingly, the MME receives a bearer establishment response from the eNB, indicating that the dedicated bearer of the PDN connection has been established.
[0301] The bearer establishment response may include the eNB's IP address and TEID.
[0302] S716, the MME sends a create bearer response to the SGW;
[0303] Correspondingly, the SGW receives a create bearer response from the MME to indicate that the dedicated bearer for the PDN connection has been established.
[0304] The bearer creation response can include the eNB's IP address and TEID.
[0305] S717, SGW sends a create bearer response to PGW;
[0306] Correspondingly, the PGW receives a create bearer response from the SGW, indicating that the dedicated bearer for the PDN connection has been established.
[0307] S718, PGW sends a bearer establishment complete message to PCRF;
[0308] Correspondingly, the PCRF receives a bearer establishment completion message from the PGW, which indicates that the dedicated bearer of the PDN connection has been established.
[0309] For example, the PGW sends a RAR message to the PCRF to indicate that the private bearer of the PDN connection has been established; correspondingly, the PCRF sends an acknowledgment message, such as a RAA message, to the PGW.
[0310] S719, IMS voice data is transmitted between the UE and PGW via a second bearer connected through a PDN.
[0311] For example, the second bearer of the PDN connection is an UP-based bearer. After the call setup phase is completed, the UE can transmit IMS voice data via the user-to-PGW.
[0312] Using the above method, the MME creates a PDN connection for the UE that simultaneously supports CP CIoT EPS optimized transmission and UP CIoT EPS optimized transmission. This means the UE can transmit SIP signaling through the default bearer of the PDN connection, and / or transmit IMS voice data through the dedicated bearer of the same PDN connection. In other words, the UE creating a user plane bearer to transmit IMS voice data provides QoS guarantees for IMS voice data transmission, thereby improving voice call quality.
[0313] The above Figure 6 and Figure 7 This explanation focuses on a narrowband IoT device requesting a core network element to establish a first connection (e.g., a PDN connection). This first connection supports both user plane-based and control plane-based transmissions. In comparison, the following... Figures 8 to 10 This example illustrates how core network elements establish a first connection and a second connection (for example, which can be viewed as two PDN connections) for narrowband IoT devices. The first connection can support user plane-based transmission, and the second connection can support control plane-based transmission.
[0314] Figure 8 This is a schematic flowchart of a communication method 800 provided in this application. Figure 8 As shown, this method primarily focuses on the information interaction between the first core network element and the second core network element. It establishes a first connection supporting user plane transmission and a second connection supporting control plane transmission for narrowband IoT devices. Specifically, the second connection is used to transmit IMSSIP signaling, and the first connection is used to transmit IMS voice data. The method includes several steps; for details not covered herein, please refer to existing protocols.
[0315] S801, the narrowband IoT device sends a second request message (e.g., PDN connectivity request) to the first core network element;
[0316] Correspondingly, the first core network element receives a second request message from the narrowband IoT device.
[0317] The second request message is used to request the establishment of a first connection (e.g., PDN connection #1). The second request message includes a first bearer identifier of the second connection (e.g., default EBI of PDN connection #2) and an APN indicator IMS carried in the second request message (e.g., APN = IMS). The first connection is a connection between a narrowband IoT device and a second core network element.
[0318] Understandably, this method is applicable to scenarios where narrowband IoT devices access the network via satellite and perform IMS voice services, especially in scenarios where access is via narrowband, high-orbit satellites (e.g., NB-NTN, NB-GEO, NB-IoT NTN, or NB-IoT(GEO)) to perform IMS voice services.
[0319] For example, the narrowband IoT device can be a UE, the first core network element can be an MME, and the second core network element can be a PGW, without limitation.
[0320] In this application, the second connection is used to transmit SIP signaling, and the first bearer identifier of the second connection is used to indicate the first bearer of the second connection. The first bearer of the second connection can be referred to as the default bearer of the second connection. The first connection is used to transmit IMS voice data, and the second bearer of the first connection can be referred to as the default bearer or a dedicated bearer of the second connection, without limitation.
[0321] In other words, the second request message can be understood as a request from a narrowband IoT device to establish the first connection as a connection that supports UP CIoT EPS optimized transmission, that is, the first connection is used to transmit data related to IMS services (e.g., voice services), which can be user plane-based transmissions (e.g., IMS voice data).
[0322] In one possible implementation, the narrowband IoT device can instruct the IMS via an APN to request the establishment of a second connection (e.g., PDN connection #2) with the first core network element for either CP CIoT EPS optimized transmission or UP CIoT EPS optimized transmission. Specific implementation details can be found in steps S610-S630 of method 600 above, and will not be elaborated here for brevity. It is understood that the narrowband IoT device can register to the IMS network via the second PDN connection.
[0323] Optionally, this application does not limit the timing of establishing the first connection and the second connection. For example, the first core network element may establish the first connection first and then establish the second connection; or, the first core network element may establish the second connection first and then establish the first connection; or, the first core network element may establish the first connection and the second connection simultaneously, without limitation.
[0324] For example, a narrowband IoT device sends a second request message to a first core network element via a base station. For instance, the narrowband IoT device may send a second request message to the base station to request the establishment of the first connection, and this second request message carries APN=IMS; correspondingly, the base station sends a second request message to the first core network element to request the establishment of the first connection.
[0325] S802, the first core network element determines to establish the first connection based on the first information.
[0326] In other words, the first core network element determines the session corresponding to the establishment of the first connection based on the first information.
[0327] The first piece of information includes at least one of the following: the RAT type, APN, contract information of the narrowband IoT device, or location information of the narrowband IoT device.
[0328] For the specific implementation method, please refer to the relevant description of step S620 of method 600 above. For the sake of brevity, it will not be described here again.
[0329] For example, after determining to establish the first connection, the first core network element can execute the session establishment process corresponding to the first connection. For instance, the first core network element (e.g., MME) can initiate a session establishment request for the first connection to the second core network element (e.g., PGW) through the serving gateway SGW. The specific implementation method can be referred to the relevant descriptions of steps S803-S805 below, which will not be explained here.
[0330] Optionally, step S801 and step S802 can be executed or not. That is, it is optional for the narrowband IoT device to initiate a request to establish the first connection, and it is optional for the first core network element to determine whether to establish a session corresponding to the first connection based on the first information. In other words, the request from the first core network element to the second core network element to establish a session corresponding to the first connection in step S803 can be initiated proactively by the first core network element or triggered by a request from the narrowband IoT device; there is no limitation on this. Furthermore, the request from the first core network element to the second core network element to establish a session corresponding to the first connection in step S803 can be initiated by the first core network element after determining whether to establish a session corresponding to the first connection based on the first information, or it can be initiated by the first core network element without making a determination, defaulting to establishing a session for the narrowband IoT device to establish the first connection; there is no limitation on this.
[0331] S803, the first core network element sends a first request message (create session request) to the second core network element;
[0332] Correspondingly, the second core network element receives the first request message from the first core network element.
[0333] The first request message is used to request the establishment of a session corresponding to the first connection. The first request message includes the first bearer identifier of the second connection (e.g., default EBI of PDN connection#2). The first connection and the second connection are associated. The APN of both the first connection and the second connection indicates IMS (e.g., APN = IMS). Both the first connection and the second connection are connections between narrowband IoT devices and second core network elements.
[0334] In other words, the first core network element and the second core network element exchange information to establish a first connection and a second connection for narrowband IoT devices. Both the first and second connections are used to transmit information related to IMS services. For example, the first core network element can send a first request message to the second core network element through the SGW.
[0335] S804, the second core network element stores the association between the first connection and the second connection.
[0336] In this application, the first connection and the second connection are associated, which can be understood as: the default bearer of the second connection (i.e., the first bearer of the second connection) and the default bearer of the first connection are associated. This association is used for the replacement of the dedicated bearer (used for transmitting IMS voice data) of the second connection by subsequent second core network elements (e.g., PGW), and / or the conversion of the transmission addresses of uplink and downlink voice data.
[0337] For example, the first connection in this application is used to transmit IMS voice data, and the second connection is used to transmit SIP signaling. For the SIP signaling and IMS service data related to IMS services, the sender or receiver can be a narrowband IoT device or the IMS network side. For instance, when a second core network element (e.g., PGW) sends IMS voice data to a narrowband IoT device (e.g., UE), it can replace the destination address of the IMS voice data with the UE address corresponding to the first connection, which is the address of the narrowband IoT device. Similarly, when a second core network element (e.g., PGW) sends IMS voice data to the IMS network side, it can replace the source address of the IMS voice data with the UE address corresponding to the second connection, which is the address of the narrowband IoT device.
[0338] Optionally, the narrowband IoT device in this application embodiment may have multiple IP addresses. For example, for the first connection, the narrowband IoT device may have one IP address (e.g., IP address #1); for the second connection, the narrowband IoT device may also have one IP address (e.g., IP address #2), and there is no limitation thereto.
[0339] Optionally, step S804 may or may not be executed. For example, if it is not executed, in the subsequent step S808, the second core network element can obtain the association relationship between the first connection and the second connection from the first core network element or other network elements, without limitation.
[0340] S805, the second core network element sends a first response message (create sessionresponse) to the first core network element;
[0341] Correspondingly, the second core network element receives the first response message from the first core network element.
[0342] The first response message is used to indicate that the session corresponding to the first connection has been established.
[0343] Understandably, this first response message is a response to the first request message.
[0344] For example, the second core network element can send a first response message to the first core network element through the SGW.
[0345] Optionally, this application does not limit the execution order of steps S804 and S805. For example, the second core network element may execute step S804 first and then step S805; or, the second core network element may execute step S805 first and then step S804; or, the second core network element may execute steps S804 and S805 simultaneously, without limitation.
[0346] S806, the first core network element sends a second response message (e.g., PDNconnectivity Accept) to the narrowband IoT device;
[0347] Correspondingly, the narrowband IoT device receives a second response message from the first core network element.
[0348] The second response message is used to indicate acceptance of the first connection establishment.
[0349] Understandably, this second response message is a response to the second request message.
[0350] Optionally, step S806 may or may not be performed.
[0351] It should be noted that the process of establishing the first bearer of the second connection involved in this application can refer to existing relevant descriptions, such as the establishment of the first bearer of the second connection between the narrowband IoT device and the base station through information interaction. For the sake of brevity, it will not be described here.
[0352] Based on the above implementation, once the first and second connections between the narrowband IoT device and the second core network element are established, the narrowband IoT device can transmit SIP signaling through the first bearer (or default bearer) of the second connection. For example, the narrowband IoT device can initiate a registration process or a call setup process to the IMS network element by sending SIP signaling; there are no limitations on this.
[0353] In this application, assuming the first bearer of the second connection is used to transmit IMS Session Initiation Protocol (SIP) signaling, when a narrowband physical network (NB-IoT) device initiates a call setup process, i.e., when the NB-IoT device has a need to transmit IMS voice data, the NB-IoT device and the first core network element can initiate a process to establish the second bearer of the first connection to transmit IMS voice data. In other words, the NB-IoT device can transmit IMS SIP signaling through the first bearer of the second connection, and / or transmit IMS voice data through the second bearer of the first connection. The second bearer of the first connection can be referred to as the default bearer or a dedicated bearer of the first connection, without limitation. Optionally, the method further includes the following steps S807-S812.
[0354] S807, the second core network element receives the fourth request message (e.g., RAR).
[0355] The fourth request message is used to request modification of the second connection in order to transmit IMS voice data.
[0356] For example, the second core network element receives a fourth request message from the PCRF. The fourth request message is used to request the establishment of a dedicated bearer for the second connection, that is, the dedicated bearer of the second connection is used to transmit IMS voice data, or in other words, the fourth request message is used to request the creation of a dedicated bearer on the second connection for transmitting IMS voice data.
[0357] S808, the second core network element determines the second bearer for establishing the first connection based on the fourth request message and the association between the first connection and the second connection. The second bearer of the first connection is used to transmit IMS voice data.
[0358] In other words, after receiving the fourth request message requesting the establishment of a dedicated bearer for the second connection, the second core network element can automatically switch (replace or convert) to the first connection to perform the establishment of the second bearer based on the association between the first connection and the second connection. The second bearer of the first connection is used to transmit IMS voice data.
[0359] For example, the second core network element can set the default EBI of the first connection to the LBI and initiate the creation process of the second bearer of the first connection to the first network element, or in other words, initiate the bearer modification process of the second connection. Further, the base station and the narrowband IoT device perform signaling interaction to create the second bearer of the first connection. The specific implementation of the second bearer can be referred to the existing relevant descriptions, which will not be described here for the sake of brevity.
[0360] S809, the second core network element sends a fifth request message (creat / updatebearer request) to the first core network element;
[0361] Correspondingly, the first core network element receives the fifth request message sent from the second core network element.
[0362] The fifth request message is used to request the establishment of a second bearer for the first connection. The fifth request message includes the default bearer identifier of the first connection (e.g., LBI = default EBI of PDN connection #1). The default bearer identifier of the first connection is used to identify the default bearer of the first connection, and / or, to identify the first connection.
[0363] For example, the first core network element determines a second bearer identifier (e.g., EBI#1) for the first connection. The second bearer identifier of the first connection is used to indicate the second bearer of the first connection, which can be the default bearer or a dedicated bearer of the first connection, without limitation.
[0364] For example, the second core network element can send a fifth request message to the first core network element through the SGW.
[0365] S810, the first core network element sends a third request message (bearer setup / modify request) to the narrowband IoT device;
[0366] Correspondingly, narrowband IoT devices receive third request messages from core network elements.
[0367] The third request message is used to request the establishment of a second bearer for the first connection. The second bearer of the first connection is used to transmit IMS voice data. The third request message includes the identifier of the second bearer of the first connection (e.g., EBI#1).
[0368] For example, the first core network element can send a third request message to the narrowband IoT device via a base station. Further, the narrowband IoT device and the base station engage in signaling interaction to establish a second bearer for the first connection. For instance, the base station and the narrowband IoT device exchange RRC reconfiguration messages to establish the data radio bearer corresponding to the second bearer of the first connection. Specific implementation details can be found in existing descriptions and will not be elaborated upon for brevity.
[0369] S811, narrowband IoT devices send a third response message (bearer setup / modify response) to the first core network element;
[0370] Correspondingly, the first core network element receives a third response message from the narrowband IoT device.
[0371] The third response message is used to indicate that the second bearer of the first connection has been established. The third response message may include the second bearer identifier of the first connection (e.g., EBI#1).
[0372] Understandably, this third response message is a response to the third request message. For example, a narrowband IoT device can send a third response message to a first core network element via a base station.
[0373] S812, the first core network element sends the fifth response message (creat / updatebearer response) to the second core network element;
[0374] Correspondingly, the first core network element receives the fifth response message from the narrowband IoT device.
[0375] The fifth response message is used to indicate that the second bearer of the first connection has been established. The fifth response message may include the second bearer identifier of the first connection (e.g., EBI#1).
[0376] Understandably, this fifth response message is a response to the fifth request message. For example, the first core network element can send the fifth response message to the second core network element via the SGW.
[0377] Optionally, the second core network element can also send a re-authentication / authorization request (RAR) message to the PCRF, and correspondingly, the PCRF sends a re-authentication / authorization response (RAR) message to the second core network element.
[0378] In this application, the first bearer of the second connection can be a bearer based on the control plane transmission, and the second bearer of the first connection can be a bearer based on the user plane transmission; or, the first bearer of the second connection is a bearer based on the user plane transmission, and the second bearer of the first connection is a bearer based on the control plane transmission. For example, a narrowband IoT device can transmit IMS voice data using UP CIoT EPS optimization based on the first connection, and / or transmit SIP signaling using CP CIoT EPS optimization based on the second connection.
[0379] In other words, the first bearer of the second connection in this application is used to transmit SIP signaling, which can be transmitted based on the control plane or the user plane. The second bearer of the first connection is used to transmit IMS voice data, which can be transmitted based on the control plane or the user plane, without limitation.
[0380] Based on the above implementation, once the second bearer of the first connection between the narrowband IoT device and the second core network element is established, the narrowband IoT device can transmit IMS voice data through the second bearer (or dedicated bearer) of the first connection.
[0381] The following example illustrates the transmission of IMS voice data between narrowband IoT devices and the IMS network via a second core network element.
[0382] In one example, taking uplink transmission as an example, a narrowband IoT device can send first data (e.g., uplink IMS voice data) to a second core network element through the second bearer of the first connection. For instance, the narrowband IoT device can send the first data to a base station, which forwards it to the SGW, and finally the SGW forwards the first data to the second core network element. Understandably, the first data is sent through the second bearer of the first connection. Correspondingly, after receiving the first data from the narrowband IoT device through the second bearer of the first connection, the second core network element can, based on the association between the first and second connections, replace the source address of the first data with the UE address corresponding to the second connection, such as the address of the narrowband IoT device, and send the first data to the IMS network. Understandably, after receiving the first data, the IMS network can determine that the sender of the first data is the narrowband IoT device based on the source address corresponding to the first data.
[0383] In another example, taking uplink transmission as an example, the IMS network sends second data (e.g., downlink IMS voice data) to the second core network element. Correspondingly, after receiving the second data from the IMS network, the second core network element can replace the destination address of the second data with the UE address corresponding to the first connection, such as the address of the narrowband IoT device, according to the association between the first connection and the second connection, and send the second data to the narrowband IoT device through the second bearer of the first connection. Correspondingly, the narrowband IoT device can receive the second data on the second bearer of the first connection.
[0384] Using the above method, the first core network element and the second core network element interact to establish a first connection supporting user plane-based transmission and a second connection supporting control plane-based transmission for narrowband IoT devices. Specifically, the first bearer of the second connection is used to transmit IMS SIP signaling, and the second bearer of the first connection is used to transmit IMS voice data. In other words, the second core network element can create a second connection supporting CP CIoT EPS optimized transmission and a first connection supporting UP CIoT EPS optimized transmission for narrowband IoT devices. That is, by creating a user plane bearer (e.g., the second bearer of the first connection) to transmit IMS voice data, QoS guarantees can be provided for the IMS voice data of narrowband IoT devices, thereby improving voice call quality.
[0385] To facilitate understanding, the following will be combined with Figure 9 and Figure 10This document illustrates how a core network element creates a first connection supporting user plane transmission and a second connection supporting control plane transmission for a narrowband IoT device. Specifically, the narrowband IoT device can transmit SIP signaling and IMS voice data through different connections. In the examples below, the narrowband IoT device is represented by the UE, the first core network element by the MME, and the second core network element by the PGW as the execution entities. It is understood that the process described below is merely illustrative, and the embodiments of this application are not limited thereto. Details not described below can be found above. Figure 8 The relevant descriptions in the text will not be repeated below.
[0386] Figure 9 This is a schematic flowchart of a communication method 900 provided in this application. Figure 9 As shown, the UE requests the MME to create PDN connection #2 (i.e., the first connection) to transmit IMS voice data. This method mainly includes the following steps, and the parts not described in detail can be referred to the existing protocol.
[0387] For example, assume that the UE registers with the network via satellite (e.g., GEO) and is a narrowband device. In this implementation, the UE requests the MME to create a PDN connection (e.g., PDN connection #1) using IMS as the APN. Correspondingly, the MME creates two associated PDN connections (e.g., PDN connection #1 and PDN connection #2), where PDN connection #1 is used to transmit IMS Session Initiation Protocol (SIP) signaling, and PDN connection #2 is used to transmit IMS voice data.
[0388] S900, the UE requests the creation of PDN connection #1 (i.e., the second connection) with APN=IMS.
[0389] For example, the PDN connection #1 may be a CP CIoT EPS optimized transmission.
[0390] For example, a UE can send SIP signaling to the IMS network through the default bearer of PDN connection #1 (i.e., the first bearer of the second connection) to request registration with the IMS network.
[0391] S901, the UE sends a PDN connection request (e.g., PDN connectivity request, i.e., the second request message) to the MME;
[0392] Correspondingly, the MME receives a PDN connection request from the UE.
[0393] For example, the PDN connection request includes an ESM message container carrying APN=IMS, meaning the PDN connection request is used to request the establishment of PDN connection #2 (i.e., the first connection). The PDN connection request may also include the default bearer identifier EBI of PDN connection #1 (i.e., the first bearer identifier of the second connection).
[0394] In this application, the PDN connection #2 requested by the UE is associated with the PDN connection #1 corresponding to the EBI. For a detailed explanation, please refer to the relevant description of method 800 above. For the sake of brevity, it will not be explained here.
[0395] Understandably, both PDN connection #1 and PDN connection #2 are PDN connections between the UE and the PGW, used to transmit SIP signaling and IMS voice data, respectively.
[0396] S902, the MME sends a session creation request (e.g., create session request, i.e., the first request message) to the SGW;
[0397] Correspondingly, the SGW receives a session creation request from the MME.
[0398] For example, the session creation request may include the default bearer identifier of PDN connection #1, and the session creation request is used to request the creation of a session corresponding to PDN connection #2.
[0399] In one implementation, before executing step S902, the MME can determine whether to create a session corresponding to PDN connection #2 for the UE. For example, the MME can determine whether to create PDN connection #2 for the UE based on first information. The first information includes the UE's RAT and APN. Optionally, the first information may also include at least one of the following: the UE's subscription information or the UE's location information, without limitation. For a detailed interpretation of the first information and the MME's judgment basis and implementation method, please refer to the relevant description of step S620 of method 600 above; for brevity, it will not be explained here.
[0400] S903, SGW and PGW perform a session creation process, or in other words, establish a data transmission channel.
[0401] For example, the SGW sends a session creation request to the PGW, requesting the establishment of a session corresponding to the PDN connection; correspondingly, once the session corresponding to the PDN connection is established, the PGW sends a session creation response to the SGW. The session creation request may include the default bearer identifier for PDN connection #1.
[0402] S904, PGW stores the association between PDN connection #2 and PDN connection #1.
[0403] Alternatively, the PGW maintains the association between the default bearer identifier of PDN connection #1 and the default bearer identifier of PDN connection #2. This association is used for subsequent association replacements for dedicated bearer operations on PDN connection #1, and / or for address translation of uplink and downlink IMS voice data transmission. Understandably, this association means that when the PGW receives a request to create a dedicated bearer for PDN connection #1, it can automatically switch to PDN connection #2 to perform the operation, i.e., establish a dedicated bearer for PDN connection #2 (i.e., the second bearer of the first connection) for transmitting IMS voice data.
[0404] S905, SGW sends a create session response to MME;
[0405] Correspondingly, the MME receives a session creation response from the SGW, indicating that the session corresponding to PDN connection #2 has been established.
[0406] The session creation response can include the SGW's IP address and TEID.
[0407] S906, the MME sends a PDN connection acceptance (e.g., PDN connectivity Accept, i.e., the second response message) to the UE through the eNB;
[0408] Correspondingly, the UE receives a PDN connection acceptance from the MM via the eNB, which indicates acceptance of PDN connection #2 establishment.
[0409] S907, the eNB sends its IP address and TEID to the MME;
[0410] Correspondingly, the MME receives the eNB's IP address and TEID from the eNB.
[0411] S908, MME and PGW exchange information to modify the session corresponding to PDN connection #2.
[0412] For example, the MME and SGW perform a session modification operation, with the MME sending the eNB's address and TEID to the SGW.
[0413] S909, the UE transmits SIP signaling through PDN connection #1.
[0414] For example, after PDN connection #1 is established, when the UE needs to initiate a registration procedure or a call setup procedure, the UE can send SIP signaling to the PGW through the default bearer of PDN connection #1. This SIP signaling may include registration or call setup related information.
[0415] S910, PCRF initiates authentication request.
[0416] The specific implementation of steps S909-S910 can be found in the description of step S709 in the above method 700.
[0417] S911, PGW and PCRF perform a recertification process.
[0418] For example, after receiving the establishment request for a dedicated bearer of PDN connection #1 from the PCRF, the PGW can determine, based on the stored information #a, i.e., the association between PDN connection #1 and PDN connection #2, to transmit IMS voice data through the bearer on PDN connection #2. This bearer on PDN connection #2 can be either the default bearer of PDN connection #2 or a dedicated bearer of PDN connection #2; there is no limitation on this. Then, the PGW can set the default bearer identifier of PDN connection #2 to LBI and initiate a bearer creation / modification process for PDN connection #2. For details, see steps S913-S917 below.
[0419] S912, PGW determines PDN connection #2 based on the association stored in step S904.
[0420] S913, the PGW sends a create / update bearer request to the MME through the SGW;
[0421] Correspondingly, the MME receives create / update bearer requests from the PGW via the SGW.
[0422] For example, the LBI carried in the create / update bearer request indicates the default EBI of PDN connection #2.
[0423] Optionally, the create / update bearer request may carry a traffic flow template (TFT) parameter, which may be generated by the PGW based on the RAR message sent by the PCRF in step S911.
[0424] S914, the MME sends a bearer setup / modify request to the eNB;
[0425] Correspondingly, the eNB receives bearer establishment / modification requests from the MME.
[0426] For example, the LBI carried in the bearer establishment / modification request indicates the default EBI of PDN connection #2.
[0427] S915, RRC reconfiguration is performed between UE and eNB.
[0428] S916, the eNB sends a create / update bearer response to the MME;
[0429] Correspondingly, the MME receives bearer establishment / modification responses from the eNB.
[0430] S917, the MME sends a bearer setup / modify response to the PGW via the SGW;
[0431] Correspondingly, the PGW receives the create / update bearer response from the MME via the SGW.
[0432] S918, PGW sends a bearer establishment complete message to PCRF;
[0433] Correspondingly, the PCRF receives a bearer establishment complete message from the PGW.
[0434] S919, the UE transmits IMS voice data through PDN connection #2.
[0435] In one example, the UE can send uplink IMS voice data to the PGW through the dedicated bearer of PDN connection #2. Correspondingly, the PGW, based on the association between PDN connection #1 and PDN connection #2, replaces the source address of the uplink IMS voice data with the UE address corresponding to PDN connection #1, and then forwards the uplink IMS voice data to the IMS network.
[0436] In another example, after receiving downlink IMS voice data from the IMS network, the PGW can identify it as IMS voice data to be sent to the UE based on the TFT parameters sent by the IMS network. Then, it maps the downlink IMS voice data to PDN connection #2, replaces the destination address of the downlink IMS voice data with the UE address corresponding to PDN connection #2, and then forwards the downlink IMS voice data to the UE.
[0437] Optionally, the TFT parameter can be the same as the TFT parameter in step S913, and there is no limitation thereto.
[0438] It is understood that any parts of steps S912-S919 that are not detailed above can be referred to the relevant descriptions of steps S711-S719 of method 700 above.
[0439] Using the above method, the UE requests the MME to create PDN connection #2 to support the transmission of IMS voice data. That is, the UE can transmit SIP signaling through the default bearer of PDN connection #1, and / or transmit IMS voice data through the default bearer or dedicated bearer of PDN connection #2, which can provide QoS guarantees for voice data and thus improve the quality of voice calls.
[0440] Figure 10 This is a schematic flowchart of a communication method 1000 provided in this application. Compared to method 900 above, where the UE actively requests the MME to create a PDN connection #2 (i.e., the first connection) associated with PDN connection #1 (i.e., the second connection), in method 1000, the MME actively triggers the creation of a PDN connection #2 associated with PDN connection #1 for the UE to transmit IMS voice data. Figure 10 As shown, the method mainly includes the following steps; for parts not described in detail, please refer to existing protocols.
[0441] For example, assume the UE registers with the network via satellite and is a narrowband device. In this implementation, the MME triggers the creation of two associated PDN connections (e.g., PDN connection #1 and PDN connection #2), where PDN connection #1 is used to transmit IMS Session Initiation Protocol (SIP) signaling, and PDN connection #2 is used to transmit IMS voice data.
[0442] S1001, the UE sends a PDN connectivity request to the MME through the eNB;
[0443] Correspondingly, the MME receives PDN connection requests from the UE via the eNB.
[0444] For example, the PDN connection request includes an ESM message container carrying APN=IMS, and the PDN connection request can be used to request the establishment of a PDN connection #1.
[0445] S1002, MME determines to create PDN connection #1 and PDN connection #2 for UE.
[0446] PDN connection #2 is associated with PDN connection #1.
[0447] Optionally, the MME stores the association between PDN connection #2 and PDN connection #1.
[0448] For example, the MME can create PDN connection #1 for the UE based on the UE's PDN connection request. The specific process can be found in the relevant descriptions of existing solutions. For instance, PDN connection #1 is a control plane-based transport, or a CP CIoT EPS-optimized PDN connection.
[0449] In addition, the MME can also determine to create PDN connection #2 for the UE, and its corresponding APN is also set to IMS.
[0450] For example, PDN connection #2 is a user plane-based transport, or a UP CIoT EPS-optimized PDN connection.
[0451] In one implementation, the MME can determine whether to create a PDN connection #2 for the UE based on the first information. The first information includes the UE's RAT and APN. Optionally, the first information may also include at least one of the following: the UE's subscription information or the UE's location information, without limitation. For a detailed interpretation of the first information and the MME's judgment criteria and implementation method, please refer to the relevant description of step S620 of method 600 above; for brevity, it will not be explained here.
[0452] Optionally, this application does not limit the creation order of PDN connection #2 and PDN connection #1. For example, the MME can create PDN connection #2 first and then create PDN connection #1; or, the MME can create PDN connection #1 first and then create PDN connection #2; or, the MME can create PDN connection #1 and PDN connection #2 at the same time.
[0453] S1003, Remaining process of PDN connection #1 creation.
[0454] S1004, the MME sends a session creation request (e.g., create session request, i.e., the first request message) to the SGW;
[0455] Correspondingly, the SGW receives a session creation request from the MME.
[0456] For example, the session creation request may include the default bearer identifier of PDN connection #1, and the session creation request is used to request the creation of the session corresponding to PDN connection #2.
[0457] S1005, the SGW and PGW perform a session creation process, or in other words, establish a data transmission channel.
[0458] S1006, PGW stores the association between PDN connection #2 and PDN connection #1.
[0459] S1007, SGW sends a create session response to MME;
[0460] Correspondingly, the MME receives a session creation response from the SGW, indicating that PDN connection #2 has been established.
[0461] The session creation response can include the SGW's IP address and TEID.
[0462] S1008, the MME sends a PDN connectivity response (e.g., PDN connectivity acceptance, i.e., the second response message) to the UE via the eNB;
[0463] Correspondingly, the UE receives a PDN connection response from the MM via the eNB, indicating acceptance of PDN connection #2 establishment.
[0464] S1009, the eNB sends its IP address and TEID to the MME;
[0465] Correspondingly, the MME receives the eNB's IP address and TEID from the eNB.
[0466] In S1010, the MME and PGW exchange information to modify the session corresponding to PDN connection #2.
[0467] For example, the MME and SGW perform a session modification operation, with the MME providing the SGW with the eNB's address and TEID.
[0468] S1011, the UE transmits SIP signaling through PDN connection #1.
[0469] For example, after PDN connection #1 is established, when the UE needs to initiate a registration procedure or a call setup procedure, the UE can send SIP signaling to the PGW through the default bearer of PDN connection #1. This SIP signaling may include registration or call setup related information.
[0470] S1012, PCRF initiates an authentication request.
[0471] S1013, PGW and PCRF initiate a recertification process.
[0472] S1014, PGW determines PDN connection #2 based on the association stored in step S904.
[0473] S1015, the PGW sends a create / update bearer request to the MME through the SGW;
[0474] Correspondingly, the MME receives create / update bearer requests from the PGW via the SGW.
[0475] For example, the LBI carried in the create / update bearer request indicates the default EBI of PDN connection #2. Optionally, the create / update bearer request may carry TFT parameters, which may be generated by the PGW based on the RAR message sent by the PCRF in step S911.
[0476] S1016, the MME sends a bearer setup / modify request to the eNB;
[0477] Correspondingly, the eNB receives bearer establishment / modification requests from the MME.
[0478] For example, the LBI carried in the bearer establishment / modification request indicates the default EBI of PDN connection #2.
[0479] S1017, RRC reconfiguration is performed between the UE and the eNB.
[0480] S1018, the eNB sends a create / update bearer response to the MME;
[0481] Correspondingly, the MME receives bearer establishment / modification responses from the eNB.
[0482] S1019, the MME sends a bearer setup / modify response to the PGW via the SGW;
[0483] Correspondingly, the PGW receives the create / update bearer response from the MME via the SGW.
[0484] S1020, PGW sends a bearer establishment complete message to PCRF;
[0485] Correspondingly, the PCRF receives a bearer establishment complete message from the PGW.
[0486] S1021, the UE transmits IMS voice data through PDN connection #2.
[0487] It is understood that any parts not detailed in steps S1004-S1021 above can be referred to the relevant descriptions of steps S902-S919 of method 900 above.
[0488] Compared to method 900 where the UE actively requests the creation of PDN connection #2, this embodiment uses the MME to trigger the creation of interrelated PDN connections #1 and #2 for the UE, supporting the transmission of SIP signaling and IMS voice data. That is, the UE can transmit SIP signaling through the default bearer of PDN connection #1, and / or transmit IMS voice data through the default bearer or dedicated bearer of PDN connection #2, providing QoS guarantees for voice data and thus improving voice call quality.
[0489] Figure 11 This is a schematic flowchart of a communication method 1100 provided in this application. Compared to method 700 above, in method 1100, the UE requests the MME to create a CP-based bearer, or in other words, requests the establishment of a PDN connection supporting control plane transmission for transmitting SIP signaling. Subsequently, when the MME receives the bearer creation request (e.g., a dedicated bearer), it creates a UP-based bearer for the UE for transmitting IMS voice data. In this case, the CP bearer of the PDN connection supports the transmission of SIP signaling, and the UP bearer of the PDN connection supports the transmission of IMS voice data. Figure 11 As shown, the method mainly includes the following steps; for parts not described in detail, please refer to existing protocols.
[0490] S1101, the UE sends a PDN connectivity request to the MME;
[0491] Correspondingly, the MME receives a PDN connection request from the UE.
[0492] For example, a PDN connection request is used to request the creation of a PDN connection that supports the CP bearer (i.e., the default bearer for the first connection). The PDN connection request includes an ESM message container, which carries APN=IMS. It can be understood that this PDN connection is a PDN connection between the UE and the PGW.
[0493] For example, suppose the UE registers with the network via satellite (e.g., GEO) and is a narrowband device. In this implementation, the UE requests the MME to create a PDN connection (i.e., the first connection) that supports CP CIoT EPS optimized transmission (i.e., control plane-based transmission) for transmitting SIP signaling, using the APN as the IMS.
[0494] Optionally, the PDN connection request may include a CP CIoT indication for requesting that the PDN connection be established as a PDN connection that supports CP CIoT EPS optimized transmission.
[0495] S1102, MME creates a PDN connection that supports CP bearer.
[0496] In other words, the MME creates a PDN connection for the UE based on the received PDN connection request, or in other words, creates a PDN connection for the UE that supports SIP signaling.
[0497] For example, the MME assigns an MME address and TEID for the S11-U, and the MME can also assign an EBI, such as EBI#1, to the default bearer of the PDN connection.
[0498] S1103, SIP signaling is transmitted between the UE and PGW via the CP bearer (also known as the default bearer of the first connection) connected through the PDN.
[0499] For details on the specific implementation of steps S1101-S1103 above, please refer to the relevant description of method 500 above. For the sake of brevity, it will not be explained here.
[0500] S1104, PCRF receives authentication requests and sends authentication responses.
[0501] S1105, PGW and PCRF initiate a recertification process.
[0502] For example, the PCRF sends a re-authentication request message, such as a RAR message, to the PGW based on the received AAR message, and the PGW returns a re-authentication response message, such as a RAA, to the PCRF.
[0503] S1106, PGW sends a create bearer request to SGW;
[0504] Correspondingly, the SGW receives a bearer creation request from the PGW. For example, the bearer creation request carries LBI=EBI#1.
[0505] For example, after receiving a request to establish a dedicated bearer for a PDN connection, the PGW can set the LBI to EBI#1, i.e., LBI = EBI#1, establish a user plane channel for it, and configure a bearer based on user plane transmission (i.e., the UP bearer of the PDN connection can be regarded as the dedicated bearer of the PDN connection).
[0506] S1107, SGW sends a create bearer request to MME;
[0507] Correspondingly, the MME receives a bearer creation request from the SGW. For example, the bearer creation request carries LBI=EBI#1.
[0508] For example, the SGW accepts the creation of a bearer based on user plane transport for the PDN connection corresponding to EBI#1.
[0509] The specific implementation of steps S1104-S1107 above can be found in the description of steps S709-S712 of method 700 above. For the sake of brevity, it will not be explained here.
[0510] S1108, the MME determines the UP bearer for creating the PDN connection (or, creating a UP-based bearer), and the CP bearer for retaining the PDN connection.
[0511] For example, the MME determines the UP bearer for creating the PDN connection and the CP bearer for reserving the PDN connection based on the first information.
[0512] The first information includes the UE's RAT and APN. Optionally, the first information may also include at least one of the following: the UE's subscription information or the UE's location information. For a detailed interpretation of the first information and the specific judgment criteria and implementation method of the MME, please refer to the relevant description of step S620 of method 600 above; for brevity, it will not be elaborated here.
[0513] S1109, the process of creating the UP bearer for the PDN connection.
[0514] For specific implementation details, please refer to the relevant descriptions of steps S713-S718 of method 700 above. For the sake of brevity, these details will not be provided here.
[0515] S1110, IMS voice data is transmitted between the UE and PGW via the UP bearer connected by the PDN.
[0516] For the specific implementation method, please refer to the relevant description of step S719 of method 700 above. For the sake of brevity, it will not be explained here.
[0517] Using the above method, the MME creates a PDN connection for the UE that simultaneously supports CP CIoT EPS optimized transmission and UP CIoT EPS optimized transmission. That is, the UE can transmit SIP signaling through the CP bearer of the PDN connection, and / or transmit IMS voice data through the UP bearer of the PDN connection. This can provide QoS guarantee for the transmission of IMS voice data, thereby improving the quality of voice calls.
[0518] It should be understood that detailed explanations of each step in methods 700 or 1100 shown above can be found in the above text. Figure 6 The relevant descriptions in Method 600, and detailed explanations of each step in Method 900 or Method 1000 shown above, can be found in the above text. Figure 8The relevant descriptions in Method 800 will not be repeated here. Furthermore, the technical solutions shown in Methods 700 and 1100 correspond to those shown in Method 600, and the technical solutions shown in Methods 900 and 1000 correspond to those shown in Method 800; therefore, the beneficial effects obtained are similar and will not be repeated here. It should also be understood that... Figure 7 , Figure 11 The process shown is Figure 6 The possible implementation flow of method 600 shown is as follows: Figure 9 , Figure 10 The process shown is Figure 8 The possible implementations of method 800 shown should not be construed as limiting this application. Those skilled in the art, based on the same concept, can make simple substitutions or modifications to one or more steps of method 600 or method 800 to achieve the same effect. Such simple modifications or substitutions should fall within the protection scope of this application.
[0519] It should also be understood that in the various embodiments shown above in conjunction with the accompanying drawings, the sequence number of each step does not imply the order of execution. The execution order of each step should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0520] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.
[0521] In the above embodiments, exemplary descriptions are mainly based on devices in the current network architecture (such as narrowband IoT device side, network side, etc.). The embodiments of this application do not limit the specific form of the device. For example, devices that can achieve the same function in the future can also be applied to the methods provided in the embodiments of this application.
[0522] It is understood that in the above-described method embodiments, the methods and operations implemented by the device (such as the narrowband IoT device side, network side, etc.) can also be implemented by the device's components (such as chips or circuits).
[0523] The above text combined Figures 1 to 10 The communication method embodiments of this application have been described in detail below, and will be discussed in conjunction with... Figure 11 and Figure 12The communication device-side embodiments of this application are described in detail. It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments; therefore, any parts not described in detail can be referred to the foregoing method embodiments. These devices can be used to implement the functions of the narrowband IoT device side or network side in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments.
[0524] Figure 12 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 12 As shown, the communication device 1200 may include a processing module 1210 and a communication module 1220. Optionally, the communication device 1200 may further include a storage module 1230 for storing device program code and / or data. The processing module 1210 may read instructions and / or data from the storage module 1230 to enable the device to implement the aforementioned method embodiments.
[0525] In an optional embodiment, the communication device 1200 can be used to implement Figure 6 or Figure 8 The method shown in the embodiment is executed by the narrowband IoT device. For example, processing module 1210 is used to implement... Figure 6 or Figure 8 The processing steps shown in the embodiment are executed by the narrowband IoT device; the communication module 1220 is used to implement... Figure 6 or Figure 8 In the illustrated embodiment, the steps of sending and / or receiving are performed by the narrowband IoT device.
[0526] For example, the communication module 1220 is used to send a first request message, which requests the establishment of a first connection. The first connection supports user plane-based transmission and control plane-based transmission. The APN carried in the first request message indicates IMS. The first connection is a connection between a narrowband IoT device and a core network element. The communication module 1220 is also used to receive a first response message, which indicates that the first connection has been established.
[0527] For example, the communication module 1220 is also configured to send a first request message when a narrowband IoT device accesses NB-IoT via satellite.
[0528] In an optional embodiment, the communication device 1200 can be used to implement Figure 6 or Figure 8 The method shown in the embodiment is executed by the core network element side. For example, processing module 1210 is used to implement... Figure 6 or Figure 8 The processing steps shown in the embodiment are executed by the core network element side; the communication module 1220 is used to implement... Figure 6 or Figure 8In the illustrated embodiment, the core network element side performs the sending and / or receiving steps.
[0529] For example, the communication module 1220 is used to receive a first request message, which is used to request the establishment of a first connection. The first connection supports user plane-based transmission and control plane-based transmission. The APN carried in the first request message indicates IMS. The first connection is a connection between a narrowband IoT device and a core network element. The communication module 1220 is also used to send a first response message, which is used to indicate that the first connection has been established.
[0530] For example, the processing module 1210 is used to determine the session corresponding to the establishment of the first connection based on the first information; wherein the first information includes at least one of the following: the RAT type, APN, subscription information of the narrowband IoT device, or location information of the narrowband IoT device.
[0531] For example, the processing module 1210 is also configured to determine the session corresponding to the establishment of the first connection when the RAT type indicates that the narrowband IoT device accesses NB-IoT via satellite, and / or the APN indicates IMS.
[0532] For example, the processing module 1210 is further configured to determine, based on the first information, the session corresponding to the establishment of the first connection when the first request message carries indication information.
[0533] In an optional embodiment, the communication device 1200 can be used to implement Figure 6 or Figure 8 The method shown in the embodiment is executed by the core network element side. For example, processing module 1210 is used to implement... Figure 6 or Figure 8 The processing steps shown in the embodiment are executed by the core network element side; the communication module 1220 is used to implement... Figure 6 or Figure 8 In the illustrated embodiment, the core network element side performs the sending and / or receiving steps.
[0534] For example, the communication module 1220 is used to send a first request message, which is used to request the establishment of a session corresponding to the first connection. The first request message includes a first bearer identifier of the second connection. The first connection and the second connection are associated. The APN of both the first connection and the second connection indicates IMS. The first connection and the second connection are both connections between narrowband IoT devices and second core network elements. The communication module 1220 is also used to receive a first response message, which is used to indicate that the session corresponding to the first connection has been established.
[0535] For example, the processing module 1210 is used to determine the session corresponding to the establishment of the first connection based on the first information; wherein the first information includes at least one of the following: the RAT type, APN, subscription information of the narrowband IoT device, or location information of the narrowband IoT device.
[0536] For example, the processing module 1210 is also configured to determine the session corresponding to the establishment of the first connection when the RAT type indicates that the narrowband IoT device accesses NB-IoT via satellite, and / or the APN indicates IMS.
[0537] In an optional embodiment, the communication device 1200 can be used to implement Figure 6 or Figure 8 The method shown in the embodiment is executed by the core network element side. For example, processing module 1210 is used to implement... Figure 6 or Figure 8 The processing steps shown in the embodiment are executed by the core network element side; the communication module 1220 is used to implement... Figure 6 or Figure 8 In the illustrated embodiment, the core network element side performs the sending and / or receiving steps.
[0538] For example, the communication module 1220 is used to receive a first request message, which is used to request the establishment of a session corresponding to the first connection. The first request message includes a first bearer identifier of the second connection. The first connection and the second connection are associated. The APN of the first connection and the second connection are both IMS. The first connection and the second connection are both connections between narrowband IoT devices and second core network elements. The communication module 1220 is also used to send a first response message, which is used to indicate that the session corresponding to the first connection has been established.
[0539] For example, the processing module 1210 is also used to save the association between the first connection and the second connection.
[0540] For example, the first bearer of the second connection is used to transmit IMS SIP signaling, and the communication module 1220 is also used to receive a fourth request message, which requests modification of the second connection to transmit IMS voice data; the processing module 1210 is also used to determine the second bearer for establishing the first connection based on the fourth request message and the association between the first connection and the second connection, and the second bearer of the first connection is used to transmit IMS voice data; the communication module 1220 is also used to send a fifth request message, which requests the establishment of the second bearer for the first connection.
[0541] For example, the communication module 1220 is further configured to receive first data from a narrowband IoT device through a second bearer of the first connection; the processing module 1210 is further configured to replace the source address of the first data with the address of the narrowband IoT device corresponding to the second connection according to the association relationship between the first connection and the second connection; the communication module 1220 is further configured to send the first data to the IMS network.
[0542] For example, the communication module 1220 is further configured to receive second data from the IMS network; the processing module 1210 is further configured to replace the destination address of the second data with the address of the narrowband IoT device corresponding to the first connection according to the association relationship between the first connection and the second connection; the communication module 1220 is further configured to send the second data to the narrowband IoT device through the second bearer of the first connection.
[0543] For a more detailed description of the processing module 1210 and the communication module 1220, please refer to [the relevant documentation]. Figure 6 The relevant descriptions in the method embodiments shown are directly obtained and will not be repeated here.
[0544] Optionally, the communication module can also be referred to as a communication unit, transceiver module, transceiver unit, transceiver, transceiver device, input / output circuit, input / output interface, communication interface, transceiver circuit, interface circuit, or transceiver device, etc. The transceiver unit includes a receiving unit and / or a transmitting unit; the transmitting unit can also be called an output unit, and the receiving unit can also be called an input unit. The processing module can also be referred to as a processor, processing board, processing unit, or processing device, etc. The storage module can also be referred to as a memory, storage unit, or storage device, etc. Optionally, the communication module is used to perform the transmitting and receiving operations on the narrowband IoT device side or the core network element side in the above method. The device in the communication module used to implement the receiving function can be considered as the receiving module, and the device in the communication module used to implement the transmitting function can be considered as the transmitting module; that is, the communication module can include a receiving module and a transmitting module.
[0545] In one possible design, the aforementioned processing module and / or communication module can be implemented as a virtual module. For example, the processing module can be implemented as a software functional unit or a virtual device, and the communication module can be implemented as a software function or a virtual device. In another possible design, the processing module or communication module can also be implemented as a physical device. For example, if the device is implemented using a chip / chip circuit, the communication module can be an input / output circuit and / or a communication interface, performing input operations (corresponding to the aforementioned receiving operation) and output operations (corresponding to the aforementioned sending operation); the processing module can be an integrated processor, a microprocessor, or an integrated circuit.
[0546] The module division in this embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used. Furthermore, the functional modules in the various examples of this embodiment can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.
[0547] Figure 13 This is a schematic diagram of another communication device provided in an embodiment of this application. For example... Figure 13 As shown, the communication device 1300 includes a processing circuit 1310 and a communication circuit 1320. The processing circuit 1310 and the communication circuit 1320 are coupled to each other.
[0548] It can be understood that the processing circuit 1310 can be one or more processors, or it can be all or part of the processing functions of one or more processors.
[0549] It is understood that the communication circuit 1320 can be one or more transceivers or input / output interfaces. Optionally, the transceiver may include a transmitter and / or a receiver to respectively implement the transmission and reception operations in the embodiments; if the transceiver is an input / output interface, it transmits the corresponding output and receives the corresponding input.
[0550] Optionally, the communication device 1300 may further include one or more memories 1330 for storing instructions executed by the processing circuit 1310, or storing input data required for the running instructions of the processing circuit 1310, or storing data generated after the running instructions of the processing circuit 1310.
[0551] It is understood that the memory 1330 may be located outside the processing circuit 1310, or inside the processing circuit 1310.
[0552] As an example, processing circuit 1310 is used to implement the above. Figure 12 The processing module 1210 performs the functions described above, and the communication circuit 1320 is used to implement these functions. Figure 12 The communication module 1220 has the function of [the above], and the memory 1330 is used to implement the above. Figure 12 The function of storage module 1230 in the middle.
[0553] As an example, the communication device 1300 can be a narrowband IoT device or a core network element, or it can be a chip applied in a narrowband IoT device or a core network element.
[0554] When the communication device 1300 is a narrowband IoT device or a core network element, the communication circuit can be a transceiver.
[0555] When the communication device 1300 is a chip, the communication circuit can be an input / output circuit, a bus, pins, or other types of communication interfaces. The input circuit in the input / output circuit can be used for receiving, and the output interface can be used for transmitting.
[0556] This application also provides a computer program product that, when run on a processor, can implement the communication method executed by the narrowband IoT device side or the communication method executed by the core network element side in the above method embodiments.
[0557] This application also provides a computer-readable storage medium containing computer instructions that, when executed on a processor, can implement the communication method executed by the narrowband IoT device or the core network element in the above method embodiments.
[0558] This application also provides a communication system, including the aforementioned narrowband IoT device side and core network element side. The narrowband IoT device side can be used to implement the communication method implemented by the narrowband IoT device side in the above method embodiments, and the core network element side can be used to implement the communication method implemented by the core network element side in the above method embodiments.
[0559] It is understood that the processor in the embodiments of this application may be any of the following devices or all or part of the circuitry used for processing functions: a central processing unit (CPU), a processor for AI, or other general-purpose processors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.
[0560] For example, the processor used for AI can be one or more of the following: graphics processing unit (GPU), neural processing unit (NPU), tensor processing unit (TPU), and data processing unit (DPU).
[0561] For example, a processor for AI may include one or more of the following: an AI core, a digital vision pre-processing (DVPP) module, a task scheduler (TS), an L3 cache, an AI CPU, a control CPU, an L2 cache, a universal serial bus (USB) interface, a network interface card (NIC), a peripheral component interconnect express (PCIe) interface (PCIe is a high-speed serial computer expansion bus standard), a double data rate (DDR) / high bandwidth memory (HBM) interface, a generation purpose input / output (GPIO) / inter-integrated circuit (I2C) bus, etc. It is understood that the specific meanings of these terms are well known to those skilled in the art and will not be elaborated upon here.
[0562] The terms “unit”, “module”, etc., used in this specification may be used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution.
[0563] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0564] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0565] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0566] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0567] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0568] In the above embodiments, the functions of each functional unit can be implemented entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. This computer program product includes one or more computer instructions (or programs). When the computer program instructions (or programs) are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).
[0569] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to existing solutions, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0570] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A communication method, characterized in that, Applications include narrowband IoT devices, including: Send a first request message, which is used to request the establishment of a first connection. The first connection supports user plane-based transmission and control plane-based transmission. The access point name (APN) carried in the first request message indicates Internet Protocol IP Multimedia Subsystem (IMS). The first connection is a connection between a narrowband IoT device and a core network element. Receive a first response message, which indicates that the first connection has been established.
2. The method according to claim 1, characterized in that, Sending the first request message includes: When the narrowband IoT device accesses the narrowband IoT (NB-IoT) via satellite, the first request message is sent.
3. The method according to claim 1 or 2, characterized in that, The first request message includes indication information, which indicates that the first connection supports both user plane-based and control plane-based transmissions.
4. The method according to any one of claims 1 to 3, characterized in that, The first bearer of the first connection is used to transmit IMS Session Initiation Protocol (SIP) signaling, and the method further includes: Receive a second request message, the second request message being used to request the establishment of a second bearer for the first connection, the second bearer of the first connection being used to transmit IMS voice data; A second response message is sent, which indicates that the second bearer of the first connection has been established.
5. The method according to claim 4, characterized in that, The first bearer is the bearer corresponding to the control plane-based transmission, and the second bearer is the bearer corresponding to the user plane-based transmission; or, The first bearer is the bearer corresponding to the user plane-based transmission, and the second bearer is the bearer corresponding to the control plane-based transmission.
6. A communication method, characterized in that, Applied to core network elements, including: Receive a first request message, the first request message is used to request the establishment of a first connection, the first connection supports user plane-based transmission and control plane-based transmission, the access point name (APN) carried in the first request message indicates Internet Protocol IP Multimedia Subsystem (IMS), and the first connection is a connection between a narrowband Internet of Things (IoT) device and a core network element. Send a first response message, which indicates that the first connection has been established.
7. The method according to claim 6, characterized in that, The first request message includes indication information, which indicates that the first connection supports both user plane-based and control plane-based transmissions.
8. The method according to claim 6 or 7, characterized in that, Before sending the first response message, the method further includes: The session corresponding to the first connection is determined to be established based on the first information; The first information includes at least one of the following: the wireless access technology (RAT) type of the narrowband IoT device, the APN, the subscription information of the narrowband IoT device, or the location information of the narrowband IoT device.
9. The method according to claim 8, characterized in that, The step of determining the session corresponding to the first connection based on the first information includes: If the RAT type indicates that the narrowband IoT device accesses narrowband IoT (NB-IoT) via satellite, and / or the APN indicates IMS, then the session corresponding to the first connection is determined to be established.
10. The method according to claim 8 or 9, characterized in that, The step of determining the session corresponding to the first connection based on the first information includes: If the indication information is carried in the first request message, the session corresponding to the first connection is determined to be established based on the first information.
11. The method according to any one of claims 6 to 10, characterized in that, The first bearer of the first connection is used to transmit IMS Session Initiation Protocol (SIP) signaling, and the method further includes: Send a second request message, the second request message being used to request the establishment of a second bearer for the first connection, the second bearer of the first connection being used to transmit IMS voice data; A second response message is received, which indicates that the second bearer of the first connection has been established.
12. The method according to claim 11, characterized in that, The first bearer is the bearer corresponding to the control plane-based transmission, and the second bearer is the bearer corresponding to the user plane-based transmission; or, The first bearer is the bearer corresponding to the user plane-based transmission, and the second bearer is the bearer corresponding to the control plane-based transmission.
13. A communication method, characterized in that, Applied to the first core network elements, including: Send a first request message, which is used to request the establishment of a session corresponding to the first connection. The first request message includes a first bearer identifier of the second connection. The first connection and the second connection are associated. The access point name (APN) of the first connection and the second connection both indicate Internet Protocol IP Multimedia Subsystem (IMS). The first connection and the second connection are both connections between narrowband IoT devices and second core network elements. Receive a first response message, which indicates that the session corresponding to the first connection has been established.
14. The method according to claim 13, characterized in that, Before sending the first request message, the method further includes: The session corresponding to the first connection is determined to be established based on the first information; The first information includes at least one of the following: the wireless access technology (RAT) type of the narrowband IoT device, the APN, the subscription information of the narrowband IoT device, or the location information of the narrowband IoT device.
15. The method according to claim 14, characterized in that, The step of determining the session corresponding to the first connection based on the first information includes: If the RAT type indicates that the narrowband IoT device accesses narrowband IoT (NB-IoT) via satellite, and / or the APN indicates IMS, then the session corresponding to the first connection is determined to be established.
16. The method according to any one of claims 13 to 15, characterized in that, Before sending the first request message, the method further includes: Receive a second request message, the second request message being used to request the establishment of the first connection, the second request message including a first bearer identifier of the second connection, and the APN carried in the second request message indicating the IMS; A second response message is sent, which indicates that the first connection has been established.
17. The method according to any one of claims 13 to 16, characterized in that, The first bearer of the second connection is used to transmit IMS Session Initiation Protocol (SIP) signaling, and the method further includes: Send a third request message, the third request message being used to request the establishment of a second bearer for the first connection, the third request message including a second bearer identifier for the first connection, the second bearer of the first connection being used to transmit IMS voice data; A third response message is received, which indicates that the second bearer of the first connection has been established.
18. The method according to claim 17, characterized in that, The first bearer is the bearer corresponding to the control plane-based transmission, and the second bearer is the bearer corresponding to the user plane-based transmission; or, The first bearer is the bearer corresponding to the user plane-based transmission, and the second bearer is the bearer corresponding to the control plane-based transmission.
19. A communication method, characterized in that, Applied to the second core network elements, including: Receive a first request message, the first request message is used to request the establishment of a session corresponding to the first connection, the first request message includes a first bearer identifier of the second connection, wherein the first connection and the second connection are associated, the access point name (APN) of the first connection and the second connection are both Internet Protocol IP Multimedia Subsystem (IMS), and the first connection and the second connection are both connections between narrowband IoT devices and the second core network element; Send a first response message, which indicates that the session corresponding to the first connection has been established.
20. The method according to claim 19, characterized in that, The method further includes: Save the association between the first connection and the second connection.
21. The method according to claim 19 or 20, characterized in that, The first bearer of the second connection is used to transmit IMS Session Initiation Protocol (SIP) signaling, and the method further includes: Receive a fourth request message, which is used to request modification of the second connection to transmit IMS voice data; Based on the fourth request message and the association between the first connection and the second connection, a second bearer for establishing the first connection is determined, and the second bearer of the first connection is used to transmit the IMS voice data; A fifth request message is sent, which is used to request the establishment of a second bearer for the first connection.
22. The method according to claim 21, characterized in that, The first bearer is the bearer corresponding to the control plane-based transmission, and the second bearer is the bearer corresponding to the user plane-based transmission; or, The first bearer is the bearer corresponding to the user plane-based transmission, and the second bearer is the bearer corresponding to the control plane-based transmission.
23. The method according to any one of claims 19 to 22, characterized in that, The method further includes: The first data is received from the narrowband IoT device via the second bearer of the first connection; Based on the association between the first connection and the second connection, the source address of the first data is replaced with the address of the narrowband IoT device corresponding to the second connection; The first data is sent to the IMS network.
24. The method according to any one of claims 19 to 23, characterized in that, The method further includes: Receive second data from the IMS network; Based on the association between the first connection and the second connection, the destination address of the second data is replaced with the address of the narrowband IoT device corresponding to the first connection; The second data is sent to the narrowband IoT device via the second bearer of the first connection.
25. A communication device, characterized in that, It includes at least one processor, said at least one processor being configured to execute a computer program or instructions to cause the method as described in any one of claims 1 to 12 to be performed, or to cause the method as described in any one of claims 13 to 24 to be performed.
26. A communication system, characterized in that, It includes core network elements, which are used to perform the method as described in any one of claims 6 to 12.
27. A communication system, characterized in that, It includes a first core network element and a second core network element, wherein the first core network element is used to perform the method as described in any one of claims 13 to 18, and the second core network element is used to perform the method as described in any one of claims 19 to 24.
28. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a computer, cause the method as described in any one of claims 1 to 12 or 13 to 24 to be performed.
29. A computer program product, characterized in that, The computer program product stores a computer program or instructions that, when executed on a computer, cause the method as described in any one of claims 1 to 12 or 13 to 24 to be performed.