Communication method and apparatus, device, and readable storage medium
By sending or receiving non-IP data in the terminal's IP communication connection, the packet header is reduced, solving the problem of poor call quality caused by excessively large packet headers and achieving a smoother communication experience.
Patent Information
- Application Number
- PCT/CN2026/094776
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-06-12
- Filing Date
- 2026-05-06
- Publication Date
- 2026-11-12
AI Technical Summary
In some access scenarios, the terminal's transmission rate is low, and the packet header is too large, resulting in poor call quality and affecting user experience.
By establishing an IP-type communication connection at the terminal, sending or receiving non-IP data through the first bearer, reducing or omitting IP packet headers, such as IPv6, UDP, and RTP headers, can reduce the size of the packet headers.
This avoids the degradation of call quality caused by an excessively large header, improves the smoothness of communication, reduces latency and lag, and enhances the user experience.
Smart Images

Figure CN2026094776_12112026_PF_FP_ABST
Abstract
Description
Communication methods, apparatus, devices and readable storage media
[0001] Cross-references to related applications
[0002] This application claims priority to Chinese Patent Application No. 202510591226.1, filed on May 8, 2025, and Chinese Patent Application No. 202510781828.3, filed on June 12, 2025, the entire contents of which are incorporated herein by reference. Technical Field
[0003] This application belongs to the field of communication technology, specifically relating to a communication method, apparatus, device, and readable storage medium. Background Technology
[0004] Currently, data packets based on Internet Protocol (IP), such as Real-time Transport Protocol (RTP) packets, have relatively large headers. For example, an RTP packet based on Internet Protocol version 6 (IPv6) has a 60-byte header, consisting of a 40-byte IPv6 header, an 8-byte User Datagram Protocol (UDP) header, and a 12-byte RTP header. An IPv4-based RTP packet has a 40-byte header, consisting of a 20-byte Internet Protocol version 4 (IPv4) header, an 8-byte UDP header, and a 12-byte RTP header. These RTP packets can be for voice services, video services, or other services.
[0005] In some access scenarios (such as satellite access), the terminal's transmission rate is low, and excessively large packet headers can lead to poor call quality and affect user experience. Summary of the Invention
[0006] This application provides a communication method, apparatus, device, and readable storage medium to solve the problem of reduced call quality caused by excessively large packet headers.
[0007] Firstly, a communication method is provided, including:
[0008] When a terminal establishes a first communication connection of type IP and the first communication connection includes a first bearer, the terminal sends non-IP data through the first bearer of the first communication connection; or, the terminal receives non-IP data through the first bearer of the first communication connection.
[0009] Secondly, a communication method is provided, including:
[0010] When a first communication connection of type IP is established on the terminal, and the first communication connection includes a first bearer,
[0011] The first network device receives non-IP data from the first bearer and generates IP data based on the non-IP data, wherein the source address of the IP data is the first IP address; or,
[0012] The first network device receives IP data whose destination address is a first IP address, generates non-IP data based on the IP data, and sends the non-IP data to the terminal through the first bearer;
[0013] Wherein, the first IP address is the IP address corresponding to the first communication connection.
[0014] Thirdly, a communication device is provided, comprising:
[0015] The first sending unit is configured to send non-IP data through the first bearer of the first communication connection when a first IP-type communication connection is established at the terminal and the first communication connection includes a first bearer; or...
[0016] The first receiving unit is configured to receive non-IP data through the first bearer of the first communication connection when a first communication connection of type IP is established at the terminal and the first communication connection includes a first bearer.
[0017] Fourthly, a communication device is provided, comprising:
[0018] The second receiving unit is configured to, when a first communication connection of type IP is established at the terminal and the first communication connection includes a first bearer, receive non-IP data from the first bearer, and generate IP data based on the non-IP data, wherein the source address of the IP data is a first IP address; or...
[0019] The second sending unit is configured to receive IP data whose destination address is a first IP address when a first communication connection of type IP is established at the terminal and the first communication connection includes a first bearer, generate non-IP data based on the IP data, and send the non-IP data to the terminal through the first bearer;
[0020] Wherein, the first IP address is the IP address corresponding to the first communication connection.
[0021] Fifthly, a communication device is provided, including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first or second aspect.
[0022] In a sixth aspect, a terminal is provided, including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method described in the first aspect.
[0023] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to send non-IP data through the first bearer of the first communication connection when the terminal establishes a first communication connection of type IP and the first communication connection includes a first bearer; or, the terminal receives non-IP data through the first bearer of the first communication connection.
[0024] Eighthly, a network-side device is provided, including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.
[0025] In a ninth aspect, a network-side device is provided, including a processor and a communication interface, wherein the processor is configured to, when a terminal establishes a first communication connection of type IP and the first communication connection includes a first bearer, receive non-IP data from the first bearer and generate IP data based on the non-IP data, wherein the source address of the IP data is a first IP address; or, receive IP data whose destination address is the first IP address, generate non-IP data based on the IP data, and send the non-IP data to the terminal through the first bearer; wherein the first IP address is the IP address corresponding to the first communication connection.
[0026] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.
[0027] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the first aspect, and the network-side device can be used to perform the steps of the method as described in the second aspect.
[0028] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the steps of the method as described in the first or second aspect.
[0029] In a thirteenth aspect, a computer program / program product is provided, the computer program or program product being stored in a storage medium, the computer program or program product being executed by at least one processor to perform the steps of the method as described in the first or second aspect.
[0030] In this embodiment, the terminal can receive or send non-IP data through the first bearer of the first communication connection. This avoids the problem of degraded call quality caused by excessively large packet headers of transmitted data. In this way, users can enjoy smoother communication, reduce latency and stuttering, and improve the user experience. Attached Figure Description
[0031] Figure 1 is a flowchart of the call establishment process in related technologies;
[0032] Figure 2 is a schematic diagram of a communication system provided in an embodiment of this application;
[0033] Figure 3 is a flowchart of a communication method provided in an embodiment of this application;
[0034] Figure 4 is a flowchart of another communication method provided in an embodiment of this application;
[0035] Figure 5 is a flowchart of Scheme 1a of Embodiment 1;
[0036] Figure 6 is a flowchart of scheme 1b of embodiment 1;
[0037] Figure 7 is a flowchart of Example 2;
[0038] Figure 8 is a schematic diagram of uplink and downlink data transmission in Embodiment 3;
[0039] Figure 9 is a schematic diagram of uplink and downlink data transmission in Embodiment 4;
[0040] Figure 10 is a structural diagram of a communication device provided in an embodiment of this application;
[0041] Figure 11 is a structural diagram of another communication device provided in an embodiment of this application;
[0042] Figure 12 is a structural diagram of a communication device provided in an embodiment of this application;
[0043] Figure 13 is a structural diagram of a terminal provided in an embodiment of this application;
[0044] Figure 14 is a structural diagram of a network-side device provided in an embodiment of this application. Detailed Implementation
[0045] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.
[0046] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.
[0047] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.
[0048] It is worth noting that the technology described in this 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, such as Non-Terrestrial Network (NTN) systems, Vehicle-to-Everything (V2X), Internet of Vehicles (IoV), Machine-Type Communications (MTC), Internet of Things (IoT), Machine-to-Machine (M2M), or future mobile communication systems. As a possible application scenario, NTN systems may include satellite systems. Based on their altitude, i.e., their orbital altitude, satellites can be classified into highly elliptical orbit (HEO) satellites, geosynchronous earth orbit (GEO) satellites, medium earth orbit (MEO) satellites, and low earth orbit (LEO) satellites. Furthermore, NTN systems may also include non-terrestrial network-side equipment (or airborne network-side equipment) such as High Altitude Platform Station (HAPS) communication systems. The non-terrestrial network-side equipment involved in this application is not limited to the examples mentioned above.
[0049] The terms "system" and "network" used in the embodiments of this application are often used interchangeably, and the described technologies can be used with respect to the systems and radio technologies mentioned above, as well as other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems.th Generation 6G communication system.
[0050] To facilitate understanding of the embodiments of this application, the following technical points are introduced first:
[0051] Related technology 1: Satellite access.
[0052] A satellite communication system consists of three parts: the satellite terminal, the ground terminal, and the user terminal. The satellite terminal acts as a relay station in the air, amplifying the electromagnetic waves transmitted from the ground station and sending them back. Based on their operating orbit, satellite communication systems are generally classified into the following three categories:
[0053] 1) Low Earth Orbit (LEO) satellite communication system: 500-2000 km above the ground, with relatively low transmission latency and power consumption, but the coverage area of each satellite is also relatively small.
[0054] 2) Medium Earth Orbit (MEO) satellite communication system: 2000-20000 km above the ground. The transmission delay is greater than that of low Earth orbit satellites, but the coverage area is also larger.
[0055] 3) Geosynchronous Earth Orbit (GEO): 35,800 km above the Earth's surface, i.e., geostationary orbit. Theoretically, global coverage can be achieved using three GEO satellites.
[0056] Currently, user equipment (e.g., user equipment (UE)) can directly access the network via satellite to make voice calls.
[0057] UE accessing the network via satellite can be understood as UE accessing an IP Multimedia Subsystem (IMS) network, a 6G network, a 5th Generation (5G) network, or a 4th Generation (4G) network via satellite; or UE initiating a call request via satellite.
[0058] Related technology 2: Call establishment process.
[0059] Referring to Figure 1, the process for UE-1 as the calling party is as follows:
[0060] Step 1: UE-1 registers with the 4G network;
[0061] Step 2: UE-1 establishes a Packet Data Network (PDN) connection for transmitting voice services;
[0062] Step 3: UE-1 initiates a call request to UE-2 via an Invite message, carrying information about the voice media to be established in the Session Description Protocol (SDP) offer of the Invite message;
[0063] Step 4: After receiving the Invite message, the Proxy Call Session Control Function (P-CSCF) sends the Invite message to the Serving Call Session Control Function (S-CSCF).
[0064] Step 5: The S-CSCF sends an Invite message to UE-2;
[0065] Step 6: UE-2 replies with a response message, which carries an SDP answer to negotiate the information of the voice media to be established;
[0066] Step 7: The S-CSCF sends a response message to the P-CSCF;
[0067] Step 8: The P-CSCF sends an Authentication and Authorization Request (AAR) to the Policy and Charging Rules Function (PCRF). The AAR carries negotiated media information, which is obtained from the SDP answer.
[0068] Among them, PCRF is the equipment for 4G networks, and its corresponding equipment for 5G networks is the Policy Control Function (PCF).
[0069] Step 9: The PCRF sends a defined Quality of Service (QoS) policy to the Packet Data Network Gateway (PGW);
[0070] Among them, PGW is a device for 4G networks, and its corresponding device for 5G networks is the Session Management Function (SMF).
[0071] The aforementioned PGW can also be a 4G and 5G co-located SMF and Packet Data Network Gateway-Control Plane (PGW-C).
[0072] Step 10: The PGW sends an Update Bearer request to the Serving Gateway (SGW) to establish a dedicated voice bearer;
[0073] Step 11: The SGW sends an update bearer request to the Mobility Management Entity (MME) to establish a dedicated voice bearer;
[0074] Among them, MME is the equipment of 4G network, and its corresponding equipment of 5G network is Access and Mobility Management Function (AMF);
[0075] Step 12: The MME sends a Bearer Modify request to the base station. This message contains the QoS parameters corresponding to the voice dedicated bearer and the EPS Bearer ID (EBI) corresponding to the voice dedicated bearer.
[0076] This message may also include a Non-Access Stratum (NAS) layer message, used to notify the UE to establish a new dedicated bearer. For 4G systems, this message is a Session Management Request message, and for 5G systems, it is a PDU session modification command message.
[0077] EPS bearer is a concept for dedicated bearers in 4G, and its corresponding 5G concept is QoS flow.
[0078] Each EPS bearer has an identifier, namely EBI.
[0079] The EBI corresponding to the default EPS bearer of the PDN connection can also be called the Linked EPS Bearer ID (LBI).
[0080] Since a data PDN connection can only establish one default EPS bearer in a narrowband Internet of Things (NB-IoT) system, the EBI corresponding to the data PDN connection is the EBI of the default EPS bearer.
[0081] Step 13: The base station sends a Radio Resource Control (RRC) connection reconfiguration message to the UE. This message contains Signaling Radio Bearer To Add Modify (SRB-ToAddMod) information, which is used to establish the Data Radio Bearer (DRB) corresponding to the voice dedicated bearer.
[0082] Step 14: The UE replies with an RRC connection reconfiguration response message;
[0083] Step 15: The base station sends a bearer modification response message to the MME;
[0084] Step 16: The MME sends an update bearer response message to the SGW;
[0085] Step 17: The SGW sends an update bearer response message to the PGW;
[0086] Step 18: PGW sends a response message to PCRF to notify PCRF whether the PCRF sending strategy has been executed;
[0087] Step 19: The PCRF sends a response message to the P-CSCF to notify whether the dedicated voice bearer has been successfully established;
[0088] Step 20: If the dedicated voice bearer is successfully established, the P-CSCF sends a response message to UE-1; otherwise, it sends a cancel message to UE-2 to end the call.
[0089] Step 21: When the user of UE-2 answers the call, UE-2 sends a 200 OK message;
[0090] Step 22: The 200 OK message is routed to UE-1. UE-1 determines that the user of UE-2 has answered the call based on the 200 OK message and starts the call.
[0091] Figure 2 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 21 and a network-side device 22.
[0092] Among them, terminal 21 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipborne equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), game console, personal computer (PC), ATM or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. Furthermore, terminal 21 can be any of the terminals described above, or it can be a chip within a terminal, such as a modem chip, a system-on-a-chip (SoC), etc. It should be noted that the specific type of terminal 21 is not limited in the embodiments of this application.
[0093] Network-side equipment 22 may include access network equipment or core network equipment. Access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, radio access network unit, or satellite. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc. The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.
[0094] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized Network Configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. The core network functions include: BSF (Block Network Function), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF). It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.
[0095] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).
[0096] The communication methods, apparatus, devices, and readable storage media provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.
[0097] Referring to Figure 3, an embodiment of this application provides a communication method applied to a terminal, the specific steps of which include:
[0098] Step 31: If a first communication connection of type IP is established on the terminal and the first communication connection includes a first bearer, the terminal sends non-IP data through the first bearer of the first communication connection; or, the terminal receives non-IP data through the first bearer of the first communication connection.
[0099] Optionally, the terminal can directly access the network via satellite to make voice calls.
[0100] Optionally, “communication connection” in this document includes, but is not limited to, at least one of the following: PDN connection, Protocol Data Unit (PDU) session.
[0101] Optionally, the first communication connection may include, but is not limited to, at least one of the following: a first PDN connection, a first PDU session. For example, the first PDN connection is an IP-based PDN connection, and the first PDU session is an IP-based PDU session.
[0102] Optionally, the first bearer can be a dedicated bearer, such as a voice-dedicated bearer.
[0103] Optionally, the non-IP data includes at least one of the following: non-IP based data, non-IP based voice data, non-IP based packet, and non-IP based RTP packet.
[0104] Optional, non-IP data may include one of the following:
[0105] 1) Data that does not contain an IP header, a UDP header, or an RTP header; or,
[0106] 2) Data that does not contain IP headers, does not contain UDP headers, and only contains simplified or compressed RTP headers; or,
[0107] 3) Data that does not contain IP headers, Transmission Control Protocol (TCP) headers, or RTP headers; or,
[0108] 4) Data that does not contain IP headers or TCP headers, but only simplified or compressed RTP headers; or,
[0109] 5) Data that does not contain an IP header or a UDP header; or,
[0110] 6) Data that does not contain an IP header or a TCP header; or,
[0111] 7) Data that does not contain an IP header; or,
[0112] 8) Data containing an IP header but not a UDP header; or,
[0113] 9) Data that includes the IP header but not the TCP header.
[0114] It should be noted that the simplified RTP header can be understood as the RTP header obtained after deleting some parameters of the RTP header; the compressed RTP header can be understood as the parameters obtained after compressing some parameters of the RTP header, for example, compressing a parameter from 16 bits to 8 bits.
[0115] Optional, non-IP-based data may include one of the following:
[0116] 1) Data that does not contain an IP header, a UDP header, or an RTP header; or,
[0117] 2) Data that does not contain IP headers, does not contain UDP headers, and only contains simplified or compressed RTP headers; or,
[0118] 3) Data that does not contain IP headers, TCP headers, or RTP headers; or,
[0119] 4) Data that does not contain IP headers or TCP headers, but only simplified or compressed RTP headers; or,
[0120] 5) Data that does not contain an IP header or a UDP header; or,
[0121] 6) Data that does not contain an IP header or a TCP header; or,
[0122] 7) Packets that do not contain an IP header; or,
[0123] 8) A packet containing an IP header but not a UDP header; or,
[0124] 9) Packets containing IP headers but not TCP headers.
[0125] Optionally, non-IP-based voice data may include one of the following:
[0126] 1) Voice data that does not contain an IP header, a UDP header, or an RTP header; or,
[0127] 2) Voice data that does not contain an IP header, does not contain a UDP header, and only contains a simplified or compressed RTP header; or,
[0128] 3) Voice data that does not contain IP headers, TCP headers, or RTP headers; or,
[0129] 4) Voice data that does not contain IP headers or TCP headers, but only contains simplified or compressed RTP headers; or,
[0130] 5) Voice data that does not contain an IP header or a UDP header; or,
[0131] 6) Voice data that does not contain an IP header or a TCP header; or,
[0132] 7) Voice data that does not contain an IP header; or,
[0133] 8) Voice data containing an IP header but not a UDP header; or,
[0134] 9) Voice data that includes an IP header but not a TCP header.
[0135] Optionally, non-IP-based packets may include one of the following:
[0136] 1) A data packet that does not contain an IP header, a UDP header, or an RTP header; or,
[0137] 2) Packets that do not contain IP headers or UDP headers, but only simplified or compressed RTP headers; or,
[0138] 3) Packets that do not contain IP headers, TCP headers, or RTP headers; or,
[0139] 4) Data packets that do not contain IP headers or TCP headers, but only contain simplified or compressed RTP headers; or,
[0140] 5) Packets that do not contain an IP header or a UDP header; or,
[0141] 6) Packets that do not contain IP headers or TCP headers; or,
[0142] 7) Packets that do not contain an IP header; or,
[0143] 8) A packet containing an IP header but not a UDP header; or,
[0144] 9) Packets containing IP headers but not TCP headers.
[0145] Optionally, non-IP-based Real-Time Transport Protocol (RTP) packets may include one of the following:
[0146] 1) Real-time Transport Protocol (RTP) packets that do not contain an IP header, a UDP header, or an RTP header; or,
[0147] 2) Real-time Transport Protocol (RTP) data packets that do not contain IP headers or UDP headers, but only contain simplified or compressed RTP headers; or,
[0148] 3) Real-time Transport Protocol (RTP) data packets that do not contain IP headers, TCP headers, or RTP headers; or,
[0149] 4) Real-time Transport Protocol (RTP) data packets that do not contain IP headers or TCP headers, but only contain simplified or compressed RTP headers; or,
[0150] 5) Real-time Transport Protocol (RTP) packets that do not contain IP headers or UDP headers; or,
[0151] 6) Real-time Transport Protocol (RTP) packets that do not contain IP headers or TCP headers; or,
[0152] 7) Real-time Transport Protocol (RTP) packets that do not contain an IP header; or,
[0153] 8) A packet containing an IP header but not a UDP header; or,
[0154] 9) Packets containing IP headers but not TCP headers.
[0155] Optionally, the data in this document may be data from voice services, video services, or other services; this application does not impose any restrictions.
[0156] Optionally, the data packets in this document may be data packets for voice services, data packets for video services, or data packets for other services; this application does not impose any restrictions.
[0157] In one implementation, when a terminal establishes a first communication connection of type IP and the first communication connection includes a first bearer, the terminal sends non-IP data through the first bearer of the first communication connection.
[0158] In another implementation, when a terminal establishes a first communication connection of type IP and the first communication connection includes a first bearer, the terminal receives non-IP data through the first bearer of the first communication connection.
[0159] In another implementation, when a terminal establishes a first communication connection of type IP and the first communication connection includes a first bearer, the terminal sends non-IP data through the first bearer of the first communication connection, and the terminal receives non-IP data through the first bearer of the first communication connection.
[0160] In this embodiment, the terminal can transmit non-IP data through the first bearer of the first communication connection. This avoids the problem of degraded call quality caused by excessively large data packet headers. In this way, users can enjoy smoother communication, reduce latency and stuttering, and improve the user experience.
[0161] In one embodiment of this application, the method further includes at least one of the following:
[0162] The terminal sends a first message, which is used to request the establishment of the first communication connection, to request registration, to initiate a call request, or to respond to a call request. The first message contains first information, which indicates that the terminal supports a first feature.
[0163] The terminal receives second information, which indicates at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the communication peer supports the first feature.
[0164] The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
[0165] It should be noted that non-IP data may include at least one of the following: non-IP data packets, non-IP-based data, non-IP-based voice data, non-IP-based data packets, and non-IP-based Real-Time Transport Protocol (RTP) data packets.
[0166] It should be noted that the communication peer refers to the communication device that communicates with the terminal. The communication peer can be the terminal device or a device on the network side.
[0167] In this embodiment, by negotiating with the network side whether to support or activate the first feature, the first feature can be effectively confirmed and activated, thereby ensuring consistency and optimization of data processing and transmission capabilities between the two parties, and improving the efficiency and performance of overall communication.
[0168] Optionally, the first message includes terminal capabilities, which include the first information. For example, terminal capabilities may include, but are not limited to, UE core network capabilities.
[0169] Optionally, the first message can be a communication connection request message, such as a PDN connectivity request message or a PDU session request message.
[0170] In one implementation, the terminal sends a communication connection request message, which includes first information, and the terminal receives a communication connection acceptance message, which carries second information.
[0171] In one implementation, the terminal sends a communication connection request message, which includes first information; the terminal receives a communication connection acceptance message; and the terminal receives a session management request message, which carries second information.
[0172] Optionally, the first message can be an attach request message.
[0173] In one implementation, the terminal sends an attach request message including first information, the terminal receives an attach accept message, and the terminal receives a session management request message carrying second information.
[0174] Optionally, the first message can be an IMS registration request message.
[0175] In one implementation, the terminal sends an IMS registration request message, which includes first information, and the terminal receives a 200 OK message corresponding to the IMS registration request, which carries second information.
[0176] Optionally, the first message can be a call request, such as an IMS Invite request message.
[0177] In one implementation, the terminal sends a call request message, which includes first information, and the terminal receives a 200 OK message corresponding to the call request, which carries second information.
[0178] Optionally, the first message can be a response message corresponding to the call request, such as a 183 response message.
[0179] In one implementation, after receiving a call request message from a communication peer, the terminal responds with a message containing first information, while the call request message received by the terminal carries second information.
[0180] In one embodiment of this application, the method further includes at least one of the following:
[0181] The terminal receives a second message, which is used to establish the first bearer, and the second message contains third information.
[0182] The terminal determines, based on the third information, that the first bearer is used to transmit non-IP data;
[0183] The third information indicates at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the first bearer is used to transmit non-IP data;
[0184] The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
[0185] It should be noted that the third information instructing the terminal to start or activate the first feature can be understood or replaced as: the third information instructing the start or activation of the first feature.
[0186] In this embodiment, by receiving instruction information from the network side through the terminal, the first bearer is determined to be used for transmitting non-IP data, thereby realizing effective support and processing of non-IP data and further enhancing the flexibility and adaptability of communication.
[0187] Optionally, the second message can be a dedicated bearer setup request message, which carries third information.
[0188] In one implementation, the terminal receives a dedicated bearer establishment request message, which includes third information. The terminal determines, based on the third information, that the first bearer is used to transmit non-IP data.
[0189] In one embodiment of this application, the method further includes:
[0190] The terminal stores a fourth piece of information, which indicates at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the first bearer is used to transmit non-IP data.
[0191] It should be noted that the fourth information instructing the terminal to start or activate the first feature can be understood or replaced as: the fourth information instructing the start or activation of the first feature.
[0192] In one implementation, after receiving the second information or the second message, the terminal saves the fourth information.
[0193] In this embodiment, relevant information is saved on the terminal to ensure that the network's support capabilities and feature activation status can be quickly confirmed in subsequent communications, thereby optimizing the transmission and processing efficiency of non-IP data.
[0194] In one embodiment of this application, the terminal transmits non-IP data through a first bearer of the first communication connection, including:
[0195] The terminal's IMS module generates non-IP data and sends the non-IP data to the terminal's NAS module or communication module.
[0196] The NAS module or communication module of the terminal maps the non-IP data to the first bearer, and sends the non-IP data to the wireless access network device through the first bearer.
[0197] The communication module is used for the terminal's fourth-generation mobile communication technology (4G), fifth-generation mobile communication technology (5G), or sixth-generation mobile communication technology (6G).
[0198] Optionally, the communication module is a module within the modem chip or a module within the SoC chip.
[0199] It should be noted that the 4G communication of the terminal includes: communication between the terminal and a 4G network, or communication within a 4G network. The 5G communication of the terminal includes: communication between the terminal and a 5G network, or communication within a 5G network. The 6G communication of the terminal includes: communication between the terminal and a 6G network, or communication within a 6G network.
[0200] It should be noted that the IMS module in this article can be understood or replaced as: IMS layer, IMS stack, or IMS software; the NAS module can be understood or replaced as: NAS layer, NAS stack, or NAS software.
[0201] In one embodiment of this application, the terminal receives non-IP data through a first bearer of the first communication connection, including:
[0202] The NAS module or communication module of the terminal receives non-IP data through the first bearer;
[0203] The NAS module or communication module of the terminal sends the non-IP data to the IMS module of the terminal.
[0204] In one embodiment of this application, the terminal sending non-IP data through the first bearer of the first communication connection includes:
[0205] The terminal's IMS module generates IP data and sends the IP data to the terminal's NAS module or communication module;
[0206] The terminal's NAS module or communication module generates non-IP data based on the IP data, maps the non-IP data to the first bearer, and sends the non-IP data to the wireless access network device through the first bearer; or...
[0207] The NAS module or communication module of the terminal maps the IP data to the first bearer, and the NAS module or communication module of the terminal generates non-IP data based on the IP data, and sends the non-IP data to the wireless access network device through the first bearer.
[0208] The communication module is used for 4G, 5G, or 6G communication of the terminal.
[0209] In one embodiment of this application, generating non-IP data based on the IP data includes: deleting at least one of the IP header, UDP header, and RTP header of the IP data.
[0210] In one embodiment of this application, mapping the non-IP data to the first bearer includes:
[0211] Based on the fifth piece of information, the non-IP data is mapped to the first bearer;
[0212] The fifth piece of information indicates that the first bearer is used to transmit non-IP data, or that the first bearer is used to transmit voice data.
[0213] It should be noted that when the fifth information is used to indicate that the first bearer is used to transmit voice data, the NAS module or communication module of the terminal maps the non-IP data to the first bearer based on the fact that the non-IP data received from the IMS module contains voice data and the first bearer is used to transmit voice data.
[0214] In one embodiment of this application, the terminal transmits non-IP data through the first bearer of the first communication connection, including:
[0215] The NAS module or communication module of the terminal receives non-IP data through the first bearer;
[0216] The NAS module or communication module of the terminal generates IP data based on the non-IP data and sends the IP data to the IMS module of the terminal.
[0217] In one embodiment of this application, the NAS module or communication module of the terminal generates IP data based on the non-IP data, including:
[0218] The NAS module or communication module of the terminal generates IP data based on the Session Description Protocol (SDP) negotiation results, IP 5-tuples, or IP 4-tuples obtained during the call setup process.
[0219] The NAS module or communication module of the terminal generates IP data based on the Session Description Protocol (SDP) negotiation result obtained during the call setup process, including:
[0220] The terminal's IMS module obtains the SDP negotiation result during the call setup process. The SDP negotiation result includes: the terminal's IP address, the terminal's port number, the communication peer's IP address, and the communication peer's port number. The terminal's IMS module then sends the SDP negotiation result to the terminal's NAS module or communication module.
[0221] The NAS module or communication module of the terminal generates IP data based on the IP address of the terminal, the port number of the terminal, the IP address of the communication peer, and the port number of the communication peer contained in the SDP negotiation result.
[0222] The NAS module or communication module of the terminal generates IP data based on the IP 5-tuple obtained during the call setup process, including:
[0223] The terminal's IMS module obtains an IP 5-tuple during the call setup process. The IP 5-tuple includes: the terminal's IP address, the terminal's port number, the peer's IP address, the peer's port number, and the protocol. The terminal's IMS module then sends the IP 5-tuple to the terminal's NAS module or communication module.
[0224] The NAS module or communication module of the terminal generates IP data based on the IP quintuple.
[0225] The protocol indicates the transport layer protocol used, such as UDP or TCP.
[0226] The NAS module or communication module of the terminal generates IP data based on the IP quadtuple obtained during the call setup process, including:
[0227] The terminal's IMS module obtains an IP quadtuple during the call setup process. The IP quadtuple includes: the terminal's IP address, the terminal's port number, the peer's IP address, and the peer's port number. The terminal's IMS module then sends the IP quadtuple to the terminal's NAS module or communication module.
[0228] The NAS module or communication module of the terminal generates IP data based on the IP quadruple.
[0229] It is understood that the embodiments of this application are applicable to scenarios including but not limited to 4th Generation (4G) networks, 5th Generation (5G) networks, 6th Generation (6G) networks, or future mobile communication technology networks. The embodiments of this application cover existing and future mobile communication networks, ensuring their strong adaptability in rapidly evolving communication technologies.
[0230] Referring to Figure 4, an embodiment of this application provides a communication method applied to a first network device, which includes, but is not limited to, at least one of a RAN node, MME, SGW, and PGW. Specific steps include:
[0231] Step 41: When a first communication connection of type IP is established on the terminal and the first communication connection includes a first bearer, the first network device receives non-IP data from the first bearer and generates IP data based on the non-IP data, wherein the source address of the IP data is the first IP address; or, the first network device receives IP data whose destination address is the first IP address, generates non-IP data based on the IP data, and sends the non-IP data to the terminal through the first bearer.
[0232] Wherein, the first IP address is the IP address corresponding to the first communication connection.
[0233] In this embodiment, the first network device can receive or send non-IP data through the first bearer of the first communication connection. This avoids the problem of degraded call quality caused by excessively large packet headers of transmitted data. In this way, users can enjoy smoother communication, reduce latency and stuttering, and improve user experience.
[0234] Optionally, the non-IP data includes at least one of the following: non-IP-based data, non-IP-based voice data, non-IP-based data packets, and non-IP-based Real-Time Transport Protocol (RTP) data packets.
[0235] Optional, non-IP data may include one of the following:
[0236] 1) Data that does not contain an IP header, a UDP header, or an RTP header; or,
[0237] 2) Data that does not contain IP headers, does not contain UDP headers, and only contains simplified or compressed RTP headers; or,
[0238] 3) Data that does not contain IP headers, Transmission Control Protocol (TCP) headers, or RTP headers; or,
[0239] 4) Data that does not contain IP headers or TCP headers, but only simplified or compressed RTP headers; or,
[0240] 5) Data that does not contain an IP header or a UDP header; or,
[0241] 6) Data that does not contain an IP header or a TCP header; or,
[0242] 7) Data that does not contain an IP header; or,
[0243] 8) Data containing an IP header but not a UDP header; or,
[0244] 9) Data that includes the IP header but not the TCP header.
[0245] Optional, non-IP-based data may include one of the following:
[0246] 1) Data that does not contain an IP header, a UDP header, or an RTP header; or,
[0247] 2) Data that does not contain IP headers, does not contain UDP headers, and only contains simplified or compressed RTP headers; or,
[0248] 3) Data that does not contain IP headers, TCP headers, or RTP headers; or,
[0249] 4) Data that does not contain IP headers or TCP headers, but only simplified or compressed RTP headers; or,
[0250] 5) Data that does not contain an IP header or a UDP header; or,
[0251] 6) Data that does not contain an IP header or a TCP header; or,
[0252] 7) Packets that do not contain an IP header; or,
[0253] 8) A packet containing an IP header but not a UDP header; or,
[0254] 9) Packets containing IP headers but not TCP headers.
[0255] Optionally, non-IP-based voice data may include one of the following:
[0256] 1) Voice data that does not contain an IP header, a UDP header, or an RTP header; or,
[0257] 2) Voice data that does not contain an IP header, does not contain a UDP header, and only contains a simplified or compressed RTP header; or,
[0258] 3) Voice data that does not contain IP headers, TCP headers, or RTP headers; or,
[0259] 4) Voice data that does not contain IP headers or TCP headers, but only contains simplified or compressed RTP headers; or,
[0260] 5) Voice data that does not contain an IP header or a UDP header; or,
[0261] 6) Voice data that does not contain an IP header or a TCP header; or,
[0262] 7) Voice data that does not contain an IP header; or,
[0263] 8) Voice data containing an IP header but not a UDP header; or,
[0264] 9) Voice data that includes an IP header but not a TCP header.
[0265] Optionally, non-IP-based packets may include one of the following:
[0266] 1) A data packet that does not contain an IP header, a UDP header, or an RTP header; or,
[0267] 2) Packets that do not contain IP headers or UDP headers, but only simplified or compressed RTP headers; or,
[0268] 3) Packets that do not contain IP headers, TCP headers, or RTP headers; or,
[0269] 4) Data packets that do not contain IP headers or TCP headers, but only contain simplified or compressed RTP headers; or,
[0270] 5) Packets that do not contain an IP header or a UDP header; or,
[0271] 6) Packets that do not contain IP headers or TCP headers; or,
[0272] 7) Packets that do not contain an IP header; or,
[0273] 8) A packet containing an IP header but not a UDP header; or,
[0274] 9) Packets containing IP headers but not TCP headers.
[0275] Optionally, non-IP-based Real-Time Transport Protocol (RTP) packets may include one of the following:
[0276] 1) Real-time Transport Protocol (RTP) packets that do not contain an IP header, a UDP header, or an RTP header; or,
[0277] 2) Real-time Transport Protocol (RTP) data packets that do not contain IP headers or UDP headers, but only contain simplified or compressed RTP headers; or,
[0278] 3) Real-time Transport Protocol (RTP) data packets that do not contain IP headers, TCP headers, or RTP headers; or,
[0279] 4) Real-time Transport Protocol (RTP) data packets that do not contain IP headers or TCP headers, but only contain simplified or compressed RTP headers; or,
[0280] 5) Real-time Transport Protocol (RTP) packets that do not contain IP headers or UDP headers; or,
[0281] 6) Real-time Transport Protocol (RTP) packets that do not contain IP headers or TCP headers; or,
[0282] 7) Real-time Transport Protocol (RTP) packets that do not contain an IP header; or,
[0283] 8) Real-time Transport Protocol (RTP) packets that include an IP header but not a UDP header; or,
[0284] 9) Real-time Transport Protocol (RTP) packets that include an IP header but not a TCP header.
[0285] Optionally, the terminal can directly access the network via satellite to conduct voice or video call services.
[0286] Optionally, the first communication connection may include, but is not limited to, at least one of the following: a first PDN connection, a first PDU session. For example, the first PDN connection is an IP-based PDN connection, and the first PDU session is an IP-based PDU session.
[0287] Optionally, the first bearer can be a dedicated bearer.
[0288] In one implementation, when a first communication connection of type IP is established at the terminal and the first communication connection includes a first bearer, the first network device receives non-IP data from the first bearer and generates IP data based on the non-IP data, wherein the source address of the IP data is a first IP address.
[0289] In another implementation, when a terminal establishes a first communication connection of type IP and the first communication connection includes a first bearer, the first network device receives IP data whose destination address is a first IP address, generates non-IP data based on the IP data, and sends the non-IP data to the terminal through the first bearer.
[0290] In another implementation, when a terminal establishes a first communication connection of type IP and the first communication connection includes a first bearer, a first network device receives non-IP data from the first bearer and generates IP data based on the non-IP data, wherein the source address of the IP data is a first IP address, and the first network device receives IP data with a destination address of the first IP address, generates non-IP data based on the IP data, and sends the non-IP data to the terminal through the first bearer.
[0291] In one embodiment of this application, the method further includes at least one of the following:
[0292] The first network device receives a third message, which is used to request the establishment of the first communication connection or to request registration. The third message contains first information, which indicates that the terminal supports a first feature.
[0293] The first network device sends second information, the second information indicating at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the communication peer supports the first feature;
[0294] The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
[0295] In this embodiment, by negotiating with the network side whether to support or activate the first feature, the first feature can be effectively confirmed and activated, thereby ensuring consistency and optimization of data processing and transmission capabilities between the two parties, and improving the efficiency and performance of overall communication.
[0296] In one embodiment of this application, the third message includes PCO parameters, and the PCO parameters include the first information.
[0297] It should be noted that a PCO can be a regular PCO or an extended PCO (ePCO).
[0298] In another embodiment of this application, the third message includes terminal capabilities, which include the first information. For example, terminal capabilities may include, but are not limited to, UE core network capabilities.
[0299] Optionally, the third message may include, but is not limited to, at least one of the following: a communication connection request message, or a session creation request message. The third message and the first message may be the same message or different messages.
[0300] Optionally, the first network device sends the second information, including: the first network device sends a session creation response message, a bearer creation request message, a communication connection acceptance message, or a dedicated bearer establishment request message, and the session creation response message, the bearer creation request message, the communication connection acceptance message, or the dedicated bearer establishment request message carries the second information.
[0301] In one embodiment of this application, the second information is included in the PCO parameters of a message carrying the second information. For example, a session creation response message, a bearer creation request message, a communication connection acceptance message, or a dedicated bearer establishment request message includes PCO parameters, which include the second information.
[0302] In one implementation, a first network device (e.g., a RAN node or MME) receives a communication connection request message containing first information, and the first network device sends a communication connection acceptance message or a dedicated bearer establishment request message, which includes second information.
[0303] In another embodiment, a first network device (e.g., an SGW or a PGW) receives a session creation request message containing first information, and the first network device sends a session creation response message or a bearer creation request message, which includes second information. In one embodiment of this application, the method further includes:
[0304] The first network device sends a fourth message, which is used to establish the first bearer. The fourth message contains third information, which is used to determine that the first bearer is used to transmit non-IP data.
[0305] The third information indicates at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the first bearer is used to transmit non-IP data;
[0306] The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
[0307] Optionally, the fourth message can be a create bearer request message or a dedicated bearer establishment request message.
[0308] Optionally, the fourth message can be the same message as the second message or a different message.
[0309] In one implementation, the first network device sends a create bearer request message, which includes third information.
[0310] In another implementation, the first network device sends a dedicated bearer establishment request message, which includes third information.
[0311] In one implementation, generating IP data based on the non-IP data includes:
[0312] The first network device generates IP data based on the data flow filter, IP 5-tuple, or IP 4-tuple obtained during the call setup process. The data flow filter, IP 5-tuple, or IP 4-tuple includes the first IP address.
[0313] It is understood that the embodiments of this application are applicable to scenarios including but not limited to 4G networks, 5G networks, 6G networks, or future mobile communication technology networks. The scope of application of the embodiments of this application covers existing and future mobile communication networks, ensuring that they remain highly adaptable to rapidly evolving communication technologies.
[0314] Example 1: During the establishment of the first bearer, negotiate whether to support or activate the first feature.
[0315] Scheme 1a and Scheme 1b are two parallel schemes, but they are established at different times.
[0316] Scheme 1a involves establishing the communication connection and the first bearer in one process; Scheme 1b involves establishing the communication connection and the first bearer in two processes.
[0317] Option 1a: When establishing a communication connection, the first bearer is established simultaneously.
[0318] Referring to Figure 5, the specific steps are as follows:
[0319] Step 1-2: During the registration or communication connection establishment process, UE-1 sends a communication connection request message. The communication connection request message carries first information, which is used to indicate that the UE supports the first feature.
[0320] Optionally, the first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data, wherein processing non-IP data includes, but is not limited to, converting non-IP data into IP data.
[0321] Optionally, UE-1 carries the first information through the PCO parameter, that is, the first message includes the PCO parameter, which includes the first information.
[0322] Step 3: The MME sends a Create session Request message to the SGW or PGW, carrying this first information.
[0323] Step 4: The PGW sends a Create Session Response message or a Create Bearer Request message. The Create Session Response message or Create Bearer Request message carries second information, which indicates at least one of the following:
[0324] 1) The network side supports the first feature;
[0325] Optionally, the network side includes, but is not limited to, PGW.
[0326] 2) UE-1 starts or activates the first feature.
[0327] Optionally, the PGW carries second information via the PCO parameter, i.e., the Create Session Response message or Create Bearer Request message includes the PCO parameter, which includes the second information.
[0328] 3) The communication peer supports the first feature;
[0329] The communication peer can be a terminal device, such as UE-2 communicating with UE-1; or a network-side device, such as an access gateway (AGW).
[0330] It should be noted that the PCO parameter is a parameter directly communicated between the UE and the PGW. The MME does not parse the content of the PCO parameter, so the MME can be an existing MME. This implementation method requires minimal changes to the network.
[0331] Step 5: The MME sends a communication connection acceptance message or a dedicated bearer establishment request message to the RAN node.
[0332] Step 6: The RAN node sends a Non-Access Stratum (NAS) message to UE-1.
[0333] Optionally, NAS messages may include communication connection acceptance messages or dedicated bearer establishment request messages.
[0334] Step 7: UE-1 records network-side support for the first feature, or UE-1 starts or activates the first feature.
[0335] Optionally, UE-1 records newly established Evolved Packet System (EPS) bearers and data radio bearers (DRBs) for transmitting voice data.
[0336] DRB is part of EPS bearer and serves as the communication bearer between UE and base station.
[0337] During the Session Description Protocol (SDP) negotiation process between UE-1 and the communication peer, P-CSCF sends an IP 5-tuple to PCRF, PCRF sends an IP 5-tuple to PGW, and PGW saves the IP 5-tuple for use in Embodiments 3 and 4 to convert non-IP-based voice data into IP-based voice data, or to convert non-IP-based Real-Time Transport Protocol (RTP) data packets into IP-based RTP data packets.
[0338] Optionally, the PCRF sends an IP 5-tuple to the PGW, including: the PCRF sends data flow filter parameters to the PGW, the data flow filter parameters containing the IP 5-tuple.
[0339] Optionally, the IP 5-tuple includes at least one of the following: source IP address, source port number, destination IP address, destination port number, and protocol (e.g., UDP protocol).
[0340] Option 1b: Separate the establishment of communication connection and the establishment of the first bearer.
[0341] Referring to Figure 6, the specific steps are as follows:
[0342] Steps 1-3: Refer to the description of steps 1-3 in Figure 5.
[0343] Step 4: PGW sends a Create session Response message.
[0344] Step 5: The MME sends a communication connection acceptance message to the RAN node.
[0345] Step 6: The RAN node sends the NAS message to UE-1.
[0346] Optionally, NAS messages include communication connection acceptance messages.
[0347] Step 7: During the IMS session negotiation process, the PCRF sends a Session Modification Request message to the PGW to request the establishment of the first bearer.
[0348] The session modification request message contains an IP 5-tuple of the voice data packet. The PGW records this IP 5-tuple for use in Embodiments 3 and 4 to convert non-IP-based voice data into IP-based voice data, or to convert non-IP-based Real-Time Transport Protocol (RTP) data packets into IP-based RTP data packets.
[0349] Step 8: The PGW sends a Create Bearer Request message, which carries second information indicating at least one of the following:
[0350] 1) The network side supports the first feature;
[0351] Optionally, the network side includes, but is not limited to, PGW.
[0352] 2) UE starts or activates the first feature.
[0353] 3) The communication peer supports the first feature;
[0354] The communication peer can be a terminal device, such as UE-2 communicating with UE-1; or a network-side device, such as an access gateway (AGW).
[0355] Optionally, the PGW carries a second piece of information via the PCO parameter.
[0356] Step 9: The MME sends a session management request message to the RAN node. The session management request message carries the second information.
[0357] Step 10: The RAN node sends the NAS message to UE-1.
[0358] Optionally, NAS messages include session management request messages.
[0359] Step 11: UE-1 records that the network side supports the first feature, or UE-1 starts or activates the first feature.
[0360] Optionally, the newly established EPS bearer and DRB in the UE-1 record are used for transmitting voice data.
[0361] Optionally, in this embodiment, the UE-1 does not carry indication information supporting Robust Header Compression (ROHC) in its radio capabilities.
[0362] Example 2: When UE-1 attaches, negotiate whether to support or enable the first feature.
[0363] Referring to Figure 7, the specific steps are as follows:
[0364] Step 1: During the registration process, UE-1 sends an attach request message to the MME, indicating that the UE supports the first feature through the UE core network capability in the attach request message.
[0365] Step 2: The MME sends a create session request message to the SGW or PGW. The create session request message carries indication information that UE-1 supports the first feature.
[0366] Optionally, the PGW records information about the first feature supported by UE-1.
[0367] Step 3: PGW sends a Create session Response message.
[0368] Step 4: The MME sends an attach accept message to the RAN node. This message carries information about network support for the first feature, for example, via the EPS network feature support parameter. The MME indicates network support for the first feature in the Core Network Capability section of the accept message.
[0369] Step 5: The RAN node sends the NAS message to UE-1.
[0370] Optionally, NAS messages include attach accept messages.
[0371] Step 6: The UE node records the network support for the first feature.
[0372] Step 7-11: Refer to step 7-11 in Figure 6.
[0373] If steps 7-11 are not enhanced, UE-1 can start or activate the first feature by default based on the network side's support for the first feature; PGW can start or activate the first feature by default based on UE-1's support for the first feature.
[0374] Optionally, in this embodiment, UE-1 does not carry indication information supporting ROHC in its radio capabilities.
[0375] Example 3: Uplink and downlink data transmission - Enhanced IMS module.
[0376] See Figure 8 for details:
[0377] Uplink (UL) transmission:
[0378] (1) The UE’s IMS module generates non-IP data and sends it to the NAS module or communication module.
[0379] (2) The NAS module or communication module of the UE maps the non-IP data to the first bearer and transmits it to the base station through the DRB corresponding to the first bearer.
[0380] The UE maps the non-IP data to the first bearer based on the information recorded in step 7 of Figure 5, or step 11 of Figure 6 or Figure 7.
[0381] Downlink (DL) transmission:
[0382] After receiving an RTP packet, the PGW maps it to the first bearer according to the packet filter.
[0383] The PGW removes the IP or UDP header, modifies the RTP header, and then sends it to the UE via the mapped first bearer.
[0384] (3) The NAS module or communication module of the UE will send the non-IP data received from the first bearer to the IMS module.
[0385] Example 4: Uplink and downlink data transmission - IMS module not enhanced.
[0386] See Figure 9 for details:
[0387] UL transmission:
[0388] (1) The UE’s IMS module normally generates IP-based RTP packets (i.e., IP data). After the NAS module or communication module receives the RTP packet, it uses a packet filter to map it to the first bearer.
[0389] (2) The UE’s NAS module or communication module deletes the IP packet header or UDP packet header, modifies the RTP packet header, and then transmits it to the base station through the DRB corresponding to the first mapped bearer.
[0390] DL transfer:
[0391] After receiving the RTP packet, the PGW maps it to the first bearer according to the packet filter, deletes the IP or UDP packet header, modifies the RTP packet header, and then sends the non-IP data to the UE through the mapped first bearer.
[0392] (3) The NAS module or communication module adds an IP header or UDP header to the non-IP data, and sends the IP data obtained after modifying the RTP header to the IMS module.
[0393] Referring to Figure 10, an embodiment of this application provides a communication device applied to a terminal. The device 100 includes:
[0394] The first sending unit 101 is configured to send non-IP data through the first bearer of the first communication connection when an IP-type first communication connection is established at the terminal and the first communication connection includes a first bearer; or,
[0395] The first receiving unit 102 is configured to send non-IP data through the first bearer of the first communication connection when a first communication connection of type IP is established at the terminal and the first communication connection includes a first bearer, and to receive non-IP data through the first bearer of the first communication connection.
[0396] In one embodiment of this application,
[0397] The first sending unit 101 is further configured to send a first message, the first message being used to request the establishment of the first communication connection / to request registration, to initiate a call request, or to respond to a call request, the first message containing first information indicating that the terminal supports a first feature; or...
[0398] The first receiving unit 102 is further configured to receive second information, the second information indicating at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the communication peer supports the first feature;
[0399] The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
[0400] In one embodiment of this application, the first receiving unit 102 is further configured to perform at least one of the following:
[0401] Receive a second message, the second message being used to establish the first bearer, the second message containing third information;
[0402] Based on the third information, it is determined that the first bearer is used to transmit non-IP data;
[0403] The third information indicates at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the first bearer is used to transmit non-IP data;
[0404] The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
[0405] In one embodiment of this application, the device 100 further includes a first processing unit for storing fourth information, the fourth information indicating at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the first bearer is used to transmit non-IP data.
[0406] In one embodiment of this application, the first sending unit 101 is further configured to generate non-IP data through the IP Multimedia Subsystem (IMS) module of the terminal, and send the non-IP data to the Non-Access Stratum (NAS) module or communication module of the terminal; map the non-IP data to the first bearer through the NAS module or communication module of the terminal, and send the non-IP data to the wireless access network (WLAN) device through the first bearer. The communication module is used for 4G, 5G, or 6G communication of the terminal.
[0407] In one embodiment of this application, mapping the non-IP data to the first bearer via the NAS module or communication module of the terminal includes:
[0408] The NAS module or communication module of the terminal maps the non-IP data to the first bearer according to the fifth information;
[0409] The fifth piece of information indicates that the first bearer is used to transmit non-IP data, or that the first bearer is used to transmit voice data.
[0410] In one embodiment of this application, receiving non-IP data via the terminal through the first bearer of the first communication connection includes:
[0411] The terminal's NAS module or communication module receives non-IP data through the first bearer;
[0412] The non-IP data is transmitted to the IMS module of the terminal via the NAS module or communication module of the terminal. The communication module is used for 4G, 5G, or 6G communication of the terminal.
[0413] In one embodiment of this application, the terminal transmits non-IP data through a first bearer of the first communication connection, including:
[0414] IP data is generated by the IMS module of the terminal and sent to the NAS module or communication module of the terminal.
[0415] The terminal's NAS module or communication module generates non-IP data based on the IP data, maps the non-IP data to the first bearer, and sends the non-IP data to the wireless access network device through the first bearer; or, the terminal's NAS module or communication module maps the IP data to the first bearer, generates non-IP data based on the IP data, and sends the non-IP data to the wireless access network device through the first bearer; wherein, the communication module is used for the terminal's 4G communication, 5G communication, or 6G communication.
[0416] In one embodiment of this application, transmitting non-IP data via the terminal through the first bearer of the first communication connection includes:
[0417] The terminal's NAS module or communication module receives non-IP data through the first bearer;
[0418] The terminal's NAS module or communication module generates IP data based on the non-IP data and sends the IP data to the terminal's IMS module.
[0419] In one embodiment of this application, the first message includes a Protocol Configuration Option (PCO) parameter, wherein the PCO parameter includes the first information;
[0420] or,
[0421] The first message includes terminal capabilities, and the terminal capabilities include the first information.
[0422] In one embodiment of this application, the second information is included in the PCO parameters of the message used to carry the second information.
[0423] In one embodiment of this application, the NAS module or communication module of the terminal generates IP data based on the non-IP data, including: the NAS module or communication module of the terminal generates IP data based on the Session Description Protocol (SDP) negotiation result, IP 5-tuple or IP 4-tuple obtained during the call setup process.
[0424] In one embodiment of this application, the non-IP data includes at least one of the following: non-IP-based voice data; non-IP-based data packets; non-IP-based Real-Time Transport Protocol (RTP) data packets; voice data without IP headers or UDP headers; voice data without IP headers, UDP headers, or RTP headers; and voice data without IP headers or UDP headers but containing simplified or compressed RTP headers.
[0425] In one embodiment of this application, the first bearer is a dedicated bearer.
[0426] The apparatus provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG3 and achieve the same technical effect. To avoid repetition, it will not be described again here.
[0427] Referring to Figure 11, an embodiment of this application provides a communication device applied to a first network device. The device 110 includes:
[0428] The second receiving unit 111 is configured to, when a first communication connection of type IP is established at the terminal and the first communication connection includes a first bearer, receive non-IP data from the first bearer and generate IP data based on the non-IP data, wherein the source address of the IP data is a first IP address; or,
[0429] The second sending unit 112 is used to receive IP data whose destination address is a first IP address when a first communication connection of type IP is established at the terminal and the first communication connection includes a first bearer, generate non-IP data according to the IP data, and send the non-IP data to the terminal through the first bearer.
[0430] Wherein, the first IP address is the IP address corresponding to the first communication connection.
[0431] In one embodiment of this application,
[0432] The second receiving unit 111 is further configured to receive a third message, the third message being used to request the establishment of the first communication connection or to request registration, the third message containing first information indicating that the terminal supports a first feature; or...
[0433] The second sending unit 112 is also used to send second information, the second information indicating at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the communication peer supports the first feature.
[0434] The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
[0435] In one embodiment of this application, the second sending unit 112 is further configured to send a fourth message, the fourth message being used to establish the first bearer, the fourth message containing third information, the third information being used to determine that the first bearer is used to transmit non-IP data;
[0436] The third information indicates at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the first bearer is used to transmit non-IP data;
[0437] The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
[0438] In one embodiment of this application, the third message includes PCO parameters, and the PCO parameters include the first information;
[0439] or,
[0440] The third message includes terminal capabilities, and the terminal capabilities include the first information.
[0441] In one embodiment of this application, the second information is included in the PCO parameters of the message used to carry the second information.
[0442] In one embodiment of this application, generating IP data based on the non-IP data includes: the first network device generating IP data based on a data flow filter, an IP 5-tuple, or an IP 4-tuple obtained during the call setup process; wherein the data flow filter, IP 5-tuple, or IP 4-tuple includes the first IP address.
[0443] In one embodiment of this application, the non-IP data includes at least one of the following: non-IP-based voice data; non-IP-based data packets; non-IP-based Real-Time Transport Protocol (RTP) data packets; voice data without IP headers or UDP headers; voice data without IP headers, UDP headers, or RTP headers; and voice data without IP headers or UDP headers but containing simplified or compressed RTP headers.
[0444] In one embodiment of this application, the first bearer is a dedicated bearer.
[0445] The apparatus provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG4 and achieve the same technical effect. To avoid repetition, it will not be described again here.
[0446] 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 method embodiment shown in Figure 3 above, 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 method embodiment shown in Figure 4 above, and achieve the same technical effect. To avoid repetition, it will not be described again here.
[0447] 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 FIG3. 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 shown in FIG10.
[0448] Specifically, Figure 13 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.
[0449] 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.
[0450] Those skilled in the art will understand that the terminal 1300 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the 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.
[0451] 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.
[0452] 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.
[0453] 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 809 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.
[0454] 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.
[0455] Optionally, the radio frequency unit 1301 is used to send non-IP data through the first bearer of the first communication connection when a first communication connection of type IP is established at the terminal and the first communication connection includes a first bearer; or, to receive non-IP data through the first bearer of the first communication connection.
[0456] Optionally, the radio frequency unit 1301 is also used for at least one of the following:
[0457] Send a first message, the first message being used to request the establishment of the first communication connection or to request registration, the first message containing first information, the first information indicating that the terminal supports a first feature;
[0458] Receive second information, the second information indicating at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the communication peer supports the first feature;
[0459] The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
[0460] Optionally, the radio frequency unit 1301 is also used for at least one of the following:
[0461] Receive a second message, the second message being used to establish the first bearer, the second message containing third information;
[0462] Based on the third information, it is determined that the first bearer is used to transmit non-IP data;
[0463] The third information indicates at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the first bearer is used to transmit non-IP data;
[0464] The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
[0465] Optionally, the processor 1310 is also configured to store fourth information indicating at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the first bearer is used to transmit non-IP data.
[0466] Optionally, the radio frequency unit 1301 is further configured to generate non-IP data through the IP Multimedia Subsystem (IMS) module of the terminal, and send the non-IP data to the Non-Access Stratum (NAS) module or communication module of the terminal; map the non-IP data to the first bearer through the NAS module or communication module of the terminal, and send the non-IP data to the wireless access network (WLAN) device through the first bearer. The communication module is used for 4G, 5G, or 6G communication technologies of the terminal.
[0467] Optionally, the radio frequency unit 1301 is further configured to receive non-IP data via the first bearer through the NAS module or communication module of the terminal; and to transmit the non-IP data to the IMS module of the terminal through the NAS module or communication module of the terminal. The communication module is used for 4G, 5G, or 6G communication of the terminal.
[0468] Optionally, the radio frequency unit 1301 is further configured to generate IP data through the IMS module of the terminal and send the IP data to the NAS module or communication module of the terminal; generate non-IP data based on the IP data through the NAS module or communication module of the terminal, map the non-IP data to the first bearer, and send the non-IP data to the wireless access network device through the first bearer; or,
[0469] The NAS module or communication module of the terminal maps the IP data to the first bearer, and the NAS module or communication module of the terminal generates non-IP data based on the IP data, and sends the non-IP data to the wireless access network device through the first bearer.
[0470] The communication module is used for 4G, 5G, or 6G communication of the terminal.
[0471] Optionally, the processor 1310 is further configured to map the non-IP data to the first bearer based on the fifth information;
[0472] The fifth piece of information indicates that the first bearer is used to transmit non-IP data, or that the first bearer is used to transmit voice data.
[0473] Optionally, the radio frequency unit 1301 is further configured to receive non-IP data through the first bearer via the NAS module or communication module of the terminal; generate IP data based on the non-IP data through the NAS of the terminal; and send the IP data to the IMS module of the terminal.
[0474] Optionally, the first message includes a protocol configuration option (PCO) parameter, wherein the PCO parameter includes the first information;
[0475] or,
[0476] The first message includes terminal capabilities, and the terminal capabilities include the first information.
[0477] Optionally, the second information is included in the PCO parameters of the message that carries the second information.
[0478] Optionally, the NAS module or communication module of the terminal generates IP data based on the non-IP data, including:
[0479] The NAS module or communication module of the terminal generates IP data based on the Session Description Protocol (SDP) negotiation results, IP 5-tuples, or IP 4-tuples obtained during the call setup process.
[0480] Optionally, the non-IP data includes at least one of the following: non-IP-based voice data; non-IP-based data packets; non-IP-based Real-Time Transport Protocol (RTP) data packets; voice data without IP headers or UDP headers; voice data without IP headers, UDP headers, or RTP headers; and voice data without IP headers or UDP headers but containing simplified or compressed RTP headers.
[0481] Optionally, the first bearer is a dedicated bearer.
[0482] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment shown in Figure 3, and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.
[0483] 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 FIG4. 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.
[0484] Specifically, this application embodiment also provides a network-side device, which can be the communication device shown in FIG11. As shown in FIG14, the network-side device 1400 includes: an antenna 1401, a radio frequency device 1402, a baseband device 1403, a processor 1404, and a memory 1405. The antenna 1401 is connected to the radio frequency device 1402. In the uplink direction, the radio frequency 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 radio frequency device 1402, which processes the received information and then transmits it through the antenna 1401.
[0485] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 1403, which includes a baseband processor.
[0486] 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.
[0487] The network-side device may also include a network interface 1406, such as a Common Public Radio Interface (CPRI).
[0488] 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 each module shown in FIG11 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.
[0489] Optionally, the radio frequency device 1402 is used to receive non-IP data from the first bearer when a first communication connection of type IP is established at the terminal, and the first communication connection includes a first bearer, and generate IP data based on the non-IP data, wherein the source address of the IP data is a first IP address; or, to receive IP data with a destination address of the first IP address, generate non-IP data based on the IP data, and send the non-IP data to the terminal through the first bearer; wherein the first IP address is the IP address corresponding to the first communication connection.
[0490] Optionally, the radio frequency device 1402 is also used for at least one of the following:
[0491] Receive a third message, the third message being used to request the establishment of the first communication connection or to request registration, the third message containing first information, the first information indicating that the terminal supports a first feature;
[0492] Send a second message, the second message indicating at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the communication peer supports the first feature;
[0493] The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
[0494] Optionally, the radio frequency device 1402 is further configured to send a fourth message for establishing the first bearer, the fourth message containing third information for determining that the first bearer is used to transmit non-IP data;
[0495] The third information indicates at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the first bearer is used to transmit non-IP data;
[0496] The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
[0497] Optionally, the third message includes PCO parameters, and the PCO parameters include the first information;
[0498] or,
[0499] The third message includes terminal capabilities, and the terminal capabilities include the first information.
[0500] Optionally, the second information is included in the PCO parameters of the message that carries the second information.
[0501] Optionally, generating IP data based on the non-IP data includes: the first network device generating IP data based on a data flow filter, IP 5-tuple, or IP 4-tuple obtained during the call setup process; wherein the data flow filter, IP 5-tuple, or IP 4-tuple contains the first IP address.
[0502] Optionally, the non-IP data includes at least one of the following: non-IP-based voice data; non-IP-based data packets; non-IP-based Real-Time Transport Protocol (RTP) data packets; voice data without IP headers or UDP headers; voice data without IP headers, UDP headers, or RTP headers; and voice data without IP headers or UDP headers but containing simplified or compressed RTP headers.
[0503] Optionally, the first bearer is a dedicated bearer.
[0504] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment shown in Figure 4, and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.
[0505] 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 method embodiments shown in FIG3 or FIG4 above and achieve the same technical effect. To avoid repetition, they will not be described again here.
[0506] 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.
[0507] 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 method embodiments shown in FIG3 or FIG4 above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0508] 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.
[0509] 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 method embodiments shown in FIG3 or FIG4 above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0510] This application also provides a wireless communication system, including a terminal and a network-side device. The terminal can be used to perform the steps of the method shown in FIG3 provided in this application embodiment, and the network-side device can be used to perform the steps of the method shown in FIG4 provided in this application embodiment.
[0511] 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.
[0512] 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 one or more instructions to cause a terminal or network-side device to execute the methods described in the various embodiments of this application.
[0513] 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
1. A communication method, comprising: When a terminal establishes a first communication connection of type Internet Protocol (IP) and the first communication connection includes a first bearer, the terminal sends non-IP data through the first bearer of the first communication connection; or, the terminal receives non-IP data through the first bearer of the first communication connection.
2. The method according to claim 1, wherein, The method further includes at least one of the following: The terminal sends a first message, which is used to request the establishment of the first communication connection, to request registration, to initiate a call request, or to respond to a call request. The first message contains first information, which indicates that the terminal supports a first feature. The terminal receives second information, which indicates at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the communication peer supports the first feature. The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
3. The method according to claim 1 or 2, wherein, The method further includes at least one of the following: The terminal receives a second message, which is used to establish the first bearer, and the second message contains third information. The terminal determines, based on the third information, that the first bearer is used to transmit non-IP data; The third information indicates at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the first bearer is used to transmit non-IP data; The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
4. The method according to claim 2 or 3, wherein, The method further includes: The terminal stores a fourth piece of information, which indicates at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the first bearer is used to transmit non-IP data.
5. The method according to any one of claims 1 to 4, wherein, The terminal sending non-IP data through the first bearer of the first communication connection includes: The IP Multimedia Subsystem (IMS) module of the terminal generates non-IP data and sends the non-IP data to the Non-Access Layer (NAS) module or communication module of the terminal. The NAS module or communication module of the terminal maps the non-IP data to the first bearer, and sends the non-IP data to the wireless access network device through the first bearer; The communication module is used for the terminal's fourth-generation mobile communication technology (4G), fifth-generation mobile communication technology (5G), or sixth-generation mobile communication technology (6G).
6. The method according to any one of claims 1 to 5, wherein, The terminal receives non-IP data through the first bearer of the first communication connection, including: The NAS module or communication module of the terminal receives non-IP data through the first bearer; The NAS module or communication module of the terminal sends the non-IP data to the IMS module of the terminal; The communication module is used for 4G, 5G, or 6G communication of the terminal.
7. The method according to any one of claims 1 to 6, wherein, The terminal sends non-IP data through the first bearer of the first communication connection, including: The terminal's IMS module generates IP data and sends the IP data to the terminal's NAS module or communication module; The terminal's NAS module or communication module generates non-IP data based on the IP data, maps the non-IP data to the first bearer, and sends the non-IP data to the wireless access network device through the first bearer; or... The NAS module or communication module of the terminal maps the IP data to the first bearer, and the NAS module or communication module of the terminal generates non-IP data based on the IP data, and sends the non-IP data to the wireless access network device through the first bearer. The communication module is used for 4G, 5G, or 6G communication of the terminal.
8. The method according to claim 5 or 7, wherein, Mapping the non-IP data to the first bearer includes: Based on the fifth piece of information, the non-IP data is mapped to the first bearer; The fifth piece of information indicates that the first bearer is used to transmit non-IP data, or that the first bearer is used to transmit voice data.
9. The method according to any one of claims 1 to 8, wherein, The terminal sends non-IP data through the first bearer of the first communication connection, including: The NAS module or communication module of the terminal receives non-IP data through the first bearer; The NAS module or communication module of the terminal generates IP data based on the non-IP data and sends the IP data to the IMS module of the terminal.
10. The method according to claim 2, wherein, The first message includes the Protocol Configuration Option (PCO) parameter, and the PCO parameter includes the first information; or, The first message includes terminal capabilities, and the terminal capabilities include the first information.
11. The method according to claim 2, wherein, The second information is contained in the PCO parameters of the message that carries the second information.
12. The method according to claim 9, wherein, The NAS module or communication module of the terminal generates IP data based on the non-IP data, including: The NAS module or communication module of the terminal generates IP data based on the Session Description Protocol (SDP) negotiation results, IP 5-tuples, or IP 4-tuples obtained during the call setup process.
13. The method according to any one of claims 1 to 12, wherein, The non-IP data includes at least one of the following: Non-IP-based voice data; Non-IP-based data packets; Non-IP-based real-time transport protocol data packets; Voice data that does not include IP headers or UDP headers; Voice data that does not include IP headers, UDP headers, or Real-Time Transport Protocol (RTP) headers; Voice data that does not include IP headers or UDP headers, but includes simplified or compressed RTP headers.
14. The method according to any one of claims 1 to 13, wherein, The first carrier is a dedicated carrier.
15. A communication method, comprising: When a first communication connection of type IP is established on the terminal, and the first communication connection includes a first bearer, The first network device receives non-IP data from the first bearer and generates IP data based on the non-IP data, wherein the source address of the IP data is the first IP address; or, The first network device receives IP data whose destination address is a first IP address, generates non-IP data based on the IP data, and sends the non-IP data to the terminal through the first bearer; Wherein, the first IP address is the IP address corresponding to the first communication connection.
16. The method according to claim 15, wherein, The method further includes at least one of the following: The first network device receives a third message, which is used to request the establishment of the first communication connection or to request registration. The third message contains first information, which indicates that the terminal supports a first feature. The first network device sends second information, the second information indicating at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the communication peer supports the first feature; The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
17. The method according to claim 15 or 16, wherein, The method further includes: The first network device sends a fourth message, which is used to establish the first bearer. The fourth message contains third information, which is used to determine that the first bearer is used to transmit non-IP data. The third information indicates at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the first bearer is used to transmit non-IP data; The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
18. The method according to claim 16, wherein, The third message includes PCO parameters, and the PCO parameters include the first information; or, The third message includes terminal capabilities, and the terminal capabilities include the first information.
19. The method of claim 16, wherein, The second information is contained in the PCO parameters of the message that carries the second information.
20. The method of claim 15, wherein, Generating IP data based on the non-IP data includes: The first network device generates IP data based on the data stream filter, IP 5-tuple or IP 4-tuple obtained during the call setup process; The data flow filter, IP 5-tuple, or IP 4-tuple contains the first IP address.
21. The method according to any one of claims 15 to 20, wherein, The non-IP data includes at least one of the following: Non-IP-based voice data; Non-IP-based data packets; Non-IP-based real-time transport protocol data packets; Voice data excluding IP headers and UDP headers; Voice data that does not include IP headers, UDP headers, or RTP headers; Voice data that does not include IP headers or UDP headers, but includes simplified or compressed RTP headers.
22. The method according to any one of claims 15 to 21, wherein, The first carrier is a dedicated carrier.
23. A communication device, comprising: The first sending unit is configured to send non-IP data through the first bearer of the first communication connection when a first IP-type communication connection is established at the terminal and the first communication connection includes a first bearer; or... The first receiving unit is configured to receive non-IP data through the first bearer of the first communication connection when a first communication connection of type IP is established at the terminal and the first communication connection includes a first bearer.
24. The apparatus according to claim 23, wherein, The first sending unit is further configured to send a first message, the first message being used to request the establishment of the first communication connection, to request registration, to initiate a call request, or to respond to a call request, the first message containing first information indicating that the terminal supports a first feature; or... The first receiving unit is further configured to receive second information, the second information indicating at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the communication peer supports the first feature; The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
25. A communication device, comprising: The second receiving unit is configured to receive non-IP data from the first bearer when a first communication connection of type IP is established at the terminal and the first communication connection includes a first bearer, and generate IP data based on the non-IP data, wherein the source address of the IP data is a first IP address. or, The second sending unit is configured to receive IP data whose destination address is a first IP address when a first communication connection of type IP is established at the terminal and the first communication connection includes a first bearer, generate non-IP data based on the IP data, and send the non-IP data to the terminal through the first bearer; Wherein, the first IP address is the IP address corresponding to the first communication connection.
26. The apparatus according to claim 25, wherein, The second receiving unit is further configured to receive a third message, the third message being used to request the establishment of the first communication connection or to request registration, the third message containing first information, the first information indicating that the terminal supports a first feature; The second sending unit is further configured to send second information, the second information indicating at least one of the following: the network side supports the first feature, the terminal starts or activates the first feature, and the communication peer supports the first feature; The first feature includes at least one of the following: generating non-IP data, sending non-IP data, receiving non-IP data, parsing non-IP data, and processing non-IP data.
27. A terminal comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as claimed in any one of claims 1 to 14.
28. A network-side device comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as claimed in any one of claims 15 to 22.
29. A chip comprising a processor and a communication interface coupled to the processor, the processor being configured to execute a program or instructions to implement the steps of the method as claimed in any one of claims 1 to 22.
30. A readable storage medium on which a program or instructions are stored, wherein the program or instructions, when executed by a processor, implement the steps of the method as claimed in any one of claims 1 to 22.
31. A computer program / program product stored in a storage medium, the computer program or program product being executed by at least one processor to implement the steps of the method as claimed in any one of claims 1 to 22.
