Communication method and apparatus, and communication device

Abstract

The present application belongs to the technical field of communications. Disclosed are a communication method and apparatus, and a communication device. The communication method in the embodiments of the present application comprises: a first network device receiving target communication data; and the first network device transmitting the target communication data on the basis of a first correspondence, wherein the first correspondence comprises the correspondence between first information and first address information, the first information comprises at least one of information of a first terminal and information of a target bearer, the target bearer is a non-IP data transmission (NIDD) bearer used for transmitting communication data for the first terminal, and the first address information is address information which is allocated by the first network device to the first terminal and used for the communication between the first network device and a second terminal.

Description

Communication method, apparatus and communication device

[0001] Cross-reference

[0002] The present application claims priority to the Chinese patent application No. 202410953610.7, filed on July 16, 2024, and entitled "Communication method, apparatus and communication device", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

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

[0004] In the related art, signaling and voice data in the process of 4G and 5G calls are all based on User Datagram Protocol (UDP), Transmission Control Protocol (TCP) or Internet Protocol (IP) transmission.

[0005] However, in the transmission based on UDP, TCP or IP provided in the related art, the message header is large, such as the size of the IPv4 message header is 20 bytes, the size of the UDP message header is 8 bytes, etc., which results in not only low transmission efficiency in the communication data transmission based on UDP or IP or TCP, but also the problem of waste of air interface resources for the scenario with limited air interface resources. SUMMARY

[0006] The embodiments of the present application provide a communication method, apparatus and communication device, which can improve the transmission efficiency and reduce the overhead of air interface resources.

[0007] In a first aspect, a communication method is provided, comprising: receiving, by a first network device, target communication data; and transmitting, by the first network device, the target communication data according to a first correspondence relationship, wherein the first correspondence relationship comprises a correspondence relationship between first information and first address information, the first information comprises at least one of information of a first terminal and information of a target bearer, the target bearer is a Non-IP Data Delivery (NIDD) bearer used for transmitting communication data for the first terminal, and the first address information is address information allocated by the first network device for the first terminal and used for communication between the first network device and a second terminal.

[0008] In a second aspect, a communication method is provided, comprising: establishing, by a third network device, a target bearer for a first terminal during a call setup procedure between the first terminal and a second terminal; wherein the target bearer is a non-IP data delivery, NIDD, bearer for delivering communication data for the first terminal.

[0009] In a third aspect, a communication method is provided, comprising: receiving, by a second network device, ninth information; and sending, by the second network device, tenth information to a third network device according to the ninth information; wherein, in a case that the ninth information is from a first terminal and is used to request establishment of a target bearer for the first terminal, the tenth information is used to request establishment of the target bearer for the first terminal; or, in a case that the ninth information is from the third network device and is used to indicate establishment of a target bearer for the first terminal, the tenth information is used to indicate information of the target bearer; the target bearer is a non-IP data delivery, NIDD, bearer for delivering communication data for the first terminal.

[0010] In a fourth aspect, a communication method is provided, comprising: receiving, by a first terminal, sixth information from a second network device or a third network device, the sixth information being used to instruct the first terminal to initiate a target bearer creation procedure; and initiating, by the first terminal, the target bearer creation procedure for creating a target bearer; wherein the target bearer is a non-IP data delivery, NIDD, bearer for delivering communication data for the first terminal.

[0011] In a fifth aspect, a communication apparatus is provided, comprising: a transmission module configured to receive target communication data; and the transmission module is further configured to perform transmission of the target communication data according to a first correspondence relationship; wherein the first correspondence relationship comprises a correspondence relationship between first information and first address information, the first information comprises at least one of information of a first terminal and information of a target bearer, the target bearer is a non-IP data delivery, NIDD, bearer for delivering communication data for the first terminal, and the first address information is address information allocated by a first network device for the first terminal and used for communication between the first network device and a second terminal.

[0012] In a sixth aspect, a communication apparatus is provided, comprising: a processing module configured to establish a target bearer for a first terminal during a call setup procedure between the first terminal and a second terminal; wherein the target bearer is a non-IP data delivery, NIDD, bearer for delivering communication data for the first terminal.

[0013] In a seventh aspect, a communication apparatus is provided, comprising: a transmission module configured to receive sixth information from a second network device or a third network device, the sixth information being used to instruct the first terminal to initiate a target bearer creation procedure; and a processing module configured to initiate the target bearer creation procedure for creating a target bearer, wherein the target bearer is a non-IP data delivery, NIDD, bearer used for transmitting communication data for the first terminal.

[0014] In an eighth aspect, a communication apparatus is provided, comprising: a transmission module configured to receive sixth information from a second network device or a third network device, the sixth information being used to instruct the first terminal to initiate a target bearer creation procedure; and a processing module configured to initiate the target bearer creation procedure for creating a target bearer, wherein the target bearer is a non-IP data delivery, NIDD, bearer used for transmitting communication data for the first terminal.

[0015] In a ninth aspect, a communication apparatus is provided, which is configured to perform the steps of the method according to the first aspect, or to implement the steps of the method according to the second aspect, or to implement the steps of the method according to the third aspect, or to implement the steps of the method according to the fourth aspect.

[0016] In a tenth aspect, a communication apparatus is provided, comprising a processor and a memory, the memory storing programs or instructions executable on the processor, which, when executed by the processor, implement the steps of the method according to the first aspect, or implement the steps of the method according to the second aspect, or implement the steps of the method according to the third aspect, or implement the steps of the method according to the fourth aspect.

[0017] In an eleventh aspect, a communication apparatus is provided, comprising a processor and a communication interface, wherein the communication interface is configured to receive target communication data; and the communication interface is further configured to transmit the target communication data according to a first correspondence relationship, wherein the first correspondence relationship comprises a correspondence relationship between first information and first address information, the first information comprises at least one of information of a first terminal and information of a target bearer, the target bearer is a non-IP data delivery, NIDD, bearer used for transmitting communication data for the first terminal, and the first address information is address information allocated by a first network device to the first terminal and used for communication between the first network device and a second terminal.

[0018] In a twelfth aspect, a communication apparatus is provided, comprising a processor and a communication interface, wherein the processor is configured to establish a target bearer for a first terminal during a call setup procedure of the first terminal and a second terminal, wherein the target bearer is a non-IP data delivery, NIDD, bearer used for transmitting communication data for the first terminal.

[0019] In a thirteenth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is configured to receive sixth information from a second network device or a third network device, the sixth information being used to indicate that the first terminal initiates a target bearer creation procedure; and the processor is configured to initiate the target bearer creation procedure for creating a target bearer, wherein the target bearer is a non-IP data delivery, NIDD, bearer used for transmitting communication data for the first terminal.

[0020] In a fourteenth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is configured to receive sixth information from a second network device or a third network device, the sixth information being used to indicate that the first terminal initiates a target bearer creation procedure; and a processing module configured to initiate the target bearer creation procedure for creating a target bearer, wherein the target bearer is a non-IP data delivery, NIDD, bearer used for transmitting communication data for the first terminal.

[0021] In a fifteenth aspect, a readable storage medium is provided, wherein a program or instructions are stored on the readable storage medium, and the program or instructions are executed by a processor to implement the steps of the method according to the first aspect, or to implement the steps of the method according to the second aspect, or to implement the steps of the method according to the third aspect, or to implement the steps of the method according to the fourth aspect.

[0022] In a sixteenth aspect, a wireless communication system is provided, comprising a terminal and a network side device, wherein the terminal is configured to implement the steps of the method according to the fourth aspect, and the network side device is configured to implement the steps of the method according to the first aspect or the second aspect or the third aspect.

[0023] In a seventeenth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface and the processor are coupled, and the processor is configured to run a program or instructions to implement the method according to the first aspect, or to implement the steps of the method according to the second aspect, or to implement the steps of the method according to the third aspect, or to implement the steps of the method according to the fourth aspect.

[0024] In an eighteenth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a storage medium, and the computer program / program product is executed by at least one processor to implement the method according to the first aspect, or to implement the steps of the method according to the second aspect, or to implement the steps of the method according to the third aspect, or to implement the steps of the method according to the fourth aspect.

[0025] In the embodiment of the present application, the first network device stores the first correspondence relationship, and the first correspondence relationship includes the correspondence relationship between at least one of the information of the first terminal and the information of the NIDD bearer and the first address information, so that when the communication data transmission between the first terminal and the second terminal is performed, the first network device can transmit the target communication data corresponding to the first terminal based on the first correspondence relationship, thereby avoiding the problems of waste of air interface resources, low transmission efficiency and the like caused by the need to perform communication data transmission based on IP or UDP or TCP in the related art. BRIEF DESCRIPTION OF DRAWINGS

[0026] FIG. 1a is a structural schematic diagram of a wireless communication system provided by an example embodiment of the present application.

[0027] FIG. 1b is a schematic diagram of a CP-based SCEF scheme provided by an example embodiment of the present application.

[0028] FIG. 1c is a schematic diagram of an SCEF connection establishment process provided by an example embodiment of the present application.

[0029] FIG. 1d is a schematic diagram of a CP-based PGW scheme provided by an example embodiment of the present application.

[0030] FIG. 1e is a schematic diagram of a UP-based PGW scheme provided by an example embodiment of the present application.

[0031] FIG. 2 is a flowchart of a communication method provided by an example embodiment of the present application.

[0032] FIG. 3a is an interaction flowchart of a communication method provided by an example embodiment of the present application.

[0033] FIG. 3b is another interaction flowchart of a communication method provided by an example embodiment of the present application.

[0034] FIG. 3c is a third interaction flowchart of a communication method provided by an example embodiment of the present application.

[0035] FIG. 4a is a fourth interaction flowchart of a communication method provided by an example embodiment of the present application.

[0036] FIG. 4b is a fifth interaction flowchart of a communication method provided by an example embodiment of the present application.

[0037] FIG. 4c is a sixth interaction flowchart of a communication method provided by an example embodiment of the present application.

[0038] FIG. 5 is a second flowchart of a communication method provided by an example embodiment of the present application.

[0039] FIG. 6 is a third flowchart of a communication method according to an example embodiment of the present application.

[0040] FIG. 7 is a fourth flowchart of a communication method according to an example embodiment of the present application.

[0041] FIG. 8 is a first schematic diagram of a communication apparatus according to an example embodiment of the present application.

[0042] FIG. 9 is a second schematic diagram of a communication apparatus according to an example embodiment of the present application.

[0043] FIG. 10 is a third schematic diagram of a communication apparatus according to an example embodiment of the present application.

[0044] FIG. 11 is a fourth schematic diagram of a communication apparatus according to an example embodiment of the present application.

[0045] FIG. 12 is a schematic diagram of a communication device according to an example embodiment of the present application.

[0046] FIG. 13 is a schematic diagram of a terminal according to an example embodiment of the present application.

[0047] FIG. 14 is a first schematic diagram of a network-side device according to an example embodiment of the present application.

[0048] FIG. 15 is a second schematic diagram of a network-side device according to an example embodiment of the present application. DETAILED DESCRIPTION

[0049] The technical solutions in the embodiments of the present application will be described clearly below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0050] The terms "first", "second", and the like in the specification are used to distinguish between similar objects, and are not used to describe a particular sequential or chronological order. It should be understood that the terms so used are interchangeable under appropriate circumstances and that the embodiments of the present application are capable of functioning in other sequences than the one described herein, and that the terms "first", "second" distinguish objects of a class, and do not limit the number of objects, for example, the first information can be one or more. In addition, "or" in the present application means at least one of the connected objects. For example, the protection scope of "A or B" at least covers three schemes, namely, scheme one: including A and not including B; scheme two: including B and not including A; scheme three: including A and B. In addition, the terms "A and / or B", "at least one of A and B", "at least one of A or B" also at least cover the above three schemes respectively. The character " / " generally represents that the front and rear associated objects are in an "or" relationship.

[0051] The term "indication" in the present application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). Among them, the direct indication can be understood as that the sender explicitly informs the receiver of the specific information, the operation to be performed or the request result, etc. in the indication sent; the indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or judges and determines the operation to be performed or the request result, etc. according to the judgment result.

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

[0053] FIG. 1a shows a block diagram of a wireless communication system to which embodiments of the present application can be applied. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a terminal-side device such as a mobile phone, a Tablet Personal Computer, a Laptop Computer, a notebook computer, a Personal Digital Assistant (PDA), a palmtop computer, a netbook, an Ultra-mobile Personal Computer (UMPC), a Mobile Internet Device (MID), an Augmented Reality (AR) device, a Virtual Reality (VR) device, a robot, a Wearable Device, a flight vehicle, a Vehicle User Equipment (VUE), a shipboard device, a Pedestrian User Equipment (PUE), a smart home (a home device with a wireless communication function such as a refrigerator, a television, a washing machine, or furniture), a game machine, a Personal Computer (PC), a kiosk, or a self-service machine. The Wearable Device includes a smart watch, a smart bracelet, a smart earphone, smart glasses, smart jewelry (a smart bracelet, a smart necklace, a smart ring, a smart necklace, a smart anklet, a smart necklace, and the like), a smart wristband, smart clothes, and the like. The vehicle-mounted device can also be referred to as a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip, or a vehicle-mounted unit. In addition, the terminal 11 can be a chip in the terminal, such as a Modem chip or a System on Chip (SoC), in addition to the above-mentioned terminals. It should be noted that the present application is not limited to the specific type of the terminal 11.

[0054] The network-side device 12 can include an access network device or a core network device, wherein the access network device can also be referred to as a Radio Access Network (RAN) device, a radio access network function or a radio access network unit. The access network device can include a base station, a Wireless Local Area Network (WLAN) Access Point (AP) or a Wireless Fidelity (WiFi) node, etc. Among them, the base station can be referred to as a Node B (NB), an Evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a relay station (RBS), a serving base station (SBS), a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home Node B (HNB), a home evolved Node B, a transmit / receive point (TRP), or some other suitable term in the art, as long as the same technical effect is achieved. The base station is not limited to a specific technical term, and it should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0055] The core network device can also be referred to as a core network node, a core network function, or a core network network element, etc., which includes but is not limited to at least one of the following: a mobility management entity (MME), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), a policy and charging rules function (PCRF), an edge application server discovery function (EASDF), a unified data management (UDM), a unified data repository (UDR), a home subscriber server (HSS), a centralized network configuration (CNC), a network repository function (NRF), a network exposure function (NEF), a local NEF (L-NEF), a binding support function (BSF), an application function (AF), a location management function (LMF), a gateway mobile location center (GMLC), a network data analytics function (NWDAF), etc. It should be noted that only the core network device in the NR system is taken as an example for introduction in the embodiments of the present application, and the specific type of the core network device is not limited. If the name of the core network device mentioned in the embodiments of the present application changes in the subsequent protocol version (for example, 6G), it is also within the protection scope of the present application.

[0056] Optionally, the core network device can be implemented by one or more function modules in one device, or can be implemented by multiple devices together, and the embodiments of the present application do not make a specific limitation hereon. It can be understood that the above function modules can be network elements in a hardware device, can be software function modules running on a special hardware, or can be virtualized function modules instantiated on a platform (for example, a cloud platform).

[0057] In order to facilitate understanding of the technical solutions of the present application, the Non-IP data transfer (NIDD) technology involved in the technical solutions of the present application is introduced as follows.

[0058] In the related art, the NIDD technology mainly includes a Service Capability Exposure Function (SCEF) scheme based on a Control Plane (CP), a PGW scheme based on the CP, and a PGW scheme based on a User Plane (UP), which are briefly introduced as follows.

[0059] (1) SCEF scheme based on CP

