Wireless communication method and communication device

Abstract

Provided are a wireless communication method and a communication device. The wireless communication method comprises: a first communication device sending a first message to a second communication device, wherein the first message includes one or more pieces of the following information: first information, which is used for controlling resources of a non-PDU session, and second information, which is used for indicating the cause for establishment of a wireless connection corresponding to the first information.

Description

Wireless communication method and communication device Technical Field

[0001] The present application relates to the field of communication technology, and more particularly, to a wireless communication method and communication device. Background Art

[0002] For some terminal devices (e.g., ambient IoT devices, zero-power terminals, etc.), the amount of data transmitted by these terminal devices is generally small due to cost and power consumption constraints. Transmitting data by establishing a protocol data unit (PDU) session may not be efficient. Therefore, for such devices, it is possible to consider using a non-PDU session to transmit data. When using a non-PDU session to transmit data, how to achieve differentiated control of data transmission is a problem that needs to be solved.

[0003] Summary of the Invention

[0004] The present application provides a wireless communication method and a communication device. The following introduces various aspects of the present application.

[0005] In a first aspect, a method for wireless communication is provided, comprising: a first communication device sends a first message to a second communication device, wherein the first message includes one or more of the following information: first information for controlling resources of a non-PDU session; and second information for indicating a reason for establishing a wireless connection corresponding to the first information.

[0006] According to a second aspect, a method for wireless communication is provided, comprising: a second communication device receives a first message sent by a first communication device, wherein the first message includes one or more of the following information: first information for controlling resources of a non-PDU session; and second information for indicating a reason for establishing a wireless connection corresponding to the first information.

[0007] According to a third aspect, a communication device is provided, which is a first communication device, and includes: a sending module for sending a first message to a second communication device, wherein the first message includes one or more of the following information: first information for controlling resources of a non-PDU session; and second information for indicating a reason for establishing a wireless connection corresponding to the first information.

[0008] In a fourth aspect, a communication device is provided, which is a second communication device, and the communication device includes: a receiving module for receiving a first message sent by a first communication device, wherein the first message includes one or more of the following information: first information for controlling resources of a non-PDU session; and second information for indicating a reason for establishing a wireless connection corresponding to the first information.

[0009] In a fifth aspect, a communication device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the communication device executes part or all of the steps in the methods of the above aspects.

[0010] In a sixth aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned communication device. In another possible design, the system may also include other devices that interact with the communication device in the solution provided in the embodiment of the present application.

[0011] In the seventh aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables a communication device (for example, a first communication device or a second communication device) to perform some or all of the steps in the methods of the above aspects.

[0012] In an eighth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a communication device (e.g., a first communication device or a second communication device) to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0013] In a ninth aspect, an embodiment of the present application provides a computer program, which is operable to enable a communication device (for example, a first communication device or a second communication device) to perform some or all of the steps in the methods of the above aspects.

[0014] In the tenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0015] When data is transmitted using a non-PDU session, an embodiment of the present application can perform differentiated control on data transmission based on the first information and / or the second information, wherein the first information and the second information are both associated with the resource control of the non-PDU session. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG1 is a diagram illustrating an example of a system architecture of a wireless communication system to which an embodiment of the present application may be applied.

[0017] Figure 2 is an example diagram of the AIoT network architecture.

[0018] FIG3 is a flow chart of a wireless communication method provided in an embodiment of the present application.

[0019] FIG4 is a schematic flow chart of a wireless communication method provided in another embodiment of the present application.

[0020] FIG5 is a flowchart of a wireless communication method provided in yet another embodiment of the present application.

[0021] FIG6 is a flowchart of a wireless communication method provided in yet another embodiment of the present application.

[0022] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0023] FIG8 is a schematic structural diagram of a communication device provided in another embodiment of the present application.

[0024] FIG9 is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0025] Communication system architecture

[0026] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, advanced long term evolution (LTE-A) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, new radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, non-terrestrial networks (NTN) system, terrestrial networks (TN) system, universal mobile telecommunication system (UMTS) system. system (UMTS), wireless local area networks (WLAN), wireless fidelity (WIFI), fifth-generation (5G) systems, etc. The technical solutions provided in this application can also be applied to other communication systems, such as future communication systems, such as the sixth-generation mobile communication system, and satellite communication systems.

[0027] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, and the embodiments of the present application can also be applied to these communication systems.

[0028] The communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0029] The communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as a dedicated spectrum.

[0030] FIG1 exemplarily illustrates a system architecture diagram of a wireless communication system to which embodiments of the present application may be applied. Taking the 5G system architecture as an example, the wireless communication system may include multiple network elements, such as terminal equipment, access network (AN) equipment, UPF network element, access and mobility management function (AMF) network element, session management function (SMF) network element, policy control function (PCF) network element, and application function (AF) network element. The wireless communication system may also include a DN, etc.

[0031] The following is an illustrative description of the functions of each part or network element involved in the wireless communication system in the 5G network.

[0032] Terminal device: A terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user apparatus. In the embodiments of the present application, a terminal device may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects, and machines, such as a handheld device or vehicle-mounted device with wireless connectivity. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a vehicle equipment, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc.

[0033] Access network equipment: Access network equipment provides network access for authorized terminal devices in a specific area and can utilize transmission channels of varying quality based on the terminal device's level and service requirements. Access network equipment manages wireless resources, provides access services to terminal devices, and forwards control signals and data between terminal devices and the core network.

[0034] An access network device may be a device in a wireless network. An access network device may also be referred to as a radio access network (RAN) device or a network device. For example, an access network device may be a base station. The access network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. A base station can also refer to a communication module, modem, or chip used to be provided in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs base station functions in device-to-device D2D, vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. The base station can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the access network device.

[0035] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0036] In some deployments, the access network device in the embodiments of the present application may refer to a CU or a DU, or the access network device may include a CU and a DU. The gNB may also include an AAU.

[0037] The access network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the access network equipment and terminal equipment are located.

[0038] UPF network element: UPF is the user plane function in the core network, which can be responsible for forwarding and receiving user data (such as business data flow) in the terminal device. UPF can be connected to the access network equipment (such as base station) and the external data network for data transmission. For example, UPF can receive user data from DN and transmit it to the terminal device through the access network equipment; or, UPF can also receive user data from the terminal device through the access network equipment and then forward it to DN. The transmission resources and scheduling functions in UPF that provide services to terminal devices are managed and controlled by SMF. In some embodiments, UPF can be divided into intermediate-UPF (I-UPF) and anchor UPF (A-UPF). Among them, I-UPF is connected to the access network, A-UPF is the UPF of the session anchor, and A-UPF can also be called PDU session anchor (PSA).

[0039] AMF network element: AMF is the mobility management function in the core network. It can be used to implement other functions of the mobility management entity (MME) in addition to session management, such as lawful interception or access authorization (or authentication). In some embodiments, in addition to performing mobility management for terminal devices, the AMF can also be responsible for forwarding session management related messages between terminal devices and SMF.

[0040] SMF network element: SMF is the session management function in the core network. It is mainly responsible for session management, Internet protocol (IP) address allocation and management of terminal devices, selection of endpoints for manageable user plane functions, policy control, or charging function interfaces, downlink data notification, and configuration of routing information for user plane functions.

[0041] PCF network element: PCF is the policy management function in the core network, which is responsible for formulating policies related to mobility management, session management, billing, etc. for terminal devices. Specifically, PCF can provide policy rule information to functional network elements of the control plane (such as AMF and SMF network elements) to manage and control mobility management and session management of terminal devices.

[0042] AF network element: The AF primarily supports interaction with the 3rd Generation Partnership Project (3GPP) core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network. Alternatively, the AF can be primarily used to communicate application-side requirements to the network. In some embodiments, the AF can be an application within the operator, such as the IP Multimedia Subsystem (IMS) technology. In some embodiments, the AF can be understood as a third-party server, such as an application server on the Internet, providing relevant service information, including providing service-related quality of service (QoS) requirement information to the PCF and sending service user plane data information to the A-UPF. In some embodiments, the AF can also be a service provider (content provider, CP). In some embodiments, if the AF is within the operator and is within the same trusted domain as other network functions (NFs), it can directly interact and access other NFs. If the AF is not within the trusted domain, it needs to access other NFs through other network elements (e.g., the NEF network element described below).

[0043] DN: A DN is a network used to transmit data. It can be a private network, such as a local area network (LAN), an external network not controlled by a carrier, such as the internet, or a proprietary network deployed jointly with carriers, such as the network that provides IMS services.

[0044] It should be understood that the above network elements in the core network can also be referred to as functional entities, and this application does not limit this. For example, the UPF network element can also be referred to as the UPF entity, and the AMF network element can also be referred to as the AMF entity, etc. It should also be understood that in some embodiments, the xx network element or the xx functional entity can also be directly referred to as xx, for example, the UPF network element (or UPF entity) can be referred to as UPF, and the AMF network element (or AMF entity) can be referred to as AMF. For the sake of convenience of description, the xx (such as UPF, AMF, etc.) mentioned in the embodiments of this application can refer to the xx network element or the xx entity, which will not be repeated later.

[0045] Optionally, the wireless communication system may also include a unified data management (UDM) network element, an authentication and authorization service function (AUSF) network element, a network slice selection function (NSSF) network element, a network exposure function (NEF) network element, a network data analysis function (NWDAF) and other network elements, but the embodiments of the present application are not limited to this.

[0046] The UDM network element is a subscription database in the core network, which can be used to generate and store subscription data of users in the network (for example, 5G network), management of authentication data and other functions. The UDM network element can support interaction with external third-party servers. The AUSF network element can be used to receive AMF's request for terminal device identity authentication, request a key from the UDM, and then forward the issued key to the AMF for authentication processing. The NSSF network element can be used for network slice selection. The NEF network element can be responsible for managing the network data opened to the outside world by 5G network elements. External non-trusted applications need to access the core network's internal data through the NEF to ensure the security of the 3GPP network. In some embodiments, the NEF network element can also provide external application QoS capability opening, event subscription, AF request distribution and other functions. The NWDAF network element can collect data from various network elements, network management systems, etc. in the core network for big data statistics, analysis or intelligent data analysis, so as to obtain analysis results on the network side or prediction data on the network side, thereby assisting each network element to more effectively control the terminal device based on the data analysis results.

