Information transmission method and apparatus, and communication device and readable storage medium

Abstract

The present application belongs to the technical field of communications. Disclosed are an information transmission method and apparatus, and a communication device and a readable storage medium. The information transmission method in the embodiments of the present application comprises: a first device sending a first message to a second device, wherein the first message is an NAS message, the first message comprises at least one container, the at least one container is used for bearing a second message, the second message comprises information related to a service supported by a terminal, and the terminal is the first device or the second device.

Description

Information transmission methods, devices, communication equipment and readable storage media

[0001] Cross-reference of related applications

[0002] This application claims priority to Chinese Patent Application No. 202411955130.0, filed in China on December 27, 2024, 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 an information transmission method, apparatus, communication equipment, and readable storage medium. Background Technology

[0004] The Basic Non-Access Stratum (NAS) protocol is responsible for the terminal's connection to the Access and Mobility Management Function (AMF), providing basic communication services such as connectivity management and mobility management. Currently, communication systems only provide connectivity (communication) services, so existing basic NAS protocols are designed solely for connectivity. However, 6G systems (6GS) can provide various new types of services, such as computing and sensing, which the current basic NAS protocol design does not support, resulting in low NAS message transmission efficiency. Summary of the Invention

[0005] This application provides an information transmission method, apparatus, communication device, and readable storage medium, which can solve the problem of low NAS message transmission efficiency in related technologies.

[0006] In a first aspect, an information transmission method is provided, executed by a first device, the method comprising:

[0007] The first device sends a first message to the second device;

[0008] The first message is a non-access stratum (NAS) message, which includes at least one container for carrying a second message. The second message includes information related to services supported by the terminal, and the terminal is either the first device or the second device.

[0009] Secondly, an information transmission device is provided, applied to a first device, the device comprising:

[0010] The sending module is used to send the first message to the second device;

[0011] The first message is a NAS message, which includes at least one container for carrying a second message. The second message includes information related to services supported by the terminal, and the terminal is either the first device or the second device.

[0012] Thirdly, an information transmission apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect.

[0013] Fourthly, a terminal is provided, the terminal 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 aspect.

[0014] Fifthly, a terminal is provided, the terminal being a first device, including a processor and a communication interface, wherein the communication interface is used to send a first message to a second device; wherein the first message is a NAS message, the first message including at least one container, the at least one container being used to carry a second message, the second message including information related to services supported by the terminal, and the terminal being either the first device or the second device.

[0015] In a sixth aspect, a network-side device is provided, the network-side device 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 aspect.

[0016] In a seventh aspect, a network-side device is provided, the network-side device being a first device, including a processor and a communication interface, wherein the communication interface is used to send a first message to a second device; wherein the first message is a NAS message, the first message including at least one container, the at least one container being used to carry a second message, the second message including information related to services supported by a terminal, and the terminal being either the first device or the second device.

[0017] In an eighth 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.

[0018] A ninth aspect provides a wireless communication system, comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the method described in the first aspect, or the network-side device is configured to perform the steps of the method described in the first aspect.

[0019] In a tenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect.

[0020] Eleventhly, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to perform the steps of the method as described in the first aspect.

[0021] In this embodiment, a first device sends a first message to a second device. The first message is a NAS message, and it includes at least one container for carrying a second message. The second message includes information related to services supported by the terminal, and the terminal is either the first device or the second device. This allows the second message to be carried via NAS messages, and since the second message includes information related to services supported by the terminal, the design based on the NAS protocol is no longer solely based on connectivity. It can also use NAS messages to transmit service-related information such as services that the terminal supports or wants to use, thereby improving the flexibility and richness of NAS messages. Furthermore, in this embodiment, devices can transmit service-related information via NAS messages, eliminating the need for separate signaling processes for different services and effectively improving information transmission efficiency. Attached Figure Description

[0022] Figure 1a is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0023] Figure 1b is a schematic diagram of the 5GS protocol architecture;

[0024] Figure 2 is a flowchart of an information transmission method provided in an embodiment of this application;

[0025] Figure 3a is one of the schematic diagrams of a protocol stack for interaction between a UE, a first network element, and a second network element that can be applied to an embodiment of this application;

[0026] Figure 3b is a schematic diagram of one of the 6G NAS protocol architectures applicable to this application;

[0027] Figure 3c is a second schematic diagram of a protocol stack for interaction between a UE, a first network element, and a second network element, applicable to an embodiment of this application.

[0028] Figure 3d is a second schematic diagram of a 6G NAS protocol architecture applicable to this application;

[0029] Figure 3e is a schematic diagram of a protocol stack for interaction between a UE, a first network element, and a second network element, applicable to an embodiment of this application.

[0030] Figure 4 is a structural diagram of an information transmission device provided in an embodiment of this application;

[0031] Figure 5 is a structural diagram of a communication device provided in an embodiment of this application;

[0032] Figure 6 is a structural diagram of a terminal provided in an embodiment of this application;

[0033] Figure 7 is a structural diagram of a network-side device provided in an embodiment of this application. Detailed Implementation

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

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

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

[0037] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems 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) radio systems. th Generation 6G communication system.

[0038] Figure 1a shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 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), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, 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. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. 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 specific technical terms. It should be noted that the embodiments in this application only use base stations in NR systems as examples for description and do not limit the specific type of base station.

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

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

[0041] To better understand, the relevant concepts that may be involved in the embodiments of this application are explained below.

[0042] Protocols are the rules and standards that define how data is connected, transmitted, and managed through a network (implemented through messages defined in the protocol). In the field of communications, protocols ensure that hardware and software operate harmoniously between different user terminals (UEs) and infrastructure. They control everything from the formation, transmission, and reception of data packets to the secure and efficient connection and communication of devices. In network systems, the protocol structure is managed in layers, with the commonly used three-layer architecture being L1, L2, and L3. This structure helps to modularly organize network functions, simplifying design, implementation, and troubleshooting. L3 (network layer) is the protocol layer actually responsible for control and management, including the Radio Resource Control (RRC) and NAS layers. For Evolved Packet System (EPS) and 5GS, the NAS layer can be further subdivided into two sublayers: Mobility Management (MM) and Connect Management (CM).

[0043] The primary function of the NAS protocol is to handle communication between the UE and core network elements. Different core network elements may provide different services. These services may be basic services, meaning the core functions provided by the network. Generally, users can enjoy these services after subscribing to them; basic services exist independently and do not depend on other services. These services may also be supplementary services, which are enhanced or supplementary functions provided to users on top of the basic services. They usually require additional subscription or configuration and only take effect if the basic services are functioning correctly. Based on this classification, NAS protocols can be divided into basic NAS protocols and service NAS protocols. Basic NAS protocols provide basic services, while service NAS protocols provide supplementary services. The basic NAS protocol and service NAS protocol in 5GS have the following design:

[0044] The Basic NAS protocol is responsible for communication between the UE and the core network elements (IE, AMF / SMF) that provide basic service functions. It provides the UE with basic communication services such as connection management and mobility management, including the following: access control related functions (such as NAS message endpoints, registration management, security functions, N2 control plane protocol endpoints), mobility management related functions, mobility management support functions for other network services (SM management service, SMS service, location service, CIoT), session management functions, etc.

[0045] The Protocol Discriminator (PD) is used to distinguish protocol types, ensuring that messages can be correctly identified and routed to the corresponding protocol entities by the routing functions in the protocol layer (located in the RR sublayer and 5GMM sublayer in Figure 1b). The Extended Protocol Discriminator (EPD) is an extension of the PD. Due to the introduction of 5GMM and 5GSM, the existing PD's indicator bits are insufficient, hence the extension. Tables 1 and 2 below show the 5GS protocol architecture, the corresponding EPD format, and the basic NAS message format, respectively.

[0046] Table 1. EPD values

[0047] Table 2.5GS NAS message format

[0048] The 5GS basic NAS protocol comprises two sublayers: the 5GS mobility management sublayer (corresponding to 5GS mobility management messages) and the 5GS session management sublayer (corresponding to 5GS session management messages). A message of a certain protocol type may contain one or more message types, thus requiring message types for differentiation. The message type determines the function of the message within the protocol in a specific direction. Therefore, the meaning of a message type depends on the protocol (the same value may have different meanings in different protocols) and the direction (within the same protocol, the same value may have different meanings when sent from the mobile station to the network and from the network to the mobile station).

[0049] The service NAS protocol is responsible for communication between the UE and core network elements that provide additional services, providing the UE with beyond communication services.

[0050] The following describes how the UE and the core network elements (referred to as CN NF for simplicity) of the additional services interact:

[0051] • Based on the control plane, information between the UE and the CN NF is transmitted as a payload of the 5GMM message through AMF pass-through.

[0052] • Based on the user plane, information between the UE and the CN NF is transmitted as a data packet, but the service NAS message format between the UE and the CN NF falls within the scope defined by the NAS protocol.

[0053] Tables 3 and 4 below provide examples of two different service NAS messages. It can be seen that the service NAS message has only one required domain message type, while other domains have different designs for different services.

[0054] Table 3. Service NAS message formats

[0055] Table 4. Service NAS message format

[0056] 6G breaks through the limitations of traditional connectivity. Beyond connectivity, it upgrades from a simple communication network to a comprehensive information service platform, capable not only of transmitting information but also providing a variety of services such as intelligent connectivity, computing, and sensing.

[0057] Currently, communication systems only provide connectivity (communication) services. Therefore, existing basic NAS protocols are designed solely based on connectivity, meaning that the resource dimension that current network systems can provide is limited to connectivity. Considering that 6G will introduce new service requirements, if the basic NAS protocol design remains solely based on connectivity, it will be impossible to achieve native support for multiple types of basic services in 6G. Furthermore, different services may require independent protocol stacks and signaling processes; without a unified protocol design, terminals or network devices from different vendors may be unable to interact.

[0058] To address the aforementioned problems, this application proposes an information transmission method for designing a new protocol. The following definitions are given and apply to all embodiments of this application.

[0059] NAS protocols can be divided into basic NAS protocols and service NAS protocols:

[0060] The Basic NAS protocol is responsible for communication between the UE and core network elements (such as 6G AMF / 6G SMF) that provide basic service functions. It provides the UE with basic services such as connection management and mobility management, including but not limited to the following: access control related functions (such as NAS message endpoint, registration management, security functions, N2 control plane protocol endpoint), mobility management related functions, mobility management support functions for other additional services (SM management service, SMS service, location service, Ambient Internet of Things (AIoT)) at the mobility management layer, session management functions, and management functions for other basic services.

[0061] The Service NAS protocol is responsible for communication between the UE and core network elements that provide additional service functions (such as service management network elements, computing management network elements / computing network elements, and perception management network elements / perception network elements).

[0062] Messages belonging to the Basic NAS protocol and the Service NAS protocol are called basic NAS messages and service NAS messages, respectively.

[0063] The first network element (e.g., the first or second device in subsequent embodiments) is responsible for at least one of the following functions: access control-related functions (e.g., N2 control plane protocol endpoint, NAS message endpoint, NAS encryption and integrity protection, NAS connection management, registration management, security functions, access authentication, access authorization, security anchor functions, etc.), mobility management-related functions (e.g., reachability management, mobility management, lawful eavesdropping service functions, etc.), and mobility management layer support functions for other network services (e.g., SM service support, SMS service support, location service support, AIoT service support, etc.). Specifically, the first network element can be a 6G AMF, eAMF, etc.