[0060] Please refer to FIG. 1b, when the UE has uplink data packets, the UE can send data to the MME through a Non-access stratum (NAS) message, the MME sends to the SCEF through an SCEF connection, and the SCEF sends to an Application Server (AS) through a Hyper Text Transfer Protocol (HTTP) message. The destination address of the HTTP message is a T8 destination address.

[0061] When the UE has downlink data packets, the AS sends to the SCEF through an HTTP message, the SCEF sends to the MME through an SCEF connection, and the MME sends to the UE through a NAS message. The destination address of the HTTP message is a T8 Long Term Transaction Reference ID (TLTRI). The T8 is an interface between the SCEF and other servers.

[0062] As shown in FIG. 1c, the building process of the SCEF connection is as follows.

[0063] S1, UE-1 initiates an attach request or a PDN connection establishment request, which carries Non-IP PDN type information.

[0064] S2, the MME sends a connection establishment request (Create Connection Request) to the SCEF according to the attach request or the PDN connection establishment request, for creating a SCEF connection, wherein the connection establishment request contains a user identity, an evolved packet system (EPS) bearer identity (EBI).

[0065] S3, the SCEF sends an NIDD configuration message to a (Proxy Call Session Control Function, P-CSCF) / IP multimedia subsystem application server (IMS AS), and the NIDD configuration message contains a user identity, a TLTRI, etc.

[0066] S4, the P-CSCF / IMS AS replies to the SCEF with an NIDD configuration response message, which carries a T8 destination address.

[0067] It is worth noting that S3-S4 can also be performed before S1, in which case the AS first sends an NIDD configuration message to the SCEF, which carries the identity of UE-1 and the T8 destination address, and then the SCEF sends a TLTRI to the AS.

[0068] S5, the SCEF sends a connection establishment response (Create Connection Response) message to the MME, to complete the SCEF connection establishment.

[0069] (2) PGW solution based on CP implementation

[0070] Please refer to Fig. 1d, when UE has uplink data packet, UE sends data to MME through NAS message, MME sends data to Packet Data Protocol GateWay (PGW) through PDN connection, PGW sends data to AS through Point-to-Point (PtP) tunnelling between PGW and AS through Service Gateway interface (SGi).

[0071] When UE has downlink data packet, AS sends data to PGW through SGi PtP tunnelling, PGW sends data to MME through PDN connection, MME sends data to UE through NAS message.

[0072] Wherein, when MME and PGW send data, they need to be forwarded through Signaling GateWay (SGW).

[0073] At present, SGi PtP tunnelling between PGW and AS has two implementation modes as follows: mode 1-mode 2.

[0074] Mode 1: SGi PtP tunnelling based on UDP / IP.

[0075] PGW pre-allocates address (such as IP address or IP address+port number) of AS, when PGW receives uplink data packet sent by MME, it sends the data packet to the pre-allocated address of AS;

[0076] PGW allocates IP address (IP address or IP address+port number) for UE and sends the IP address to AS, when AS has downlink data, it directly sends data to the IP address.

[0077] Explanation 1: address allocated by PGW for UE is only used in PGW and is not sent to UE.

[0078] Explanation 2: PGW allocating IP address for UE can be understood as PGW allocating IP address or IP address+port number for UE, the same hereinafter and will not be described again.

[0079] Mode 2: other SGi PtP tunnelling.

[0080] PGW and AS establish tunnel, for example, GPRS Tunneling Protocol (GTP)-User (U) tunnel, and PGW does not need to allocate IP address for UE.

[0081] When the PGW receives the uplink data packet sent by the MME, the PGW directly transmits the data to the AS through a tunnel.

[0082] When the AS has a downlink data packet, the AS directly transmits the data to the PGW through a tunnel.

[0083] (3) PGW solution based on UP

[0084] Please refer to FIG. 1e, when the UE has an uplink data packet, the UE sends the data to the base station through a data radio bearer (DRB), the base station sends the data to the PGW through a GTP-U tunnel, and the PGW sends the data to the AS through SGi PtP tunnelling between the PGW and the AS.

[0085] When the UE has a downlink data packet, the AS sends the data to the PGW through SGi PtP tunnelling, the PGW sends the data to the base station through a GTP-U tunnel, and the base station sends the data to the UE through a DRB.

[0086] Note: The GTP-U tunnel between the base station and the PGW needs to be forwarded through the SGW.

[0087] The implementation of SGi PtP tunnelling between the PGW and the AS is the same as the PGW solution based on CP described above, and will not be repeated here.

[0088] It should be noted that the above related technology is introduced taking the fourth generation mobile communication technology (4G) as an example, and the related technology is also applicable to a fifth generation (5G) mobile communication system or a sixth generation (6G) mobile communication system. For example, for the 5G mobile communication system, the MME can be replaced by the AMF, and the PGW can be replaced by the UPF or the SMF.

[0089] Therefore, the technical solutions provided by the embodiments of the present application will be described in detail in combination with the accompanying drawings and some embodiments and application scenarios.

[0090] As shown in FIG. 2, it is a flowchart of a communication method 200 provided by an exemplary embodiment of the present application. The method 200 can be executed by, but not limited to, a first network device, and can be executed by hardware and / or software installed in the first network device. In this embodiment, the method 200 can at least include the following steps.

[0091] S210, the first network device receives target communication data.

[0092] The first network device can be understood as a user plane network element, for example, the first network device can be, but is not limited to, an IP Multimedia Subsystem Gateway (IMS GW) and the like.

[0093] S220, the first network device transmits the target communication data according to the first correspondence relationship.

[0094] The first correspondence relationship includes or describes a correspondence relationship between first information and first address information, and the first information includes at least one of information of the first terminal and information of a target bearer, that is, the first correspondence relationship includes or describes a correspondence relationship between information of the first terminal and the first address information, and / or a correspondence relationship between information of the target bearer and the first address information.

[0095] The information of the first terminal can be, but is not limited to, a terminal identifier of the first terminal and the like.

[0096] The target bearer is a Non-IP data transfer (NIDD) bearer used or dedicated for transmitting communication data for the first terminal, for example, the target bearer can be used to transmit communication data from the first terminal to the first network device, or the first network device transmits communication data from a second terminal to the first terminal through the target bearer. In this embodiment, the target bearer can be understood as a network connection or a data channel in a network connection.

[0097] Optionally, according to different communication systems, the network connection can be, but is not limited to, a PDN connection in a 4G mobile communication system or a Protocol Data Unit (PDU) session in a 5G mobile communication system and the like.

[0098] Optionally, according to different communication systems, the data channel can be, but is not limited to, an EPS bearer in a 4G communication system or a Quality of Service (QoS) flow in a 5G communication system and the like.

[0099] The first address information is address information allocated by the first network device for the first terminal and used for communication between the first network device and a second terminal, for example, the first network device can send communication data from the first terminal to the second terminal according to the first address information, and can also send communication data from the second terminal to the first terminal based on the first address information. Wherein, the first address information can be an IP address or an IP address + port number and the like.

[0100] The target communication data can be, but is not limited to, communication data (such as signaling, voice data, etc.) sent by the first terminal to the second terminal, or communication data (such as signaling, voice data, etc.) sent by the second terminal to the first terminal, and the like, which are not limited herein.

[0101] Based on the foregoing, it can be understood that, compared with the scenario in the related art in which communication data transmission needs to be based on IP or UDP or TCP, in the present application, when performing communication data transmission between the first terminal and the second terminal, the first network device can transmit target communication data corresponding to the first terminal based on the first correspondence relationship, thereby avoiding problems such as waste of air interface resources and low transmission efficiency caused by the need for communication data transmission based on IP or UDP or TCP in the related art.

[0102] As an optional implementation, the first correspondence relationship can include, but is not limited to, at least one of the following 11) to 12).

[0103] 11) a correspondence relationship between a terminal identifier of the first terminal and the first address information.

[0104] The terminal identifier can be, but is not limited to, a Mobile Subscriber International ISDN number (MSISDN), a Session Initiation Protocol (SIP), a Uniform Resource Identifier (URI), an IP Multimedia Public Identity (IMPU), and the like.

[0105] 12) a correspondence relationship between second address information and the first address information. The second address information corresponds to the target bearer and is used for communication between the second network device and the first network device. In this embodiment, the second address information corresponding to the target bearer can be understood as follows: the information of the target bearer includes the second address information, or the information of the target bearer is related to the second address information, or the second address information is used for communication data transmission of the target bearer, or the second address information is used for transmission of communication data in the target bearer, and the like, which are not limited herein.

[0106] Optionally, the second network device can include, but is not limited to, at least one of an SCEF, a PGW, an SGW, and a UPF.

[0107] In some embodiments, the second address information can be allocated by the first network device for the first terminal, or can be allocated by the second network device for the first terminal. Based on this, the second address information can include, but is not limited to, at least one of the following 21)-25).

[0108] 21) TLTRI, which is allocated by the second network device for the first terminal, for the first network device to forward the target communication data to the second network device based on the TLTRI after receiving the target communication data from the second terminal, and then forwarded by the second network device to the first terminal, thereby realizing communication data transmission based on a non-IP or non-UDP or non-TCP scenario, improving transmission efficiency, and reducing the overhead of air interface resources.

[0109] 22) T8 destination address, which is allocated by the first network device for the first terminal, for the second network device to forward the target communication data to the first network device based on the T8 destination address after receiving the target communication data from the first terminal, thereby realizing communication data transmission based on a non-IP or non-UDP or non-TCP scenario, improving transmission efficiency, and reducing the overhead of air interface resources.

[0110] Wherein, if the second network device communicates with the first network device based on the TLTRI and the T8 destination address, the second network device can be, but is not limited to, SCEF. That is, the TLTRI and the T8 destination address in the foregoing 21)-22) correspond to the foregoing SCEF scheme based on CP.

[0111] 23) Target tunnel information, which is allocated by the first network device or the second network device for the first terminal.

[0112] Optionally, the target tunnel information includes at least one of the identifier of the target tunnel, the first network device side tunnel information corresponding to the target tunnel, and the second network device side tunnel information corresponding to the target tunnel. Wherein, the identifier of the target tunnel is allocated by the first network device or the second network device for the first terminal, the first network device side tunnel information is allocated by the first network device for the first terminal, and the second network device side tunnel information is allocated by the second network device for the first terminal.

[0113] For example, for the target tunnel information, the second network device can be configured to, after receiving target communication data from the first terminal, forward the target communication data to the first network device through the target tunnel based on the target tunnel information, so that communication data transmission under a non-IP or non-UDP or non-TCP scenario can be implemented, transmission efficiency is improved, and the cost of air interface resources is reduced.

[0114] For example, for the target tunnel information, the second network device can be configured to, after receiving target communication data from the first terminal, forward the target communication data to the first network device through the target tunnel based on the target tunnel information, so that communication data transmission under a non-IP or non-UDP or non-TCP scenario can be implemented, transmission efficiency is improved, and the cost of air interface resources is reduced.

[0115] For example, for the target tunnel information, the second network device can be configured to, after receiving target communication data from the first terminal, forward the target communication data to the first network device through the target tunnel based on the target tunnel information, so that communication data transmission under a non-IP or non-UDP or non-TCP scenario can be implemented, transmission efficiency is improved, and the cost of air interface resources is reduced.

[0116] Based on this, as a possible implementation, if the second network device communicates with the first network device based on the target tunnel information, the second network device can be, but is not limited to, a PGW or an SGW or a UPF, etc. That is, the target tunnel information described in the foregoing 23) corresponds to the mode 2 in the PGW scheme based on CP.

[0117] Optionally, the target tunnel can be, but is not limited to, the SGi PtP tunnel described above, etc.

[0118] 24) a first IP address, which is allocated by the second network device for the first terminal, and is used by the first network device to forward target communication data to the second network device based on the first IP address after receiving the target communication data from the second terminal, and then forwarded to the first terminal by the second network device, so that communication data transmission under a non-IP or non-UDP or non-TCP scenario can be implemented, transmission efficiency is improved, and the cost of air interface resources is reduced.

[0119] 25) a second IP address, which is allocated by the first network device for the first terminal, for the second network device to forward the target communication data to the first network device based on the T8 destination address after receiving the target communication data from the first terminal, thereby enabling communication data transmission based on a non-IP or non-UDP or non-TCP scenario, improving transmission efficiency, and reducing the overhead of air interface resources.

[0120] Based on this, as a possible implementation, if the second network device communicates with the first network device based on the first IP address and the second IP address, the second network device can be, but is not limited to, a PGW or an SGW or a UPF, etc. That is, the first IP address and the second IP address in the foregoing 24)-25) correspond to the mode 1 in the aforementioned PGW scheme based on the CP.

[0121] It should be noted that the second address information (such as the T8 destination address, the first network device side tunnel information, and the second IP address) allocated by the first network device for the first terminal can be understood or replaced as: the second address information allocated by the first network device for the first terminal to transmit communication data.

[0122] Correspondingly, the second address information (such as the TLT RI, the second network device side tunnel information, and the first IP address) allocated by the second network device for the first terminal can be understood or replaced as: the second address information allocated by the second network device for the first terminal to transmit communication data.

[0123] For the foregoing first correspondence, there can be various ways to obtain it. For example, as an optional implementation, the first network device can receive second information from a third network device, and then determine and save the first correspondence according to the second information and the third information, for the first network device to transmit communication data.

[0124] The third network device can be understood as a control plane network element, such as the third network device establishing a target bearer for the first terminal, etc. Alternatively, the third network device can be, but is not limited to, a P-CSCF, an IMS AS, etc.

[0125] The second information can include, but is not limited to, at least one of the terminal identifier of the first terminal, the second address information allocated by the second network device for the first terminal, such as the TLT RI, the identifier of the target tunnel, the second network device side tunnel information, the first IP address, etc.

[0126] The third information can include, but is not limited to, the first address information, second address information allocated by the first network device for the first terminal, and the like. The second address information allocated by the first network device for the first terminal can be, but is not limited to, the T8 destination address, an identifier of the target tunnel, tunnel information on the first network device side, the second IP address, and the like.

[0127] Based on the foregoing, for the target communication data, the first communication device can implement different manners for transmitting the target communication data according to the first correspondence relationship, according to different sending ends of the target communication data.

[0128] Implementation 1: In a case where the sending end of the target communication data is the first terminal, that is, the target communication data is communication data sent by the first terminal to the second terminal, the first communication device can determine the first address information according to first information (such as a terminal identifier of the first terminal, the T8 destination address, the second IP address, an identifier of the target tunnel, tunnel information on the first network device side, and the like) corresponding to the target communication data and the first correspondence relationship; generate a Real-time Transport Protocol (RTP) data packet according to the first address information and the target communication data; and finally send the RTP data packet to the second terminal. In this way, the sending of the target communication data is implemented through the first correspondence relationship, thereby avoiding the problems of low transmission efficiency and large air interface resource overhead existing when transmission needs to be based on IP or UDP or TCP in the related art.

[0129] The first information corresponding to the target communication data can be understood as first information carried in the target communication data, can be first information associated with the target communication data, or can be information carried in a message header of a message containing the target communication data, and the like, which is not limited herein.

[0130] In a case that the sending end of the target communication data is the second terminal, i.e., the target communication data is an RTP packet sent by the second terminal to the first terminal, the first communication device can determine first information according to the first address information corresponding to the target communication data and the first correspondence relationship, and then send the target communication data to the first terminal based on the first information. The first information can include second address information allocated by the second network device for the first terminal, such as the TLTRI, the first IP address, the identifier of the target tunnel, and the second network device side tunnel information. The second address information corresponds to the target bearer and is used for communication between the second network device and the first network device. In this way, the sending of the target communication data can be realized through the first correspondence relationship, avoiding the problems of low transmission efficiency and large air interface resource overhead in the related art when transmission needs to be based on IP or UDP or TCP.