[0047] In the wireless communication system shown in Figure 1, various components or network elements can communicate with each other through interfaces. For example, a terminal device can establish an access layer connection with the AN through the Uu interface, exchanging access layer messages and wireless data transmission; a terminal device can establish a non-access stratum (NAS) connection with the AMF through the N1 interface, exchanging NAS messages; the AN can connect to the AMF through the N2 interface to transmit radio bearer control information from the core network to the AN; the UPF can transmit data with the AN through the N3 interface and with the DN through the N6 interface. The interfaces connecting other components or network elements are shown in Figure 1 and are not described here in detail.

[0048] It should be understood that the network elements such as the terminal device, access network device, SMF, and PCF shown in Figure 1 are merely names and do not limit the devices themselves. In 5G networks and other future networks, the network elements corresponding to the terminal device, access network device, SMF, and PCF may also have other names, and this embodiment of the application does not specifically limit this.

[0049] It should be understood that the above-mentioned communication system is illustrated using the 5G system as an example. Of course, the present application can also be applied to other 3GPP communication systems, such as the 4G communication system, or future 3GPP communication systems, and the embodiments of the present application are not limited to this.

[0050] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0051] It should be understood that the system architecture described in the embodiments of the present application is intended to more clearly illustrate the technical solutions of the embodiments of the present application, and does not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art will know that with the evolution of network architecture, the embodiments of the present application may also be applicable to similar technical problems.

[0052] With the development of wireless communication technology, people hope to integrate wireless communication systems with various vertical industries such as logistics, manufacturing, transportation, and energy. For example, wireless communication systems can be integrated with industrial wireless sensor networks (IWSN). For another example, wireless communication systems can be integrated with smart logistics and smart warehousing. For another example, wireless communication systems can be integrated with smart home networks. However, in these industries, terminal devices usually need to have low cost, small size (such as ultra-thin), maintenance-free, long life and other characteristics. Therefore, in order to meet the above conditions, some low-power devices, zero-power devices or ambient internet of things (AIoT) devices are introduced into wireless communication systems. For example, the terminal device shown in Figure 1 can be an AIoT device or a zero-power device.

[0053] In some embodiments, AIoT devices can also be understood as zero-power devices. For example, based on the power supply method, zero-power devices can include AIoT devices, battery-free terminals, maintenance-free terminals, and so on. For ease of understanding, the following describes AIoT devices.

[0054] AIoT devices

[0055] In some embodiments, AIoT devices may also be referred to as AIoT terminals, ambient power-enabled IoT devices, environmental collection IoT devices, etc.

[0056] AIoT devices can work in an AIoT network. The AIoT network can be understood as a wireless communication network (wireless communication technology) suitable for short distances and low rates. Figure 2 shows an example of an AIoT network. As shown in Figure 2, the AIoT network may include a first device 210 and a second device 220. In some embodiments, the second device 220 may be an AIoT device. In some embodiments, the first device 210 may be a network device (such as an access network device).

[0057] In some implementations, the AIoT device may be an electronic tag, and accordingly, the network device may be a reader / writer of a (radio frequency identification, RFID) system, which is used to read the content in the electronic tag and / or to change the content in the electronic tag.

[0058] The first device 210 can send a wireless power supply signal to the second device 220 to power the second device 220. Correspondingly, the second device 220 can send data to the first device 210 via a backscattered signal. In some embodiments, the wireless power supply signal can also carry data or control information sent by the first device 210 to the second device 220. Of course, the wireless power supply signal can also be used only for power supply, which is not limited in this embodiment of the present application.

[0059] It should be noted that FIG2 exemplarily shows a first device 210 and a second device 220. Optionally, the AIoT network may further include other numbers of first devices and / or second devices, which is not limited in this embodiment of the present application.

[0060] The embodiments of this application do not limit the application scenarios of the AIoT network. For example, the AIoT network can be used in scenarios such as wireless industrial sensing networks, smart agriculture, smart warehousing and logistics, and smart homes.

[0061] A major advantage of AIoT devices is that they do not need to carry a power supply. As an implementation method, AIoT devices can combine radio frequency energy harvesting technology, backscattering technology, and low-power computing technology to achieve the advantage of device nodes not carrying a power supply. Based on this, AIoT devices can generally include an energy harvesting module, a backscattering communication module, and a low-power computing module. Continuing with Figure 2, the second device 220 may include an energy harvesting module 222 and a backscattering communication module 224. In some embodiments, the second device 220 may also include a low-power computing module 226. These modules included in the second device are introduced below.

[0062] The energy harvesting module 222 is used to harvest energy. In some implementations, the energy harvesting module 222 can harvest energy via a wireless power supply signal sent by the first device 210. The wireless power supply signal can be a "radio frequency signal" sent by a network device. Therefore, the energy harvesting module 222 can also be referred to as a "radio frequency energy harvesting module."

[0063] The core of the energy collection module 222 in collecting RF energy is to convert RF energy into DC. The energy can be stored in batteries or capacitors, or it can be directly used to drive logic circuits, digital chips or sensor devices after collection, so as to subsequently complete the modulation and transmission of backscattered signals, the collection and processing of sensor information and other functions and applications.

[0064] The backscatter communication module 224 can be used for the second device 220 to perform backscatter communication with the first device 210. As an implementation, after receiving the wireless signal sent by the first device 210, the second device 220 can modulate the wireless signal through the backscatter communication module 224 and send the modulated signal.

[0065] The low-power computing module 226 may be configured to provide computing functions, such as data processing, for the second device 220 .

[0066] With the development of communication systems, some communication systems (such as 5G systems) can support AIoT devices to access the network. For example, communication systems can support AIoT devices to access the network in the following scenarios: extreme environments that are not suitable for ordinary terminal devices; scenarios where low-power and low-cost terminal devices are used; and scenarios where battery-free terminal devices are used.

[0067] In AIoT communication technology, AIoT terminals can be divided into three categories based on the energy source and energy usage of AIoT devices: passive AIoT terminals, semi-passive AIoT terminals and active AIoT terminals.

[0068] 1. Passive AIoT Terminal

[0069] Passive AIoT terminals typically do not require internal batteries. When a passive IoT terminal approaches a network device, it is within the near-field radiation generated by the network device's antenna. At this point, the passive AIoT terminal's antenna can generate an induced current through electromagnetic induction. This induced current can power the passive AIoT terminal, driving its low-power chip circuits to demodulate forward link signals and modulate backward link signals. For backscatter links, passive AIoT terminals can use backscattering to transmit signals.

[0070] Based on the above introduction, it can be seen that the passive AIoT terminal does not require a built-in battery to drive either the forward link transmission process or the reverse link transmission process, and is a true AIoT terminal.

[0071] Passive AIoT terminals don't require batteries, so their RF and baseband circuits are very simple. For example, passive AIoT terminal devices don't require components like low-noise amplifiers (LNAs), power amplifiers (PAs), and analog-to-digital converters (ADCs). This makes passive AIoT terminals small, lightweight, inexpensive, and long-lasting.

[0072] In some implementations, passive AIoT terminals may feature one or more of the following: no battery, obtaining energy from the surrounding environment (e.g., radio waves, solar energy, wind energy, mechanical kinetic energy, etc.), no universal subscriber identify module (USIM) card, and storing energy from the surrounding environment. It should be noted that when passive AIoT terminals store energy from the surrounding environment, the amount of energy they can store is very small. Therefore, passive AIoT terminals support significantly fewer functional logic than mobile phone terminals.

[0073] 2. Semi-passive AIoT terminals

[0074] The semi-passive AIoT terminal itself does not have a conventional battery installed, but can use an energy harvesting module (for example, an RF energy harvesting module) to harvest radio wave energy and store the harvested energy in an energy storage unit (such as a capacitor). After the energy storage unit obtains energy, it can power the semi-passive AIoT terminal to drive the low-power chip circuit of the semi-passive AIoT terminal to achieve forward link signal demodulation and backward link signal modulation. For the backscatter link, the semi-passive AIoT terminal uses a backscatter implementation method to transmit the signal.

[0075] Based on the above introduction, it can be seen that the semi-passive AIoT terminal does not require a built-in battery to drive either the forward link transmission process or the reverse link transmission process. Although the energy stored in the capacitor is used in work, the energy comes from the radio energy collected by the energy harvesting module. Therefore, it is also a true AIoT terminal.

[0076] Semi-passive AIoT terminals inherit many advantages of passive AIoT terminals, or in other words, semi-passive AIoT terminals also have many advantages such as small size, light weight, low price and long service life.

[0077] 3. Active AIoT Terminal

[0078] Active AIoT terminals can have built-in batteries. These batteries power the terminals' low-power chip circuits, enabling forward link signal demodulation and reverse link signal modulation. However, for backscatter links, active AIoT terminals use backscattering to transmit signals. Therefore, the zero power consumption of active AIoT terminals is primarily due to the fact that reverse link signal transmission does not consume the terminal's own power, but rather utilizes backscattering.

[0079] Active AIoT terminals can be powered by built-in batteries, which can increase their communication distance and improve communication reliability. Therefore, active AIoT terminals are used in scenarios with relatively high requirements for communication distance and reading latency.

[0080] In some implementations, the active AIoT terminal may be an electronic tag, and the network device may be an RFID reader / writer. In this case, the built-in battery may power the RFID chip in the electronic tag to increase the read / write distance between the RFID reader / writer and the electronic tag. On the other hand, the built-in battery may power the RFID chip in the electronic tag to shorten the read / write delay of the RFID reader / writer to the electronic tag, which is beneficial to improving the reliability of communication. However, the embodiments of the present application are not limited to this. For example, the active AIoT terminal may also be an ordinary terminal device.

[0081] In some communication systems (such as 5G systems), the registration process of terminal devices is managed on a per-terminal device basis. For example, the registration process may allocate a temporary identifier to each terminal device and maintain the connection status or mobility management status of each terminal device.