[0064] 6GS layer 3 consists of multiple sublayers, including at least one of the following:

[0065] 1. Wireless Resource Management Sublayer;

[0066] 2. Mobility Management Sublayer: The main functions of the mobility management sublayer are to support terminal identification, security, mobility, and general message transmission. The messages that the mobility management sublayer can identify and process are mobility management messages (e.g., 6GS mobility management messages).

[0067] 3. Session Management Sublayer: The main function of the session management sublayer is to support Protocol Data Unit (PDU) session processing between the UE and the session management network element (e.g., 6G SMF) (transmitted through the first network element (e.g., 6G AMF)). This includes at least one of the following: PDU session authentication, authorization, establishment, modification, and publication; requesting handover of existing PDU sessions between 3GPP access and non-3GPP access, or transferring existing Packet Data Network (PDN) connections in Evolved Packet System (EPS) to 5GS. The messages that the session management sublayer can identify and process are session management messages (e.g., 6GS session management messages).

[0068] PDU session: The association between the UE and the data network that provides PDU connection services.

[0069] 4. Service Management Sublayer: The main function of the service management sublayer is to support service management session processing in the UE and service management network element (e.g., 6G service management function). The messages that the service management sublayer can identify and process are service management messages (e.g., 6GS service management messages).

[0070] A service management session refers to a bearer used for communication between a UE and a service management network element. Once a service management session is established, an information transmission channel is created between the UE and the service management network element. This information can be control signaling, data, etc. Therefore, in related technologies, if a UE wants to use service management services, it must first establish a service management session. In other words, a service management session is a network resource established between the UE and the service management network element. A service management session is sometimes also referred to as a service management connection / bearer.

[0071] 5. The specific category service management sublayer mainly supports the processing of specific category service management sessions between the UE and specific category service management network elements. The specific category service management sublayer can identify and process messages as specific category service management messages.

[0072] A specific type of service management session refers to a bearer used for communication between a UE and a specific type of service management network element. Once a specific type of service management session is established, a data transmission channel is established between the UE and the specific type of service management network element. Therefore, in related technologies, if a UE wants to use specific type of service management services, it must first establish a specific type of service management session. In other words, a specific type of service management session is a network resource established between the UE and the specific type of service management network element. A specific type of service management session is sometimes also referred to as a specific type of service management connection.

[0073] The specific category of service management sublayer here can be at least one of the following: connection management sublayer, computing management sublayer, data management sublayer, algorithm management sublayer, signaling management sublayer, and policy management sublayer.

[0074] The specific categories of service messages (also referred to as second messages) in this application include at least one of the following: session management messages, service management messages, connection management messages, computing management messages, data management messages, algorithm management messages, signaling management messages, policy management messages, PDU messages, short messages, policy messages, location messages, computing messages, sensing messages, AI messages, data messages, multimedia messages, immersive messages, security messages, task messages, AIoT messages, energy-saving messages, NTN messages, slicing messages, V2X messages, and Prose messages.

[0075] 6. Specific service sublayer: Its main function is to support specific service session processing between the UE and specific service network elements (e.g., 6G computing function, 6G sensing function). The specific service sublayer can identify and process specific service messages (e.g., 6G computing messages, 6G sensing messages).

[0076] A specific service session refers to a bearer used for communication between a UE and a specific serving network element. Once a specific service session is established, a data transmission channel is established between the UE and the specific serving network element. Therefore, in related technologies, if a UE wants to use a specific service, it must first establish a specific service session. In other words, a specific service session is a network resource established between the UE and the specific serving network element. A specific service session can sometimes also be referred to as a specific service connection.

[0077] The specific service sublayer here can be at least one of the following: PDU sublayer, SMS sublayer, policy sublayer, location sublayer, computing sublayer, perception sublayer, Artificial Intelligence (AI) sublayer, data sublayer, multimedia sublayer, immersive sublayer, security sublayer, task sublayer, AIoT sublayer, energy-saving sublayer, Non-Terrestrial Network (NTN) sublayer, slicing sublayer, Vehicle-to-Everything (V2X) sublayer, and Proximity-based Services (Prose) sublayer. The information transmission method, apparatus, terminal, and network-side equipment provided in this application embodiment will be described in detail below with reference to the accompanying drawings, through some embodiments and application scenarios.

[0078] Please refer to Figure 2, which is a flowchart of an information transmission method provided in an embodiment of this application. As shown in Figure 2, the method includes the following steps:

[0079] Step 201: The first device sends a first message to the second device, wherein the first message is a NAS message, the first message includes at least one container, the at least one container is used to carry a second message, the second message includes information related to services supported by the terminal, and the terminal is either the first device or the second device.

[0080] It should be noted that the first device can be a terminal, and the second device can be a first network element (such as 6G AMF, eAMF, etc.), that is, the terminal sends the first message to the first network element. Alternatively, the first device can also be a first network element, and the second device can be a terminal, that is, the first network element sends the first message to the terminal.

[0081] In this embodiment, a first device sends a first message to a second device. This first message is a NAS message, and it includes at least one container for carrying a second message. The second message includes information related to services supported by the terminal, and the terminal is either the first device or the second device. This allows the second message to be carried via NAS messages, and since the second message includes information related to services supported by the terminal, the design based on the NAS protocol is no longer solely based on connectivity. It can also use NAS messages to transmit service-related information such as services that the terminal supports or wants to use, thereby improving the flexibility and richness of NAS messages. Furthermore, in this embodiment, devices can transmit service-related information via NAS messages, eliminating the need to establish independent protocol stacks or signaling processes for different services, effectively improving information transmission efficiency.

[0082] It should be noted that service-related information includes, but is not limited to, at least one of the following: service control signaling messages, service management messages, and service data.

[0083] Optionally, the first message includes at least one of the following:

[0084] First information, the first information is used to indicate the message type of the first message or to indicate the protocol type to which the first message belongs;

[0085] The second information is used to indicate the integrity information of the first message;

[0086] The third information is used to indicate the sequence information of the first message;

[0087] The fourth information is used to indicate the integrity status and / or encryption status of the first message;

[0088] The fifth information is used to indicate the encryption information of the first message;

[0089] The sixth information is used to indicate that the first message is used to transmit a target object, and the target object includes at least one of message, data, and signaling;

[0090] The seventh piece of information is used to identify the connection between the terminal and the third device;

[0091] The eighth information is used to indicate the transmission direction of the first message, such as the uplink transmission direction or the downlink transmission direction;

[0092] The ninth information is used to indicate that the first message carries at least one first container, and one of the first containers is used to carry a second message of one or more message types;

[0093] The tenth information is used to indicate the type of a specific category of service messages carried by the first container;

[0094] Eleventh information, the eleventh information is used to indicate that the first message carries at least one second container, and one second container is used to carry a second message of a message type;

[0095] The twelfth piece of information is used to indicate the identification information of the third device, such as the address, ID, and fully qualified domain name (FQDN) of the third device;

[0096] The thirteenth piece of information is used to indicate the service information that the terminal supports or wants to use;

[0097] The 26th information is used to indicate the message type of the first message;

[0098] The third device is a core network element (such as the second network element mentioned above) that provides specific services to the terminal.

[0099] For example, the first message includes first information, which indicates the message type of the first message or the protocol type to which the first message belongs. For instance, if the first device is a terminal and the second device is a first network element, that is, the terminal sends a first message to the first network element, and the first message is a mobility management message, then the first information indicates that the message type of the first message is a mobility management message, thereby enabling the first network element to know the message type of the first message through the first information.

[0100] Optionally, the first message may include second information, which is used to indicate the integrity information of the first message. It should be noted that if the second information is a Message Authentication Code (MAC), the existing MAC information length is 4 bytes. In this application, MAC information of 1 byte, 2 bytes, 3 bytes, or 4 bytes can be used, thereby making the form of the second information more flexible and effectively saving information length.

[0101] Optionally, the first message may include fourth information, which indicates the integrity status and / or encryption status of the first message. For example, the fourth information may indicate that the status of the first message is at least one of the following: Integrity-protected (indicating that the first message is secure, meaning it is not easily tampered with), Integrity-protected and encrypted (indicating that the first message is both secure and encrypted, meaning it is not easily tampered with and requires decryption using a key), Integrity-protected using a new security context, Integrity-protected and encrypted using a new security context, Integrity-protected and partially encrypted, Integrity-protected and partially encrypted using a new security context, Integrity-protected using a short MAC, and Integrity-protected and encrypted using a short MAC. Thus, the second device can also determine the encryption status and / or integrity status of the first message through the fourth information.

[0102] It should be noted that, in some embodiments, the fourth information may also be used to indicate the type or purpose of the first message, including at least one of the following: a secure first message, a security header for the first message, a secure and encrypted first message, a short secure first message (used to indicate that the first message is secure, meaning that the first message is not easily tampered with and is trustworthy. The first message also has a shortened message header, meaning that only communication devices that support the transmission of this type of message (with a shortened message header) can process the first message), and a short secure and encrypted first message (used to indicate that the first message is secure and encrypted, meaning that the first message is not easily tampered with, is trustworthy, and requires decryption using a key. The first message also has a shortened message header, meaning that only communication devices that support the transmission of this type of message (with a shortened message header) can process the first message).

[0103] Optionally, the first message may further include the fifth information, which is used to indicate the encryption information of the first message, so that the second device can know the encryption information of the first message based on the fifth information, so as to better decrypt the first message.

[0104] It should be noted that the aforementioned second, third, fourth, and fifth information can be categorized under the first security information, which is used to indicate security control information related to the first message. The first security information can be placed in an Information Element (IE), such as a Mobility Management Information Header IE or a Security Control Information Header IE; the first security information may also include at least one of the following:

[0105] IEI is used to identify primary security information;

[0106] The length field of the first security information is used to indicate the length of the first security information.

[0107] The content field of the first security information is used to indicate the content of the first security information (that is, at least one of the second to fifth information);

[0108] The type field of the first security information is used to indicate the type of the first security information, such as short MAC, key set identifier (ng Key Set Identifier, ngKSI), and sequence number.

[0109] Optionally, the first message may further include a sixth message, which indicates that the first message is used to transmit at least one of messages, data, and signaling. Thus, the second device can know the type of content transmitted by the first message or the function of the first message based on the sixth message. For example, if the sixth message indicates data, the first message may not only be responsible for transmitting mobility management-related information with the second device, but may also be used for transparent data transmission, that is, providing additional data transmission services.

[0110] Optionally, the first message may further include seventh information, which is used to indicate bearer information associated with the first message or to identify the connection between the terminal and the third device. For example, the seventh information may be an EPS Bearer Identity (EBI) and a PDU session, as used in related technologies. ID, or newly added bearer information, wherein the newly added bearer information includes at least one of the following: PDU bearer identifier / PDU session identifier, SMS bearer identifier / SMS session identifier, policy bearer identifier / policy session identifier, location bearer identifier / location session identifier, computing bearer identifier / computing session identifier, sensing bearer identifier / sensing session identifier, AI bearer identifier / AI session identifier, data bearer identifier / data session identifier, multimedia bearer identifier / multimedia session identifier, immersive bearer identifier / immersive session identifier, security bearer identifier / security session identifier, task bearer identifier / task session identifier, AIoT bearer identifier / AIoT session identifier, energy-saving bearer identifier / energy-saving session identifier, NTN bearer identifier / NTN session identifier, service management bearer identifier / service management session identifier, connection management bearer identifier / connection management session identifier, computing management bearer identifier / computing management session identifier, data management bearer identifier / data management session identifier, algorithm management bearer identifier / algorithm management session identifier, signaling management bearer identifier / signaling management session identifier; policy management bearer identifier / policy management session identifier, data management bearer identifier / data management session identifier, etc.