[0131] It should be noted that, for communication between the first terminal and the second terminal, in addition to the aforementioned configuration of the NIDD bearer between the first terminal and the first network device, for the second terminal and the first network device, the first address information can be an IP address, a port number, or the like, or information of an NIDD bearer used for transmitting communication data of the second terminal.

[0132] That is, as an optional implementation manner, when performing communication between the first terminal and the second terminal, the data transmission between the first terminal and the first network device can be based on the NIDD bearer only, or the data transmission between the first terminal, the second terminal, and the first network device can all be based on the NIDD bearer, so as to further improve the transmission efficiency and reduce the overhead of air interface resources.

[0133] Of course, for the aforementioned target bearer, i.e., the NIDD bearer used for transmitting communication data of the first terminal, the creation manner can also be various. For example, as an optional implementation manner, the third network device can establish the target bearer for the first terminal in a call establishment process or a signaling negotiation process of the first terminal and the second terminal, so that when performing communication data transmission between the first terminal and the second terminal, the first terminal and the first network device can perform communication data transmission based on the target bearer, avoiding the problems of waste of air interface resources and low transmission efficiency caused by communication data transmission based on IP or UDP or TCP in the related art.

[0134] In some embodiments, when the third communication device establishes the target bearer for the first terminal, the implementation process can include any one of the following manner 1 and manner 2, but is not limited thereto.

[0135] Manner 1: The third network device adds (or adds) the target bearer in the created network connection. The network connection can be, but is not limited to, a PDN connection in a 4G mobile communication system, or a PDU session in a 5G mobile communication system, and the like, without limitation.

[0136] Exemplarily, the process of adding the target bearer in the created network connection by the third network device can include, but is not limited to: the third network device sends fourth information to the second network device, for requesting to establish the target bearer for the first terminal in the created network connection; then, the third network device receives fifth information sent by the second network device, the fifth information being used to indicate information of the target bearer.

[0137] Optionally, the fourth information can be carried by, but is not limited to, a NIDD configuration message, and the fourth information can include, but is not limited to, second address information allocated by the first network device for the first terminal. The fifth information can be carried by, but is not limited to, a NIDD configuration response message, and the fifth information can include, but is not limited to, second address information allocated by the second network device for the first terminal. The second address information is used for communication between the first network device and the second network device.

[0138] For example, if the second network device is a SCEF, that is, corresponding to the aforementioned SCEF scheme based on CP implementation, the fourth information can include a T8 destination address allocated by the first network device for the first terminal, and the fifth information can include a TLTRI allocated by the second network device for the first terminal.

[0139] For another example, if the second network device is a PGW, that is, corresponding to the aforementioned manner 2 in the PGW scheme based on CP implementation, the fourth information includes tunnel information or an identifier of a target tunnel on the first network device side, and the fifth information includes tunnel information or an identifier of a target tunnel on the second network device side.

[0140] For still another example, if the second network device is a PGW, that is, corresponding to the aforementioned manner 1 in the PGW scheme based on CP implementation, the fourth information can include the second IP information, and the fifth information can include the first IP information.

[0141] Of course, for the second network device, after receiving the fourth information from the third network device, the process of adding the target bearer to the already created network connection based on the fourth information may include, but is not limited to: the second network device may send a request message to the fourth network device to request modification of the already created network connection, that is, to add the target bearer to the already created network connection. The request message may be, but is not limited to, a modify connection request, and may carry information about the target bearer, such as the target bearer's identifier, Quality of Service (QoS) parameters, etc.

[0142] Next, the fourth network device further requests the first terminal to modify the target bearer based on the request message from the second network device. Then, based on the modification result reported by the first terminal, the fourth network device sends a response message to the second network device, such as a modification connection response.

[0143] Optionally, the fourth network device can be understood as a network element in the core network that interacts with the access network, such as the MME in a 4G mobile communication system or the AMF in a 5G mobile communication system, without any limitation.

[0144] Method 2: The third network device establishes the target bearer for the first terminal according to the target bearer establishment process initiated by the first terminal.

[0145] The target bearer establishment process can also be understood as a connection establishment process, such as a PDN connection establishment process or a PDU session establishment process, to establish the target bearer.

[0146] In this embodiment, the target bearer establishment process initiated by the first terminal can be triggered by the third network device, the second network device, or the first terminal itself, thereby improving the flexibility of triggering the target bearer establishment process.

[0147] For example, assuming the target bearer establishment process is triggered by the third network device, then the process by which the third network device establishes the target bearer for the first terminal according to the target bearer creation process initiated by the first terminal may include, but is not limited to: the third network device sending a sixth message to the first terminal, the sixth message being used to instruct the first terminal to initiate the target bearer creation process; then, after receiving the sixth message, the first terminal may initiate the target bearer creation process according to the sixth message to create the target bearer; finally, the third network device establishing the target bearer for the first terminal according to a seventh message from the second network device, the seventh message being used to request the establishment of the target bearer.

[0148] For example, assuming the target bearer establishment process is triggered by the second network device, the third network device establishes the target bearer for the first terminal according to the target bearer creation process initiated by the first terminal. This includes: the second network device (such as SCEF or PGW) sending a sixth message to the first terminal, the sixth message being used to instruct the first terminal to initiate the target bearer creation process; then, after receiving the sixth message, the first terminal can initiate the target bearer creation process according to the sixth message to create the target bearer; finally, the third network device establishes the target bearer for the first terminal according to an eighth message from the second network device, the eighth message being used to request the establishment of the target bearer for the first terminal.

[0149] For example, assuming the target bearer establishment process is initiated by the first terminal, the process by which the third network device establishes the target bearer for the first terminal according to the target bearer creation process initiated by the first terminal may include, but is not limited to: the first terminal actively initiating a request to establish the target bearer based on the result of call negotiation; or, the first terminal actively initiating a request to establish the target bearer when initiating a call request or receiving a call request, and the third network device may establish the target bearer for the first terminal when it receives the request sent by the first terminal.

[0150] For the aforementioned Method 2, taking a 4G communication system as an example, when the first terminal initiates the target bearer establishment process, its implementation process may include: the first terminal sending a request message to a fourth network device to request the establishment of a PDN connection. The request message may carry the IMS voice access point name (APN), voice data indication, etc. Next, the fourth network device may further send a request message to a second network device based on the request message from the first terminal to request the establishment of the PDN connection. The request message sent by the fourth network device may also carry the IMS voice APN, voice data indication, etc. Then, after receiving the request message from the fourth network device, the second network device may send the seventh or eighth information to the third network device. The seventh or eighth information carries the second address information allocated by the second network device to the first terminal according to the request message, the IMS voice APN, voice data indication, etc., so that the third network device creates a target bearer for the first terminal based on the seventh or eighth information. Thus, the target bearer establishment process is completed.

[0151] Optionally, the fourth network device can be understood as a network element in the core network that interacts with the access network, such as the MME in a 4G mobile communication system and the AMF in a 5G mobile communication system, without any limitation.

[0152] In some embodiments, to enable the transmission of communication data of the first terminal based on the aforementioned established target bearer, the third network device may send second information to the first network device. The second information is related to the target bearer and is used to determine a first correspondence. The first correspondence includes a correspondence between the first information and first address information. The first information includes at least one of the information of the first terminal and the information of the target bearer. The first address information is address information allocated by the first network device to the first terminal and used for communication between the first network device and the second terminal. Therefore, after receiving the target communication data, the first network device can transmit the target communication data based on the first correspondence, achieving the goal of data transmission between the first terminal and the first network device based on the target bearer, improving transmission efficiency, and reducing air interface resource overhead.

[0153] In some embodiments, before establishing the target bearer, if the third communication device receives a call request from the first terminal, it may request the first network device to allocate third information to the first terminal. The third information may include, but is not limited to, the first address information.

[0154] Of course, in addition to the first address information, the third information may also include second address information allocated by the first network device to the first terminal, such as T8 destination address, first IP address, target tunnel identifier, first network device side tunnel information, etc., for the establishment of target bearer, thereby realizing communication between the second network device and the first network device.

[0155] Based on this, in some embodiments, after requesting the first address information, the third network device may also send Session Description Protocol (SDP) information to the second terminal. The SDP information includes the first address information for communication data transmission between the second terminal and the first network device. For example, the second terminal sends the target communication data to the first network device according to the first address information, and then the first network device sends the target communication data to the first terminal according to the first correspondence and the first address information. Alternatively, the first network device may send the target communication data from the first terminal according to the first correspondence related to the first address information.

[0156] In this embodiment of the application, by establishing a NIDD bearer for transmitting voice data for the terminal during the communication process, the transmission efficiency of communication data can be improved and the overhead of air interface resources can be reduced while ensuring normal voice calls.

[0157] Based on the description of each implementation method in the aforementioned method embodiment 200, for ease of understanding, the implementation process of the communication method provided in this application will be further explained below with reference to a 4G communication system.

[0158] Example 1

[0159] Assuming in a 4G communication system, the first network device is an IMS GW, the second network device is an SCEF, the third network device is a P-CSCF / IMS AS, and the fourth network device is an MME, and the third network device adds the target bearer to the already created PDN connection, that is, after the P-CSCF / IMS AS completes SDP negotiation with the second terminal (which can be referred to as UE-2), it initiates the process of adding the target bearer (such as EPS bearer) to the already created PDN connection, then, referring to Figure 1b (i.e., the SCEF scheme based on CP) and Figure 3a, the implementation process of the communication method provided in this example 1 is as follows.

[0160] S300, UE-1 establishes SCEF connection.

[0161] The SCEF connection can be understood as a special type of PDN connection. The process of establishing an SCEF connection will not be described in detail here.

[0162] S301, UE-1 sends a call message.

[0163] The call message may be, but is not limited to, an I1 Invite message, a Circuit Switched (CS) Setup message, a simplified SIP Invite message, etc., and the call message may include the UE-2 terminal identifier, such as MSISDN, SIP URI, or IMPU.

[0164] It should be noted that the simplified SIP Invite message mentioned in the context of this application is based on the normal IMS Invite message, with unnecessary parameters simplified, such as IP address, routing address, SDP, etc.

[0165] The I1 Invite message is an application layer protocol message defined by the 3rd Generation Partnership Project (3GPP) and is used by the terminal for session control.

[0166] S302, P-CSCF / IMS AS requests IMS GW to allocate third information for UE-1, namely, information for transmitting voice data.

[0167] When requesting third information, the P-CSCF / IMS AS can provide the IMS GW with the terminal identifier of UE-1, such as MSISDN, SIP URI, or IMPU.

[0168] The third information may include the first address information allocated by the IMS GW to UE-1 for transmission between the IMS GW and UE-2, such as sending communication data from UE-1 to UE-2, or sending communication data from UE-2 to UE-1. Optionally, the first address information may include, but is not limited to, an IP address or an IP address plus a port number.

[0169] In addition to the first address information, the third information may also include a second address information, such as a T8 destination address, allocated by the IMS GW to the first terminal for communication between the IMS GW and SCEF.

[0170] It is worth noting that when the third information includes the first address information, the third information can also be understood or replaced as information used for SDP negotiation, information used for establishing an RTP connection, or information used for transmitting RTP data, etc., without any limitation.

[0171] S303, the P-CSCF / IMS AS generates a SIP Invite message and sends it to the second terminal via the S-CSCF. The SIP Invite message contains SDP information (such as an SDP offer) that includes the first address information, for use by the UE-2 to communicate with the IMS GW based on the first address information.

[0172] S304, P-CSCF / IMS AS receives a response message sent by UE-2, such as 183 response message, which contains an SDP answer.

[0173] S305, P-CSCF / IMS AS sends a fourth message to SCEF to request the establishment of a target bearer for UE-1, i.e., a transmission channel for transmitting voice data.

[0174] The fourth information may be carried in the NIDD configuration message, and the fourth information may include the T8 destination address allocated by the IMS GW to the UE-1 for the transmission of voice data between the SCEF and the IMS GW.

[0175] The T8 destination address corresponds to the target bearer to be established, or in other words, the information of the target bearer includes the T8 destination address.

[0176] It is worth noting that, regarding the T8 destination address, in addition to the aforementioned IMS GW actively providing it to the P-CSCF / IMS AS in S302, the P-CSCF / IMS AS can also request it from the IMS GW after S304.

[0177] S306, SCEF sends a first request to MME, such as a connection modification request, to add a target bearer to the established SCEF connection.

[0178] The first request may include, but is not limited to, information about the target bearer, such as the target bearer's identifier and QoS parameters. Specifically, if the target bearer is an EPS bearer, then the target bearer's information is the EPS identifier; if the target bearer is a QoS flow, then the target bearer's information is the QoS flow identifier.

[0179] S307, the MME sends a second request to UE-1, such as a modify connection request, to instruct the addition of a target bearer in the established SCEF connection, wherein the second request carries information about the target bearer to be established.

[0180] S308, UE-1 sends a second response to the MME, such as a connection modification response.

[0181] S309, MME sends a first response to SCEF, such as a modify connection response.

[0182] S310, SCEF sends a fifth message to P-CSCF / IMS AS to indicate the information carried by the target.

[0183] The fifth information may carry, but is not limited to, an NIDD configuration response message, and includes a TLTRI allocated by the SCEF for the UE-1, for use in transmitting voice data between the SCEF and the IMS GW.

[0184] S311, P-CSCF / IMS AS provides second information to IMS GW based on fifth information, and IMS GW saves the first correspondence based on the second information and third information.

[0185] The second information may include the TLTRI of SCEF, the terminal identifier of UE-1, etc. The third information may include the terminal identifier of UE-1, first address information, T8 destination address, etc.

[0186] Based on this, the first correspondence may include, but is not limited to, at least one of the following.

[0187] Relationship 1: The correspondence between the terminal identifier and the first address information of UE-1.

[0188] Relationship 2: The correspondence between the first address information and TLTRI.

[0189] Relationship 3: The correspondence between the first address information and the T8 destination address.

[0190] In step S312, the P-CSCF / IMS AS generates a response message based on the 183 message and sends it to UE-1, such as an I1 progress message, a CS call proceeding message, or a simplified SIP 183 message. Note that the simplified SIP 183 message mentioned in this application context does not include the SDP answer.

[0191] S313, P-CSCF / IMS AS receives 180 response message sent by UE-2.

[0192] S314, the P-CSCF / IMS AS generates a response message based on the 180 message from UE-2, such as an I1 progress message, a CS Alerting message, or a simplified 180 response message, and sends the response message to UE-1. Note that the simplified SIP 180 response message mentioned in this application context does not include information such as IP address or routing address.

[0193] S315, the P-CSCF / IMS AS generates a response message, such as an I1 success message, a CS CONNECT message, or a simplified 200 OK response message, based on the 200 OK response message sent from UE-2, and sends the response message to UE-1. Note that the simplified SIP 200 OK response message mentioned in this application context does not include information such as IP address or routing address.

[0194] S316, the UE sends uplink voice data, which is sent via NIDD.

[0195] S317, after receiving the target communication data (i.e., uplink voice data) from UE-1, the IMS GW generates an RTP data packet, such as an RTP data packet containing an IP header, according to the first correspondence.

[0196] The process of the IMS GW generating RTP data packets based on the first correspondence may include: the IMS GW determining the first address information based on at least one of the second address information or the terminal identifier of UE-1 carried or corresponding in the uplink voice data, and the first correspondence, and then using the first address information to generate RTP data packets.

[0197] For example, the IMS GW determines the first address information based on the UE-1 identifier contained in the uplink voice data (e.g., HTTP message) sent by the SCEF and the first correspondence.

[0198] For example, the IMS GW determines the first address information based on the T8 destination address contained in the uplink voice data (e.g., HTTP message) sent by SCEF and the first correspondence.