[0082] In some implementations, the terminal device registration process can be based on NAS messages. For example, the state transition between the terminal device's mobility management states is based on NAS messages. Data transmission between the terminal device and the data network is generally carried out through a PDU session established on the user plane. As such, the terminal device needs to establish a PDU session in order to send or receive data. For example, even if the terminal device only sends or receives a small amount of data, a PDU session needs to be established.

[0083] As can be seen from the above description, a communication system (such as a 5G system) can provide data transmission services between terminal devices and data networks through PDU sessions. Some communication systems can also provide differentiated quality of service (QoS) guarantees for different service data flows transmitted in the same PDU session based on different business requirements. As an implementation method, nodes in the communication system can implement resource control or resource scheduling for PDU sessions based on QoS parameters. For example, terminal devices, access network devices, and UPFs can all implement resource control or resource scheduling for PDU sessions based on QoS parameters.

[0084] The embodiments of the present application do not limit the QoS parameters. Exemplarily, the QoS parameters may include one or more of the following parameters: 5G QoS identifier (5QI), allocation and retention priority (ARP), rate control parameters, etc.

[0085] However, for some terminal devices, such as the AIoT devices mentioned above, the amount of data transmitted by these terminal devices is generally small due to cost and power consumption constraints, and transmitting data by establishing a PDU session is not efficient. For example, in an AIoT network, in order to minimize power consumption during communication, the length of data reported by AIoT devices is generally relatively small. In this case, transmitting data by establishing a PDU session is not efficient for AIoT devices.

[0086] As a possible solution to address the above issues, non-PDU session transmission can be considered. However, when using non-PDU session transmission, existing QoS control mechanisms cannot be used to achieve differentiated control of data transmission. Therefore, how to achieve differentiated control of data transmission when using non-PDU session transmission becomes a problem that needs to be solved.

[0087] Based on this, embodiments of the present application provide a wireless communication method and communication device to implement differentiated control of data transmission in non-PDU session scenarios. For example, a core network, access network device, or terminal device can control data transmission in non-PDU session scenarios as needed, implementing differentiated control for non-PDU sessions.

[0088] The embodiments of the present application can be applied to any scenario in which data is transmitted in a non-PDU session manner. It should be understood that the "non-PDU session" mentioned in the embodiments of the present application may refer to other methods of transmitting data other than transmitting data by establishing a PDU session. In other words, transmitting data in a "non-PDU session" manner may refer to transmitting data without establishing a PDU session. The embodiments of the present application do not specifically limit the implementation method of transmitting data in a non-PDU session manner. For example, as an implementation method, transmitting data in a non-PDU session manner may refer to transmitting data between communication devices through NAS messages or NAS signaling, or transmitting data in a non-PDU session manner may refer to transmitting data between communication devices through a control plane. As another implementation method, transmitting data in a non-PDU session manner may refer to transmitting data between communication devices by transmitting short messages. Wherein, when transmitting short messages, an end-to-end service path may not be established (that is, no PDU session is established).

[0089] In some embodiments, the embodiments of the present application can be applied to scenarios where a core network (such as a network element in the core network) performs differentiated control on non-PDU sessions.

[0090] In some embodiments, the embodiments of the present application can be applied to scenarios where terminal devices perform differentiated control on non-PDU sessions.

[0091] In some embodiments, the embodiments of the present application can be applied to scenarios where access network equipment performs differentiated control on non-PDU sessions.

[0092] The following describes an embodiment of the method of the present application in conjunction with the accompanying drawings. Figure 3 is a flow chart of a wireless communication method provided by an embodiment of the present application. The method shown in Figure 3 is described from the perspective of the interaction between a first communication device and a second communication device. For ease of understanding, the following first describes the first and second communication devices of the embodiment of the present application.

[0093] In the embodiments of the present application, the first communication device and the second communication device are respectively the transceiver and receiver of the first message. The first communication device is the sender or initiator of the first message, and the second communication device is the receiver of the first message. A detailed description of the first message can be found below and will not be detailed here for the sake of brevity.

[0094] The embodiment of the present application does not impose any specific limitation on the first communication device, as long as it can send the first message. The following examples introduce several possible implementation forms of the first communication device.

[0095] In some embodiments, the first communication device may be a network element in a core network. That is, the first communication device may be a network element in the core network that can send the first message. For example, the first communication device may be a network element in the core network used for terminal device registration.

[0096] Taking the NR system as an example, the first communication device may be an AMF, UDM, etc. in the core network. Taking the LTE system as an example, the first communication device may be a mobility management entity (MME) in the core network. Of course, the embodiments of the present application are not limited to this. In some possible implementations, the first communication device may also be other network elements in the core network, such as SMF, PCF, etc.; or, the first communication device may also be a network element in the core network in a future communication system, such as a network element in a future communication system that can send a first message, or a network element in a future communication system for terminal device registration, etc.

[0097] In some embodiments, the first communication device may be a terminal device. That is, in some embodiments, the terminal device may send the first message.

[0098] In addition to the possible implementation forms of the first communication device listed above, the first communication device may also be other network elements, nodes, or devices, which is not limited in the embodiments of the present application. For example, the first communication device may also be a third-party server or a third-party application. As a possible implementation, the third-party server or third-party application may send the first message to a network element in the core network to provide the information carried in the first message (for example, the first information and / or second information mentioned later).

[0099] In the embodiment of the present application, the second communication device can receive the first message sent by the first communication device. The embodiment of the present application does not specifically limit the second communication device, as long as it can receive the first message sent by the first communication device. The following examples illustrate several possible implementations of the second communication device.

[0100] In some embodiments, the second communication device may be a network element in the core network. That is, the second communication device may be a network element in the core network capable of receiving the first message. For example, the second communication device may be a network element in the core network capable of interacting with an external server or application, or may be a node or network element in the core network capable of transmitting data using a non-PDU session.

[0101] Taking the NR system as an example, the second communication device may be an NEF, AMF, etc. in the core network. Of course, the embodiments of the present application are not limited thereto. In some possible implementations, the second communication device may also be other network elements in the core network, such as AIoT-related network elements (AIoT NF) in the core network; or, the second communication device may be other nodes or network elements in the core network for transmitting data in a non-PDU session manner, such as when the SMF is a transmission node for a non-PDU session, the second communication device may be an SMF, etc.; or, the second communication device may also be a network element in the core network of a future communication system, such as a network element in a future communication system that can receive the first message, or a network element in a future communication system that can interact with an external server or application, or a node or network element in a future communication system that can transmit data in a non-PDU session manner, etc.

[0102] In some embodiments, the second communication device may be a terminal device. That is, in some embodiments, the terminal device may receive the first message.

[0103] In some embodiments, the second communication device may be an access network device. That is, the access network device may receive the first message sent by another node, network element, or device. For example, in an NR system, the second communication device may be a gNB. For example, in an LTE system, the second communication device may be an eNB, etc.

[0104] For ease of understanding, several specific examples of the first communication device and the second communication device are given below. It should be understood that the following examples are not intended to limit the technical solution of the present application to only be used for interaction between the following communication devices.

[0105] In some embodiments, the first communication device and the second communication device may both be network elements in the core network. As an example, the first communication device may be an AMF, and the second communication device may be an NEF or an AIoT NF. As another example, the first communication device may be a UDM, and the second communication device may be an AMF. As yet another example, the first communication device may be an AMF, and the second communication device may be an SMF (for example, an SMF serving as a node for transmitting data in a non-PDU session).

[0106] In some embodiments, the first communication device may be a network element in a core network, and the second communication device may be a terminal device. As an example, the first communication device may be an AMF, and the second communication device may be a terminal device. As another example, the first communication device may be an SMF, and the second communication device may be a terminal device.

[0107] In some embodiments, the first communication device may be a third-party server or a third-party application, and the second communication device may be a network element in the core network. As an example, the first communication device may be a third-party server, and the second communication device may be an AMF. In some embodiments, the third-party server or third-party application may be an entity corresponding to a database of a service provider, capable of providing service-related information.

[0108] In some embodiments, the first communication device may be a terminal device, and the second communication device may be an access network device. As an example, the first communication device may be a terminal device, and the second communication device may be a gNB.

[0109] In some embodiments, the first communication device may be a network element in a core network, and the second communication device may be an access network device. As an example, the first communication device may be an AMF, and the second communication device may be an access network device.

[0110] Based on the introduction of the first communication device and the second communication device, the method shown in Figure 3 is introduced below. The method shown in Figure 3 may include step S310.

[0111] In step S310, the first communication device sends a first message to the second communication device.

[0112] In an embodiment of the present application, the first message can be any message exchanged between the first communication device and the second communication device. The embodiment of the present application is not limited to this. As long as the first message contains information related to resource control or resource scheduling of the non-PDU session, for example, as long as the first message contains the first information and / or second information mentioned later, it will be sufficient.

[0113] In some embodiments, the first message may be a message for establishing a data transmission channel. For example, the first message may be used to establish a data transmission channel corresponding to a non-PDU session.

[0114] As an implementation method, the first communication device may send a first message to the second communication device to establish a data transmission channel corresponding to the non-PDU session. In this case, the first communication device and the second communication device may both be network elements in the core network. As an example, the first communication device may be a node, network element or device (such as AMF) that initiates a request to establish a data transmission channel, and the second communication device may be a node, network element or device on the non-PDU session transmission path, or the second communication device may be a node, network element or device on a data transmission channel based on a non-PDU session, such as the second communication device may be NEF, AIoT NF or other node, network element or device located on the non-PDU session transmission path.

[0115] The embodiment of the present application does not specifically limit the type (or granularity) of the data transmission channel corresponding to the non-PDU session. Exemplarily, the data transmission channel may include one or more of the following: a data transmission channel for a terminal device, a data transmission channel for a terminal device group (such as a first terminal device group), and a data transmission channel for a service (such as a first service).

[0116] Taking the data transmission channel as an example, which is a data transmission channel for a terminal device, after the data transmission channel is established, it can be used to transmit data of the terminal device, for example, to transmit data of the terminal device in a non-PDU session manner.