[0111] Optionally, the first message may further include eighth information, which indicates the transmission direction of the first message, such as uplink or downlink, allowing the same message to be used for both. Related technologies use different message type encodings to distinguish the transmission direction of the same message; for example, "01100111" indicates UL NAS transport and "01111000" indicates DL NAS transport. Now, the eighth information can be used to distinguish different transmission directions of the same message. This allows 1 bit to be used to distinguish different transmission directions of the same message. In related technologies, message types are encoded with 8 bits to indicate different message types of two types of basic NAS messages. There are 37 different message types in 5GMM messages and 19 different message types in 5GSM messages. However, considering that future technologies may have multiple types of basic NAS messages, 8 bits may not be sufficient. Using 1 bit of eighth information can save on message type encoding and can be used to indicate more message types, preventing the 8-bit message type encoding from becoming insufficient.

[0112] Optionally, the first message may further include a ninth message, which indicates that the first message carries at least one first container, and one of the first containers carries a second message of one or more message types (for example, the second message may be a service message of a specific category as mentioned above). In other words, one of the first containers is used to carry one or more service messages of a specific category. Thus, according to the indication of the ninth message, the second device can know that the first device wants to connect to a service management network element. The second device can then send relevant information to the corresponding service management network element according to the ninth message. The second device may have already obtained the address information or identification information of the service management network element in advance.

[0113] Optionally, the first message may further include tenth information, which is used to indicate the type of a specific category of service messages carried by the first container, so that the second device can also know the type of a specific category of service messages carried by the first container based on the tenth information.

[0114] Optionally, the first message may further include eleventh information, which indicates that the first message carries at least one second container, the second container being used to carry a second message of a message type, or in other words, a second container being used to carry a service message of a specific category, so that the second device can know the type of specific service message carried by the second container based on the eleventh information.

[0115] Optionally, the first message may further include twelfth information, which is used to indicate the identification information of the third device. The third device is a core network element that provides specific services to the terminal. For example, if the terminal is the first device, the second device can determine which core network element needs to provide services to the terminal based on the identification of the third device. Therefore, the second device can send relevant information to the corresponding core network element to request it to provide services to the terminal.

[0116] Optionally, the first message may also include thirteenth information, which is used to indicate the service information supported or desired by the terminal. For example, if the terminal is a first device, the second device can also know the service information supported or desired by the terminal, so that the second device can send relevant information to the core network element that supports or desires the service information supported by the terminal, in order to request the corresponding core network element to provide services to the terminal.

[0117] In this embodiment, a first device sends a first message to a second device. The first message includes at least one of the first to thirteenth pieces of information as described above. This information includes information indicating the first and second containers carried by the first message, and / or information indicating the services supported or desired by the terminal, etc. This allows the NAS protocol-based design to go beyond just connection-based design, enabling the transmission of service-related information such as services supported or desired by the device based on NAS messages, thereby improving the flexibility and richness of NAS message information. Furthermore, in this embodiment, devices can transmit service-related information via NAS messages, eliminating the need to establish independent protocol stacks or signaling processes for different services, effectively improving information transmission efficiency.

[0118] Optionally, in this embodiment of the application, the first information is indicated by any of the following:

[0119] The encoding in the Extended Protocol Authentication Element (EPD); for example, the first message is indicated by any unused encoding in the Extended Protocol Authentication Element (EPD) to indicate the message type of the first message or to indicate the protocol type to which the first message belongs;

[0120] Arbitrary encoding in IE (First Internet Explorer);

[0121] Any encoding in the first IE, and indicating that the first IE is an enhanced protocol authenticator through encoding in the protocol authenticator IE, for example, indicating that the first IE is an enhanced protocol authenticator through unused encoding in the protocol authenticator IE.

[0122] The first IE is different from the extended protocol identifier IE. The first IE can be understood as a newly added IE, that is, an IE added on the basis of the existing IE in the prior art. The function of the first IE is the same as that of the extended protocol identifier IE.

[0123] In this embodiment of the application, the first information is indicated by any of the above encoding methods, which effectively improves the flexibility of the first information encoding.

[0124] Optionally, the message type of the first message is a mobility management message.

[0125] Optionally, the protocol type to which the second message belongs includes at least one of the following:

[0126] Session Management Sublayer, Service Management Sublayer, Connection Management Sublayer, Computation Management Sublayer, Data Management Sublayer, Algorithm Management Sublayer, Signaling Management Sublayer, Policy Management Sublayer, Protocol Data Unit (PDU) Sublayer, Short Message Sublayer, Policy Sublayer, Location Sublayer, Computation Sublayer, Perception Sublayer, Artificial Intelligence (AI) Sublayer, Data Sublayer, Multimedia Sublayer, Immersive Sublayer, Security Sublayer, Task Sublayer, Environmental Internet of Things (AIoT) Sublayer, Energy Saving Sublayer, Non-Terrestrial Network (NTN) Sublayer, Slicing Sublayer, V2X Sublayer, Prose Sublayer; or,

[0127] The message type of the second message includes at least one of the following:

[0128] Session management messages, service management messages, connection management messages, compute management messages, data management messages, algorithm management messages, signaling management messages, policy management messages, PDU messages, short messages, policy messages, location messages, compute messages, perception messages, AI messages, data messages, multimedia messages, immersive messages, security messages, task messages, AIoT messages, energy-saving messages, NTN messages, slicing messages, V2X messages, and Prose messages.

[0129] Understandably, when the protocol type of the second message is the session management sublayer, the second message can be a session management message; when the protocol type of the second message is the service management message, the second message can be a service management message, and so on.

[0130] In this embodiment, when the first message is a mobility management message, different types of second messages are carried by different types of containers. For example, AI messages are carried by containers used to carry AI messages, and perception messages are carried by containers used to carry perception messages. This design also allows NAS messages to carry different types of second messages through different types of containers. The second messages include information related to services supported by the terminal, thus enabling the transmission of service-related information based on NAS messages. This makes the design based on the NAS protocol no longer just a connection-based design; devices can transmit service-related information through NAS messages, eliminating the need to establish independent protocol stacks or signaling processes for different services, effectively improving information transmission efficiency.

[0131] Optionally, if the first message includes the thirteenth information or the terminal wants to use a specific service, the first message may include at least one of the ninth and eleventh information.

[0132] It is worth noting that a terminal's desire to use a specific service can manifest in at least one of the following ways: the terminal receives a specific service message from the upper layer, or the terminal wants to transmit a specific service message.

[0133] Understandably, the thirteenth information is used to indicate the service information supported or desired by the terminal, the ninth information is used to indicate that the first message carries at least one first container, and the eleventh information is used to indicate that the first message carries at least one second container. The first container is used to carry one or more service messages of a specific category, and the second container is used to carry a service message of a specific category, thereby enabling the transmission of service information through NAS messages.

[0134] Optionally, if the first message includes the ninth information, the first device performs at least one of the following:

[0135] The second message is carried using a payload container type IE, and the message type of the second message includes at least one of the following: connection management message, computation management message, data management message, algorithm management message, signaling management message, and policy management message;

[0136] The second message is carried by the first container IE, and the message type of the second message is a service management message.

[0137] The second message is carried by multiple first container IEs, and the message type of the second message includes at least one of the following: connection management message, computing management message, data management message, algorithm management message, signaling management message, and policy management message.

[0138] Understandably, the ninth information is used to indicate that the first message carries at least one first container. If the first message sent by the first device to the second device includes the ninth information, that is, the first message carries at least one first container, and the first container is used to carry one or more service messages of a specific category, then the first device can use the first container to carry the second message. The message type of the second message can be a service message of a specific category, such as a connection management message, a computing management message, a data management message, an algorithm management message, a signaling management message, or a policy management message, thereby making the message type of the second message match the category of the service message carried by the first container.

[0139] Optionally, if the first message includes the eleventh information, the first device performs at least one of the following:

[0140] The second message is carried using a payload container;

[0141] The second message is carried using multiple second container IEs;

[0142] The second message is at least one of the following: PDU message, short message, policy message, location message, computing message, perception message, AI message, data message, multimedia message, immersive message, security message, task message, AIoT message, energy-saving message, NTN message, slice message, V2X message, and Prose message.

[0143] Understandably, the eleventh information is used to indicate that the first message carries at least one second container. The first message sent from the first device to the second device includes the eleventh information, meaning the first message carries at least one second container. Since the second container carries a specific type of service message, the first device can use the second container to carry a second message. The message type of the second message can be a specific type of service message, such as a PDU message, SMS message, policy message, location message, computing message, sensing message, AI message, data message, multimedia message, immersive message, security message, task message, AIoT message, energy-saving message, NTN message, etc. This ensures that the message type of the second message matches the category of the service message carried by the second container, thus enabling the transmission of service-type information (the second message) through the first message (NAS message). This makes the NAS protocol-based design no longer solely based on connectivity, allowing devices to transmit service-type information through NAS messages, improving information transmission efficiency.

[0144] Optionally, when the first message includes the ninth information and the first device uses a first container IE to carry the second message, or uses multiple first containers of specific categories to carry the second message, or when the first message includes the eleventh information and the first device uses multiple second container IEs to carry the second message, the second message includes at least one of the following:

[0145] The fourteenth piece of information is used to indicate the protocol type to which the second message belongs;

[0146] The fifteenth piece of information is used to indicate the message type of the second message;

[0147] The sixteenth piece of information is used to identify the connection between the terminal and the third device;

[0148] The seventeenth piece of information is used to indicate the transmission direction of the second message;

[0149] The eighteenth piece of information is used to indicate the Procedure Transaction Identity (PTI);

[0150] The nineteenth message, which is used to indicate the application mode of the second message;

[0151] The twentieth information is used to indicate the attributes of the first session, which is a bearer used by the terminal to communicate with a third device or a connection between the terminal and a third device that provides a specific service.

[0152] In this embodiment of the application, the second message includes at least one of the fourteenth to twentieth information as described above. Based on the fourteenth to twentieth information, the second device can also know the message type, transmission direction, and application mode of the second message, which is more helpful for the second device to process the second message.

[0153] Optionally, if the terminal supports NTN or the terminal wants to use NTN services, the first message includes at least one of the following:

[0154] The first information is used to indicate that the message type of the first message is a mobility management message, a mobility management message with an optimized header, or a message for NTN services.

[0155] The second information and the third information; the second information may be a shorter version of the second information.

[0156] The fourth information is further used to indicate that the first message has a short header or that the first message is used for NTN service;

[0157] The fifth piece of information;

[0158] The twenty-sixth piece of information;

[0159] The second message includes at least one of the following:

[0160] The 21st message is used to indicate whether the transmission of the second message is complete, and can also use certain bits to indicate whether there is further uplink data in the second message;

[0161] The 22nd message is used to indicate the message type of the second message.

[0162] It should be noted that when the first information indicates that the message type of the first message is a mobility management message, the sixth information can be used to indicate that the first message is a mobility management message with an optimized header.