[0199] For example, the IMS GW determines the first address information based on the TLTRI contained in the uplink voice data (e.g., HTTP message) sent by the SCEF and the first correspondence.

[0200] It is understood that the uplink voice data sent by the aforementioned SCEF refers to the uplink voice data from UE-1 being sent to the IMS GW via the SCEF (which can also be understood as the target bearer).

[0201] S318, the IMS GW transmits the generated RTP packets through the RTP channel with UE-2.

[0202] It is understandable that the RTP channel between the IMS GW and UE-2 is established during the SDP negotiation process in steps S303-S304.

[0203] In addition to uplink voice data, the IMS GW can also receive RTP data packets from UE-2 via the RTP channel, i.e., downlink RTP data.

[0204] S320, the IMS GW generates downlink voice data to be sent to UE-1 based on the RTP data packet, then determines the target address (i.e., the first information in method embodiment 200) based on the first address information corresponding to the downlink voice data and the first correspondence, and sends the generated downlink voice data to the target address.

[0205] The target address includes second address information (such as TLTRI) and source address information of downlink voice data.

[0206] S321, the IMS GW sends the downlink voice data to the TLTRI, and the SCEF further sends it to the MME. The MME then sends the downlink voice data to UE-1 via a Non-Access Stratum (NAS) message.

[0207] It is understood that the implementation process of each step of the communication method provided in Example 1 can refer to the relevant description in the aforementioned method embodiment 200, and will not be repeated here. In addition, Example 1 may include, but is not limited to, the aforementioned S300-S321, that is, Example 1 may include more or fewer steps than described above, and no limitation is made here.

[0208] Example 2

[0209] Assuming in a 4G communication system, the first network device is an IMS GW, the second network device is a PGW / SGW, the third network device is a P-CSCF / IMS AS, and the fourth network device is an MME, and the third network device adds the target bearer to the already created PDN connection, that is, after the P-CSCF / IMS AS completes SDP negotiation with the second terminal (denoted as UE-2), it initiates the process of adding the target bearer (such as EPS bearer) to the already created PDN connection, then, referring to Figure 1d (i.e., mode 2 in the PGW scheme based on CP) and Figure 3b, the implementation process of the communication method provided in this example 2 is as follows.

[0210] S330, UE-1 establishes SCEF connection.

[0211] The SCEF connection can be understood as a special type of PDN connection. The process of establishing an SCEF connection will not be described in detail here.

[0212] S331, UE-1 sends a call message.

[0213] The call message may be, but is not limited to, an I1 Invite message, a CS Setup message, or a simplified SIP Invite message, and may include the UE-2 terminal identifier, such as MSISDN, SIP URI, or IMPU.

[0214] S332, P-CSCF / IMS AS requests IMS GW to allocate third information for UE-1, namely, information for transmitting voice data.

[0215] When requesting third information, the P-CSCF / IMS AS can provide the IMS GW with the terminal identifier of UE-1, such as MSISDN, SIP URI, or IMPU.

[0216] Furthermore, the third information includes the first address information allocated by the IMS GW to UE-1 for transmission between the IMS GW and UE-2, such as sending communication data from UE-1 to UE-2, or sending communication data from UE-2 to UE-1. Optionally, the first address information may include, but is not limited to, IP address and port number.

[0217] Furthermore, the third information may also include second address information allocated by the IMS GW to the first terminal (or SGi PtP tunneling), i.e., IMS GW-side tunneling information (such as SGi PtP tunneling information), for communication between the IMS GW and the PGW / SGW. Optionally, the IMS GW-side tunneling information may include, but is not limited to, the IMS GW's IP address and port number.

[0218] It is worth noting that when the third information includes the first address information, the third information can also be understood or replaced as information used for SDP negotiation, information used for establishing an RTP connection, or information used for transmitting RTP data, etc., without any limitation.

[0219] S333, the P-CSCF / IMS AS generates a SIP Invite message and sends it to the second terminal via the S-CSCF. The SIP Invite message contains the first address information (such as an SDP offer) in its SDP information, for use by the UE-2 to communicate with the IMS GW based on the first address information.

[0220] S334, P-CSCF / IMS AS receives a response message sent by UE-2, such as a 183 response message, which contains an SDP answer.

[0221] S335, the P-CSCF / IMS AS sends a fourth message to the PGW / SGW to request the establishment of a target bearer for UE-1, i.e., a transmission channel for transmitting voice data.

[0222] The fourth information may be carried in the NIDD configuration message, and the fourth information may include the identification information of SGi PtP tunneling allocated by the IMS GW to the UE-1 and the SGi PtP tunneling information on the IMS GW side, for use in transmitting voice data between the PGW / SGW and the IMS GW.

[0223] The identification information of the SGi PtP tunneling, the SGi PtP tunneling information on the IMS GW side, and the target bearer to be established correspond to each other. In other words, the information of the target bearer includes the identification information of the SGi PtP tunneling and / or the SGi PtP tunneling information on the IMS GW side.

[0224] It is worth noting that, regarding the identification information of SGi PtP tunneling and the SGi PtP tunneling information on the IMS GW side, in addition to the aforementioned provision by the IMS GW to the P-CSCF / IMS AS in S332, the P-CSCF / IMS AS may also request the information from the IMS GW after S334.

[0225] S336, the PGW / SGW sends a first request, such as a modify connection request, to the MME to add a target bearer to the established PGW / SGW connection.

[0226] The first request may include, but is not limited to, information about the target bearer, such as the target bearer's identifier and QoS parameters. Specifically, if the target bearer is an EPS bearer, then the target bearer's information is the EPS identifier; if the target bearer is a QoS flow, then the target bearer's information is the QoS flow identifier.

[0227] S337, the MME sends a second request to UE-1, such as a modify connection request, to instruct the addition of a target bearer in the established PGW / SGW connection, wherein the second request carries information about the target bearer to be established.

[0228] S338, UE-1 sends a response message to the MME, such as "modify connection response".

[0229] S339, the MME sends a response message to the PGW / SGW, such as a modify connection response.

[0230] S340, the PGW / SGW sends a fifth message to the P-CSCF / IMS AS to indicate the information of the target bearer.

[0231] The fifth information may carry, but is not limited to, NIDD configuration response messages, and includes PGW-side tunnel information allocated by the PGW / SGW to the UE-1, such as SGi PtP tunnel information, for use in transmitting voice data between the PGW / SGW and the IMS GW.

[0232] S341, P-CSCF / IMS AS provides second information to IMS GW based on the fifth information, and IMS GW saves the first correspondence based on the second information and the third information.

[0233] The second information may include PGW-side tunnel information of the PGW / SGW, the terminal identifier of UE-1, and the identifier of the target tunnel. The third information includes the terminal identifier of UE-1, first address information, IMS GW-side tunnel information, and the identifier of the target tunnel.

[0234] Based on this, the first correspondence may include, but is not limited to, at least one of the following.

[0235] Relationship 1: The correspondence between the terminal identifier and the first address information of UE-1.

[0236] Relationship 2: The correspondence between the first address information and the PGW-side tunnel information.

[0237] Relationship 3: The correspondence between the first address information and the tunnel information on the IMS GW side.

[0238] Relationship 4: The correspondence between the first address information and the identifier of the target tunnel.

[0239] S342, the P-CSCF / IMS AS generates a response message based on the 183 message and sends it to UE-1, such as an I1 progress message, a CS Call proceeding message, or a simplified SIP 183 message.

[0240] S343, P-CSCF / IMS AS receives 180 response message sent by UE-2.

[0241] S344, the P-CSCF / IMS AS generates a response message based on the 180 message from UE-2, such as an I1 progress message, a CS Alerting message, or a simplified 180 response message, and sends the response message to UE-1.

[0242] S345, the P-CSCF / IMS AS receives the 200 OK response message sent from UE-2 and generates a response message, such as an I1 success message, a CS CONNECT message, or a simplified 200 OK response message, and sends the response message to UE-1.

[0243] S346, the UE sends uplink voice data, which is sent via NIDD.

[0244] S347, after receiving the target communication data (i.e., uplink voice data) from UE-1, the IMS GW generates an RTP data packet, such as an RTP data packet with an IP header, according to the first correspondence.

[0245] The process of the IMS GW generating RTP data packets based on the first correspondence may include: the IMS GW determining the first address information based on at least one of the second address information or the terminal identifier of UE-1 carried or corresponding in the uplink voice data, and the first correspondence, and then using the first address information to generate RTP data packets.

[0246] For example, the IMS GW determines the first address information based on the UE-1 identifier contained in the uplink voice data (e.g., HTTP message) sent by the PGW / SGW and the first correspondence.

[0247] For example, when the PGW / SGW transmits uplink voice data to the IMS GW based on the target tunnel, the IMS GW determines the first address information based on at least one of the PGW / SGW-side tunnel information corresponding to the target tunnel, the IMS GW-side tunnel information, and the first correspondence.

[0248] For example, when the PGW / SGW transmits uplink voice data to the IMS GW based on the target tunnel, the IMS GW determines the first address information according to the tunnel identifier of the target tunnel and the first correspondence.

[0249] It is understood that the uplink voice data sent by the aforementioned PGW / SGW refers to uplink voice data from UE-1 that is transmitted to the IMS GW via the PGW / SGW (which can also be understood as the target bearer).

[0250] S348, the IMS GW transmits the generated RTP packets through the RTP channel with UE-2.

[0251] It is understandable that the RTP channel between the IMS GW and UE-2 is established during the SDP negotiation process in steps S333-S334.

[0252] In addition to uplink voice data, the IMS GW can also receive RTP data packets from UE-2 via the RTP channel, i.e., downlink RTP data.

[0253] S350, the IMS GW generates downlink voice data to be sent to UE-1 based on the RTP data packet, then determines the target address (i.e., the first information in method embodiment 200) based on the first address information and the first correspondence contained in the RTP data packet, and sends the generated downlink voice data to the target address. Optionally, the first address information packet is included in the IP header of the RTP data packet.

[0254] The target address includes second address information (such as PGW / SGW side tunnel information, target tunnel identifier) ​​and source address information of downlink voice data.

[0255] S351, the IMS GW sends the downlink voice data to the PGW / SGW based on the PGW / SGW side tunnel information or the identifier of the target tunnel. The PGW / SGW then sends the data to the MME, and the MME sends the downlink voice data to UE-1 via a NAS message.

[0256] It is worth noting that in this Example 2, when UE-1 communicates with PGW / SGW, in addition to the aforementioned communication via NAS signaling in the control plane, it can also be sent to the access network device, such as the base station, via DRB as shown in Figure 1e. The base station then sends the message to PGW / SWG via PDN connection. This Example 2 does not impose any restrictions on this.

[0257] It is understood that the implementation process of each step of the communication method provided in Example 2 can be referred to the relevant description in the aforementioned method embodiment 200, and will not be repeated here. In addition, Example 2 may include, but is not limited to, the aforementioned S330-S351, that is, Example 2 may include more or fewer steps than described above, and no limitation is made here.

[0258] Example 3

[0259] Assuming in a 4G communication system, the first network device is an IMS GW, the second network device is a PGW / SGW, the third network device is a P-CSCF / IMS AS, and the fourth network device is an MME, and the third network device adds the target bearer to the already created PDN connection, that is, after the P-CSCF / IMS AS completes SDP negotiation with the second terminal (denoted as UE-2), it initiates the process of adding the target bearer (such as EPS bearer) to the already created PDN connection, then, referring to Figure 1d (i.e., mode 1 in the PGW scheme based on CP) and Figure 3c, the implementation process of the communication method provided in this example 3 is as follows.

[0260] S360, UE-1 establishes SCEF connection.

[0261] The SCEF connection can be understood as a special type of PDN connection. The process of establishing an SCEF connection will not be described in detail here.

[0262] S361, UE-1 sends a call message.

[0263] The call message may be, but is not limited to, an I1 Invite message, a CS Setup message, or a simplified SIP Request (Invite) message, and may include the UE-2 terminal identifier, such as MSISDN, SIP URI, or IMPU.

[0264] S362, P-CSCF / IMS AS requests IMS GW to allocate third information for UE-1, namely, information for transmitting voice data.

[0265] When requesting third information, the P-CSCF / IMS AS can provide the IMS GW with the terminal identifier of UE-1, such as MSISDN, SIP URI, or IMPU.

[0266] Furthermore, the third information includes the first address information allocated by the IMS GW to UE-1 for transmission between the IMS GW and UE-2, such as sending communication data from UE-1 to UE-2, or sending communication data from UE-2 to UE-1. Optionally, the first address information may include, but is not limited to, IP address and port number.

[0267] Furthermore, the third information may also include second address information, such as a first IP address, assigned by the IMS GW to the first terminal for communication between the IMS GW and the PGW / SGW. Optionally, the first IP address may include, but is not limited to, the IP address and port number of the IMS GW.

[0268] It is worth noting that when the third information includes the first address information, the third information can also be understood or replaced as information used for SDP negotiation, information used for establishing an RTP connection, or information used for transmitting RTP data, etc., without any limitation.

[0269] S363, the P-CSCF / IMS AS generates a SIP Invite message and sends it to the second terminal via the S-CSCF. The SIP Invite message contains the first address information (such as an SDP offer) in its SDP information, for use by the UE-2 to communicate with the IMS GW based on the first address information.

[0270] S364, P-CSCF / IMS AS receives a response message sent by UE-2, such as 183 response message, which contains an SDP answer.

[0271] S365, the P-CSCF / IMS AS sends a fourth message to the PGW / SGW to request the establishment of a target bearer for UE-1, i.e., a transmission channel for transmitting voice data.

[0272] The fourth information may be carried in the NIDD configuration message, and the fourth information may include a second IP address allocated by the IMS GW to the UE-1 for transmitting voice data between the PGW / SGW and the IMS GW.

[0273] The first IP address corresponds to the target bearer to be established. Alternatively, the target bearer information includes the second IP address.

[0274] It is worth noting that, regarding the second IP address, in addition to the aforementioned IMS GW actively providing it to the P-CSCF / IMS AS in S362, the P-CSCF / IMS AS can also request it from the IMS GW after S364.

[0275] S366, the PGW / SGW sends a first request, such as a modify connection request, to the MME to add a target bearer to the established PGW / SGW connection.

[0276] The first request may include, but is not limited to, information about the target bearer, such as the target bearer's identifier and QoS parameters. Specifically, if the target bearer is an EPS bearer, then the target bearer's information is the EPS identifier; if the target bearer is a QoS flow, then the target bearer's information is the QoS flow identifier.

[0277] S367, the MME sends a second request to UE-1, such as a modify connection request, to instruct the addition of a target bearer in the established PGW / SGW connection, wherein the second request carries information about the target bearer to be established.

[0278] S368, UE-1 sends a response message to the MME, such as "modify connection response".

[0279] S369, the MME sends a response message to the PGW / SGW, such as a modify connection response.

[0280] S370, the PGW / SGW sends a fifth message to the P-CSCF / IMS AS to indicate the information of the target bearer.

[0281] The fifth information may carry, but is not limited to, an NIDD configuration response message, and includes a first IP address allocated by the PGW / SGW to the UE-1 for transmitting voice data between the PGW / SGW and the IMS GW.

[0282] S371, P-CSCF / IMS AS provides second information to IMS GW based on the fifth information, and IMS GW saves the first correspondence based on the second information and the third information.

[0283] The second information may include the first IP address of the PGW / SGW, the terminal identifier of UE-1, etc. The third information includes the terminal identifier of UE-1, the first address information, the second IP address, etc.

[0284] Based on this, the first correspondence may include, but is not limited to, at least one of the following.

[0285] Relationship 1: The correspondence between the terminal identifier and the first address information of UE-1.

[0286] Relationship 2: The correspondence between the first address information and the first IP address.

[0287] Relationship 3: The correspondence between the first address information and the second IP address.