[0117] Taking the data transmission channel as an example, which is a data transmission channel for the first terminal device group, after the data transmission channel is established, it can be used to transmit data of the first terminal device group, for example, to transmit data of the first terminal device group in a non-PDU session manner.

[0118] Taking the data transmission channel as an example, the data transmission channel for the first service, after the data transmission channel is established, it can be used to transmit data of the first service, for example, in a non-PDU session manner.

[0119] In some embodiments, the first message may be a message related to the registration of the terminal device. For example, the first message may be a message indicating a registration result of the terminal device, such as a registration acceptance message.

[0120] As an implementation, the first communication device may send a first message to the second communication device to indicate the registration status of the terminal device. In this case, the first communication device may be a network element in the core network, and the second communication device may be a terminal device; alternatively, the first communication device may be a network element in the core network, and the second communication device may be an access network device, etc. As an example, the first communication device may be a core network element that receives a registration request from a terminal device or a core network element that determines a registration result of a terminal device (such as an AMF), and the second communication device may be a device that initiates a registration request from a terminal device or a device that receives a registration result of a terminal device (such as a terminal device).

[0121] In some embodiments, the first message may be a message for establishing a wireless connection (such as an RRC connection, an RRC reconnection, etc.), or in other words, the first message may be a message related to establishing a wireless connection with the terminal device. For example, the first message may be a wireless connection establishment request message.

[0122] As an implementation, the first communication device may send a first message to the second communication device to request to establish a wireless connection. In this case, the first communication device may be a terminal device, and the second communication device may be an access network device.

[0123] In some embodiments, the first message may be a message indicating service-related information. For example, the first message may be a message indicating information such as a service category or a service level (eg, the first information mentioned below).

[0124] As an implementation method, the first communication device may send a first message to the second communication device to indicate service-related information. In this case, the first communication device and the second communication device may both be network elements in the core network; or the first communication device may be a third-party server or a third-party application (e.g., an entity corresponding to a database of a service provider), and the second communication device may be a network element in the core network. As an example, the first communication device may be a requester of service-related information (e.g., AMF), and the second communication device may be a provider of service-related information (e.g., UDM, third-party server, etc.).

[0125] In addition to the implementation forms of the first message listed above, the first message may also be other messages containing information related to resource control or resource scheduling of non-PDU sessions.

[0126] The embodiment of the present application does not limit the granularity of the first message. As an implementation method, the first message can be associated with a terminal device, or in other words, the granularity of the first message can be each terminal device or each device (per UE or per device). As another implementation method, the first message can be associated with a terminal device group, or in other words, the granularity of the first message can be the terminal device group or device group (UE group or device group) where the terminal device is located. As another implementation method, the first message can be associated with a service, or in other words, the granularity of the first message can be each service (per service). However, the embodiment of the present application is not limited to this. For example, the granularity of the first message can also be multiple services, etc.

[0127] In some embodiments, the granularity of the first message may also be understood as the granularity of the first information and / or the second information included in the first message, which is not limited in this application.

[0128] In some embodiments, the first message may carry a corresponding identifier to indicate the granularity of the first message. For example, when the granularity of the first message is per UE or per device, the first message may carry a UE ID or a device ID to indicate that the granularity of the first message is per UE or per device. Alternatively, when the granularity of the first message is a UE group, the first message may carry a group ID or multiple UE IDs to indicate that the granularity of the first message is a UE group or a device group. Alternatively, when the granularity of the first message is per service, the first message may carry service information to indicate that the granularity of the first message is per service.

[0129] In some embodiments, the first message may include first information and / or second information. In some embodiments, the first information and / or second information may be associated with resource control of a non-PDU session. The first information and the second information are described below. First, the first information is described.

[0130] The first information can be used to control resources for non-PDU sessions. In some embodiments, controlling resources for non-PDU sessions facilitates differentiated control of data transmission using non-PDU sessions. For example, core network elements, terminal devices, access network devices, etc. can achieve differentiated control of data transmission using non-PDU sessions by controlling resources for non-PDU sessions.

[0131] In some embodiments, the first information used to control resources of the non-PDU session may include one or more of the following: access control of the non-PDU session, and resource allocation or resource scheduling of the non-PDU session.

[0132] As an example, the first information can be used to control access to a non-PDU session. For example, the first information can be used to determine whether a terminal device is allowed to access a non-PDU session. Alternatively, the first information can be used to determine the terminal devices (such as the number, specific terminal devices, etc.) or terminal device groups that are allowed to access a non-PDU session. Alternatively, the first information can be used to determine the terminal devices or terminal device groups that are allowed to access a non-PDU session for a first service (such as a certain service or certain services).

[0133] As another example, the first information may be used to allocate or schedule resources for a non-PDU session. In other words, the first information may be used to allocate or schedule resources for a non-PDU session. For example, the first information may be used to determine which terminal device or devices may use the resources of the non-PDU session for data transmission.

[0134] As yet another example, the first information may be used for access control and resource allocation for a non-PDU session.

[0135] In some embodiments, the "access to a non-PDU session" mentioned in the embodiments of the present application can be understood as access to a node, network element or device on the non-PDU session transmission path. For example, the first information is used to determine whether the terminal device is allowed to access a non-PDU session. It can be understood that the first information is used to determine whether the terminal device is allowed to access a node (such as NEF, AIoT NF, etc.) on the non-PDU session transmission path. For another example, the first information is used to determine the terminal device or terminal device group allowed to access the non-PDU session. It can be understood that the first information is used to determine the terminal device or terminal device group allowed to access the node on the non-PDU session transmission path.

[0136] In some embodiments, the "access to a non-PDU session" mentioned in the embodiments of the present application can be understood as access to the service corresponding to the non-PDU session. For example, the first information is used to determine whether the terminal device is allowed to access the non-PDU session, which can be understood as the first information is used to determine whether the terminal device is allowed to access the service corresponding to the non-PDU session (such as the first service). For another example, the first information is used to determine the terminal device or terminal device group allowed to access the non-PDU session, which can be understood as the first information is used to determine the service corresponding to the non-PDU session.

[0137] In some embodiments, the first information may be used to perform access control and / or resource allocation for a non-PDU session, and the first information is used to indicate whether a terminal device is allowed to access the non-PDU session. For example, when the first information corresponds to a terminal device, the first information may be used to perform access control and / or resource allocation for the non-PDU session, and is used to indicate whether a terminal device is allowed to access the non-PDU session.

[0138] In some embodiments, the first information may be used to perform access control and / or resource allocation for a non-PDU session, and the first information is used to indicate the terminal devices in a terminal device group (such as a first terminal device group) that are allowed to access the non-PDU session. For example, when the first information corresponds to a terminal device group, the first information may be used to perform access control and / or resource allocation for a non-PDU session, and is used to indicate the terminal devices in the terminal device group that are allowed to access the non-PDU session.

[0139] In some embodiments, the first information may be used to perform access control and / or resource allocation for a non-PDU session, and the first information is used to indicate a terminal device or terminal device group that is allowed to access the non-PDU session for the first service. For example, when the first information corresponds to the first service, the first information may be used to perform access control and / or resource allocation for the non-PDU session, and is used to indicate a terminal device or terminal device group that is allowed to access the non-PDU session for the first service.

[0140] The embodiment of the present application does not limit the implementation method of the first information indicating whether access control and / or resource allocation is performed on the non-PDU session. As a possible implementation method, the first information may use 1 bit to indicate whether access control and / or resource allocation is performed on the non-PDU session. For example, when the value of the first information is "1", it may indicate that access control and / or resource allocation is performed on the non-PDU session, and when the value of the first information is "0", it may indicate that access control and / or resource allocation is not performed on the non-PDU session. Alternatively, when the value of the first information is "0", it may indicate that access control and / or resource allocation is performed on the non-PDU session, and when the value of the first information is "1", it may indicate that access control and / or resource allocation is not performed on the non-PDU session. As another possible implementation method, the first information may use multiple bits (two or more) to indicate whether access control and / or resource allocation is performed on the non-PDU session. For example, when the value of the first information is "yes", "true" or other values ​​used to indicate access control and / or resource allocation for non-PDU sessions, it can be considered that access control and / or resource allocation for non-PDU sessions is required; when the value of the first information is "no", "false" or other values ​​used to indicate no access control and / or resource allocation for non-PDU sessions, it can be considered that access control and / or resource allocation for non-PDU sessions is not required.

[0141] The embodiments of the present application do not limit the implementation manner in which the first information indicates whether the terminal device is allowed to access a non-PDU session. As a possible implementation manner, the first information may use one bit to indicate whether the terminal device is allowed to access a non-PDU session. For example, a value of "1" in the first information may indicate that the terminal device is allowed to access a non-PDU session, while a value of "0" in the first information may indicate that the terminal device is not allowed to access a non-PDU session. Alternatively, a value of "0" in the first information may indicate that the terminal device is allowed to access a non-PDU session, while a value of "1" in the first information may indicate that the terminal device is not allowed to access a non-PDU session. As another possible implementation manner, the first information may use multiple bits (two or more) to indicate whether the terminal device is allowed to access a non-PDU session. For example, if the value of the first information is "yes," "true," or other values ​​indicating that the terminal device is allowed to access a non-PDU session, the terminal device may be considered to be allowed to access a non-PDU session; if the value of the first information is "no," "false," or other values ​​indicating that the terminal device is not allowed to access a non-PDU session, the terminal device may be considered to be not allowed to access a non-PDU session.