[0163] Optionally, the second twentieth piece of information may include at least one of the following:

[0164] Control Plane (CP) user data; in this case, the second message includes user data.

[0165] In the case of a Short Message Service (SMS) message, the second message may not include the twentieth eleventh message, the first message may not include the third message, and the second message includes an SMS message.

[0166] Location Services (LCS) information; in this case, the first message may not include the third information, and the second message contains the LCS message container.

[0167] In the case of signaling, the second message may not include the 21st information, the first message may not include the third information, and the second message includes a signaling message.

[0168] In this embodiment, when the terminal supports NTN or wants to use NTN services, the information content included in the first message and the information content included in the second message are defined to better facilitate the second device in processing the first and second messages based on the aforementioned information content. It can also be seen that the first message contains only the necessary content. This is because in NTN scenarios, air interface resources are limited and expensive. In satellite communication, the amount of data transmitted over the air interface should be minimized. Besides the raw data, the number of data encapsulation layers, message headers, and control information bytes should be reduced as much as possible.

[0169] It is worth noting that NTN service here can also be described as Geosynchronous Earth Orbit (GEO) voice service, satellite service, etc., referring to network services accessed via satellite.

[0170] Optionally, if the terminal supports AIoT or the terminal wants to use AIoT services, the first message includes at least one of the following:

[0171] The first information is used to indicate that the message type of the first message is a mobility management message, a mobility management message with an optimized header, or a message for AIoT services.

[0172] The fourth information, when the first information is used to indicate that the message type of the first message is a mobility management message, is further used to indicate...

[0173] The first message is a mobility management message with an optimized header or a message for AIoT services;

[0174] The second message includes at least one of the following:

[0175] The 23rd message is used to indicate different message types, which include at least one of the following: inventory request message, inventory response message, read request message, read response message, write request message, and write response message;

[0176] A key identifier, which is used for encryption between the terminal and the AIoT service network element;

[0177] User face and control face identifiers;

[0178] The 24th information is used to indicate the AIoT session identifier;

[0179] The twenty-fifth message is used to indicate the encryption status of the second message.

[0180] In this embodiment of the application, it is defined that when the terminal supports AIoT or the terminal wants to use AIoT services, the information content included in the first message and the information content included in the second message are more helpful for the second device to process the first message and the second message according to the above information content.

[0181] Understandably, the first device sends a first message to the second device, thereby enabling the second device to receive the first message sent by the first device. This application also provides an information transmission method, the method comprising the following steps:

[0182] The second device receives a first message sent by the first device, wherein the first message is a NAS message, the first message includes at least one container, the at least one container is used to carry a second message, the second message includes information related to services supported by the terminal, and the terminal is either the first device or the second device.

[0183] It should be noted that the relevant content involved in the embodiments of this application, such as the message content and related concepts included in the first message and the second message, are described in the method embodiment shown in Figure 2 above, and will not be repeated here.

[0184] To better understand the technical solution of this application, the technical solution of this application will be described below through specific embodiments.

[0185] Example 1

[0186] In this embodiment, the second device (e.g., the first network element) is responsible for forwarding other basic NAS messages and some service NAS messages. That is, at this time, other basic NAS messages and some service NAS messages need to be carried in mobility management messages. The forwarding path of the NAS messages is: UE (i.e., the first device mentioned above) → base station → first network element (i.e., the second device mentioned above) → serving network element (i.e., the third device mentioned above).

[0187] Implementation Method 1: Basic NAS messages include mobility management and session management messages (in this case, layer 3 has two sub-layers, that is, two first messages or fourteenth messages (e.g., EPD)). The specific scheme is as follows:

[0188] The terminal sends a first message to a first network element, wherein the first message is a mobility management message and includes at least one of the following:

[0189] (1) First information, used to indicate the protocol type to which the first message belongs, wherein the first information is used to indicate that the first message belongs to a mobility management message, including at least one of the following implementation forms:

[0190] 1) Use any value from the reserved field in the existing EPD value list, such as "00011110", to identify mobility management messages, as shown in Table 5 below:

[0191] Table 5. EPD value

[0192] 2) Extend the existing PD and use a new IE to identify mobility management messages. This method is compatible with both 6G and 5G. Existing EPD residual values ​​are all encoded as "reserved". Considering the existing protocol specification that "An IE is defined to be syntactically incorrect in a message if it contains at least one value defined as "reserved", to avoid using the reserved value of the EPD IE being considered a syntactic error, the idea introduced by EPD is adopted: extend the PD value and use a new IE to identify the protocol to which mobility management and session management messages belong.

[0193] Specifically, PD "1101" is used to indicate Enhancement of the PD, and an ENPD values ​​IE is added. Any value in this IE, such as "00001111", indicates a mobility management message; as shown in Tables 6 and 7 below:

[0194] Table 6. PD value

[0195] Table 7. ENPD value

[0196] 3) Directly use a new IE to identify mobility management messages; specifically, add a first IE, which is used to identify the protocol to which the message belongs, and use any value in the IE, such as "00000000", to indicate that it is a mobility management message.

[0197] (2) Second information, used to indicate the integrity information (e.g., MAC) of the first message; it is worth noting that if the second information is MAC, the existing MAC information length is 4 bytes, and here MAC information with a length of 1 / 2 / 3 / 4 bytes can be used;

[0198] (3) Third information, used to indicate the sequence information (e.g., sequence number) of the first message;

[0199] (4) Fourth information, used to indicate the integrity and / or encryption status of the first message (e.g., security header type);

[0200] The fourth information may indicate that the integrity and / or encryption status of the first message is at least one of the following: integrity, integrity and encryption, integrity using a new security context, integrity and encryption using a new security context, integrity and partial encryption, integrity and partial encryption using a new security context, integrity using a short MAC, and integrity and encryption using a short MAC.

[0201] Optionally, the fourth information may also be used to indicate the type or purpose of the first message, including at least one of the following: a security-protected first message, a security header for the first message, a secure and encrypted first message, or a short security-protected first message.

[0202] (5) The fifth piece of information is used to indicate the encryption information of the first message (e.g., ngKSI);

[0203] It is worth noting that the second to fifth pieces of information here can be categorized under the first security information. The first security information is used to indicate security control information related to the first message. The first security information can be placed in an IE (e.g., a mobility management security control information header). The first security information includes at least one of the following:

[0204] IEI is used to identify primary security information;

[0205] The length field of the first security information is used to indicate the length of the first security information.

[0206] The content field of the first security information is used to carry the content of the first security information (the second to fifth information);

[0207] The type field of the first security information is used to indicate the type of the first security information, such as: short MAC, ngKSI, and sequence number;

[0208] (6) Sixth information: used to indicate the message type or purpose of the first message; (e.g., registration request, deregistration request, service request, etc.).

[0209] Understandably, mobility management messages include many messages (more than 40 in 5G), each with a different type or function, requiring differentiation using sixth information. Different messages have different decoding functions, thus requiring identification.

[0210] (7) Twenty-seventh information: used to indicate the type of the first message or the application mode of the first message (e.g., registration type, service type (MT, MO, etc.));

[0211] It should be noted that after determining the type of the first message, the twenty-sixth information is a more detailed classification. For example, if the first message is a registration request message, but registration request messages have different types, such as initial registration, emergency registration, etc., the twenty-sixth information can be used to indicate the application mode of the registration request message, such as emergency registration.

[0212] (8) Twenty-eighth information: Identification information used to indicate the recipient of the first message and / or the sender;

[0213] The base station can use this information to select the first network element. For example, the twenty-eighth piece of information can be a 5G-S-TMSI, used to identify one or more AMFs and their corresponding UEs. After receiving the twenty-eighth piece of information, the base station can select an AMF that can provide services to the UE.

[0214] (9) Seventh information: used to indicate the bearer information associated with the first message or to identify the connection between the UE and the service network element;

[0215] The seventh piece of information can be an existing EBI or PDU session ID, and includes at least one of the following: PDU bearer identifier / PDU session identifier, SMS bearer identifier / SMS session identifier, policy bearer identifier / policy session identifier, location bearer identifier / location session identifier, computing bearer identifier / computing session identifier, sensing bearer identifier / sensing session identifier, AI bearer identifier / AI session identifier, data bearer identifier / data session identifier, multimedia bearer identifier / multimedia session identifier, immersive bearer identifier / immersive session identifier, security bearer identifier / security session identifier, task bearer identifier / task session identifier, AIoT bearer identifier / AIoT session identifier, energy-saving bearer identifier / energy-saving session identifier, NTN bearer identifier / NTN session identifier, service management bearer identifier / service management session identifier, connection management bearer identifier / connection management session identifier, computing management bearer identifier / computing management session identifier, data management bearer identifier / data management session identifier, algorithm management bearer identifier / algorithm management session identifier, signaling management bearer identifier / signaling management session identifier, policy management bearer identifier / policy management session identifier, data management bearer identifier / data management session identifier, etc.

[0216] (10) Eighth information, used to indicate the transmission direction of the first message (e.g., uplink) (the purpose of introducing this information is that the uplink and downlink can use the same message);

[0217] Existing technologies use message type to distinguish the transmission direction of the same message, such as UL NAS transport and DL NAS transport. Now, an eighth bit can be used to distinguish different transmission directions of the same message. The advantage of this is that only 1 bit can be used to distinguish different transmission directions of the same message, saving the encoding bits of the sixth bit.

[0218] It is worth noting that: the information mentioned in (7) to (10) here can be attributed to the first MM control information. The first MM control information is used to indicate the control information of the first message. All control information related to the first message can be placed in an IE (e.g., mobility management control information header). The first MM control information may also include at least one of the following:

[0219] IEI is used to identify the first MM control information;

[0220] The length field of the first MM control information is used to indicate the length of the first MM control information;

[0221] The content field of the first MM control information is used to carry the content of the first MM control information (the seventh to tenth information);

[0222] (11) Thirteenth information, used to indicate the services supported or desired by the UE, the thirteenth information including at least one of the following:

[0223] a. Capability information, used to indicate that the UE supports a first service, which may include at least one of the following: SMS, UE policy, LCS, computing service, sensing service, AI service, data service, multimedia service, immersive service, security service, mission, AIoT service, energy saving service, NTN service;

[0224] b. UE usage settings information, used to indicate the terminal's usage settings information to the network, wherein the terminal's usage settings information may include at least one of the following: voice centric, data centric, signalalling / connection centric, computing centric, algorithm centric;

[0225] c. Preference indication information, used to indicate the specific service requested by the UE, which may include at least one of the following: SMS, UE policy, LCS, computing service, sensing service, AI service, data service, multimedia service, immersive service, security service, task, AIoT service, energy saving service, NTN service.

[0226] In this embodiment, the first message can carry the second message. Referring to Figure 3a, the first network element sends the second message to the second network element. At this time, the first network element will pass the second message through to the second network element without parsing the second message. The second message can be a data payload / container or a service NAS message.

[0227] The first message also includes at least one of the following:

[0228] (1) Ninth information, used to indicate that the first message carries at least one first container, the first container being used to carry a second message of one or more message types. In some embodiments, the first container may also be called a service management message container.

[0229] The implementation method of the ninth information is as follows:

[0230] a. A payload container is used to carry the second message, the message type of which includes at least one of the following: connection management message, computation management message, data management message, algorithm management message, signaling management message, and policy management message. Each container is used to carry the corresponding management message, i.e., the second message;