[0288] S372, the P-CSCF / IMS AS generates a response message based on the 183 message and sends it to UE-1, such as an I1 progress message, a CS Call proceeding message, or a simplified SIP 183 message.

[0289] S373, P-CSCF / IMS AS receives 180 response message sent by UE-2.

[0290] S374, the P-CSCF / IMS AS generates a response message, such as an I1 progress message, a CS Alerting message, or a simplified 180 response message, based on the 180 message from UE-2, and sends the response message to UE-1.

[0291] S375, the P-CSCF / IMS AS receives the 200 OK response message sent from UE-2 and generates a response message, such as an I1 success message, a CS CONNECT message, or a simplified 200 OK response message, and sends the response message to UE-1.

[0292] S376, the UE sends uplink voice data, which is sent via NIDD.

[0293] S377, after receiving the target communication data (i.e., uplink voice data) from UE-1, the IMS GW generates an RTP data packet, such as an RTP data packet with an IP header, according to the first correspondence.

[0294] The process of the IMS GW generating RTP data packets based on the first correspondence may include: the IMS GW determining the first address information based on at least one of the second address information or the terminal identifier of UE-1 carried or corresponding in the uplink voice data, and the first correspondence, and then using the first address information to generate RTP data packets.

[0295] For example, the IMS GW determines the first address information based on the UE-1 identifier contained in the uplink voice data (e.g., HTTP message) sent by the PGW / SGW and the first correspondence.

[0296] For example, the IMS GW determines the first address information based on the source IP address (i.e., the first IP address) of the uplink voice data and the first correspondence.

[0297] For example, the IMS GW determines the first address information based on the destination IP address (i.e., the second IP address) of the uplink voice data and the first correspondence.

[0298] It is understood that the uplink voice data sent by the aforementioned PGW / SGW refers to uplink voice data from UE-1 that is transmitted to the IMS GW via the PGW / SGW (which can also be understood as the target bearer).

[0299] S378, the IMS GW transmits the generated RTP packets through the RTP channel with UE-2.

[0300] It is understandable that the RTP channel between the IMS GW and UE-2 is established during the SDP negotiation process in steps S363-S364.

[0301] In addition to uplink voice data, the IMS GW can also receive RTP data packets from UE-2 via the RTP channel, i.e., downlink RTP data.

[0302] S380, the IMS GW generates downlink voice data to be sent to UE-1 based on the RTP data packet, then determines the target address (i.e., the first information in method embodiment 200) based on the first address information and the first correspondence contained in the RTP data packet, and sends the generated downlink voice data to the target address.

[0303] The target address includes second address information (such as the first IP address) and source address information of the downlink voice data.

[0304] S381, the IMS GW sends the downlink voice data to the PGW / SGW based on the first IP address, and the PGW / SGW further sends it to the MME. The MME then sends the downlink voice data to UE-1 via a NAS message.

[0305] It is worth noting that in this Example 3, when UE-1 communicates with PGW / SGW, in addition to the aforementioned communication via NAS signaling in the control plane, it can also be sent to the access network device, such as the base station, via DRB as shown in Figure 1e. The base station then sends the message to PGW / SWG via PDN connection. This Example 3 does not impose any restrictions on this.

[0306] It is understood that the implementation process of each step of the communication method provided in Example 3 can refer to the relevant description in the aforementioned method embodiment 200, and will not be repeated here. In addition, Example 3 may include, but is not limited to, the aforementioned S360-S381, that is, Example 3 may include more or fewer steps than described above, and no limitation is made here.

[0307] In Examples 1-3 above, by adding a target bearer to the existing network connection, a target bearer for voice transmission is established for UE-1. This ensures that the call can proceed normally while improving the efficiency of communication data transmission and reducing air interface resource overhead.

[0308] Example 4

[0309] In a 4G communication system, the first network device is an IMS GW, the second network device is an SCEF, the third network device is a P-CSCF / IMS AS, and the fourth network device is an MME. The third network device establishes the target bearer for the first terminal according to the target bearer establishment process initiated by the first terminal. That is, after the P-CSCF / IMS AS completes SDP negotiation with the second terminal (which can be referred to as UE-2), it triggers UE-1 to establish a new SCEF connection to transmit communication data.

[0310] Based on this, please refer to Figure 1b (i.e., the SCEF scheme based on CP) and Figure 4a. The implementation process of the communication method provided in this example 4 is as follows.

[0311] S400, UE-1 establishes SCEF connection.

[0312] The SCEF connection can be understood as a special type of PDN connection. The process of establishing an SCEF connection will not be described in detail here.

[0313] S401, UE-1 sends a call message.

[0314] The call message may be, but is not limited to, an I1 Invite message, a CS Setup message, or a simplified SIP Invite message, and may include the UE-2 terminal identifier, such as MSISDN, SIP URI, or IMPU.

[0315] S402, P-CSCF / IMS AS requests IMS GW to allocate third information for UE-1, namely, information for transmitting voice data.

[0316] When requesting third information, the P-CSCF / IMS AS can provide the IMS GW with the terminal identifier of UE-1, such as MSISDN, SIP URI, or IMPU.

[0317] Furthermore, the third information includes the first address information allocated by the IMS GW to UE-1 for transmission between the IMS GW and UE-2, such as sending communication data from UE-1 to UE-2, or sending communication data from UE-2 to UE-1. Optionally, the first address information may include, but is not limited to, an IP address or an IP address plus a port number.

[0318] In addition to the first address information, the third information may also include a second address information, such as a T8 destination address, allocated by the IMS GW to the first terminal for communication between the IMS GW and SCEF.

[0319] It is worth noting that when the third information includes the first address information, the third information can also be understood or replaced as information used for SDP negotiation, information used for establishing an RTP connection, or information used for transmitting RTP data, etc., without any limitation.

[0320] S403, the P-CSCF / IMS AS generates a SIP Invite message and sends it to the second terminal via the S-CSCF. The SIP Invite message contains the first address information (such as an SDP offer) in its SDP information, for use by the UE-2 to communicate with the IMS GW based on the first address information.

[0321] S404, P-CSCF / IMS AS receives a response message sent by UE-2, such as 183 response message, which contains an SDP answer.

[0322] S405, the P-CSCF / IMS AS generates a response message based on the 183 message and sends it to UE-1. The response message may be, but is not limited to, an I1 progress message, a CS Call proceeding message, or a simplified SIP 183 message.

[0323] Optionally, the response message may include a sixth piece of information to instruct UE-1 to establish an SCEF connection for transmitting voice data, i.e., a target bearer.

[0324] It is worth noting that the core idea of ​​S405 is to trigger UE-1 to establish an SCEF connection or PDN connection for transmitting voice data. Of course, in addition to S405, other implementation methods are also possible. For example, an SMS message carrying sixth information can be sent to UE-1 via SCEF to instruct UE-1 to establish an SCEF connection or PDN connection for transmitting voice data; or, UE-1 can actively initiate a request to establish an SCEF connection or PDN connection for transmitting voice data based on the response message received from step S405.

[0325] S406, UE-1 initiates a target bearer establishment procedure, such as a PDN connection establishment request.

[0326] For example, a PDN connection establishment request can carry information for requesting the establishment of a target bearer, such as IMS voice APN and voice data indication.

[0327] The process by which UE-1 establishes an SCEF connection through a PDN connection establishment request will not be described in detail here.

[0328] S407. After receiving a PDN connection establishment request, the MME can send a PDN connection establishment request, such as Create connection request, to the SCEF and carry information for requesting the establishment of the target bearer, such as IMS voice APN, voice data indication, etc.

[0329] Optionally, the information carried in the PDN connection establishment request in S406 and the PDN connection establishment request in S407 can be the same or different. This is because the PDN connection establishment request in S406 and the PDN connection establishment request in S407 are different messages; that is, the information carried in the PDN connection establishment request in S406 and the PDN connection establishment request in S407 is transmitted through different parameters.

[0330] S408, SCEF sends the seventh message to P-CSCF / IMS AS.

[0331] The seventh piece of information can be carried in the NIDD configuration message, and the seventh piece of information may include the information used to request the establishment of the target bearer and the TLTRI. The information used to request the establishment of the target bearer may be, but is not limited to, IMS voice APN, voice data indication, etc.

[0332] The TLTRI is information about the SCEF connection to be established (i.e., the target bearer) for communication between the SCEF and the IMS GW, such as transmitting voice data.

[0333] S409, P-CSCF / IMS AS provides second information to IMS GW, and IMS GW saves the first correspondence based on the second information and the third information.

[0334] The second information may include the TLTRI of SCEF, the terminal identifier of UE-1, etc. The third information includes the terminal identifier of UE-1, the first address information, the T8 destination address, etc.

[0335] Based on this, the first correspondence may include, but is not limited to, at least one of the following.

[0336] Relationship 1: The correspondence between the terminal identifier and the first address information of UE-1.

[0337] Relationship 2: The correspondence between the first address information and TLTRI.

[0338] Relationship 3: The correspondence between the first address information and the T8 destination address.

[0339] S410, P-CSCF / IMS AS sends response information corresponding to the seventh information to SCEF, which may be carried in the NIDD configuration response message, and the response information may carry the T8 destination address.

[0340] S411, the P-CSCF / IMS AS generates a response message based on the 183 message and sends it to UE-1, such as an I1 progress message, a CS Call proceeding message, or a simplified SIP 183 message.

[0341] S412, P-CSCF / IMS AS receives 180 response message sent by UE-2.

[0342] S413, the P-CSCF / IMS AS generates a response message, such as an I1 progress message, a CS Alerting message, or a simplified 180 response message, based on the 180 response message from UE-2, and sends the response message to UE-1.

[0343] S414, the P-CSCF / IMS AS generates a response message, such as an I1 success message, a CS CONNECT message, or a simplified 200 OK response message, based on the 200 OK response message sent from UE-2, and sends the response message to UE-1.

[0344] S415, UE-1 sends uplink voice data, which is sent via NIDD.

[0345] S416, after receiving the target communication data (i.e., uplink voice data) from UE-1, the IMS GW generates an RTP data packet, such as an RTP data packet with an IP header, according to the first correspondence.

[0346] The process of the IMS GW generating RTP data packets based on the first correspondence may include: the IMS GW determining the first address information based on at least one of the second address information or the terminal identifier of UE-1 carried or corresponding in the uplink voice data, and the first correspondence, and then using the first address information to generate RTP data packets.

[0347] For example, the IMS GW determines the first address information based on the UE-1 identifier contained in the uplink voice data (e.g., HTTP message) sent by the SCEF and the first correspondence.

[0348] For example, the IMS GW determines the first address information based on the T8 destination address contained in the uplink voice data (e.g., HTTP message) sent by SCEF and the first correspondence.

[0349] For example, the IMS GW determines the first address information based on the TLTRI contained in the uplink voice data (e.g., HTTP message) sent by the SCEF and the first correspondence.

[0350] It is understood that the uplink voice data sent by the aforementioned SCEF refers to the uplink voice data from UE-1 being sent to the IMS GW via the SCEF (which can also be understood as the target bearer).

[0351] S417, the IMS GW transmits the generated RTP packets through the RTP channel with UE-2.

[0352] It is understandable that the RTP channel between the IMS GW and UE-2 is established during the SDP negotiation process in steps S403-S404.

[0353] In addition to uplink voice data, the IMS GW can also receive RTP data packets from UE-2 via the RTP channel, i.e., downlink RTP data.

[0354] S419, the IMS GW generates downlink voice data to be sent to UE-1 based on the RTP data packet, then determines the target address (i.e., the first information in method embodiment 200) based on the first address information and the first correspondence contained in the RTP data packet, and sends the generated downlink voice data to the target address.

[0355] The target address includes second address information (such as TLTRI) and source address information of downlink voice data.

[0356] S420, the IMS GW sends the downlink voice data to the TLTRI, and the SCEF further sends it to the MME. The MME then sends the downlink voice data to UE-1 via a Non-Access Stratum (NAS) message.

[0357] It is understood that the implementation process of each step of the communication method provided in Example 4 can refer to the relevant description in the aforementioned method embodiment 200, and will not be repeated here. In addition, Example 4 may include, but is not limited to, the aforementioned S400-S420, that is, Example 4 may include more or fewer steps than described above, and no limitation is made here.

[0358] Example 5

[0359] In a 4G communication system, the first network device is an IMS GW, the second network device is an SCEF, the third network device is a P-CSCF / IMS AS, and the fourth network device is an MME. The third network device establishes the target bearer for the first terminal according to the target bearer establishment process initiated by the first terminal. That is, after the P-CSCF / IMS AS completes SDP negotiation with the second terminal (which can be referred to as UE-2), it triggers UE-1 to establish a new SCEF connection to transmit communication data.

[0360] Based on this, please refer to Figure 1d (i.e., mode 2 in the PGW scheme based on CP) and Figure 4b. The implementation process of the communication method provided in this example 3 is as follows.

[0361] S430, UE-1 establishes SCEF connection.

[0362] The SCEF connection can be understood as a special type of PDN connection. The process of establishing an SCEF connection will not be described in detail here.

[0363] S431, UE-1 sends a call message.

[0364] The call message may be, but is not limited to, an I1 Invite message, a CS Setup message, or a simplified SIP Invite, and may include the UE-2 terminal identifier, such as MSISDN, SIP URI, or IMPU.

[0365] S432, P-CSCF / IMS AS requests IMS GW to allocate third information for UE-1, namely, information for transmitting voice data.

[0366] When requesting third information, the P-CSCF / IMS AS can provide the IMS GW with the terminal identifier of UE-1, such as MSISDN, SIP URI, or IMPU.

[0367] Furthermore, the third information includes the first address information allocated by the IMS GW to UE-1 for transmission between the IMS GW and UE-2, such as sending communication data from UE-1 to UE-2, or sending communication data from UE-2 to UE-1. Optionally, the first address information may include, but is not limited to, an IP address or an IP address plus a port number.

[0368] In addition to the first address information, the third information may also include a second address information, such as a T8 destination address, allocated by the IMS GW to the first terminal for communication between the IMS GW and SCEF.

[0369] It is worth noting that when the third information includes the first address information, the third information can also be understood or replaced as information used for SDP negotiation, information used for establishing an RTP connection, or information used for transmitting RTP data, etc., without any limitation.

[0370] S433, the P-CSCF / IMS AS generates a SIP Invite message and sends it to the second terminal via the S-CSCF. The SIP Invite message contains the first address information (such as an SDP offer) in its SDP information, for use by the UE-2 to communicate with the IMS GW based on the first address information.

[0371] S434, the P-CSCF / IMS AS receives a response message sent by UE-2, such as a 183 response message, which contains an SDP answer.

[0372] S435, the P-CSCF / IMS AS generates a response message based on the 183 message and sends it to UE-1. The response message may be, but is not limited to, an I1 progress message, a CS Call proceeding message, or a simplified SIP 183 message.

[0373] Optionally, the response message may include a sixth piece of information to instruct UE-1 to establish an SCEF connection for transmitting voice data, i.e., a target bearer.

[0374] It is worth noting that the core idea of ​​S435 is to trigger UE-1 to establish an SCEF connection for transmitting voice data. Of course, in addition to S435, other implementation methods are also possible. For example, a text message carrying sixth information can be sent to UE-1 via SCEF to instruct UE-1 to establish an SCEF connection for transmitting voice data.

[0375] S436, UE-1 initiates a target bearer establishment procedure, such as a PDN connection establishment request.

[0376] For example, a PDN connection establishment request can carry information for requesting the establishment of a target bearer, such as IMS voice APN and voice data indication.

[0377] The process by which UE-1 establishes an SCEF connection through a PDN connection establishment request will not be described in detail here.