[0142] The embodiments of the present application do not limit the implementation method for the first information indicating whether access control and / or resource allocation are performed for a non-PDU session, and whether a terminal device is allowed to access the non-PDU session. As a possible implementation method, the first information may use two bits to indicate whether access control and / or resource allocation are performed for a non-PDU session, and whether a terminal device is allowed to access the non-PDU session. One of the two bits is used to indicate whether access control and / or resource allocation are performed for a non-PDU session, and the other bit is used to indicate whether a terminal device is allowed to access the non-PDU session. For example, when the value of the first information is "1,1", it may indicate that access control and / or resource allocation are performed for a non-PDU session, and the terminal device is allowed to access the non-PDU session; when the value of the first information is "1,0", it may indicate that access control and / or resource allocation are performed for a non-PDU session, and the terminal device is not allowed to access the non-PDU session; when the value of the first information is "0,0", it may indicate that access control and / or resource allocation are not performed for a non-PDU session, and the terminal device is not allowed to access the non-PDU session, etc. Of course, the first information can also use more than two bits to indicate whether access control and / or resource allocation are performed on non-PDU sessions, and whether the terminal device is allowed to access non-PDU sessions, wherein some of the more than two bits are used to indicate whether access control and / or resource allocation are performed on non-PDU sessions, and the other part of the bits are used to indicate whether the terminal device is allowed to access non-PDU sessions.

[0143] In some embodiments, the first information may correspond to (or be associated with, related to, etc.) a service. The following takes the correspondence between the first information and the first service as an example for introduction.

[0144] In some embodiments, the first information corresponding to the first service can be understood as indicating relevant information of the first service. For example, the first information can indicate a service class and / or service level corresponding to the first service.

[0145] The business category corresponding to the first business can also be understood as a business type, a business category, etc. The embodiment of the present application does not limit the business type corresponding to the first business, and the first business can be any type of business. For example, the first business can be an inventory service or an inventory service (inventory service); or, the first business can be a data reporting service, such as a sensor data reporting service (sensor data reporting service); or, the first business can be a command service (command service), such as a device switch control service, etc.

[0146] The embodiments of this application do not limit the manner in which service categories are divided. For example, the service categories may include the service categories listed above, or they may also include other service categories, such as short message services, video services, etc. Of course, service categories may also be divided in other ways than those listed in this application.

[0147] The service level corresponding to the first service can also be understood as a service priority. The embodiment of the present application does not limit the service level corresponding to the first service. For example, the first service can be a service with a higher priority (such as an emergency service, a data transmission service with higher latency requirements, etc.), or the first service can be a service with a lower priority (such as a data transmission service with lower latency requirements).

[0148] The embodiments of this application do not limit the manner in which service levels are divided. For example, service levels may include high-priority services and low-priority services; or, service levels may include the highest-priority service, the higher-priority service, the lower-priority service, and the lowest-priority service. Of course, priorities may also be divided in other ways than those listed in this application. For example, service levels may include the first level, the second level, and the third level. The criteria for dividing different levels may be arbitrarily set according to actual needs.

[0149] In some embodiments, the first information may include other service-related information in addition to the service category and / or service level corresponding to the first service, which is not limited in this embodiment of the present application. For example, the first information may also include other information such as the service identifier and the service's latency requirements.

[0150] The embodiment of the present application does not limit the identification method of the first service. For example, the first service can be identified by one or more of the following: the application ID (application ID) corresponding to the first service, the data network name (DNN), and the single network slice selection assistance information (S-NSSAI).

[0151] As mentioned above, the granularity of the first message can also be understood as the granularity of the first information and / or second information contained in the first message. The granularity of the first information is described below using the example that the granularity of the first message refers to the granularity of the first information.

[0152] In some embodiments, the first information may correspond to a terminal device, or in other words, the granularity of the first information may be per UE or per device.

[0153] In some embodiments, if the first information corresponds to a terminal device, the first information may be used to indicate whether the terminal device is allowed to access a non-PDU session. For example, the first information may be used to indicate whether the terminal device is allowed to access a node on the transmission path of the non-PDU session. Alternatively, the first information may be used to indicate whether the terminal device is allowed to access the service corresponding to the non-PDU session.

[0154] In some embodiments, the first information may correspond to a terminal device group (eg, a first terminal device group), or in other words, the granularity of the first information may be a UE group or a device group.

[0155] In some embodiments, if the first information corresponds to a terminal device group, the first information may be used to indicate the terminal devices in the terminal device group that are allowed to access the non-PDU session. For example, the first information may be used to indicate the terminal devices in the terminal device group that are allowed to access nodes on the transmission path of the non-PDU session. Alternatively, the first information may be used to indicate the terminal devices in the terminal device group that are allowed to access the service corresponding to the non-PDU session.

[0156] In some embodiments, the first information used to indicate the terminal devices in the terminal device group that are allowed to access non-PDU sessions may include one or more of the following: the number of terminal devices in the terminal device group that are allowed to access non-PDU sessions, and which specific terminal devices in the terminal device group are allowed to access non-PDU sessions.

[0157] As an implementation manner, the first information may carry the ID of the terminal device to indicate which terminal devices are allowed to access the non-PDU session.

[0158] In some embodiments, the first information may correspond to a service (such as the first service), or in other words, the granularity of the first information may be per service.

[0159] In some embodiments, if the first information corresponds to a service, the first information may be used to indicate a terminal device or terminal device group that is allowed to access a non-PDU session for the service. For example, the first information may be used to indicate a terminal device or terminal device group that is allowed to access a node on the non-PDU session transmission path for the service. Alternatively, the first information may be used to indicate a terminal device or terminal device group that is allowed to access the service.

[0160] The embodiments of the present application do not limit the implementation manner in which the first information indicates the terminal device group that accesses the service. As one implementation manner, the first information may carry a terminal device group identifier (group ID) to indicate the terminal device group that is allowed to access the service. As another implementation manner, the first information may carry identifiers of multiple terminal devices (multiple UE IDs) to indicate the terminal device group that is allowed to access the service.

[0161] The embodiment of the present application facilitates differentiated control for different terminal devices or different terminal device groups or different services by indicating the first information corresponding to different terminal devices or different terminal device groups or different services.

[0162] The second information is introduced below.

[0163] In some embodiments, the second information may be used to indicate a radio connection establishment cause (eg, an RRC connection establishment cause) corresponding to the first information.

[0164] In some embodiments, the second information may include a correspondence between the first information and the reason for establishing the wireless connection. In other words, the second information may include a setting relationship between the reason for establishing the wireless connection corresponding to the first information.

[0165] In some embodiments, the second information may include a wireless connection establishment reason corresponding to the first information.

[0166] In some embodiments, when the first information is different, the reason for establishing the wireless connection corresponding to the first information is different. In other words, the correspondence between the first information and the reason for establishing the wireless connection may include multiple types. Taking the example of the first information being used to indicate the service category or service level of the first service, when the service category or service level indicated by the first information is different, the reason for establishing the wireless connection corresponding to the first information may be different. For example, when the service category indicated by the first information is inventory service, the reason for establishing the wireless connection corresponding to the first information may be reason A; when the service category indicated by the first information is sensor data reporting service, the reason for establishing the wireless connection corresponding to the first information may be reason B; when the service category indicated by the first information is command service, the reason for establishing the wireless connection corresponding to the first information may be reason C; when the service category indicated by the first information is short message service, the reason for establishing the wireless connection corresponding to the first information may be reason D, etc.

[0167] In some embodiments, the second information includes the correspondence between the first information and the reason for establishing the wireless connection, which can be understood as the second information including one or more of the following: inventory service corresponding to reason A; sensor data reporting service corresponding to reason B; command service corresponding to reason C; short message service corresponding to reason D, etc.

[0168] In some embodiments, the second information includes the reason for establishing the wireless connection corresponding to the first information, which can be understood as the second information including one or more of the following: reason A, reason B, reason C, reason D, etc.

[0169] In some embodiments, the first message may include the first information. For example, when the first message is used to establish a data transmission channel corresponding to a non-PDU session, the first message may include the first information. Alternatively, when the first message is a message for indicating the registration result of the terminal device (such as a registration acceptance message), the first message may include the first information. Alternatively, when the first message is a wireless connection establishment request message (such as an RRC connection establishment request message), the first message may include the first information.

[0170] In some embodiments, the first message may include the second information. For example, when the first message is a message indicating the registration result of the terminal device (such as a registration acceptance message), the first message may include the second information. Alternatively, when the first message is a wireless connection establishment request message (such as an RRC connection establishment request message), the first message may include the second information.

[0171] In some embodiments, the first message may include both the first information and the second information. For example, when the first message is a message indicating the registration result of the terminal device (such as a registration acceptance message), the first message may include the first information and the second information. Alternatively, when the first message is a wireless connection establishment request message (such as an RRC connection establishment request message), the first message may include the first information and the second information.

[0172] In some embodiments, the first message may include other information in addition to the first information and / or the second information, which is not limited in the embodiments of the present application. For example, the first message may include identification information of the terminal device, identification information of the terminal device group, identification information of the first service, etc.

[0173] It should be noted that, in some embodiments, if a first message contains one of the first information and the second information, the first message is considered to be equivalent to or the same as the information contained in the first message, or in other words, in this case, the first message can be replaced by the information contained in the first message. Taking the example of a first message containing the first information but not the second information, it can be considered that the first message and the first information are equivalent. In this case, the first communication device sending the first message to the second communication device can be replaced by the first communication device sending the first information to the second communication device. Taking the example of a first message containing the second information but not the first information, it can be considered that the first message and the second information are equivalent. In this case, the first communication device sending the first message to the second communication device can be replaced by the first communication device sending the second information to the second communication device.

[0174] In this way, when data is transmitted in a non-PDU session manner, the embodiment of the present application can perform differentiated control on data transmission based on the first information and / or the second information.

[0175] In some embodiments, the core network (such as a network element of the core network) may perform access control or resource allocation on resources for data transmission corresponding to a non-PDU session based on the first information and / or the second information.

[0176] In some embodiments, when multiple services conflict on a terminal device, the terminal device may process the services based on the first information and / or the second information, for example, by discarding the services. As an implementation, the terminal device may discard services based on service category. For example, when multiple services conflict, the terminal device may discard a sensor data reporting service. As another implementation, the terminal device may discard services based on service level. For example, when multiple services conflict, the terminal device may discard a service with a lower priority.

[0177] In some embodiments, the access network device may perform access control or resource allocation on resources for data transmission corresponding to the non-PDU session based on the first information and / or the second information.