[0231] b. Use a first container IE to carry the second message, and the message type of the second message is a service management message.

[0232] c. Use multiple first container IEs to carry the second message, and the message type of the second message includes at least one of the following: connection management message, computing management message, data management message, algorithm management message, signaling management message, and policy management message.

[0233] It should be noted that here, "container" refers to AMF not parsing the content within the container. When the first container is a service management container and the second message is a computation message, using the service management container IE to carry the second message can also be described as the service management container being used to transmit computation messages. That is, when the terminal wants to transmit computation messages, the terminal can set the service management container IE in the first message as a computation message and set the service management container type IE as a computation message container.

[0234] (2) Eleventh information, used to indicate that the first message carries at least one second container;

[0235] The implementation method of the eleventh message:

[0236] a. Use a payload container to carry the second message.

[0237] b. Use a second container (IE) to carry the second message;

[0238] The message type of the second message includes at least one of the following: PDU message, short message, policy message, location message, computing message, perception message, AI message, data message, multimedia message, immersive message, security message, task message, AIoT message, energy-saving message, and NTN message.

[0239] It should be noted that the difference between the ninth and eleventh information is that after the first network element receives the ninth information from the UE, it transmits it to a unified service management network element or a specific type of service management network element, and then the unified service management network element or the specific type of service management network element transmits the specific service message to the specific service network element; after the first network element receives the eleventh information from the UE, it directly transmits the specific service message to the specific service network element.

[0240] It should be noted that here, "container" refers to AMF not parsing the content within the container. When the second container is a compute container and the second message is a compute message, using the compute container IE to carry the second message can also be described as the compute container being used to transmit compute messages. That is, when the terminal wants to transmit a compute message, the terminal can set the compute container IE in the first message as the compute message.

[0241] (3) The twelfth information, which is used to indicate the identification information of the second network element (i.e., the aforementioned third device), that is, the routing information used to indicate the content of the second message, can be at least one of the following: network element identification information, network element address information, or information received from the service NAS layer;

[0242] (4) The twenty-first message, used to indicate whether the second message has been transmitted successfully; (e.g., Downlink Data Expected (DDX)).

[0243] In some implementations, the second message may also be referred to as Service NAS messages. The second message can be a message or raw data, including at least one of the following:

[0244] (1) The twenty-ninth message is used to indicate different service operations (e.g., connection management, signaling, path switching, identification request, security establishment, information transmission, etc.); further, it is used to indicate different service operations under the same service type;

[0245] (2) The twenty-third message is used to indicate different message types, such as request messages, response messages, completion messages, and commands;

[0246] (3) The eighteenth information is used to indicate the message flow information associated with the first message, to identify the message flow (for a given PD and SAP), and can be used to associate a pair of bidirectional messages (request-response);

[0247] (4) Thirty information, used to indicate information related to routing / authentication or information provided by higher layers, including at least one of the following:

[0248] IP Address Configuration / URL: Used for routing payload;

[0249] Key: Used for authentication;

[0250] (5) Seventh information: Same as above, used to identify the connection between UE and service network element, including at least one of the following: PDU bearer identifier / PDU session identifier, short message bearer identifier / short message session identifier, policy bearer identifier / policy session identifier, location bearer identifier / location session identifier, computing bearer identifier / computing session identifier, sensing bearer identifier / sensing session identifier, AI bearer identifier / AI session identifier, data bearer identifier / data session identifier, multimedia bearer identifier / multimedia session identifier, immersive bearer identifier / immersive session identifier, security bearer identifier / security session identifier, task bearer identifier / task session identifier, AIoT bearer identifier / AIoT session identifier, energy saving bearer identifier / energy saving session identifier, NTN bearer identifier / NTN session identifier;

[0251] (6) Sequence number (counter): Used to record the number of service message transmissions;

[0252] (7) Information provided by the upper level;

[0253] (8) Raw data.

[0254] For example, the format of the second message is shown in Table 8 below:

[0255] Table 8. Second Message Format

[0256] The following examples illustrate the design of the first message in several business scenarios.

[0257] Scenario 1: NTN business scenario

[0258] Understandably, satellite communication has the following characteristics:

[0259] Limited and expensive bandwidth: Due to limited spectrum resources, satellite communication bandwidth is relatively restricted, especially in high-demand frequency bands (such as Ku and Ka bands). Therefore, satellite bandwidth resources are usually more expensive than terrestrial networks. This imposes certain limitations on applications with high bandwidth requirements, such as video transmission and big data transmission.

[0260] The complexity of two-way communication: Two-way message exchange in satellite communication is quite complex because limitations in latency, power, and bandwidth can affect the timing of ACK, retransmission, or acknowledgment.

[0261] Significant latency: Satellites, especially geostationary orbit (GEO) satellites, are approximately 35,786 kilometers above the Earth. The signal travels a considerable amount of time between the satellite and the ground, resulting in significant communication latency (typically around 500 milliseconds). This latency poses challenges for real-time communication, voice calls, or low-latency applications such as remote control.

[0262] Based on the above characteristics, it can be seen that message transmission in satellite scenarios has the following characteristics:

[0263] In satellite communication, the amount of data transmitted over the air interface should be kept as small as possible. In addition to the raw data, the number of data encapsulation layers, message headers and control information bytes should be reduced as much as possible.

[0264] It is necessary to indicate to the receiving end whether there is any further data transmission;

[0265] When the data volume is small and the transmission frequency is relatively low, signaling / data can be transmitted using the CP method.

[0266] When transmitting NTN service data using the CP method, considering the above characteristics and based on the solution provided in this application, the first message includes at least one of the following:

[0267] (1) First information, used to indicate the protocol type to which the first message belongs or the message type of the first message. In this case, the first information is used to indicate that the first message belongs to the mobility management message.

[0268] In another implementation, a new value can be used to indicate that the first message has a short header or that the first message is used for NTN services.

[0269] (2) Second information, used to indicate the integrity information (e.g., MAC) of the first message;

[0270] (3) Third information, used to indicate the sequence information (e.g., sequence number) of the first message;

[0271] (4) Fourth information, used to indicate the integrity and / or encryption status of the first message (e.g., security header type);

[0272] In another implementation, the new value can be used to indicate that the first message has a short header or that the first message is used for NTN services. Understandably, NTN can be applied to scenarios such as military and emergency situations and involves cross-border access, thus requiring high security. Therefore, all messages are fully encrypted by default, and the fourth information is used to indicate the type or purpose of the first message.

[0273] (5) The fifth piece of information is used to indicate the encryption information of the first message (e.g., ngKSI);

[0274] It's worth noting that the fifth and fourth pieces of information can be combined into a single byte, for example, using existing KSI and sequence number IE. The benefits of combining them into one byte include improved encoding efficiency and reduced encoding bytes.

[0275] (6) Twenty-sixth information: used to indicate the message type of the first message; (e.g., registration request, service request, etc.); for example, new value can be used to indicate that the first message has a short message header or that the first message is for NTN service;

[0276] (7) Twenty-first message: used to indicate whether the second message has been transmitted (e.g., DDX);

[0277] (8) Twenty-second information, used to indicate the type information of the second message.

[0278] For example, Tables 9 and 10 below show two design examples of the first message format in this business scenario, where the data payload carries the second message:

[0279] Table 9. First Message Format

[0280] Table 10. First Message Format

[0281] The twenty-second piece of information can be set to at least one of the following:

[0282] If CP user data: then the data payload contains user data, meaning the second message is user data in this case;

[0283] SMS: It can omit the twenty-first and third messages, and the data payload contains the SMS message, meaning the second message is an SMS message in this case.

[0284] LCS container: can be without third information, the data payload contains LCS message container, that is, the second message is LCS message in this case;

[0285] Signalling: can omit the 21st and 3rd messages, and the data payload contains the signaling message, meaning the second message is the signaling message in this case.

[0286] Scenario 2: AIoT Business Scenarios

[0287] AIoT services share the same underlying principles as NTN services, but one key difference is that NTN services often have stricter security requirements (NTN is used in scenarios such as public security and maritime affairs, where service data privacy needs to be guaranteed), thus requiring robust NAS layer security and encryption. However, AIoT services are used in scenarios like factories and farms where security requirements are weaker, and service data privacy can rely solely on the APP layer, so security-related information may not be necessary.

[0288] In this scenario, based on the technical solution provided in this application, the first message may include at least one of the following:

[0289] (1) First information, used to indicate the protocol type to which the first message belongs or the message type of the first message. In this case, the first information is used to indicate that the first message belongs to the mobility management message.

[0290] In another implementation, a new value can be used to indicate that the first message has a short header or that the first message is used for AIoT services.

[0291] (2) Fourth information, used to indicate the integrity and / or encryption status of the first message (e.g., security header type);

[0292] In another implementation, a new value can be used to indicate that the first message has a short header or that the first message is used for AIoT services.

[0293] For example, Tables 11 and 12 below are two design examples of the first message format in this AIoT business scenario:

[0294] Table 11. First Message Format

[0295] Table 12. First Message Format

[0296] In this business scenario, the second information may include at least one of the following:

[0297] The twenty-third message is used to indicate different message types, including at least one of the following: inventory request, inventory response, read operation, and write operation;

[0298] Key ID, used for encryption between UE and AioTF, can be 3 bits.

[0299] User plane and control plane flags can be 1 bit.

[0300] The 24th piece of information can be the AIoT session ID;

[0301] The twenty-fifth message is used to indicate the encryption status of the second message.

[0302] In this embodiment, when the first message is a mobility management message, since the session management message needs to be carried within the mobility management message for transmission, it does not require security-related information. Therefore, the session management message can serve as the second message. In this case, the second message includes at least one of the following:

[0303] The fourteenth piece of information is used to indicate the protocol type to which the second message belongs. In this case, it is used to indicate that the protocol type of the second message is the session management sublayer.

[0304] The fifteenth piece of information is used to indicate the message type of the second message, and in this case, it is used to indicate that the message type of the second message is a session management message;

[0305] The sixteenth piece of information is used to identify the connection between the terminal and the third device;

[0306] The seventeenth piece of information is used to indicate the transmission direction of the second message;

[0307] The eighteenth piece of information is used to indicate the Procedure Transaction Identity (PTI);

[0308] The nineteenth piece of information is used to indicate the message type or application mode of the second message;

[0309] The twentieth information is used to indicate the attributes of the first session, which is a bearer used by the terminal to communicate with a third device or a connection between the terminal and a third device that provides a specific service.

[0310] It should be noted that the nineteenth and twentieth messages here can be categorized under the first SM control information. The first SM control information is used to indicate the control information for the second message. All control information related to the second message can be placed in one IE (e.g., session management control information header). The first SM control information may also include at least one of the following:

[0311] IEI is used to identify the first SM control information;

[0312] The length field of the first SM control information is used to indicate the length of the first SM control information;

[0313] The content field of the first SM control information is used to carry the content of the first SM control information (the seventeenth and eighteenth information).

[0314] Please refer to Figure 3b, which is a schematic diagram of the 6G NAS protocol architecture. Layer 3 of the 6GS service includes: radio resource management function, mobility management function, and session management function. In this embodiment, the mobility management and session management protocols, as well as the protocol stack architecture for communication between the UE and service network elements, are defined. Other service NAS messages are transmitted via a 6G-AMF forwarding mechanism, meaning the next hop for 6G-AMF is the service network element. This enables the deployment of 6G networks and provides better compatibility with 5GS, reducing upgrade costs and complexity. Simultaneously, the user experience during the transition from 5G to 6G is smoother, reducing inconvenience caused by architectural changes.