[0378] S437. After receiving a PDN connection establishment request, the MME can send a PDN connection establishment request, such as Create connection request, to the SCEF and carry information for requesting the establishment of the target bearer, such as IMS voice APN, voice data indication, etc. in the PDN connection establishment request.

[0379] Optionally, the information carried in the PDN connection establishment request in S436 and the PDN connection establishment request in S437 can be the same or different. This is because the PDN connection establishment request in S436 and the PDN connection establishment request in S437 are different messages; that is, the information carried in the PDN connection establishment request in S436 and the PDN connection establishment request in S437 is transmitted through different parameters.

[0380] S438, SCEF sends the seventh message to P-CSCF / IMS AS.

[0381] The seventh piece of information can be carried in the NIDD configuration message, and it may include information for requesting the establishment of the target bearer and PGW / SGW-side tunnel information. The information for requesting the establishment of the target bearer may be, but is not limited to, IMS voice APN, voice data indication, etc.

[0382] The PGW / SGW side tunnel information is the information of the SCEF connection to be established (i.e., the target bearer), which is used for communication between the SCEF and the IMS GW, such as transmitting voice data.

[0383] S439, P-CSCF / IMS AS provides second information to IMS GW, and IMS GW saves the first correspondence based on the second information and the third information.

[0384] The second information may include SCEF's PGW / SGW-side tunnel information, the identifier of the target tunnel, and the terminal identifier of UE-1. The third information includes the terminal identifier of UE-1, first address information, IMS GW-side tunnel information, and the identifier of the target tunnel.

[0385] Based on this, the first correspondence may include, but is not limited to, at least one of the following.

[0386] Relationship 1: The correspondence between the terminal identifier and the first address information of UE-1.

[0387] Relationship 2: The correspondence between the first address information and the PGW-side tunnel information.

[0388] Relationship 3: The correspondence between the first address information and the tunnel information on the IMS GW side.

[0389] Relationship 4: The correspondence between the first address information and the identifier of the target tunnel.

[0390] S440, P-CSCF / IMS AS sends response information corresponding to the eighth information to SCEF, such as being carried in the NIDD configuration response message, and the response information may carry IMS GW-side tunnel information or the identifier of the target tunnel, etc.

[0391] S441, the P-CSCF / IMS AS generates a response message based on the 183 message and sends it to UE-1, such as an I1 progress message, a CS Call proceeding message, or a simplified 183 response message.

[0392] S442, P-CSCF / IMS AS receives 180 response message sent by UE-2.

[0393] S443, the P-CSCF / IMS AS generates a response message, such as an I1 progress message or a CS Alerting message, based on the 180 message from UE-2, and sends the response message to UE-1.

[0394] S444, the P-CSCF / IMS AS receives the 200 OK response message sent from UE-2 and generates a response message, such as an I1 success message, a CS CONNECT message, or a simplified 200 OK response message, and sends the response message to UE-1.

[0395] S445, the UE sends uplink voice data, which is sent via NIDD.

[0396] S446, after receiving the target communication data (i.e., uplink voice data) from UE-1, the IMS GW generates an RTP data packet, such as an RTP data packet with an IP header, according to the first correspondence.

[0397] The process of the IMS GW generating RTP data packets based on the first correspondence may include: the IMS GW determining the first address information based on at least one of the second address information or the terminal identifier of UE-1 carried or corresponding in the uplink voice data, and the first correspondence, and then using the first address information to generate RTP data packets.

[0398] For example, the IMS GW determines the first address information based on the UE-1 identifier contained in the uplink voice data (e.g., HTTP message) sent by the PGW / SGW and the first correspondence.

[0399] For example, when the PGW / SGW transmits uplink voice data to the IMS GW based on the target tunnel, the IMS GW determines the first address information based on at least one of the PGW / SGW-side tunnel information corresponding to the target tunnel, the IMS GW-side tunnel information, and the first correspondence.

[0400] For example, when the PGW / SGW transmits uplink voice data to the IMS GW based on the target tunnel, the IMS GW determines the first address information according to the tunnel identifier of the target tunnel and the first correspondence.

[0401] It is understood that the uplink voice data sent by the aforementioned PGW / SGW refers to uplink voice data from UE-1 that is transmitted to the IMS GW via the PGW / SGW (which can also be understood as the target bearer).

[0402] S447, the IMS GW transmits the generated RTP packets through the RTP channel with UE-2.

[0403] It is understandable that the RTP channel between the IMS GW and UE-2 is established during the SDP negotiation process in steps S433-S434.

[0404] In addition to uplink voice data, the IMS GW can also receive RTP data packets from UE-2 via the RTP channel, i.e., downlink RTP data.

[0405] S449, the IMS GW generates downlink voice data to be sent to UE-1 based on the RTP data packet, then determines the target address (i.e., the first information in method embodiment 200) based on the first address information and the first correspondence contained in the RTP data packet, and sends the generated downlink voice data to the target address.

[0406] The target address includes second address information (such as PGW / SGW side tunnel information, target tunnel identifier) ​​and source address information of downlink voice data.

[0407] S450, the IMS GW sends the downlink voice data to the PGW / SGW based on the PGW / SGW side tunnel information or the identifier of the target tunnel. The PGW / SGW then sends the data to the MME, and the MME sends the downlink voice data to UE-1 via a NAS message.

[0408] It is worth noting that in this Example 5, when UE-1 communicates with PGW / SGW, in addition to the aforementioned communication via NAS signaling in the control plane, it can also be sent to the access network device, such as the base station, via DRB as shown in Figure 1e. The base station then sends the message to PGW / SWG via PDN connection. This Example 5 does not impose any restrictions on this.

[0409] It is understood that the implementation process of each step of the communication method provided in Example 5 can be referred to the relevant description in the aforementioned method embodiment 200, and will not be repeated here. In addition, Example 5 may include, but is not limited to, the aforementioned S430-S450, that is, Example 5 may include more or fewer steps than described above, and no limitation is made here.

[0410] Example 6

[0411] In a 4G communication system, the first network device is an IMS GW, the second network device is a PGW / SGW, the third network device is a P-CSCF / IMS AS, and the fourth network device is an MME. The third network device establishes the target bearer for the first terminal according to the target bearer establishment process initiated by the first terminal. That is, after the P-CSCF / IMS AS completes SDP negotiation with the second terminal (which can be referred to as UE-2), it triggers UE-1 to establish a new SCEF connection to transmit communication data.

[0412] Based on this, please refer to Figure 1d (i.e., mode 1 in the PGW scheme based on CP) and Figure 4c. The implementation process of the communication method provided in this example 3 is as follows.

[0413] S460, UE-1 establishes SCEF connection.

[0414] The SCEF connection can be understood as a special type of PDN connection. The process of establishing an SCEF connection will not be described in detail here.

[0415] S461, UE-1 sends a call message.

[0416] The call message may be, but is not limited to, an I1 Invite message, a CS Setup message, or a simplified SIP Invite message, and may include the UE-2 terminal identifier, such as MSISDN, SIP URI, or IMPU.

[0417] S462, P-CSCF / IMS AS requests IMS GW to allocate third information for UE-1, namely, information for transmitting voice data.

[0418] When requesting third information, the P-CSCF / IMS AS can provide the IMS GW with the terminal identifier of UE-1, such as MSISDN, SIP URI, or IMPU.

[0419] Furthermore, the third information includes the first address information allocated by the IMS GW to UE-1 for transmission between the IMS GW and UE-2, such as sending communication data from UE-1 to UE-2, or sending communication data from UE-2 to UE-1. Optionally, the first address information may include, but is not limited to, IP address and port number.

[0420] Furthermore, the third information may also include second address information, such as a first IP address, assigned by the IMS GW to the first terminal for communication between the IMS GW and the PGW / SGW. Optionally, the first IP address may include, but is not limited to, the IP address and port number of the IMS GW.

[0421] It is worth noting that when the third information includes the first address information, the third information can also be understood or replaced as information used for SDP negotiation, information used for establishing an RTP connection, or information used for transmitting RTP data, etc., without any limitation.

[0422] S463, the P-CSCF / IMS AS generates a SIP Invite message and sends it to the second terminal via the S-CSCF. The SIP Invite message contains the first address information (such as an SDP offer) in its SDP information, for use by the UE-2 to communicate with the IMS GW based on the first address information.

[0423] S464, P-CSCF / IMS AS receives a response message sent by UE-2, such as 183 response message, which contains an SDP answer.

[0424] S465, the P-CSCF / IMS AS generates a response message based on the 183 message and sends it to UE-1. The response message may be, but is not limited to, an I1 progress message, a CS Call proceeding message, or a simplified SIP 183 message.

[0425] Optionally, the response message may include a sixth piece of information to instruct UE-1 to establish an SCEF connection for transmitting voice data, i.e., a target bearer.

[0426] It is worth noting that the core idea of ​​S465 is to trigger UE-1 to establish an SCEF connection for transmitting voice data. Of course, in addition to S465, there can be other implementation methods. For example, SCEF can also be used to send a text message carrying sixth information to UE-1 to instruct UE-1 to establish an SCEF connection for transmitting voice data.

[0427] S466, UE-1 initiates a target bearer establishment procedure, such as a PDN connection establishment request.

[0428] For example, a PDN connection establishment request can carry information for requesting the establishment of a target bearer, such as IMS voice APN and voice data indication.

[0429] The process by which UE-1 establishes an SCEF connection through a PDN connection establishment request will not be described in detail here.

[0430] S467. After receiving a PDN connection establishment request, the MME can send a PDN connection establishment request, such as Create connection request, to the SCEF and carry information for requesting the establishment of the target bearer, such as IMS voice APN, voice data indication, etc. in the PDN connection establishment request.

[0431] Optionally, the information carried in the PDN connection establishment request in S466 and the PDN connection establishment request in S467 can be the same or different. This is because the PDN connection establishment request in S466 and the PDN connection establishment request in S467 are different messages; that is, the information carried in the PDN connection establishment request in S466 and the PDN connection establishment request in S467 is transmitted through different parameters.

[0432] S468, SCEF sends the seventh message to P-CSCF / IMS AS.

[0433] The seventh piece of information can be carried in the NIDD configuration message, and the seventh piece of information may include the information used to request the establishment of the target bearer and the first IP address. The information used to request the establishment of the target bearer may be, but is not limited to, IMS voice APN, voice data indication, etc.

[0434] The first IP address is the information of the SCEF connection to be established (i.e., the target bearer) for communication between the PGW / SGW and the IMS GW, such as the transmission of voice data.

[0435] S469, P-CSCF / IMS AS provides second information to IMS GW, and IMS GW saves the first correspondence based on the second information and the third information.

[0436] The second information may include a first IP address, the terminal identifier of UE-1, etc. The third information includes the terminal identifier of UE-1, first address information, second IP address, etc.

[0437] Based on this, the first correspondence may include, but is not limited to, at least one of the following.

[0438] Relationship 1: The correspondence between the terminal identifier and the first address information of UE-1.

[0439] Relationship 2: The correspondence between the first address information and the first IP address.

[0440] Relationship 3: The correspondence between the first address information and the second IP address.

[0441] S470, P-CSCF / IMS AS sends a response message corresponding to the eighth message to SCEF, which may be carried in the NIDD configuration response message, and the response message may carry a second IP address.

[0442] S471, the P-CSCF / IMS AS generates a response message based on the 183 message and sends it to UE-1, such as an I1 progress message, a CS Call proceeding message, or a simplified SIP 183 message.

[0443] S472, P-CSCF / IMS AS receives 180 response message sent by UE-2.

[0444] S473, the P-CSCF / IMS AS generates a response message based on the 180 message from UE-2, such as an I1 progress message, a CS Alerting message, or a simplified 180 response message, and sends the response message to UE-1.

[0445] S474, the P-CSCF / IMS AS receives the 200 OK response message sent from UE-2 and generates a response message, such as an I1 success message or a simplified 200 OK response to the CS CONNECT message, and sends the response message to UE-1.

[0446] S475, the UE sends uplink voice data, which is sent via NIDD.

[0447] S476, after receiving the target communication data (i.e., uplink voice data) from UE-1, the IMS GW generates an RTP data packet, such as an RTP data packet with an IP header, according to the first correspondence.

[0448] The process of the IMS GW generating RTP data packets based on the first correspondence may include: the IMS GW determining the first address information based on at least one of the second address information or the terminal identifier of UE-1 carried or corresponding in the uplink voice data, and the first correspondence, and then using the first address information to generate RTP data packets.

[0449] For example, the IMS GW determines the first address information based on the UE-1 identifier contained in the uplink voice data (e.g., HTTP message) sent by the PGW / SGW and the first correspondence.

[0450] For example, the IMS GW determines the first address information based on the source IP address (i.e., the first IP address) of the uplink voice data and the first correspondence.

[0451] For example, the IMS GW determines the first address information based on the destination IP address (i.e., the second IP address) of the uplink voice data and the first correspondence.

[0452] It is understood that the uplink voice data sent by the aforementioned PGW / SGW refers to uplink voice data from UE-1 that is transmitted to the IMS GW via the PGW / SGW (which can also be understood as the target bearer).

[0453] S477, the IMS GW transmits the generated RTP packets through the RTP channel with UE-2.

[0454] It is understandable that the RTP channel between the IMS GW and UE-2 is established during the SDP negotiation process in steps S463-S464.

[0455] In addition to uplink voice data, the IMS GW can also receive RTP data packets from UE-2 via the RTP channel, i.e., downlink RTP data.

[0456] S479, the IMS GW generates downlink voice data to be sent to UE-1 based on the RTP data packet, then determines the target address (i.e., the first information in method embodiment 200) based on the first address information and the first correspondence contained in the RTP data packet, and sends the generated downlink voice data to the target address.

[0457] The target address includes second address information (such as the first IP address) and source address information of the downlink voice data.

[0458] S480, the IMS GW sends the downlink voice data to the PGW / SGW based on the first IP address, and the PGW / SGW further sends it to the MME. The MME then sends the downlink voice data to UE-1 via a NAS message.

[0459] It is worth noting that in this Example 6, when UE-1 communicates with PGW / SGW, in addition to the aforementioned communication via NAS signaling in the control plane, it can also be sent to the access network device, such as the base station, via DRB as shown in Figure 1e. The base station then sends the message to PGW / SWG via PDN connection. This Example 6 does not impose any restrictions on this.

[0460] It is understood that the implementation process of each step of the communication method provided in Example 6 can be referred to the relevant description in the aforementioned method embodiment 200, and will not be repeated here. In addition, Example 6 may include, but is not limited to, the aforementioned S460-S480, that is, Example 6 may include more or fewer steps than described above, and no limitation is made here.

[0461] In the communication methods provided in Examples 4-6 above, the target bearer establishment process initiated by UE-1 establishes a target bearer for UE-1 to transmit voice, which can improve the transmission efficiency of communication data and reduce air interface resource overhead while ensuring normal call operation.

[0462] Figure 5 shows a flowchart of a communication method 500 provided in an exemplary embodiment of this application. This method 500 can be executed by, but is not limited to, a third network device, specifically by hardware and / or software installed in the third network device. In this embodiment, the method 500 may include at least the following steps.

[0463] S510, during the call establishment process between the first terminal and the second terminal, the third network device establishes a target bearer for the first terminal.

[0464] The target bearer is a non-IP data transmission NIDD bearer used to transmit communication data to the first terminal.

[0465] In some embodiments, establishing a target bearer for the first terminal includes any one of the following: the third network device adds the target bearer to an existing network connection; the third network device establishes the target bearer for the first terminal according to the target bearer establishment process initiated by the first terminal.

[0466] In some embodiments, the third network device adds the target bearer to an already created network connection, including: the third network device sending fourth information to the second network device, the fourth information being used to request the establishment of the target bearer for the first terminal in the already created network connection; the third network device receiving fifth information sent by the second network device, the fifth information being used to indicate information about the target bearer.