[0178] As mentioned above, the sending and receiving ends of the first message may be different in different scenarios. For ease of understanding, several specific embodiments are given below. It should be noted that the embodiments listed below are only used to exemplify the sending and receiving ends of the first message, as well as the possible implementation processes of the embodiments of the present application in different scenarios, and are not used to limit the embodiments of the present application. In other words, the embodiments of the present application can also be applied to other scenarios where differentiated control of non-PDU session data transmission can be achieved through the first message.

[0179] It should be noted that the steps in the embodiments listed below may be partially or completely executed, and the embodiments of the present application are not limited thereto. For example, steps S410 to S450 in Embodiment 1 may be executed in their entirety; alternatively, steps S420 and S430 may be executed in Embodiment 1. For another example, steps S610 to S650 in Embodiment 3 may be executed in their entirety; alternatively, steps S610 to S630 may be executed in Embodiment 3.

[0180] It should also be noted that the embodiments listed below can be implemented individually or in combination, and the embodiments of this application are not limited to this. For example, Example 1 can be implemented individually or in combination with Example 3. For another example, Example 2 can be implemented individually or in combination with Example 3, etc.

[0181] Example 1: Core network controls non-PDU sessions

[0182] In the first embodiment, the first communication device and the second communication device are both network elements in the core network. For example, the first communication device is an AMF, and the second communication device is an NEF or an AIoT NF.

[0183] In the first embodiment, the first message is used to establish a data transmission channel corresponding to the non-PDU session.

[0184] Figure 4 is a flow chart illustrating a method for wireless communication provided by another embodiment of the present application. The method illustrated in Figure 4 is described from the perspective of interaction between multiple devices, network elements, or nodes. The method illustrated in Figure 4 may include steps S410 to S450, which are described below.

[0185] In step S410, the terminal device sends a registration request message to the first communication device.

[0186] In some embodiments, the registration request message may carry identification information of the terminal device, such as the terminal device ID.

[0187] In some embodiments, the registration request message may carry relevant information of the service request (such as request information of the first service). The embodiment of the present application does not limit the relevant information of the service request carried in the registration request message. For example, the relevant information of the service request may use one or more of the following identifiers: application ID, DNN, S-NSSAI.

[0188] This embodiment of the present application does not limit the service (such as the first service) carried in the registration request message. For example, the service may be one or more of the following service types: inventory service, sensor data reporting service, command service.

[0189] In some embodiments, the service carried in the registration request message may be a service requested to be used by the terminal device, or in other words, the service may be a service for the terminal device.

[0190] In some embodiments, the service carried in the registration request message may be a service requested to be used by the terminal device group, or in other words, the service may be a service for the terminal device group.

[0191] In step S420, the first communication device sends a first message to the second communication device. The first message is used to establish a data transmission channel corresponding to the non-PDU session. In other words, the first message is a data transmission channel establishment request message to establish a data transmission channel corresponding to the non-PDU session.

[0192] In some embodiments, the granularity of the first message may be per UE or per device, or UE group or device group, or per service. In some embodiments, taking into account the different granularities of the first message, the first message may carry identification information characterizing the granularity of the first message. For example, the first message may carry UE ID or device ID or group ID or service information (such as application ID, DNN, S-NSSAI, etc.). As an example, the first message may carry UE ID or device ID to indicate that the granularity of the first message is per UE or per device. As another example, the first message may carry group ID to indicate that the granularity of the first message is UE group or device group. As yet another example, the first message may carry service information to indicate that the granularity of the first message is per service.

[0193] In some embodiments, the first message carries first information, for example, information about a service category and / or service level, such as information about a service category and / or service level corresponding to the first service.

[0194] In some embodiments, before the first communication device sends the first message to the second communication device, the first communication device may first obtain first information corresponding to a service (such as the first service) carried in the registration request message.

[0195] As an implementation manner, the first communication device may obtain first information corresponding to the first service from the UDM. For example, the first communication device may obtain first information corresponding to a service requested by a terminal device or a terminal device group from the UDM.

[0196] As another implementation, the first communication device may obtain the first information corresponding to the first service from a database of a service provider (e.g., a third-party server or a third-party application). For example, the first communication device may obtain the first information corresponding to the service requested by the terminal device or the terminal device group from the UDM.

[0197] In step S430, the second communication device sends a response message to the first communication device in response to the first message. For example, the second communication device sends a response message to the first communication device in response to the data transmission channel request message. In some embodiments, the response message may be used to indicate that the data transmission channel corresponding to the non-PDU session has been established.

[0198] In some embodiments, the second communications device may perform access control or resource allocation according to the first information.

[0199] The second communication device performing access control or resource allocation according to the first information may include multiple possibilities. As one possible implementation method, when the first information corresponds to a terminal device, the second communication device performing access control or resource allocation according to the first information may include: for the terminal device, determining whether the terminal device is allowed to access a non-PDU session (such as accessing the second communication device). As another possible implementation method, when the first information corresponds to a terminal device group, the second communication device performing access control or resource allocation according to the first information may include: for the terminal device group, determining the terminal devices in the terminal device group that are allowed to access a non-PDU session (such as accessing the second communication device), for example, determining the number of terminal devices in the terminal device group that are allowed to access a non-PDU session and / or which specific terminal devices in the terminal device group are allowed to access a non-PDU session. As another possible implementation method, when the first information corresponds to a service, the second communication device performing access control or resource allocation according to the first information may include: determining the terminal device or terminal device group that is allowed to access a non-PDU session (such as accessing the second communication device) for the service.

[0200] In step S440, the first communication device returns a registration acceptance message to the terminal device.

[0201] In step S450, the terminal device returns a registration completion message to the first communication device.

[0202] Example 2: Terminal device controls non-PDU session

[0203] In the second embodiment, the first communication device is a network element in the core network, and the second communication device is a terminal device. For example, the first communication device is an AMF, and the second communication device is a terminal device.

[0204] In the second embodiment, the first message is a registration acceptance message.

[0205] Figure 5 is a flow chart of a wireless communication method according to another embodiment of the present application. The method shown in Figure 5 is described from the perspective of interaction between multiple devices, network elements, or nodes. The method shown in Figure 5 may include steps S510 to S550, which are described below.

[0206] In step S510, the second communication device sends a registration request message to the first communication device.

[0207] In some embodiments, the registration request message may carry identification information of the terminal device, such as the terminal device ID.

[0208] In some embodiments, the registration request message may carry relevant information of the service request (such as request information of the first service). The embodiment of the present application does not limit the relevant information of the service request carried in the registration request message. For example, the relevant information of the service request may use one or more of the following identifiers: application ID, DNN, S-NSSAI.

[0209] This embodiment of the present application does not limit the service (such as the first service) carried in the registration request message. For example, the service may be one or more of the following service types: inventory service, sensor data reporting service, command service.

[0210] In some embodiments, the service carried in the registration request message may be a service requested to be used by the terminal device, or in other words, the service may be a service for the terminal device.

[0211] In some embodiments, the service carried in the registration request message may be a service requested to be used by the terminal device group, or in other words, the service may be a service for the terminal device group.

[0212] In step S520, the first communication device sends a data transmission channel establishment request message to the NEF or AIoT NF.

[0213] In some embodiments, the granularity of the request message for establishing a data transmission channel may be per UE or per device, or UE group or device group, or per service. In some embodiments, taking into account the different granularities of the request message for establishing a data transmission channel, the request message for establishing a data transmission channel may carry identification information characterizing the granularity of the request message for establishing a data transmission channel. For example, the request message for establishing a data transmission channel may carry UE ID or device ID or group ID or service information (such as application ID, DNN, S-NSSAI, etc.). As an example, the request message for establishing a data transmission channel may carry UE ID or device ID to indicate that the granularity of the request message for establishing a data transmission channel is per UE or per device. As another example, the request message for establishing a data transmission channel may carry group ID to indicate that the granularity of the request message for establishing a data transmission channel is UE group or device group. As yet another example, the request message for establishing a data transmission channel may carry service information to indicate that the granularity of the request message for establishing a data transmission channel is per service.

[0214] In some embodiments, the data transmission channel establishment request message carries first information, for example, service category and / or service level information, such as service category and / or service level information corresponding to the first service.

[0215] In some embodiments, before the first communication device sends a request message for establishing a data transmission channel to the NEF or AIoT NF, the first communication device may first obtain first information corresponding to a service (such as the first service) carried in the registration request message.

[0216] As an implementation manner, the first communication device may obtain first information corresponding to the first service from the UDM. For example, the first communication device may obtain first information corresponding to a service requested by a terminal device or a terminal device group from the UDM.

[0217] As another implementation, the first communication device may obtain the first information corresponding to the first service from a database of a service provider (e.g., a third-party server or a third-party application). For example, the first communication device may obtain the first information corresponding to the service requested by the terminal device or the terminal device group from the UDM.

[0218] In step S530, the NEF or AIoT NF sends a response message to the data transmission channel request message to the first communication device. In some embodiments, the response message can be used to indicate that the data transmission channel corresponding to the non-PDU session is established.

[0219] In some embodiments, the NEF or AIoT NF may perform access control or resource allocation based on the first information.

[0220] NEF or AIoT NF performing access control or resource allocation according to the first information may include multiple possibilities. As one possible implementation manner, when the first information corresponds to a terminal device, NEF or AIoT NF performing access control or resource allocation according to the first information may include: determining, for the terminal device, whether the terminal device is allowed to access a non-PDU session (such as accessing NEF or AIoT NF). As another possible implementation manner, when the first information corresponds to a terminal device group, NEF or AIoT NF performing access control or resource allocation according to the first information may include: determining, for the terminal device group, the terminal devices in the terminal device group that are allowed to access a non-PDU session (such as accessing NEF or AIoT NF), for example, determining the number of terminal devices in the terminal device group that are allowed to access a non-PDU session and / or which specific terminal devices in the terminal device group are allowed to access a non-PDU session. As another possible implementation manner, when the first information corresponds to a service, NEF or AIoT NF performing access control or resource allocation according to the first information may include: determining, for the service, the terminal device or terminal device group that is allowed to access a non-PDU session (such as accessing NEF or AIoT NF).

[0221] In step S540, the first communication device sends a first message to the second communication device, wherein the first message is a registration acceptance message.