[0315] Implementation method 2: The basic NAS message includes a mobility management message, a session management message, and a unified service management message (at this time, layer 3 has 3 sub-layers, that is, there are 3 first messages or fourteenth messages (e.g., EPD)).

[0316] Similar to Embodiment 1 above, the difference is that in Embodiment 2, the mobility management message can only carry one first container, and cannot be multiple first containers or multiple second containers. Please refer to Figures 3c and 3d. Figure 3c is the protocol stack for interaction between the UE, the first network element, and the second network element (service management network element). Figure 3d is a schematic diagram of the 6G NAS protocol architecture, where Layer 3 of 6GS includes: 6G radio resource management function, 6G mobility management function, and 6G connection management function. The connection management function includes 6G session management function and 6G service management function.

[0317] In this implementation, only service management messages need to be forwarded through the AMF. Service messages are forwarded through the service management network element (deployed closer to the UE), which improves forwarding efficiency.

[0318] In this embodiment, the design of the session management message is the same as that in embodiment 1 above, and will not be repeated here.

[0319] In this embodiment, the service management message can be a container carrying specific service messages (e.g., a container carrying computation messages, a container carrying awareness messages, etc.). It should be noted that here, "container" refers to the AMF not parsing the content within the container. The service management message carrying a container for computation messages can also be described as the service management message being able to transmit computation messages; that is, when the terminal wants to transmit computation messages, the terminal can set the computation container (IE) in the service management message as a computation message. In this case, the second message includes at least one of the following:

[0320] (1) Fourteenth information: Used to indicate the protocol type to which the second message belongs. In this case, the fourteenth information is used to indicate that the second message belongs to 6G service management messages. The implementation is the same as that mentioned in mobility management messages, but different values ​​are used to indicate 6GS service management messages:

[0321] (2) Sixteenth information: used to indicate the bearer information associated with the second message or to identify the connection between the terminal and the third device;

[0322] Here, a new ID can be used to identify the connection between the terminal and the third device, such as a service bearer identifier / service session identifier, or a task bearer identifier / task session identifier.

[0323] (3) Fifteenth message: used to indicate the message type of the second message; this can be a new message type, such as a service session establishment request message, a service session release request message, etc.

[0324] (4) Nineteenth information: used to indicate the type of the second message or the application mode of the second message; this can be a new message type, such as a service session message type (specifically including IPv4, IPv6, non-IP);

[0325] (5) Twentieth message: used to indicate the attributes of the bearer associated with the second message; specifically, the twentieth message is a temporary session, always on, service session, or task session.

[0326] (6) The 31st message is used to indicate that the container type carried by the second message is a specific service NAS container type;

[0327] For example, the implementation of the thirty-first information may be to use IEI to indicate a specific service NAS container type, which includes at least one of the following: computing service container IE, sensing service container IE, AIoT service container IE, NTN service container IE, etc.

[0328] (7) The eighteenth piece of information, which indicates that the routing information for the second message can be at least one of the following: network element identification information, network element address information, or information received from the service NAS layer;

[0329] (8) Third messages, such as NTN service message, AIoT service message, sensing service message, control signalling message, etc.

[0330] Implementation Method 3: Basic NAS messages include mobility management messages, session management messages, and multiple specific service messages / multiple specific category service messages (in this case, layer 3 has multiple sub-layers, i.e., more than 3 first messages or fourteenth messages (e.g., EPD)). Please refer to Figure 3e, which shows the protocol stack for interaction between the UE, the first network element, and the second network element (service network element). In this implementation method, specific service messages are still carried in 6G MM messages, realizing network deployment that supports multiple services in 6GS and ensuring normal interaction between terminals and network devices from different manufacturers. In an optional implementation, the specific service network element can be a specific category of service management network element. The specific category of service management network element receives the message from the first network element and then forwards it to the specific service network element.

[0331] In this embodiment, the design of the mobility management message is the same as in embodiment 1. The difference is that in this embodiment, the mobility management message needs to carry multiple specific service containers or multiple service containers of specific categories. If 6G also uses the payload container mechanism, multiple payload container types need to be added to indicate that the payload type carried is a specific service container or multiple service containers of specific categories. If the payload container mechanism is not used, a new IE is needed to carry the service container or multiple service containers of specific categories.

[0332] In this embodiment, the design of the session management message is the same as in embodiment 1, and will not be repeated here.

[0333] This implementation includes specific service messages. A first message can be used to identify each EPD with a specific service message or a specific category of service messages. The specific service messages are at the same level as 6G SM messages and need to be carried in mobility management messages, so MAC addresses are not required.

[0334] In this implementation, the second message includes at least one of the following:

[0335] (1) Fourteenth message: used to indicate the protocol type (e.g., EPD) to which the second message belongs, and its implementation includes at least one of the following:

[0336] The fourteenth piece of information is used to indicate that the message type of the second message belongs to a plurality of specific service messages, the specific service messages including at least one of the following: 6GS session management messages, 6G SMS messages, 6G UE policy messages, 6G LCS messages, computing messages, sensing messages, AI messages, data messages, multimedia messages, immersive messages, security messages, task messages, AIoT messages, energy-saving messages, and NTN messages;

[0337] The fourteenth piece of information is used to indicate multiple specific categories of service messages, which include at least one of the following:

[0338] Connection management messages / connection messages, computation management messages / computation messages, data management messages / data messages, algorithm management messages / algorithm messages, data transmission messages, signaling transmission messages, and policy transmission messages;

[0339] (2) Sixteenth information: used to indicate the bearer information or identification information associated with the second message;

[0340] The sixteenth piece of information includes at least one of the following: Short Message Bearer Identifier / Short Message Session Identifier, Policy Bearer Identifier / Policy Session Identifier, Location Bearer Identifier / Location Session Identifier, Computation Bearer Identifier / Computation Session Identifier, Sensing Bearer Identifier / Sensing Session Identifier, AI Bearer Identifier / AI Session Identifier, Data Bearer Identifier / Data Session Identifier, Multimedia Bearer Identifier / Multimedia Session Identifier, Immersive Bearer Identifier / Immersive Session Identifier, Security Bearer Identifier / Security Session Identifier, Task Bearer Identifier / Task Session Identifier, AIoT Bearer Identifier / AIoT Session Identifier, Energy Saving Bearer Identifier / Energy Saving Session Identifier, NTN Bearer Identifier / NTN Session Identifier; Connection Management Bearer Identifier / Connection Management Session Identifier, Computation Management Bearer Identifier / Computation Management Session Identifier, Data Management Bearer Identifier / Data Management Session Identifier, Algorithm Management Bearer Identifier / Algorithm Management Session Identifier, Signaling Management Bearer Identifier / Signaling Management Session Identifier; Policy Management Bearer Identifier / Policy Management Session Identifier;

[0341] (3) Fifteenth message: used to indicate the message type of the second message; this can be a new message type, such as a specific service session establishment request message, a specific service session release request message, etc.

[0342] (4) Nineteenth message: used to indicate the type of the first message or the application mode of the first message; this can be a new message type, such as a specific service session message type (specifically including IPv4, IPv6, non-IP);

[0343] (5) Eighteenth message: used to indicate the attributes of the first session (e.g., temporary, always on);

[0344] Optionally, the eighteenth information includes at least one of the following: temporary session, SMS session, policy session, LCS session, computing session, sensing session, AI session, data session, multimedia session, immersive session, security session, task session, AIoT session, energy-saving session, NTN session, connection management session, computing management session, data management session, algorithm management session, signaling management session, and policy management session.

[0345] When basic NAS includes multiple specific categories of service messages, the second message also includes at least one of the following:

[0346] (6) Thirty-second information, used to indicate that the container type carried by the second message is a specific service NAS type;

[0347] For example, using IEI to identify a specific service NAS container indicates at least one of the following types: computing service container IE, sensing service container IE, AIoT service container IE, NTN service container IE, etc.

[0348] (7) The eighteenth piece of information, which indicates that the routing information for the second message can be at least one of the following: network element identification information, network element address information, or information received from the service NAS layer;

[0349] (8) Third messages, such as NTN service message, AIoT service message, sensing service message, control signalling message.

[0350] Example 2:

[0351] In this embodiment, the third network element (e.g., the 6G MM network element) is responsible for forwarding the service NAS message. At this time, the first network element is split into the third network element and the fourth network element. The service NAS message still needs to be carried in the mobility management message.

[0352] Implementation method 1a: basic NAS includes mobility management and session management (in this case, layer 3 has 2 sub-layers, that is, 2 EPDs).

[0353] The difference from Embodiment 1 is that the functions of the mobility management sublayer are simplified. The main function of the mobility management sublayer is to support mobility and general message transmission.

[0354] Implementation method 1b: Basic NAS includes mobility management, access control management, and session management (in this case, layer 3 has 3 sub-layers, that is, 3 EPDs).

[0355] The difference between this implementation and the above-described implementation 1a is that an access control management sublayer is added, that is, a new EPD is added to identify the access control management sublayer.

[0356] Implementation 2a: Basic NAS includes mobility management, session management and a unified service management message (in this case, layer 3 has 3 sub-layers, i.e. 3 EPDs).

[0357] The difference from Embodiment 1 is that the functions of the mobility management sublayer are simplified. The main function of the mobility management sublayer is to support mobility and general message transmission.

[0358] Implementation method 2b: Basic NAS includes mobility management, access control management, session management and a unified service management message (in this case, layer 3 has 4 sub-layers, i.e. 4 EPDs).

[0359] The difference from implementation method 2a is that an access control management sublayer is added, that is, a new EPD is added to identify the access control management sublayer.

[0360] Implementation 3a: Basic NAS includes mobility management, session management, and multiple specific service messages / multiple specific categories of service messages (in this case, layer 3 has multiple sub-layers, i.e., more than 4 EPDs).

[0361] The difference from Embodiment 1 is that the functions of the mobility management sublayer are simplified. The main function of the mobility management sublayer is to support mobility and general message transmission.

[0362] Implementation 3b: Basic NAS includes mobility management, access control management, session management, and multiple specific service messages / multiple specific categories of service messages (in this case, layer 3 has multiple sub-layers, i.e., more than 4 EPDs).

[0363] The difference from implementation method 3a is that an access control management sublayer is added, that is, a new EPD is added to identify the access control management sublayer.

[0364] The design of the first and second messages in this embodiment is based on the above embodiment one, and will not be repeated here.

[0365] The information transmission method provided in this application enables NAS protocol-based designs to go beyond just connection-based designs. It also enables the transmission of service information, such as services that devices can support or want to use, based on NAS messages. Devices can transmit service information through NAS messages, eliminating the need to establish independent protocol stacks or signaling processes for different services, thus effectively improving information transmission efficiency.

[0366] The information transmission method provided in this application can be executed by an information transmission device. This application uses an information transmission device executing the information transmission method as an example to illustrate the information transmission device provided in this application.

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

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

[0369] Specifically, referring to Figure 4, which is a structural diagram of an information transmission device provided in an embodiment of this application, the device is applied to a first device, which can be a terminal or a network-side device. As shown in Figure 4, the information transmission device 400 includes:

[0370] Sending module 401 is used to send a first message to the second device;

[0371] The first message is a NAS message, which includes at least one container for carrying a second message. The second message includes information related to services supported by the terminal, and the terminal is either the first device or the second device.

[0372] Optionally, the first message includes at least one of the following:

[0373] First information, the first information is used to indicate the message type of the first message or to indicate the protocol type to which the first message belongs;

[0374] The second information is used to indicate the integrity information of the first message;

[0375] The third information is used to indicate the sequence information of the first message;

[0376] The fourth information is used to indicate the integrity status and / or encryption status of the first message;

[0377] The fifth information is used to indicate the encryption information of the first message;

[0378] The sixth information is used to indicate that the first message is used to transmit a target object, and the target object includes at least one of message, data, and signaling;

[0379] The seventh piece of information is used to identify the connection between the terminal and the third device;

[0380] The eighth information is used to indicate the transmission direction of the first message;

[0381] The ninth information is used to indicate that the first message carries at least one first container, and one of the first containers is used to carry a second message of one or more message types;

[0382] The tenth information is used to indicate the type of a specific category of service messages carried by the first container;

[0383] Eleventh information, the eleventh information is used to indicate that the first message carries at least one second container, and one second container is used to carry a second message of a message type;

[0384] The twelfth piece of information is used to indicate the identifier of the third device;

[0385] The thirteenth piece of information is used to indicate the service information that the terminal supports or wants to use;

[0386] The 26th information is used to indicate the message type of the first message;

[0387] The third device is a core network element that provides specific services to the terminal.

[0388] Optionally, the first information may be indicated by any of the following:

[0389] The encoding of the Extended Protocol Authentication Information element in IE;

[0390] Arbitrary encoding in IE (First Internet Explorer);

[0391] The first IE contains arbitrary encoding, and the encoding in the protocol authentication IE indicates that the first IE is an enhanced protocol authentication IE;

[0392] The first IE is different from the extended protocol identifier IE.

[0393] Optionally, the message type of the first message is a mobility management message.

[0394] Optionally, the protocol type to which the second message belongs includes at least one of the following:

[0395] Session Management Sublayer, Service Management Sublayer, Connection Management Sublayer, Computation Management Sublayer, Data Management Sublayer, Algorithm Management Sublayer, Signaling Management Sublayer, Policy Management Sublayer, Protocol Data Unit (PDU) Sublayer, Short Message Sublayer, Policy Sublayer, Location Sublayer, Computation Sublayer, Perception Sublayer, Artificial Intelligence (AI) Sublayer, Data Sublayer, Multimedia Sublayer, Immersive Sublayer, Security Sublayer, Task Sublayer, Environmental Internet of Things (AIoT) Sublayer, Energy Saving Sublayer, Non-Terrestrial Network (NTN) Sublayer, Slicing Sublayer, V2X Sublayer, Prose Sublayer; or,

[0396] The message type of the second message includes at least one of the following:

[0397] Session management messages, service management messages, connection management messages, compute management messages, data management messages, algorithm management messages, signaling management messages, policy management messages, PDU messages, short messages, policy messages, location messages, compute messages, perception messages, AI messages, data messages, multimedia messages, immersive messages, security messages, task messages, AIoT messages, energy-saving messages, NTN messages, slicing messages, V2X messages, and Prose messages.

[0398] Optionally, if the first message includes the thirteenth information or the terminal wants to use a specific service, the first message may include at least one of the ninth and eleventh information.

[0399] Optionally, if the first message includes the ninth information, the device includes a first processing module for performing at least one of the following:

[0400] The second message is carried by a payload container type IE, and the message type of the second message includes at least one of the following: connection management message, computing management message, data management message, algorithm management message, signaling management message, and policy management message;

[0401] The second message is carried by the first container IE, and the message type of the second message is a service management message.

[0402] The second message is carried by multiple first container IEs, and the message type of the second message includes at least one of the following: connection management message, computing management message, data management message, algorithm management message, signaling management message, and policy management message.

[0403] Optionally, if the first message includes the eleventh information, the device includes a second processing module for performing at least one of the following:

[0404] The second message is carried using a payload container;

[0405] The second message is carried using multiple second container IEs;

[0406] The message type of the second message includes at least one of the following: PDU message, short message, policy message, location message, computing message, perception message, AI message, data message, multimedia message, immersive message, security message, task message, AIoT message, energy-saving message, NTN message, slice message, V2X message, and Prose message.

[0407] Optionally, the second message includes at least one of the following:

[0408] The fourteenth piece of information is used to indicate the protocol type to which the second message belongs;

[0409] The fifteenth piece of information is used to indicate the message type of the second message;

[0410] The sixteenth piece of information is used to identify the connection between the terminal and the third device;

[0411] The seventeenth piece of information is used to indicate the transmission direction of the second message;

[0412] The eighteenth piece of information is used to indicate the process transaction identifier (PTI).

[0413] The nineteenth message, which is used to indicate the application mode of the second message;

[0414] The twentieth information is used to indicate the attributes of the first session, which is a bearer used by the terminal to communicate with a third device or a connection between the terminal and a third device that provides a specific service.

[0415] Optionally, if the terminal supports NTN or the terminal wants to use NTN services, the first message includes at least one of the following:

[0416] The first information is used to indicate that the message type of the first message is a mobility management message, a mobility management message with an optimized header, or a message for NTN services.

[0417] The second information and the third information;

[0418] The fourth information is used to indicate that the first message has a short header or that the first message is used for NTN service;

[0419] The fifth piece of information;

[0420] The twenty-sixth piece of information;

[0421] The 21st message is used to indicate whether the transmission of the second message has been completed.

[0422] The 22nd message is used to indicate the message type of the second message.

[0423] Optionally, if the terminal supports AIoT or the terminal wants to use AIoT services, the first message includes at least one of the following:

[0424] The first information is used to indicate that the message type of the first message is a mobility management message, a mobility management message with an optimized header, or a message for AIoT services.

[0425] The fourth information, when the first information is used to indicate that the message type of the first message is a mobility management message, is further used to indicate...

[0426] The first message is a mobility management message with an optimized header or a message for AIoT services;

[0427] The second message includes at least one of the following:

[0428] The 23rd message is used to indicate different message types, which include at least one of the following: inventory request message, inventory response message, read request message, read response message, write request message, and write response message;

[0429] Key identifier;

[0430] User face and control face identifiers;

[0431] The 24th information is used to indicate the AIoT session identifier;

[0432] The twenty-fifth message is used to indicate the encryption status of the second message.

[0433] In this embodiment, the first message transmitted by the device is a NAS message. The first message includes at least one container for carrying a second message. The second message includes information related to services supported by the terminal, and the terminal is either the first device or the second device. This allows the second message to be carried via NAS messages, and since the second message includes information related to services supported by the terminal, the design based on the NAS protocol is no longer solely based on connectivity. It can also transmit service-related information, such as services supported or desired by the terminal, based on NAS messages, thereby improving the flexibility and richness of NAS message information. Furthermore, in this embodiment, devices can transmit service-related information via NAS messages, eliminating the need to establish independent protocol stacks or signaling processes for different services, effectively improving information transmission efficiency.

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

[0435] As shown in Figure 5, this application embodiment also provides a communication device 500, including a processor 501 and a memory 502. The memory 502 stores a program or instructions that can run on the processor 501. When the program or instructions are executed by the processor 501, they implement the various steps of the above-described information transmission method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0436] 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 FIG2. 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 information transmission device shown in FIG4. Specifically, FIG6 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0437] The terminal 600 includes, but is not limited to, at least some of the following components: radio frequency unit 601, network module 602, audio output unit 603, input unit 604, sensor 605, display unit 606, user input unit 607, interface unit 608, memory 609, and processor 610.

[0438] Those skilled in the art will understand that terminal 600 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to processor 610 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 6 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.

[0439] It should be understood that, in this embodiment, the input unit 604 may include a graphics processor 6041 and a microphone 6042. The graphics processor 6041 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 606 may include a display panel 6061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 607 includes at least one of a touch panel 6071 and other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include two parts: a touch detection device and a touch controller. Other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

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

[0441] The memory 609 can be used to store software programs or instructions, as well as various data. The memory 609 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 609 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 609 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0442] Processor 610 may include one or more processing units; optionally, processor 610 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 610.

[0443] In one embodiment, terminal 600 is a first device, wherein radio frequency unit 601 is used to send a first message to a second device, wherein the first message is a non-access stratum (NAS) message, the first message includes at least one container, the at least one container is used to carry a second message, the second message includes information related to services supported by the terminal, and the terminal is either the first device or the second device.

[0444] In this embodiment, a terminal sends a first message to a second device. This first message is a NAS message, and it includes at least one container for carrying a second message. The second message includes information related to services supported by the terminal. The terminal is either the first device or the second device. This allows the second message to be carried via NAS messages, and since the second message includes information related to services supported by the terminal, the design based on the NAS protocol is no longer solely based on connectivity. It can also use NAS messages to transmit service-related information such as services that the terminal supports or wants to use, thereby improving the flexibility and richness of NAS messages. Furthermore, in this embodiment, devices can transmit service-related information via NAS messages, eliminating the need to establish independent protocol stacks or signaling processes for different services, effectively improving information transmission efficiency.

[0445] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description in the information transmission method of the method embodiment, and achieve the same or corresponding technical effect. In order to avoid repetition, it will not be described again here.

[0446] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG2. 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.

[0447] Specifically, this application also provides a network-side device. As shown in FIG7, the network-side device 700 includes a processor 701, a network interface 702, and a memory 703. The network-side device may be the information transmission device shown in FIG4. The network interface 702 is, for example, a Common Public Radio Interface (CPRI).

[0448] Specifically, the network-side device 700 in this application embodiment further includes: instructions or programs stored in memory 703 and executable on processor 701. Processor 701 calls the instructions or programs in memory 703 to execute the methods executed by each module shown in FIG4 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0449] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described information transmission method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

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

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

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

[0453] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described information transmission method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0454] This application also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the information transmission method described above, and the network-side device can be used to perform the steps of the information transmission method described above.

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

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

[0457] 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. An information transmission method, comprising: The first device sends a first message to the second device; The first message is a non-access stratum (NAS) message, which includes at least one container for carrying a second message. The second message includes information related to services supported by the terminal, and the terminal is either the first device or the second device.

2. The method according to claim 1, wherein, The first message includes at least one of the following: First information, which is used to indicate the protocol type to which the first message belongs; The second information is used to indicate the integrity information of the first message; The third information is used to indicate the sequence information of the first message; The fourth information is used to indicate the integrity status and / or encryption status of the first message; The fifth information is used to indicate the encryption information of the first message; The sixth information is used to indicate that the first message is used to transmit a target object, and the target object includes at least one of message, data, and signaling; The seventh piece of information is used to identify the connection between the terminal and the third device; The eighth information is used to indicate the transmission direction of the first message; The ninth information is used to indicate that the first message carries at least one first container, and one of the first containers is used to carry a second message of one or more message types; The tenth information is used to indicate the type of a specific category of service messages carried by the first container; Eleventh information, the eleventh information is used to indicate that the first message carries at least one second container, and one second container is used to carry a second message of a message type; The twelfth piece of information is used to indicate the identification information of the third device; The thirteenth piece of information is used to indicate the service information that the terminal supports or wants to use; The 26th information is used to indicate the message type of the first message; The third device is a core network element that provides specific services to the terminal.