[0467] In some embodiments, the fourth information includes second address information allocated by the first network device to the first terminal, and the fifth information includes second address information allocated by the second network device to the first terminal; wherein the second address information is used for communication between the first network device and the second network device.

[0468] In some embodiments, the network connection includes at least one of a PDN connection and a PDU session.

[0469] In some embodiments, the third network device establishes the target bearer for the first terminal according to the target bearer creation process initiated by the first terminal, including: the third network device sending sixth information to the first terminal, the sixth information being used to instruct the first terminal to initiate the target bearer creation process; the third network device establishing the target bearer for the first terminal according to seventh information from the second network device, the seventh information being used to request the establishment of the target bearer.

[0470] In some embodiments, the third network device establishes the target bearer for the first terminal according to the target bearer creation process initiated by the first terminal, including: the third network device establishes the target bearer for the first terminal according to eighth information from the second network device, wherein the eighth information is used to request the establishment of the target bearer for the first terminal.

[0471] In some embodiments, the method further includes: the third network device sending second information to the first network device;

[0472] Wherein, the second information is related to the target bearer and is used to determine the first correspondence relationship, the first correspondence relationship includes the correspondence relationship between the first information and the first address information, the first information includes at least one of the information of the first terminal and the information of the target bearer, and the first address information is the address information allocated by the first network device to the first terminal and used for communication between the first network device and the second terminal.

[0473] In some embodiments, the second information includes at least one of the following: the terminal identifier of the first terminal; and second address information assigned to the first terminal by the second network device.

[0474] In some embodiments, the first correspondence includes at least one of the following: a correspondence between the terminal identifier of the first terminal and the first address information; and a correspondence between the second address information and the first address information, wherein the second address information is used for communication between the second network device and the first network device.

[0475] In some embodiments, the second address information includes at least one of the following: a T8 Long Transaction Reference Identifier (TLTRI), the TLTRI being allocated by the second network device to the first terminal; a T8 destination address, the T8 destination address being allocated by the first network device to the first terminal; target tunnel information, the target tunnel information being allocated by the first network device or the second network device to the first terminal; a first IP address, the first IP address being allocated by the second network device to the first terminal; and a second IP address, the second IP address being allocated by the first network device to the first terminal.

[0476] In some embodiments, the target tunnel information includes at least one of the following: the identifier of the target tunnel; the first network device-side tunnel information corresponding to the target tunnel; and the second network device-side tunnel information corresponding to the target tunnel.

[0477] In some embodiments, the terminal identifier includes at least one of the following: Mobile Station International Subscriber Identity Serial Number (MSISDN);

[0478] Session initiation protocol (SIP) Uniform Resource Identifier (URI); IP Multimedia Public Identifier (IMPU).

[0479] In some embodiments, the method further includes: the third network device requesting the first network device to allocate third information for the first terminal, the third information including the first address information.

[0480] In some embodiments, the third information further includes second address information assigned by the first network device to the first terminal.

[0481] In some embodiments, the method further includes: the third network device sending SDP information to the second terminal, the SDP information including the first address information.

[0482] In some embodiments, at least one of the following is satisfied: the first network device includes an IMS GW; the second network device includes at least one of SCEF, PGW, SGW, and UPF; and the third network device includes at least one of P-CSCF and IMS-AS.

[0483] This method embodiment 500 has the same or corresponding technical features as the aforementioned method embodiment 200. Therefore, each implementation in this method embodiment 500 can refer to the relevant description in the aforementioned method embodiment 200 and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0484] Figure 6 shows a flowchart of a communication method 600 provided in an exemplary embodiment of this application. This method 600 can be executed by, but is not limited to, a second network device, specifically by hardware and / or software installed in the second network device. In this embodiment, the method 600 may include at least the following steps.

[0485] S610, the second network device receives the ninth message.

[0486] S620, the second network device sends the tenth information to the third network device according to the ninth information.

[0487] Wherein, when the ninth information originates from the first terminal and is used to request the establishment of a target bearer for the first terminal, the tenth information is used to request the establishment of a target bearer for the first terminal. It can be understood that the ninth information can be understood as the third request in the aforementioned method embodiment 200, and the tenth information can be understood as the seventh or eighth information in the aforementioned method embodiment 200, achieving the same or corresponding technical effects, which will not be elaborated further here.

[0488] Alternatively, if the ninth information originates from a third network device and is used to indicate the establishment of a target bearer for the first terminal, the tenth information is used to indicate information about the target bearer; the target bearer is a non-IP data transmission NIDD bearer used to transmit communication data for the first terminal. It can be understood that the ninth information can be understood as the fourth information in the aforementioned method embodiment 200, and the tenth information can be understood as the fifth information in the aforementioned method embodiment 200, achieving the same or corresponding technical effects, which will not be elaborated further here.

[0489] In some embodiments, the method further includes: the second network device sending a sixth message to the first terminal, the sixth message being used to instruct the first terminal to initiate a target bearer creation process.

[0490] In some embodiments, at least one of the following is satisfied: the second network device includes at least one of SCEF, PGW, and UPF; the third network device includes at least one of P-CSCF and IMS-AS.

[0491] This method embodiment 600 has the same or corresponding technical features as the aforementioned method embodiment 200. Therefore, each implementation in this method embodiment 600 can refer to the relevant description in the aforementioned method embodiment 200 and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0492] Figure 7 shows a flowchart of a communication method 700 provided in an exemplary embodiment of this application. This method 700 can be executed by, but is not limited to, a first terminal, and can specifically be executed by hardware and / or software installed in a second network device. In this embodiment, the method 700 may include at least the following steps.

[0493] S710, the first terminal receives sixth information from the second network device or the third network device, the sixth information being used to instruct the first terminal to initiate a target bearer creation process.

[0494] S720, the first terminal initiates the target bearer creation process to create the target bearer.

[0495] The target bearer is a non-IP data transmission NIDD bearer used to transmit communication data to the first terminal.

[0496] In some embodiments, at least one of the following is satisfied: the second network device includes at least one of SCEF, PGW, and UPF; the third network device includes at least one of P-CSCF and IMS-AS.

[0497] This method embodiment 700 has the same or corresponding technical features as the aforementioned method embodiment 200. Therefore, each implementation in this method embodiment 700 can refer to the relevant description in the aforementioned method embodiment 200 and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0498] The communication method provided in this application can be executed by a communication device. This application uses the example of a communication device executing the communication method to illustrate the communication device provided in this application.

[0499] This application provides a communication device. As an example, the communication device may be a communication equipment or a component within a communication equipment, such as a chip. The communication equipment may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0500] The communication device includes a transmission module (such as a receiving module and a transmitting module) and a processing module. The transmission module and processing module can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving module and transmitting module can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0501] Specifically, referring to Figure 8, when the communication device is a network-side device or a component within a network-side device, the communication device 800 includes a transmission module 810 for receiving target communication data; the transmission module 810 is also used to transmit the target communication data according to a first correspondence relationship; wherein, the first correspondence relationship includes a correspondence relationship between first information and first address information, the first information includes at least one of the information of a first terminal and the information of a target bearer, the target bearer is a non-IP data transmission NIDD bearer used to transmit communication data for the first terminal, and the first address information is address information allocated by the first network device to the first terminal and used for communication between the first network device and a second terminal.

[0502] In some embodiments, the first correspondence includes at least one of the following: a correspondence between the terminal identifier of the first terminal and the first address information; a correspondence between the second address information and the first address information, wherein the second address information corresponds to the target bearer and is used for communication between the second network device and the first network device.

[0503] In some embodiments, transmitting the target communication data according to the first correspondence includes: when the target communication data is communication data sent by the first terminal, determining the first address information according to the first information corresponding to the target communication data and the first correspondence; generating a Real-Time Transport Protocol (RTP) data packet according to the first address information and the target communication data; and sending the RTP data packet to the second terminal.

[0504] In some embodiments, the first information includes at least one of the following: the terminal identifier of the first terminal; and second address information assigned to the first terminal by the first network device.

[0505] In some embodiments, transmitting the target communication data according to the first correspondence includes: when the target communication data is an RTP data packet sent to the first terminal, determining the first information according to the first address information corresponding to the target communication data and the first correspondence; and sending the target communication data to the first terminal based on the first information; wherein the first information includes second address information allocated to the first terminal by the second network device.

[0506] In some embodiments, the transmission module 810 is further configured to: receive second information from a third network device; the communication device 800 further includes a processing module 810, configured to save the first correspondence relationship according to the second information and the third information; wherein the third information includes the first address information, and the second information includes at least one of the terminal identifier of the first terminal and the second address information allocated to the first terminal by the second network device.

[0507] In some embodiments, the third information further includes second address information assigned by the first network device to the first terminal.

[0508] In some embodiments, the second address information includes at least one of the following: a T8 Long Transaction Reference Identifier (TLTRI), the TLTRI being allocated by the second network device to the first terminal; a T8 destination address, the T8 destination address being allocated by the first network device to the first terminal; target tunnel information, the target tunnel information being allocated by the first network device or the second network device to the first terminal; a first IP address, the first IP address being allocated by the second network device to the first terminal; and a second IP address, the second IP address being allocated by the first network device to the first terminal.

[0509] In some embodiments, the target tunnel information includes at least one of the following: the identifier of the target tunnel; the first network device-side tunnel information corresponding to the target tunnel; and the second network device-side tunnel information corresponding to the target tunnel.

[0510] In some embodiments, the terminal identifier includes at least one of the following: Mobile Station International Subscriber Identity (MSISDN); Session Initiation Protocol (SIP) Uniform Resource Identifier (URI); IP Multimedia Public Identifier (IMPU).

[0511] In some embodiments, at least one of the following is satisfied: the first network device includes an IP Multimedia Subsystem Gateway (IMS GW); the second network device includes at least one of Service Capability Open Function (SCEF), Packet Data Network Gateway (PGW), Signaling Gateway (SGW), and User Plane Function (UPF); and the third network device includes at least one of Proxy Call Session Control Function (P-CSCF) and IP Multimedia Subsystem Application Server (IMS-AS).

[0512] The communication device 800 provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG2 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0513] Referring to Figure 9, when the communication device 900 is a terminal or a component in a terminal, the communication device 900 includes a processing module 910, used to establish a target bearer for the first terminal during the call establishment process between the first terminal and the second terminal; wherein, the target bearer is a non-IP data transmission NIDD bearer used to transmit communication data for the first terminal.

[0514] In some embodiments, establishing a target bearer for the first terminal includes any one of the following: adding the target bearer to an existing network connection; or establishing the target bearer for the first terminal according to a target bearer establishment process initiated by the first terminal.

[0515] In some embodiments, adding the target bearer to an existing network connection includes: sending fourth information to a second network device, the fourth information being used to request the establishment of the target bearer for the first terminal in the existing network connection; and receiving fifth information sent by the second network device, the fifth information being used to indicate information about the target bearer.

[0516] In some embodiments, the fourth information includes second address information allocated by the first network device to the first terminal, and the fifth information includes second address information allocated by the second network device to the first terminal; wherein the second address information is used for communication between the first network device and the second network device.

[0517] In some embodiments, the network connection includes at least one of a PDN connection and a PDU session.

[0518] In some embodiments, establishing the target bearer for the first terminal according to the target bearer creation process initiated by the first terminal includes: sending a sixth message to the first terminal, the sixth message being used to instruct the first terminal to initiate the target bearer creation process; and the third network device establishing the target bearer for the first terminal according to a seventh message from the second network device, the seventh message being used to request the establishment of the target bearer.

[0519] In some embodiments, establishing the target bearer for the first terminal according to the target bearer creation process initiated by the first terminal includes: establishing the target bearer for the first terminal according to eighth information from the second network device, wherein the eighth information is used to request the establishment of the target bearer for the first terminal.

[0520] In some embodiments, the communication device 900 further includes a transmission module for sending second information to a first network device; wherein the second information is related to the target bearer and is used to determine a first correspondence, the first correspondence including the correspondence between the first information and the first address information, the first information including at least one of the information of the first terminal and the information of the target bearer, and the first address information being the address information allocated by the first network device to the first terminal and used for communication between the first network device and the second terminal.

[0521] In some embodiments, the second information includes at least one of the following: the terminal identifier of the first terminal; and second address information assigned to the first terminal by the second network device.

[0522] In some embodiments, the first correspondence includes at least one of the following: a correspondence between the terminal identifier of the first terminal and the first address information; and a correspondence between the second address information and the first address information, wherein the second address information is used for communication between the second network device and the first network device.

[0523] In some embodiments, the second address information includes at least one of the following: a T8 Long Transaction Reference Identifier (TLTRI), the TLTRI being allocated by the second network device to the first terminal; a T8 destination address, the T8 destination address being allocated by the first network device to the first terminal; target tunnel information, the target tunnel information being allocated by the first network device or the second network device to the first terminal; a first IP address, the first IP address being allocated by the second network device to the first terminal; and a second IP address, the second IP address being allocated by the first network device to the first terminal.

[0524] In some embodiments, the target tunnel information includes at least one of the following: the identifier of the target tunnel; the first network device-side tunnel information corresponding to the target tunnel; and the second network device-side tunnel information corresponding to the target tunnel.

[0525] In some embodiments, the terminal identifier includes at least one of the following: Mobile Station International Subscriber Identity (MSISDN); Session Initiation Protocol (SIP) Uniform Resource Identifier (URI); IP Multimedia Public Identifier (IMPU).

[0526] In some embodiments, the processing module 910 is further configured to request the first network device to allocate third information for the first terminal, the third information including the first address information.

[0527] In some embodiments, the third information further includes second address information assigned by the first network device to the first terminal.

[0528] In some embodiments, the transmission module is further configured to: send SDP information to the second terminal from the third network device, wherein the SDP information includes the first address information.

[0529] In some embodiments, at least one of the following is satisfied: the first network device includes an IMS GW; the second network device includes at least one of SCEF, PGW, SGW, and UPF; and the third network device includes at least one of P-CSCF and IMS-AS.

[0530] The communication device 900 provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG5 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0531] Referring to Figure 10, when the communication device 1000 is a terminal or a component within a terminal, the communication device 1000 includes a transmission module 1010 for receiving ninth information; the transmission module 1010 is further configured to send tenth information to a third network device based on the ninth information; wherein, when the ninth information originates from a first terminal and is used to request the establishment of a target bearer for the first terminal, the tenth information is used to request the establishment of a target bearer for the first terminal; or, when the ninth information originates from a third network device and is used to indicate the establishment of a target bearer for the first terminal, the tenth information is used to indicate information about the target bearer; the target bearer is a non-IP data transmission NIDD bearer used to transmit communication data for the first terminal.

[0532] In some embodiments, the transmission module 1010 is further configured to send a sixth message to the first terminal, the sixth message being used to instruct the first terminal to initiate a target bearer creation process.

[0533] In some embodiments, at least one of the following is satisfied: the second network device includes at least one of SCEF, PGW, and UPF; the third network device includes at least one of P-CSCF and IMS-AS.

[0534] The communication device 1000 provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG6 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0535] Referring to Figure 11, when the communication device 1100 is a terminal or a component within a terminal, the communication device 1100 includes a transmission module 1110 for receiving sixth information from a second network device or a third network device, the sixth information being used to instruct the first terminal to initiate a target bearer creation process; and a processing module 1120 for initiating the target bearer creation process to create a target bearer; wherein the target bearer is a non-IP data transmission NIDD bearer used to transmit communication data to the first terminal.

[0536] In some embodiments, at least one of the following is satisfied: the second network device includes at least one of SCEF, PGW, and UPF; the third network device includes at least one of P-CSCF and IMS-AS.