[0222] In some embodiments, the first message may carry the first information and / or the second information. For example, the first message may carry information about the service category and / or service level; or the first message may carry information about the correspondence between the service category and / or service level and the reason for establishing the wireless connection; or the first message may carry information about the service category and / or service level, and information about the correspondence between the service category and / or service level and the reason for establishing the wireless connection.

[0223] In some embodiments, when multiple services conflict on a terminal device, the terminal device may process the services based on the first information and / or the second information, for example, by discarding the services. As an implementation, the terminal device may discard services based on service category. For example, when multiple services conflict, the terminal device may discard a sensor data reporting service. As another implementation, the terminal device may discard services based on service level. For example, when multiple services conflict, the terminal device may discard a service with a lower priority.

[0224] In some embodiments, the second information may be used when the terminal device needs to establish a wireless connection.

[0225] In step S550, the second communication device returns a registration completion message to the first communication device.

[0226] Example 3: Access network equipment controls non-PDU sessions

[0227] In the third embodiment, the first communication device is a terminal device, and the second communication device is an access network device.

[0228] In the third embodiment, the first message is a wireless connection establishment request message, such as an RRC connection establishment request message.

[0229] Figure 6 is a flowchart illustrating a method for wireless communication according to another embodiment of the present application. The method illustrated in Figure 6 is described from the perspective of interaction between multiple devices, network elements, or nodes. The method illustrated in Figure 6 may include steps S610 to S640, which are described below.

[0230] In step S610, the first communication device sends a first message to the second communication device. The first message is a wireless connection establishment request message.

[0231] In some embodiments, the wireless connection may be an RRC connection. In some embodiments, the wireless connection may also be other types of wireless connections.

[0232] In some embodiments, the first message may carry first information, for example, information about a service category and / or a service level.

[0233] In some embodiments, the first information carried in the first message may be obtained by the first communications device from a registration acceptance message.

[0234] In some embodiments, the first message may carry the second information. For example, the first message may carry the wireless connection establishment reason corresponding to the first information.

[0235] In some embodiments, the first message may carry the first information and the second information. For example, the first message may carry information about the service category and / or service level, and a wireless connection establishment reason corresponding to the first information.

[0236] In some embodiments, whether the first message carries the second information depends on whether the registration accept message received by the terminal device carries the second information. For example, if the registration accept message carries the second information, then the first message may carry the second information. Alternatively, if the registration accept message does not carry the second information, then the first message may not carry the second information. However, the embodiments of the present application are not limited to this. For example, if the registration accept message carries the second information, then the first message may not carry the second information.

[0237] In some embodiments, the second information carried in the registration accept message and the first message may be different. For example, the second information carried in the registration accept message is used to indicate the correspondence between the first information and the reason for establishing the wireless connection, while the second information carried in the first message is used to indicate the reason for establishing the wireless connection corresponding to the first information. In other words, in some embodiments, if the registration accept message carries information about the reason for establishing the wireless connection corresponding to the first information, then when the terminal device initiates a wireless connection, the terminal device may set or configure the reason for establishing the wireless connection based on the currently triggered service (i.e., based on the first information).

[0238] In step S620, the second communication device sends a response message to the first message to the first communication device. For example, the second communication device sends a response message to the wireless connection establishment request to the first communication device.

[0239] In some embodiments, the second communications device may perform access control or resource allocation according to the first information and / or the second information.

[0240] The second communication device performing access control or resource allocation based on the first information and / or the second information may include multiple possibilities. As a possible implementation, when the first information corresponds to the terminal device, the second communication device performing access control or resource allocation based on the first information and / or the second information may include: for the terminal device, determining whether the terminal device is allowed to access the non-PDU session (such as accessing the service corresponding to the non-PDU session). As another possible implementation, when the first information corresponds to the terminal device group, the second communication device performing access control or resource allocation based on the first information and / or the second information may include: for the terminal device group, determining the terminal devices in the terminal device group that are allowed to access the non-PDU session (such as accessing the service corresponding to the non-PDU session), for example, determining the number of terminal devices in the terminal device group that are allowed to access the non-PDU session and / or which specific terminal devices in the terminal device group are allowed to access the non-PDU session. As another possible implementation, when the first information corresponds to the service, the second communication device performing access control or resource allocation based on the first information and / or the second information may include: determining the terminal device or terminal device group that is allowed to access the non-PDU session (such as accessing the service corresponding to the non-PDU session) for the service.

[0241] In step S630, the first communication device sends a wireless connection establishment completion message to the second communication device.

[0242] In some embodiments, the wireless connection establishment complete message may carry data reported via NAS. In other words, the wireless connection establishment complete message may carry a NAS reporting message.

[0243] In some embodiments, the NAS reporting message may be a registration request message, for example, a registration request message when the first communication device re-initiates a registration request.

[0244] In some embodiments, the NAS reporting message may be another NAS message other than the registration request message.

[0245] In step S640, if the wireless connection establishment completion message carries a NAS reporting message, the AMF returns a NAS response message to the first communication device.

[0246] Taking the above NAS reporting message as a registration request message as an example, the NAS response message may be a registration accept message. Taking the above NAS reporting message as other NAS messages as an example, the NAS response message may be other NAS confirmation messages.

[0247] In some embodiments, if the above-mentioned NAS reporting message is a registration request message, after step S640, the first communication device may also return a registration completion message to the AMF.

[0248] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 6 , and the device embodiment of the present application is described in detail below in conjunction with Figures 7 to 9 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, and therefore, for portions not described in detail, reference can be made to the above method embodiment.

[0249] FIG7 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 700 shown in FIG7 can be, for example, any of the first communication devices mentioned above. The communication device 700 can include a sending module 710.

[0250] The sending module 710 can be used to send a first message to a second communication device, wherein the first message includes one or more of the following information: first information for controlling resources of a non-PDU session; and second information for indicating a reason for establishing a wireless connection corresponding to the first information.

[0251] Optionally, the first information corresponds to a first service.

[0252] Optionally, the first information is used to indicate a service category or service level corresponding to the first service.

[0253] Optionally, the first information is used to perform access control and / or resource allocation for the non-PDU session.

[0254] Optionally, the first information corresponds to a terminal device, and the first information is used to indicate whether the terminal device is allowed to access the non-PDU session.

[0255] Optionally, the first information corresponds to a first terminal device group, and the first information is used to indicate the terminal devices in the first terminal device group that are allowed to access the non-PDU session.

[0256] Optionally, the first information corresponds to a first service, and the first information is used to indicate a terminal device or a terminal device group that is allowed to access the non-PDU session for the first service.

[0257] Optionally, the first communication device and the second communication device are both network elements in a core network.

[0258] Optionally, the first message is used to establish a data transmission channel corresponding to the non-PDU session.

[0259] Optionally, the data transmission channel includes one or more of the following: a data transmission channel for a terminal device; a data transmission channel for a first terminal device group; and a data transmission channel for a first service.

[0260] Optionally, the first communication device is a network element in a core network, and the second communication device is a terminal device.

[0261] Optionally, the first message is a registration acceptance message.

[0262] Optionally, the second information includes a correspondence between the first information and a reason for establishing the wireless connection.

[0263] Optionally, the first communication device is a terminal device, and the second communication device is an access network device.

[0264] Optionally, the first message is a wireless connection establishment request message.

[0265] Optionally, the second information includes a wireless connection establishment reason corresponding to the first information.

[0266] Optionally, the sending module 710 may be a transceiver 930. The communication device 700 may further include a processor 910 and a memory 920, as specifically shown in FIG9 .

[0267] FIG8 is a schematic diagram of the structure of a communication device provided by another embodiment of the present application. The communication device 800 shown in FIG8 can be, for example, any of the second communication devices mentioned above. The communication device 800 can include a receiving module 810.

[0268] The receiving module 810 can be used to receive a first message sent by a first communication device, wherein the first message includes one or more of the following information: first information for controlling resources of a non-PDU session; and second information for indicating a reason for establishing a wireless connection corresponding to the first information.

[0269] Optionally, the first information corresponds to a first service.

[0270] Optionally, the first information is used to indicate a service category or service level corresponding to the first service.

[0271] Optionally, the first information is used to perform access control and / or resource allocation for the non-PDU session.

[0272] Optionally, the first information corresponds to a terminal device, and the first information is used to indicate whether the terminal device is allowed to access the non-PDU session.

[0273] Optionally, the first information corresponds to a first terminal device group, and the first information is used to indicate the terminal devices in the first terminal device group that are allowed to access the non-PDU session.

[0274] Optionally, the first information corresponds to a first service, and the first information is used to indicate a terminal device or a terminal device group that is allowed to access the non-PDU session for the first service.

[0275] Optionally, the first communication device and the second communication device are both network elements in a core network.

[0276] Optionally, the first message is used to establish a data transmission channel corresponding to the non-PDU session.

[0277] Optionally, the data transmission channel includes one or more of the following: a data transmission channel for a terminal device; a data transmission channel for a first terminal device group; and a data transmission channel for a first service.

[0278] Optionally, the first communication device is a network element in a core network, and the second communication device is a terminal device.

[0279] Optionally, the first message is a registration acceptance message.

[0280] Optionally, the second information includes a correspondence between the first information and a reason for establishing the wireless connection.

[0281] Optionally, the first communication device is a terminal device, and the second communication device is an access network device.

[0282] Optionally, the first message is a wireless connection establishment request message.

[0283] Optionally, the second information includes a wireless connection establishment reason corresponding to the first information.

[0284] Optionally, the receiving module 810 may be a transceiver 930. The communication device 800 may further include a processor 910 and a memory 920, as specifically shown in FIG9 .

[0285] Figure 9 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 9 indicate that the unit or module is optional. The device 900 may be used to implement the method described in the above method embodiment. The device 900 may be a chip, a terminal device, or a network device.

[0286] The device 900 may include one or more processors 910. The processor 910 may support the device 900 to implement the method described in the method embodiment above. The processor 910 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0287] The apparatus 900 may further include one or more memories 920. The memories 920 store programs that can be executed by the processor 910, causing the processor 910 to perform the methods described in the above method embodiments. The memories 920 may be independent of the processor 910 or integrated into the processor 910.