3. The method according to claim 2, wherein, The first information is indicated by any of the following: The encoding of the Extended Protocol Authentication Information element in IE; Arbitrary encoding in IE (First Internet Explorer); The first IE contains arbitrary encoding, and the encoding in the protocol authentication IE indicates that the first IE is an enhanced protocol authentication IE; The first IE is different from the extended protocol identifier IE.

4. The method according to any one of claims 2-3, wherein, The message type of the first message is a mobility management message.

5. The method according to any one of claims 2-4, wherein, The protocol type to which the second message belongs includes at least one of the following: Session Management Sublayer, Service Management Sublayer, Connection Management Sublayer, Computation Management Sublayer, Data Management Sublayer, Algorithm Management Sublayer, Signaling Management Sublayer, Policy Management Sublayer, Protocol Data Unit (PDU) Sublayer, Short Message Sublayer, Policy Sublayer, Location Sublayer, Computation Sublayer, Perception Sublayer, Artificial Intelligence (AI) Sublayer, Data Sublayer, Multimedia Sublayer, Immersive Sublayer, Security Sublayer, Task Sublayer, Environmental Internet of Things (AIoT) Sublayer, Energy Saving Sublayer, Non-Terrestrial Network (NTN) Sublayer, Slicing Sublayer, Vehicle-to-Everything (V2X) Sublayer, Proximity Services (Prose) Sublayer; or, The message type of the second message includes at least one of the following: Session management messages, service management messages, connection management messages, compute management messages, data management messages, algorithm management messages, signaling management messages, policy management messages, PDU messages, short messages, policy messages, location messages, compute messages, perception messages, AI messages, data messages, multimedia messages, immersive messages, security messages, task messages, AIoT messages, energy-saving messages, NTN messages, slicing messages, V2X messages, and Prose messages.

6. The method according to any one of claims 2-5, wherein, If the first message includes the thirteenth information or the terminal wants to use a specific service, the first message includes at least one of the ninth and eleventh information.

7. The method according to any one of claims 2-6, wherein, If the first message includes the ninth information, the first device performs at least one of the following: The second message is carried using a payload container type IE, and the protocol type to which the second message belongs includes at least one of the following: connection management message, computation management message, data management message, algorithm management message, signaling management message, and policy management message; The second message is carried by the first container IE, and the message type of the second message is a service management message. The second message is carried by multiple first container IEs, and the message type of the second message includes at least one of the following: connection management message, computing management message, data management message, algorithm management message, signaling management message, and policy management message.

8. The method according to any one of claims 2-7, wherein, If the first message includes the eleventh information, the first device performs at least one of the following: The second message is carried using a payload container; The second message is carried using multiple second container IEs; The message type of the second message includes at least one of the following: PDU message, short message, policy message, location message, computing message, perception message, AI message, data message, multimedia message, immersive message, security message, task message, AIoT message, energy-saving message, NTN message, slice message, V2X message, and Prose message.

9. The method according to any one of claims 2-8, wherein, The second message includes at least one of the following: The fourteenth piece of information is used to indicate the protocol type to which the second message belongs; The fifteenth piece of information is used to indicate the message type of the second message; The sixteenth piece of information is used to identify the connection between the terminal and the third device; The seventeenth piece of information is used to indicate the transmission direction of the second message; The eighteenth piece of information is used to indicate the process transaction identifier (PTI). The nineteenth message, which is used to indicate the application mode of the second message; The twentieth information is used to indicate the attributes of the first session, which is a bearer used by the terminal to communicate with a third device or a connection between the terminal and a third device that provides a specific service.

10. The method according to any one of claims 2-9, wherein, If the terminal supports NTN or the terminal wants to use NTN services, the first message includes at least one of the following: The first information is used to indicate that the protocol type to which the first message belongs is a mobility management message, a mobility management message with an optimized header, or a message for NTN services. The second information and the third information; The fourth information is further used to indicate that the first message has a short header or that the first message is used for NTN service; The fifth piece of information; The 26th message; The 21st message is used to indicate whether the first message has been successfully transmitted. The 22nd message is used to indicate the message type of the second message.

11. The method according to any one of claims 2-10, wherein, If the terminal supports AIoT or the terminal wants to use AIoT services, the first message includes at least one of the following: The first information is used to indicate that the protocol type to which the first message belongs is a mobility management message, a mobility management message with an optimized header, or a message for AIoT services. The fourth information, in the case where the first information is used to indicate that the protocol type to which the first message belongs is a mobility management message, is also used to indicate that the first message is a mobility management message with an optimized header or a message for AIoT services. The second message includes at least one of the following: The 23rd message is used to indicate different message types, which include at least one of the following: inventory request message, inventory response message, read request message, read response message, write request message, and write response message; Key identifier; User face and control face identifiers; The 24th information is used to indicate the AIoT session identifier; The twenty-fifth message is used to indicate the encryption status of the second message.

12. An information transmission device applied to a first device, the device comprising: The sending module is used to send the first message to the second device; The first message is a NAS message, which includes at least one container for carrying a second message. The second message includes information related to services supported by the terminal, and the terminal is either the first device or the second device.

13. The apparatus according to claim 12, wherein, The first message includes at least one of the following: First information, which is used to indicate the protocol type to which the first message belongs; The second information is used to indicate the integrity information of the first message; The third information is used to indicate the sequence information of the first message; The fourth information is used to indicate the integrity status and / or encryption status of the first message; The fifth information is used to indicate the encryption information of the first message; The sixth information is used to indicate that the first message is used to transmit a target object, and the target object includes at least one of message, data, and signaling; The seventh piece of information is used to identify the connection between the terminal and the third device; The eighth information is used to indicate the transmission direction of the first message; The ninth information is used to indicate that the first message carries at least one first container, and one of the first containers is used to carry a second message of one or more message types; The tenth information is used to indicate the type of a specific category of service messages carried by the first container; Eleventh information, the eleventh information is used to indicate that the first message carries at least one second container, and one second container is used to carry a second message of a message type; The twelfth piece of information is used to indicate the identifier of the third device; The thirteenth piece of information is used to indicate the service information that the terminal supports or wants to use; The 26th information is used to indicate the message type of the first message; The third device is a core network element that provides specific services to the terminal.

14. The apparatus according to claim 13, wherein, The first information is indicated by any of the following: The encoding of the Extended Protocol Authentication Information element in IE; Arbitrary encoding in IE (First Internet Explorer); The first IE contains arbitrary encoding, and the encoding in the protocol authentication IE indicates that the first IE is an enhanced protocol authentication IE; The first IE is different from the extended protocol identifier IE.

15. The apparatus according to any one of claims 13-14, wherein, The message type of the first message is a mobility management message.

16. The apparatus according to any one of claims 13-15, wherein, The protocol type to which the second message belongs includes at least one of the following: Session Management Sublayer, Service Management Sublayer, Connection Management Sublayer, Computation Management Sublayer, Data Management Sublayer, Algorithm Management Sublayer, Signaling Management Sublayer, Policy Management Sublayer, Protocol Data Unit (PDU) Sublayer, Short Message Sublayer, Policy Sublayer, Location Sublayer, Computation Sublayer, Perception Sublayer, Artificial Intelligence (AI) Sublayer, Data Sublayer, Multimedia Sublayer, Immersive Sublayer, Security Sublayer, Task Sublayer, Environmental Internet of Things (AIoT) Sublayer, Energy Saving Sublayer, Non-Terrestrial Network (NTN) Sublayer, Slicing Sublayer, V2X Sublayer, Prose Sublayer; or, The message type of the second message includes at least one of the following: Session management messages, service management messages, connection management messages, compute management messages, data management messages, algorithm management messages, signaling management messages, policy management messages, PDU messages, short messages, policy messages, location messages, compute messages, perception messages, AI messages, data messages, multimedia messages, immersive messages, security messages, task messages, AIoT messages, energy-saving messages, NTN messages, slicing messages, V2X messages, and Prose messages.

17. The apparatus according to any one of claims 13-16, wherein, If the first message includes the thirteenth information or the terminal wants to use a specific service, the first message includes at least one of the ninth and eleventh information.

18. The apparatus according to any one of claims 13-17, wherein, If the first message includes the ninth information, the device includes a first processing module for performing at least one of the following: The second message is carried using a payload container type IE, and the message type of the second message includes at least one of the following: connection management message, computation management message, data management message, algorithm management message, signaling management message, and policy management message; The second message is carried by the first container IE, and the message type of the second message is a service management message. The second message is carried by multiple first container IEs, and the message type of the second message includes at least one of the following: connection management message, computing management message, data management message, algorithm management message, signaling management message, and policy management message.

19. The apparatus according to any one of claims 13-18, wherein, If the first message includes the eleventh information, the device includes a second processing module for performing at least one of the following: The second message is carried using a payload container; The second message is carried using multiple second container IEs; The message type of the second message includes at least one of the following: PDU message, short message, policy message, location message, computing message, perception message, AI message, data message, multimedia message, immersive message, security message, task message, AIoT message, energy-saving message, NTN message, slice message, V2X message, and Prose message.

20. The apparatus according to any one of claims 13-19, wherein, The second message includes at least one of the following: The fourteenth piece of information is used to indicate the protocol type to which the second message belongs; The fifteenth piece of information is used to indicate the message type of the second message; The sixteenth piece of information is used to identify the connection between the terminal and the third device; The seventeenth piece of information is used to indicate the transmission direction of the second message; The eighteenth piece of information is used to indicate the process transaction identifier (PTI). The nineteenth message, which is used to indicate the application mode of the second message; The twentieth information is used to indicate the attributes of the first session, which is a bearer used by the terminal to communicate with a third device or a connection between the terminal and a third device that provides a specific service.

21. The apparatus according to any one of claims 13-20, wherein, If the terminal supports NTN or the terminal wants to use NTN services, the first message includes at least one of the following: The first information is used to indicate that the message type of the first message is a mobility management message, a mobility management message with an optimized header, or a message for NTN services. The second information and the third information; The fourth information is used to indicate that the first message has a short header or that the first message is used for NTN service; The fifth piece of information; The 26th message; The 21st message is used to indicate whether the transmission of the second message has been completed. The 22nd message is used to indicate the message type of the second message.

22. The apparatus according to any one of claims 13-21, wherein, If the terminal supports AIoT or the terminal wants to use AIoT services, the first message includes at least one of the following: The first information is used to indicate that the message type of the first message is a mobility management message, a mobility management message with an optimized header, or a message for AIoT services. The fourth information, when the first information is used to indicate that the message type of the first message is a mobility management message, is further used to indicate... The first message is a mobility management message with an optimized header or a message for AIoT services; The second message includes at least one of the following: The 23rd message is used to indicate different message types, which include at least one of the following: inventory request message, inventory response message, read request message, read response message, write request message, and write response message; Key identifier; User face and control face identifiers; The 24th information is used to indicate the AIoT session identifier; The twenty-fifth message is used to indicate the encryption status of the second message.

23. 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 information transmission method as described in any one of claims 1-11.

24. 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 information transmission method as described in any one of claims 1-11.

25. A readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the information transmission method as described in any one of claims 1-11.

26. A computer program product stored in a storage medium, the computer program product being executed by at least one processor to implement the steps of the information transmission method as claimed in any one of claims 1-11.

Images