[0537] The communication device 1100 provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG7 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0538] As shown in Figure 12, this application embodiment also provides a communication device 1200, including a processor 1201 and a memory 1202. The memory 1202 stores a program or instructions that can run on the processor 1201. For example, when the communication device 1200 is a terminal, the program or instructions executed by the processor 1201 implement the various steps of the above-described method embodiment 700 and achieve the same technical effect. When the communication device 1200 is a network-side device, the program or instructions executed by the processor 1201 implement the various steps of the above-described method embodiments 200, 600, or 700 and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0539] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG13. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal may be the communication device 1100 shown in FIG11. Specifically, FIG13 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0540] The terminal 1300 includes, but is not limited to, at least some of the following components: radio frequency unit 1301, network module 1302, audio output unit 1303, input unit 1304, sensor 1305, display unit 1306, user input unit 1307, interface unit 1308, memory 1309, and processor 1310.

[0541] Those skilled in the art will understand that terminal 1300 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to processor 1310 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 13 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0542] It should be understood that, in this embodiment, the input unit 1304 may include a graphics processor 13041 and a microphone 13042. The graphics processor 13041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1306 may include a display panel 13061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1307 includes a touch panel 13071 and at least one of other input devices 13072. The touch panel 13071 is also called a touch screen. The touch panel 13071 may include a touch detection device and a touch controller. Other input devices 13072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0543] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1301 can transmit it to the processor 1310 for processing; in addition, the radio frequency unit 1301 can send uplink data to the network-side device. Typically, the radio frequency unit 1301 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0544] The memory 1309 can be used to store software programs or instructions, as well as various data. The memory 1309 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1309 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1309 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0545] Processor 1310 may include one or more processing units; optionally, processor 1310 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1310.

[0546] The radio frequency unit 1301 is used to receive sixth information from the second network device or the third network device, the sixth information being used to instruct the first terminal to initiate a target bearer creation process; the processor 1310 is used to initiate the target bearer creation process to create a target bearer; wherein the target bearer is a non-IP data transmission NIDD bearer used to transmit communication data for the first terminal.

[0547] In some embodiments, at least one of the following is satisfied: the second network device includes at least one of SCEF, PGW, and UPF; the third network device includes at least one of P-CSCF and IMS-AS.

[0548] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of method embodiment 700 and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0549] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG2, FIG5, or FIG6. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0550] Specifically, this application embodiment also provides a network-side device, which can be the communication device shown in Figures 8-10. As shown in Figure 14, the network-side device 1400 includes: an antenna 1401, a radio frequency (RF) device 1402, a baseband device 1403, a processor 1404, and a memory 1405. The antenna 1401 is connected to the RF device 1402. In the uplink direction, the RF device 1402 receives information through the antenna 1401 and sends the received information to the baseband device 1403 for processing. In the downlink direction, the baseband device 1403 processes the information to be transmitted and sends it to the RF device 1402. The RF device 1402 processes the received information and then transmits it through the antenna 1401.

[0551] The method executed by the network-side device 1400 in the above embodiments can be implemented in the baseband device 1403, which includes a baseband processor.

[0552] The baseband device 1403 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG14. One of the chips is, for example, a baseband processor, which is connected to the memory 1405 via a bus interface to call the program in the memory 1405 and execute the network device operation shown in the above method embodiment.

[0553] The network-side device 1400 may also include a network interface 1406, such as a Common Public Radio Interface (CPRI).

[0554] Specifically, the network-side device 1400 in this application embodiment further includes: instructions or programs stored in memory 1405 and executable on processor 1404. Processor 1404 calls the instructions or programs in memory 1405 to execute the methods executed by the modules shown in FIG8, FIG9 or FIG10 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0555] Specifically, this application also provides a network-side device. As shown in FIG15, the network-side device 1500 includes a processor 1501, a network interface 1502, and a memory 1503. The network-side device may be the communication device shown in FIG8-FIG10. The network interface 1502 is, for example, a common public radio interface (CPRI).

[0556] Specifically, the network-side device 1500 in this application embodiment further includes: instructions or programs stored in memory 1503 and executable on processor 1501. Processor 1501 calls the instructions or programs in memory 1503 to execute the methods executed by the modules shown in FIG8, FIG9 or FIG10 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0557] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described communication method embodiments 200, 500, 600, or 700, and achieve the same technical effect. To avoid repetition, these will not be described again here.

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

[0559] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described communication method embodiments 200, 500, 600, or 700, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0560] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0561] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described communication method embodiments 200, 500, 600, or 700, and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0562] This application also provides a wireless communication system, including a terminal and a network-side device. The terminal can be used to implement various processes of the above-described communication method embodiment 700, and the network-side device can be used to implement various processes of the above-described communication method embodiments 200, 500, or 600, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0563] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0564] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0565] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

A communication method comprises: A first network device receives target communication data; The first network device transmits the target communication data according to a first correspondence relationship; The first correspondence relationship comprises a correspondence relationship between first information and first address information, the first information comprises at least one of information of a first terminal and information of a target bearer, the target bearer is a non-IP data transmission (NIDD) bearer for transmitting communication data for the first terminal, and the first address information is address information allocated by the first network device for the first terminal and used for communication between the first network device and a second terminal. The method of claim 1, wherein, The first correspondence relationship comprises at least one of: A correspondence relationship between a terminal identifier of the first terminal and the first address information; A correspondence relationship between second address information and the first address information, the second address information corresponds to the target bearer and is used for communication between a second network device and the first network device. The method of claim 1 or 2, wherein, The transmitting of the target communication data according to the first correspondence relationship comprises: In a case where the target communication data is communication data sent by the first terminal, determining the first address information according to first information corresponding to the target communication data and the first correspondence relationship; Generating a real-time transport protocol (RTP) data packet according to the first address information and the target communication data; Sending the RTP data packet to the second terminal. The method of any one of claims 1-3, wherein, The first information comprises at least one of: A terminal identifier of the first terminal; Second address information allocated by the first network device for the first terminal. The method of claim 1 or 2, wherein, The transmitting of the target communication data according to the first correspondence relationship comprises: In a case where the target communication data is an RTP data packet sent to the first terminal, determining the first information according to first address information corresponding to the target communication data and the first correspondence relationship; Sending the target communication data to the first terminal based on the first information; The first information comprises second address information allocated by a second network device for the first terminal. The method of any one of claims 1-5, wherein, The method further comprises: The first network device receives second information from a third network device; The first network device saves the first correspondence relationship according to the second information and third information; The third information comprises the first address information, and the second information comprises at least one of a terminal identifier of the first terminal and second address information allocated by the second network device for the first terminal. The method of claim 6, wherein, The third information further comprises second address information allocated by the first network device for the first terminal. The method of any one of claims 2-7, wherein, The second address information comprises at least one of: A T8 long-term transaction reference identifier (TLTRI) allocated by the second network device for the first terminal; A T8 destination address allocated by the first network device for the first terminal; Target tunnel information allocated by the first network device or the second network device for the first terminal; a first IP address, the first IP address being allocated to the first terminal by the second network device; a second IP address, the second IP address being allocated to the first terminal by the first network device. The method of claim 8, wherein, The target tunnel information includes at least one of the following: an identifier of the target tunnel; first network device side tunnel information corresponding to the target tunnel; second network device side tunnel information corresponding to the target tunnel. The method of any one of claims 2-9, wherein, The terminal identifier includes at least one of the following: a mobile station international subscriber identity (MSISDN); a session initiation protocol (SIP) uniform resource identifier (URI); an IP multimedia public identity (IMPU). The method of any one of claims 1-10, wherein, At least one of the following is met: The first network device includes an IP multimedia subsystem gateway (IMS GW); The second network device includes at least one of a service capability exposure function (SCEF), a packet data network gateway (PGW), a signaling gateway (SGW), and a user plane function (UPF); The third network device includes at least one of a proxy call session control function (P-CSCF) and an IP multimedia subsystem application server (IMS-AS). A communication method includes: In a call setup process of a first terminal and a second terminal, a third network device establishes a target bearer for the first terminal; The target bearer is a non-IP data transmission (NIDD) bearer for transmitting communication data for the first terminal. The method of claim 12, wherein, The third network device establishes a target bearer for the first terminal, including any of the following: The third network device adds the target bearer in an already created network connection; The third network device establishes the target bearer for the first terminal according to a target bearer establishment procedure initiated by the first terminal. The method of claim 13, wherein, The third network device adds the target bearer in an already created network connection, including: The third network device sends fourth information to a second network device, the fourth information being used to request establishment of the target bearer for the first terminal in the already created network connection; The third network device receives fifth information sent by the second network device, the fifth information being used to indicate information of the target bearer. The method of claim 14, wherein, The fourth information includes second address information allocated to the first terminal by a first network device, and the fifth information includes second address information allocated to the first terminal by the second network device; The second address information is used for communication between the first network device and the second network device. The method of any one of claims 13-15, wherein, The network connection includes at least one of a PDN connection and a PDU session. The method of claim 13, wherein, The third network device establishes the target bearer for the first terminal according to a target bearer establishment procedure initiated by the first terminal, including: The third network device sends sixth information to the first terminal, the sixth information being used to instruct the first terminal to initiate the target bearer establishment procedure; The third network device establishes the target bearer for the first terminal according to seventh information from a second network device, the seventh information being used to request establishment of the target bearer. The method of claim 13, wherein, The third network device establishes the target bearer for the first terminal according to a target bearer creation procedure initiated by the first terminal, and the method comprises: The third network device establishes the target bearer for the first terminal according to eighth information from the second network device, and the eighth information is used for requesting to establish the target bearer for the first terminal. The method of any one of claims 12-18, wherein, The method further comprises: The third network device sends second information to the first network device; The second information is related to the target bearer and is used for determining a first correspondence relationship, and the first correspondence relationship comprises a correspondence relationship between first information and first address information, the first information comprises at least one of information of the first terminal and information of the target bearer, and the first address information is address information allocated by the first network device for the first terminal and used for communication between the first network device and the second terminal. The method of claim 19, wherein, The second information comprises at least one of: Terminal identification of the first terminal; Second address information allocated by the second network device for the first terminal. The method of claim 19, wherein, The first correspondence relationship comprises at least one of: A correspondence relationship between terminal identification of the first terminal and the first address information; A correspondence relationship between second address information and the first address information, the second address information corresponding to the target bearer and used for communication between the second network device and the first network device. The method of any one of claims 15-21, wherein, The second address information comprises at least one of: T8 long-term transaction reference identification TLTRI, the TLTRI being allocated by the second network device for the first terminal; T8 destination address, the T8 destination address being allocated by the first network device for the first terminal; Target tunnel information, the target tunnel information being allocated by the first network device or the second network device for the first terminal; First IP address, the first IP address being allocated by the second network device for the first terminal; Second IP address, the second IP address being allocated by the first network device for the first terminal. The method of claim 22, wherein, The target tunnel information comprises at least one of: An identification of the target tunnel; First network device side tunnel information corresponding to the target tunnel; Second network device side tunnel information corresponding to the target tunnel. The method of any one of claims 19-23, wherein, The terminal identification comprises at least one of: Mobile station international user identification code MSISDN; Session initiation protocol SIP uniform resource identifier URI; IP multimedia public identification IMPU. The method of any one of claims 19-24, wherein, The method further comprises: The third network device requests the first network device to allocate third information for the first terminal, and the third information comprises the first address information. The method of claim 25, wherein, The third information further comprises second address information allocated by the first network device for the first terminal. The method of claim 25, wherein, The method further comprises: The third network device sends session description protocol SDP information to the second terminal, and the SDP information comprises the first address information. The method of any one of claims 12-26, wherein, At least one of the following is met: The first network device comprises an IMS GW; The second network device comprises at least one of SCEF, PGW, SGW, and UPF. The third network device comprises at least one of P-CSCF and IMS-AS. A communication method comprises: The second network device receives ninth information; The second network device sends tenth information to the third network device according to the ninth information; In a case where the ninth information is from the first terminal and is used for requesting to establish a target bearer for the first terminal, the tenth information is used for requesting to establish the target bearer for the first terminal; Or, in a case where the ninth information is from the third network device and is used for indicating to establish a target bearer for the first terminal, the tenth information is used for indicating information of the target bearer; The target bearer is a non-IP data transmission (NIDD) bearer used for transmitting communication data for the first terminal. The method of claim 29, wherein, The method further comprises: The second network device sends sixth information to the first terminal, and the sixth information is used for instructing the first terminal to initiate a target bearer creation process. The method of any one of claims 29-30, wherein, At least one of the following is met: The second network device comprises at least one of SCEF, PGW, SGW, and UPF. The third network device comprises at least one of P-CSCF and IMS-AS. A communication method comprises: The first terminal receives sixth information from the second network device or the third network device, and the sixth information is used for instructing the first terminal to initiate a target bearer creation process; The first terminal initiates the target bearer creation process for creating a target bearer; The target bearer is a non-IP data transmission (NIDD) bearer used for transmitting communication data for the first terminal. The method of claim 32, wherein, At least one of the following is met: The second network device comprises at least one of SCEF, PGW, SGW, and UPF. The third network device comprises at least one of P-CSCF and IMS-AS. A communication apparatus comprises: A transmission module is configured to receive target communication data; The transmission module is further configured to transmit the target communication data according to a first correspondence relationship; The first correspondence relationship comprises a correspondence relationship between first information and first address information, the first information comprises at least one of information of a first terminal and information of a target bearer, the target bearer is a non-IP data transmission (NIDD) bearer used for transmitting communication data for the first terminal, and the first address information is address information allocated by a first network device to the first terminal and used for communication between the first network device and a second terminal. The apparatus of claim 34, wherein, The transmission module is further configured to receive second information from a third network device; The apparatus further comprises a processing module configured to save the first correspondence relationship according to the second information and third information; The third information comprises the first address information, and the second information comprises at least one of a terminal identifier of the first terminal and second address information allocated by the second network device to the first terminal. A communication apparatus comprises: A processing module is configured to establish a target bearer for a first terminal in a call establishment process of the first terminal and a second terminal; The target bearer is a non-IP data delivery, NIDD, bearer for transmitting communication data for the first terminal. The apparatus of claim 36, wherein, The establishing the target bearer for the first terminal comprises any of the following: adding the target bearer in the created network connection; establishing the target bearer for the first terminal according to a target bearer establishment procedure initiated by the first terminal. A communication apparatus comprises: a transmission module configured to receive ninth information; the transmission module is further configured to send tenth information to a third network device according to the ninth information; wherein, in a case that the ninth information is from a first terminal and is used to request to establish a target bearer for the first terminal, the tenth information is used to request to establish the target bearer for the first terminal; or, in a case that the ninth information is from a third network device and is used to instruct to establish a target bearer for the first terminal, the tenth information is used to instruct information of the target bearer; the target bearer is a non-IP data delivery, NIDD, bearer for transmitting communication data for the first terminal. The apparatus of claim 38, wherein the transmission module is further configured to send sixth information to the first terminal, the sixth information being used to instruct the first terminal to initiate a target bearer creation procedure. A communication apparatus comprises: a transmission module configured to receive sixth information from a second network device or a third network device, the sixth information being used to instruct a first terminal to initiate a target bearer creation procedure; a processing module configured to initiate the target bearer creation procedure for creating a target bearer; wherein, the target bearer is a non-IP data delivery, NIDD, bearer for transmitting communication data for the first terminal. A communication device comprises a processor and a memory, the memory stores programs or instructions executable on the processor, and the programs or instructions are executed by the processor to implement the steps of the method according to any one of claims 1 to 33. A readable storage medium, the readable storage medium stores programs or instructions, and the programs or instructions are executed by a processor to implement the steps of the method according to any one of claims 1 to 33.

Images