[0288] The apparatus 900 may further include a transceiver 930. The processor 910 may communicate with other devices or chips via the transceiver 930. For example, the processor 910 may transmit and receive data with other devices or chips via the transceiver 930.

[0289] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0290] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0291] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0292] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0293] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0294] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0295] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0296] In the embodiments of this application, the term "include" can refer to direct inclusion or indirect inclusion. Alternatively, the term "include" in the embodiments of this application can be replaced with "indicates" or "is used to determine." For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B."

[0297] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0298] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0299] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0300] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0301] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0302] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0303] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0304] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0305] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, characterized in that: include: The first communication device sends a first message to the second communication device, where the first message includes one or more of the following information: First information, used to control resources of non-PDU sessions; as well as The second information is used to indicate a reason for establishing a wireless connection corresponding to the first information.

2. The method according to claim 1, characterized in that The first information corresponds to a first service.

3. The method according to claim 2, characterized in that The first information is used to indicate a service category or a service level corresponding to the first service.

4. The method according to any one of claims 1 to 3, characterized in that The first information is used to perform access control and / or resource allocation on the non-PDU session.

5. The method according to any one of claims 1 to 4, characterized in that The first information corresponds to a terminal device, and the first information is used to indicate whether the terminal device is allowed to access the non-PDU session.

6. The method according to any one of claims 1 to 4, characterized in that The first information corresponds to a first terminal device group, and the first information is used to indicate the terminal devices in the first terminal device group that are allowed to access the non-PDU session.

7. The method according to any one of claims 1 to 4, characterized in that The first information corresponds to a first service, and the first information is used to indicate a terminal device or a terminal device group that is allowed to access the non-PDU session for the first service.

8. The method according to any one of claims 1 to 7, characterized in that The first communication device and the second communication device are both network elements in a core network.

9. The method according to claim 8, characterized in that The first message is used to establish a data transmission channel corresponding to the non-PDU session.

10. The method according to claim 9, characterized in that The data transmission channel includes one or more of the following: Data transmission channel for terminal equipment; A data transmission channel for the first terminal device group; as well as A data transmission channel for the first service.

11. The method according to any one of claims 1 to 7, characterized in that The first communication device is a network element in a core network, and the second communication device is a terminal device.

12. The method according to claim 11, characterized in that The first message is a registration acceptance message.

13. The method according to claim 11 or 12, characterized in that: The second information includes a correspondence between the first information and a reason for establishing the wireless connection.

14. The method according to any one of claims 1 to 7, characterized in that The first communication device is a terminal device, and the second communication device is an access network device.

15. The method according to claim 14, characterized in that The first message is a wireless connection establishment request message.

16. The method according to claim 14 or 15, characterized in that The second information includes a wireless connection establishment reason corresponding to the first information.

17. A wireless communication method, characterized in that: include: The second communication device receives a first message sent by the first communication device, where the first message includes one or more of the following information: First information, used to control resources of non-PDU sessions; as well as The second information is used to indicate a reason for establishing the wireless connection corresponding to the first information.

18. The method according to claim 17, characterized in that The first information corresponds to a first service.

19. The method according to claim 18, characterized in that The first information is used to indicate a service category or a service level corresponding to the first service.

20. The method according to any one of claims 17 to 19, characterized in that The first information is used to perform access control and / or resource allocation on the non-PDU session.

21. The method according to any one of claims 17 to 20, characterized in that The first information corresponds to a terminal device, and the first information is used to indicate whether the terminal device is allowed to access the non-PDU session.

22. The method according to any one of claims 17 to 20, characterized in that The first information corresponds to a first terminal device group, and the first information is used to indicate the terminal devices in the first terminal device group that are allowed to access the non-PDU session.

23. The method according to any one of claims 17 to 20, characterized in that The first information corresponds to a first service, and the first information is used to indicate a terminal device or a terminal device group that is allowed to access the non-PDU session for the first service.

24. The method according to any one of claims 17 to 23, characterized in that The first communication device and the second communication device are both network elements in a core network.

25. The method according to claim 24, characterized in that The first message is used to establish a data transmission channel corresponding to the non-PDU session.

26. The method according to claim 25, characterized in that The data transmission channel includes one or more of the following: Data transmission channel for terminal equipment; A data transmission channel for the first terminal device group; as well as A data transmission channel for the first service.

27. The method according to any one of claims 17 to 23, characterized in that The first communication device is a network element in a core network, and the second communication device is a terminal device.

28. The method according to claim 27, characterized in that The first message is a registration acceptance message.

29. The method according to claim 27 or 28, characterized in that The second information includes a correspondence between the first information and a reason for establishing the wireless connection.

30. The method according to any one of claims 17 to 23, characterized in that The first communication device is a terminal device, and the second communication device is an access network device.

31. The method according to claim 30, characterized in that The first message is a wireless connection establishment request message.

32. The method according to claim 30 or 31, characterized in that The second information includes a wireless connection establishment reason corresponding to the first information.

33. A communication device, characterized in that: The communication device is a first communication device, and the communication device includes: A sending module, configured to send a first message to a second communication device, wherein the first message includes one or more of the following information: First information, used to control resources of non-PDU sessions; and The second information is used to indicate a reason for establishing the wireless connection corresponding to the first information.

34. The communication device according to claim 33, characterized in that The first information corresponds to a first service.

35. The communication device according to claim 34, characterized in that The first information is used to indicate a service category or a service level corresponding to the first service.

36. The communication device according to any one of claims 33 to 35, characterized in that: The first information is used to perform access control and / or resource allocation on the non-PDU session.

37. The communication device according to any one of claims 33 to 36, characterized in that: The first information corresponds to a terminal device, and the first information is used to indicate whether the terminal device is allowed to access the non-PDU session.

38. The communication device according to any one of claims 33 to 36, characterized in that: The first information corresponds to a first terminal device group, and the first information is used to indicate the terminal devices in the first terminal device group that are allowed to access the non-PDU session.

39. The communication device according to any one of claims 33 to 36, characterized in that: The first information corresponds to a first service, and the first information is used to indicate a terminal device or a terminal device group that is allowed to access the non-PDU session for the first service.

40. The communication device according to any one of claims 33 to 39, characterized in that: The first communication device and the second communication device are both network elements in a core network.

41. The communication device according to claim 40, characterized in that The first message is used to establish a data transmission channel corresponding to the non-PDU session.

42. The communication device according to claim 41, characterized in that The data transmission channel includes one or more of the following: Data transmission channel for terminal equipment; A data transmission channel for the first terminal device group; as well as A data transmission channel for the first service.

43. The communication device according to any one of claims 33 to 39, characterized in that: The first communication device is a network element in a core network, and the second communication device is a terminal device.

44. The communication device according to claim 43, characterized in that The first message is a registration acceptance message.

45. The communication device according to claim 43 or 44, characterized in that The second information includes a correspondence between the first information and a reason for establishing the wireless connection.

46. ​​The communication device according to any one of claims 33 to 39, characterized in that: The first communication device is a terminal device, and the second communication device is an access network device.

47. The communication device according to claim 46, characterized in that The first message is a wireless connection establishment request message.

48. The communication device according to claim 46 or 47, characterized in that The second information includes a wireless connection establishment reason corresponding to the first information.

49. A communication device, characterized in that: The communication device is a second communication device, and the communication device includes: A receiving module, configured to receive a first message sent by a first communication device, wherein the first message includes one or more of the following information: First information, used to control resources of non-PDU sessions; and The second information is used to indicate a reason for establishing the wireless connection corresponding to the first information.

50. The communication device according to claim 49, characterized in that The first information corresponds to a first service.

51. The communication device according to claim 50, characterized in that The first information is used to indicate a service category or a service level corresponding to the first service.

52. The communication device according to any one of claims 49 to 51, characterized in that: The first information is used to perform access control and / or resource allocation on the non-PDU session.

53. The communication device according to any one of claims 49 to 52, characterized in that: The first information corresponds to a terminal device, and the first information is used to indicate whether the terminal device is allowed to access the non-PDU session.

54. The communication device according to any one of claims 49 to 52, characterized in that: The first information corresponds to a first terminal device group, and the first information is used to indicate the terminal devices in the first terminal device group that are allowed to access the non-PDU session.

55. The communication device according to any one of claims 49 to 52, characterized in that: The first information corresponds to a first service, and the first information is used to indicate a terminal device or a terminal device group that is allowed to access the non-PDU session for the first service.

56. The communication device according to any one of claims 49 to 55, characterized in that: The first communication device and the second communication device are both network elements in a core network.

57. The communication device according to claim 56, characterized in that The first message is used to establish a data transmission channel corresponding to the non-PDU session.

58. The communication device according to claim 57, characterized in that The data transmission channel includes one or more of the following: Data transmission channel for terminal equipment; A data transmission channel for the first terminal device group; as well as A data transmission channel for the first service.

59. The communication device according to any one of claims 49 to 55, characterized in that: The first communication device is a network element in a core network, and the second communication device is a terminal device.

60. The communication device according to claim 59, characterized in that The first message is a registration acceptance message.

61. The communication device according to claim 59 or 60, characterized in that: The second information includes a correspondence between the first information and a reason for establishing the wireless connection.

62. The communication device according to any one of claims 49 to 55, characterized in that: The first communication device is a terminal device, and the second communication device is an access network device.

63. The communication device according to claim 62, characterized in that The first message is a wireless connection establishment request message.

64. The communication device according to claim 62 or 63, characterized in that The second information includes a wireless connection establishment reason corresponding to the first information.

65. A communication device, characterized in that: The device comprises a transceiver, a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the communication device executes the method according to any one of claims 1 to 32.

66. A device, characterized in that The device comprises a processor, configured to call a program from a memory so as to cause the device to execute a method as claimed in any one of claims 1 to 32.

67. A chip, characterized in that: It comprises a processor, which is used to call a program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 32.

68. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 32.

69. A computer program product, characterized in that The method comprises a program which causes a computer to execute the method according to any one of claims 1 to 32.

70. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 32.

Images