Communication method, terminal device, and core network element

Abstract

Provided in the present application are a communication method, a terminal device, and a core network element. The method comprises: a first terminal device sending first information to a first core network element by means of a user plane message, wherein the first information is used for indicating information of a second terminal device. When the first core network element collects the information of the second terminal device, a network side can acquire the information of the second terminal device, so as to sense the second terminal device. In this case, the first terminal device may not need to acquire the information of the second terminal device by means of a private interface, thereby unbinding the first terminal device and the second terminal device. For a consumer, the consumer can purchase the first terminal device of any manufacturer, that is, the sensing of the information of the second terminal device by the network side can be realized. For manufacturers or suppliers of the second terminal device, the manufacturers or suppliers do not need to deploy servers by themselves, thereby reducing costs and network complexity.

Description

Method, terminal equipment and core network element for communication Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a method, terminal equipment, and core network element for communication. Background Art

[0002] The first terminal device can implement indirect communication between the second terminal device and the network device. For example, the first terminal device can be a common terminal device, and the second terminal device can be a zero-power device. The common terminal device can serve as a transceiver for the zero-power device.

[0003] The first terminal device can perceive the second terminal device through a private interface. This means that the network cannot perceive the second terminal device's information. Because private interfaces cannot enable intercommunication between terminal devices manufactured by different manufacturers, consumers are forced to purchase both the first and second terminal devices from the same manufacturer in order to achieve indirect communication between the second terminal device. Alternatively, the manufacturer or provider of the second terminal device can deploy its own service server to alleviate the bundling between the first and second terminal devices to some extent. However, this increases costs for the manufacturer or service provider and further complicates the network structure.

[0004] Summary of the Invention

[0005] The present application provides a method, terminal device, and core network element for communication. The following introduces various aspects involved in the present application.

[0006] In a first aspect, a method for communication is provided, the method comprising: a first terminal device sends first information to a first core network element via a user plane message; wherein the first information is used to indicate information of a second terminal device.

[0007] In a second aspect, a method for communication is provided, the method comprising: a first core network element receiving first information sent by a first terminal device through a user plane message; wherein the first information is used to indicate information of a second terminal device.

[0008] In a third aspect, a method for communication is provided, the method comprising: a second core network element sends information of a first core network element to a first terminal device; wherein the first core network element is used to receive first information through a user plane message, and the first information is used to indicate information of the second terminal device.

[0009] In a fourth aspect, a terminal device is provided, which is a first terminal device, and the terminal device includes: a first sending unit, used to send first information to a first core network element through a user plane message; wherein the first information is used to indicate information of a second terminal device.

[0010] In the fifth aspect, a core network network element is provided, which is a first core network network element, and the core network network element includes: a second receiving unit, used to receive first information sent by a first terminal device through a user plane message; wherein the first information is used to indicate information of a second terminal device.

[0011] In the sixth aspect, a core network network element is provided, which is a second core network network element, and the core network network element includes: a second sending unit, used to send information of the first core network network element to the first terminal device; wherein, the first core network network element is used to receive first information through a user plane message, and the first information is used to indicate information of the second terminal device.

[0012] In the seventh aspect, a terminal device is provided, comprising a processor and a memory, 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 terminal device executes part or all of the steps in the method of the first aspect.

[0013] In the eighth aspect, a core network element is provided, comprising a processor, a memory, and a transceiver, 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 core network element performs part or all of the steps in the method of the second aspect and / or the third aspect.

[0014] In a ninth aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal device and / or core network element. In another possible design, the system may also include other devices that interact with the terminal device or core network element in the solution provided in the embodiment of the present application.

[0015] In the tenth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables the terminal device and / or core network element to execute part or all of the steps in the methods of the above aspects.

[0016] In an eleventh 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 terminal device and / or a core network element 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.

[0017] In the twelfth 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.

[0018] When the first core network element collects information about the second terminal device, the network side can obtain this information and thus perceive the second terminal device. In this case, the first terminal device no longer needs to obtain the second terminal device's information through a private interface, thus achieving unbinding of the first and second terminal devices. For consumers, they can purchase a first terminal device from any manufacturer and the network side will perceive the second terminal device's information. For the manufacturer or supplier of the second terminal device, this eliminates the need to deploy their own servers, reducing costs and network complexity. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] FIG1 is a schematic diagram of a network architecture provided in an embodiment of the present application.

[0020] FIG2 is a schematic diagram of the architecture of a zero-power communication system applicable to an embodiment of the present application.

[0021] FIG3 is a diagram showing an example of an architecture for non-direct communication applicable to an embodiment of the present application.

[0022] FIG4 is a schematic flowchart of a method for communication provided in an embodiment of the present application.

[0023] FIG5 is a schematic flowchart of a method for communication provided in Embodiment 1 of the present application.

[0024] FIG6 is a schematic flowchart of a method for communication provided in Embodiment 2 of the present application.

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

[0026] FIG8 is a schematic structural diagram of a core network element provided in an embodiment of the present application.

[0027] Figure 9 is a schematic structural diagram of another core network element provided in an embodiment of the present application.

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

[0029] The technical solution in this application will be described below with reference to the accompanying drawings.

[0030] Mobile network system architecture

[0031] Figure 1 is a schematic diagram of a network architecture provided by an embodiment of the present application. The network architecture may include terminal devices, access network (AN) network elements, and core network elements. The access network elements and core network elements may both be network-side network elements. That is, network devices may include access network elements and core network elements.

[0032] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0033] The terminal device in the embodiments of the present application 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 core network element, user agent or user device. The terminal device in the embodiments of the present application 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 with wireless connection function, a vehicle-mounted device, etc. 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 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. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in vehicle-to-everything (V2X) or device-to-device (D2D). For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through a base station.

[0034] An access network element can be an access network device. This device is used by terminals to wirelessly access the network architecture and is primarily responsible for radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. An access network device can also be referred to as a radio access network (RAN) device. For example, an access network device can be a base station. A base station may 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, transmitting and receiving point (TRP), transmitting point (TP), master eNB (MeNB), secondary eNB (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 may 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 may also refer to a communication module, modem, or chip used to be set in the aforementioned device or apparatus. A base station may also be a mobile switching center and a device that performs base station functions in D2D, 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. A base station may 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 core network element may be a core network device. The types of core network elements may include user plane function (UPF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, policy control function (PCF) network element, application function (AF), data network (DN), network slice selection function (NSSF), authentication server function (AUSF), unified data management function (UDM), network exposure function (NEF), network repository function (NRF), network slice-specific authentication and authorization function (NSSAAF). Among them, the UPF network element is mainly responsible for the transmission of user data, and other network elements can be called control plane function network elements, which are mainly responsible for authentication, authorization, registration management, session management, mobility management and policy control, etc., to ensure reliable and stable transmission of user data.

[0038] The UPF network element can be used to forward and receive data from the terminal. For example, the UPF network element can receive service data from the data network and transmit it to the terminal through the access network device; the UPF network element can also receive user data from the terminal through the access network device and forward it to the data network. Among them, the transmission resources allocated and scheduled by the UPF network element for the terminal are managed and controlled by the SMF network element. The bearer between the terminal and the UPF network element may include: the user plane connection between the UPF network element and the access network device, and the establishment of a channel between the access network device and the terminal. Among them, the user plane connection is a QoS flow that can be established between the UPF network element and the access network device to transmit data.

[0039] The AMF network element can be used to manage the terminal's access to the core network, such as terminal location update, network registration, access control, terminal mobility management, terminal attachment and detachment, etc. The AMF network element can also provide control plane storage resources for the session while providing services for the terminal's session, to store the session identifier, the SMF network element identifier associated with the session identifier, etc.

[0040] The SMF network element can be used to select a user plane network element for the terminal, redirect the user plane network element for the terminal, allocate an Internet Protocol (IP) address to the terminal, establish a bearer (also called a session) between the terminal and the UPF network element, modify and release the session, and control QoS. The session can be a protocol data unit (PDU) session.

[0041] The PCF network element is used to provide policies to the AMF network element and the SMF network element, such as QoS policy and slice selection policy.

[0042] The AF network element is used to interact with the 3GPP core network elements to support application-affected data routing, access network exposure functions, and interact with the PCF network elements for policy control.

[0043] A DN can provide data services to users on networks such as the IP Multimedia Service (IMS) and the Internet. A DN can contain multiple application servers (ASs) that provide different application services, such as carrier services, Internet access, or third-party services. The ASs can implement the AF functionality.

[0044] NSSF is used for network slice selection and supports the following functions: selecting the set of network slice instances serving the UE; determining the allowed network slice selection assistance information (NSSAI) and, when necessary, determining the mapping to the contracted single-network slice selection assistance information (S-NSSAI); determining the configured NSSAI and, when necessary, determining the mapping to the contracted S-NSSAI; determining the set of AMFs that may be used to query the UE, or determining a list of candidate AMFs based on the configuration.

[0045] AUSF is used to receive the request from AMF to authenticate the terminal, request the key from UDM, and then forward the issued key to AMF for authentication processing.

[0046] UDM includes functions such as the generation and storage of user contract data, management of authentication data, and supports interaction with external third-party servers.

[0047] NEF is used for capability exposure. That is, based on NEF, network capabilities can be exported to external networks. External, untrusted applications can access core network data through NEF to ensure network security. NEF can also provide external application QoS capability exposure, event subscription, and AF request distribution.

[0048] The NRF is used to register, manage, and monitor the status of core network elements, enabling automated management of these elements. Upon startup, a core network element must register with the NRF before it can provide services. Registration information may include the core network element's type, address, and service list.

[0049] In addition, some networks (such as 5G networks) have added a network data analytics function (NWDAF) to the core network. Based on NWDAF, data can be collected from various core network elements and network management systems, and big data statistics, analysis, or intelligent data analysis can be performed to obtain network-side analysis or prediction data, thereby assisting various network elements to more effectively control terminal device access based on the data analysis results.

[0050] In some communication systems (such as 5G systems), core network elements may also be referred to as network functions (NFs).

[0051] The network elements in Figure 1 can be network components in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). It should be noted that the network architecture shown in the above figure is only an example of the network elements included in the entire network architecture. In the embodiments of the present application, the network elements included in the entire network architecture are not limited.

[0052] Those skilled in the art will appreciate that the network architecture shown in FIG1 does not limit the network architecture. In a specific implementation, the network architecture may include more or fewer network elements than shown, or may combine certain network elements. It should be understood that in FIG1 , the AN or RAN is represented by (R)AN.

[0053] Zero-power communication technology

[0054] With the development of wireless communication technology, it has become a trend to integrate wireless communication systems with various vertical industries such as logistics, manufacturing, transportation, and energy.

[0055] However, in these industries, terminal devices typically require low cost, small size (e.g., ultra-thin), maintenance-free, and long lifespan. To address this, zero-power communication technology has been proposed. Zero-power communication systems can be used in scenarios such as wireless industrial sensor networks, smart agriculture, smart warehousing and logistics, and smart homes.

[0056] Zero-power communication technology is suitable for short-range, low-speed wireless communications. For example, 5G systems, as specified in the 3GPP standard, support network access for zero-power devices. These zero-power devices, as supported by the 3GPP standard, are primarily targeted at scenarios with the following characteristics: extreme environments unsuitable for standard devices; extremely low power consumption and cost; and battery-free devices.

[0057] The zero-power communication technology is described below with reference to FIG2 .

[0058] FIG2 illustrates the architecture of a zero-power communication system 200 applicable to an embodiment of the present application. The architecture shown in FIG2 includes communication devices such as a reader / writer 210 and a zero-power terminal device 220. The reader / writer 210 can be used to read information from the zero-power terminal device 220 and / or write information to the zero-power terminal device 220.

[0059] It should be noted that the reader / writer 210 is a communication device with reading and writing functions, and the device can be a network device or a terminal device.

[0060] The reader / writer 210 can be used to send a wireless power supply signal to the zero-power terminal device 220 to power the terminal. Accordingly, the terminal 220 can send data to the reader / writer 210 or other communication devices via backscatter signals.

[0061] The zero-power terminal device 220 can be an electronic tag or an ordinary device. The electronic tag can be composed of a coupling component and a chip. Each electronic tag can have a unique electronic code. The electronic tag can be placed on the target to be measured to achieve the purpose of marking the target object. The reader can not only read the information on the electronic tag, but also write information on the electronic tag. The reader can also provide the electronic tag with the energy required for communication. After the electronic tag enters the electromagnetic field, it can receive the radio frequency signal emitted by the reader. The electronic tag can use the energy obtained from the electromagnetic field generated in space to transmit the information stored in the electronic tag. The reader can read the information and decode it to identify the electronic tag.

[0062] Zero-power technology primarily combines RF energy harvesting, backscattering, and low-power computing to achieve the advantage of eliminating the need for power supply devices. The core of RF energy harvesting is to convert RF energy into DC. This energy can be stored in batteries or capacitors, or it can be directly used to drive logic circuits, digital chips, or sensors, completing functions and applications such as modulation and transmission of backscattered signals and collection and processing of sensor information.

[0063] As shown in FIG2 , the zero-power terminal device 220 may include an energy harvesting module 221 and a backscatter communication module 222. The energy harvesting module 221 may utilize radio frequency energy harvesting technology to harvest energy. The backscatter communication module 222 may utilize backscatter technology to perform backscatter communication. As shown in FIG2 , the zero-power terminal device 220 may also include one or more of a low-power computing module 223, a sensor module 224, and a memory 225.

[0064] In zero-power communication technology, terminals can be divided into three categories based on their energy source and energy usage: passive zero-power terminals, semi-passive zero-power terminals, and active zero-power terminals. These categories are described below.

[0065] 1) Passive zero-power terminal

[0066] Passive zero-power terminals do not require internal batteries. When a zero-power terminal approaches a reader (such as a radio frequency identification (RFID) system), it is within the near-field radiation generated by the reader's antenna. The passive zero-power terminal antenna generates an induced current through electromagnetic induction, which drives the low-power chip circuit of the zero-power terminal, thereby achieving forward link signal demodulation and backward link signal modulation. For backscatter links, the passive zero-power terminal uses backscattering to transmit signals.

[0067] It can be seen that the passive zero-power terminal does not require a built-in battery to drive either the forward link or the reverse link, and is a true zero-power terminal.

[0068] Passive zero-power terminals do not require batteries, and their RF and baseband circuits are very simple. For example, they do not require low-noise amplifiers (LNAs), power amplifiers (PAs), crystal oscillators, or analog-to-digital converters (ADCs). Therefore, passive zero-power terminals have many advantages, including small size, light weight, low price, and long service life.

[0069] Passive zero-power terminals also feature: 1) no battery; 2) the ability to draw energy from the surrounding environment (e.g., radio waves, solar energy, wind energy, mechanical kinetic energy, etc.); and 3) no universal subscriber identity module (USIM) card. These devices can also store a certain amount of energy from the surrounding environment, but the amount is minimal. Therefore, compared to standard mobile phone terminals, passive zero-power terminals support significantly fewer functional logic.

[0070] 2) Semi-passive zero-power terminal

[0071] Semi-passive zero-power terminals do not have conventional batteries themselves, but instead use radio frequency (RF) energy harvesting modules to harvest radio wave energy and store it in an energy storage unit (such as a capacitor). This energy storage unit then drives the terminal's low-power chip circuitry, enabling forward link signal demodulation and backward link signal modulation. For backscatter links, semi-passive zero-power terminals use backscattering for signal transmission.

[0072] As can be seen, semi-passive zero-power terminals do not require internal batteries for either the forward link or the reverse link. Although they utilize energy stored in the energy storage unit, this energy comes from radio energy harvested by the energy harvesting module. Therefore, this type of terminal device is also a true zero-power terminal.

[0073] Semi-passive zero-power consumption terminals inherit many advantages of passive zero-power consumption terminals, namely, small size, light weight, very low price, long service life and many other advantages.

[0074] 3) Active zero-power terminal

[0075] In some scenarios, zero-power terminals can also be active zero-power terminals, which can have built-in batteries. The battery is used to drive the low-power chip circuits of the zero-power terminal, thereby performing tasks such as demodulating forward link signals and modulating reverse link signals. However, for backscatter links, zero-power terminals use backscattering to transmit signals. Therefore, the zero-power nature of these terminals is primarily reflected in the fact that reverse link signal transmission does not require the terminal's own power, but instead uses backscattering.

[0076] Active zero-power terminals can use built-in batteries to power RFID chips, increasing the tag's read and write distance and improving communication reliability. Therefore, these terminals are suitable for use in scenarios with relatively high requirements for communication distance and read latency.

[0077] In some embodiments, the above-mentioned zero-power terminal device may include: an ambient power-enabled internet of things (AIoT) device.

[0078] In some embodiments, the first terminal device can implement indirect communication between the second terminal device and the network device, that is, the second terminal device can implement indirect communication with the network device through the first terminal device.

[0079] In Figure 3, the first terminal device 320 can be, for example, an ordinary terminal device, and the second terminal device 310 can be, for example, an AIoT terminal device (such as a tag). As shown in Figure 3, the first terminal device 320 can serve as a reader / writer for the second terminal device 330, thereby realizing backscatter communication between the first terminal device 320 and the second terminal device 330. Through the first terminal device 320, the second terminal device 330 can communicate with the network device 310. The network device 310 can be, for example, a core network element (such as an AF network element). The first terminal device 320 can communicate with the network device through a network (such as a 3GPP network or other wired broadband network).

[0080] In some scenarios, the first terminal device 320 can collect information about the second terminal device 330 through a private interface. The first terminal device 320 reports the collected data about the second terminal device 330 to the AF network element via the network. In this case, only the first terminal device can identify and perceive the second terminal device; the network cannot perceive the second terminal device 330.

[0081] If the network is unaware of the second terminal device, only the first terminal device can obtain information about the second terminal device through a private interface. Because private interfaces cannot enable intercommunication between terminal devices manufactured by different manufacturers, consumers must purchase both the first and second terminal devices to achieve indirect communication with the second terminal device. Alternatively, the manufacturer or provider of the second terminal device can deploy its own service server to alleviate the bundling between the first and second terminal devices to some extent. However, this increases costs for the manufacturer or service provider and further complicates the network structure.

[0082] The present application proposes a first core network network element. The first core network network element can be used to collect information of a second terminal device. For example, the first core network network element can be used to collect information of a specific terminal device. The specific terminal device can be a terminal device that meets the first condition. In some embodiments, the first condition may include: the terminal device performs non-direct communication, that is, the first core network network element may have the function of collecting or acquiring information of the terminal device performing non-direct communication. In some embodiments, the first condition may include: the terminal device is an AIoT device or a zero-power device, that is, the first core network network element may have the function of collecting or acquiring information of the AIoT device or the zero-power device.

[0083] When the first core network element collects information about the second terminal device, the network side can obtain the information about the second terminal device and thus perceive the second terminal device. In this case, the first terminal device does not need to obtain the information about the second terminal device through a private interface, thus achieving unbinding of the first and second terminal devices. For consumers, they can purchase a first terminal device from any manufacturer and the network side can perceive the information about the second terminal device. For the manufacturer or supplier of the second terminal device, the manufacturer or supplier does not need to deploy its own server, thus reducing costs and network complexity.

[0084] As shown in FIG. 4 , the information of the second terminal device may be indicated by the first information.

[0085] Figure 4 is a schematic flow chart of a method for communication provided by an embodiment of the present application. The method shown in Figure 4 can be performed by a first terminal device and a first core network element. The method shown in Figure 4 can include step S410.

[0086] In step S410, a first terminal device sends first information. Correspondingly, a first core network element receives the first information. The first information may be sent via a user plane message.

[0087] As described above, the first information may be used to indicate information about the second terminal device. The information about the second terminal device may be information directly or indirectly related to the second terminal device. For example, the information about the second terminal device may include one or more of the following: an identifier (ID) of the second terminal device, a signal (which may include data, indication information, etc.) sent by the second terminal device.

[0088] The first core network element may be configured to collect information about the second terminal device. Specifically, the first core network element may have the function of collecting information about the second terminal device. The second terminal device may be a specific type of terminal device. For example, the second terminal device may be an AIoT device or a zero-power device. In other words, the first core network element may have the function of collecting or acquiring information about the AIoT device or the zero-power device.

[0089] It should be noted that the first information can be sent directly, that is, the first information is sent directly by the first terminal device to the first core network element. Alternatively, the first information can be sent indirectly, that is, the first information can be sent by the first terminal device to other communication devices, and the other communication devices forward the first information to the first core network element.

[0090] After receiving the first information, the first core network element may report the first information to other core network elements. For example, the first core network element may report the first information to the AF.

[0091] The method shown in FIG4 may further include step S405. The method shown in FIG4 may be performed by a second core network element and a first terminal device. The second core network element may be a different element from the first core network element. For example, the second core network element may include one or more of the following: an SMF element and an AF element.

[0092] In step S405, the second core network element may send information about the first core network element. Correspondingly, the first terminal device may receive the information about the first core network element.

[0093] The information of the first core network element may be any information related to the first core network element. For example, the information of the first core network element may include one or more of the following information of the first core network element: address, link, fully qualified domain name (FQDN), DNN address, and single network slice selection assistance information (S-NSSAI).

[0094] As shown in Figure 4, step S405 may be performed earlier than step S410. That is, before the first terminal device sends the first information, the first terminal device may receive information from the first core network element.

[0095] It is understandable that the first terminal device can obtain the information of the first core network element through the second core network element, thereby determining that the first core network element can be used to collect information of the second terminal device, and then enable the first terminal device to determine the destination address of the first information.

[0096] The first core network element may be determined by the first terminal device and / or the network device. In other words, the first core network element may be determined by the terminal device or the network. The network device that determines the first core network element may be, for example, the second core network element.

[0097] If the first core network element is determined by the network side, the first terminal device may send a message requesting discovery of the first core network element. In response to this message, the second core network element may reply with information about the first core network element, thereby enabling the first terminal device to discover the first core network element. In other words, step S405 may include: in response to receiving the request to discover the first core network element, the second core network element sending information about the first core network element.

[0098] In the case where the first core network element is determined by the first terminal device, the first terminal device may send second information so that the network side can determine the first core network element. The second information may be used to indicate information of the first core network element.

[0099] It should be noted that the step of the first terminal device sending the second information can be implemented in combination with the step of the first terminal device sending the first information. For example, before the first terminal device sends the first information, the first terminal device can send the second information.

[0100] As an implementation, the first core network element can be determined or discovered during the PDU session establishment process. For example, step S405 can be performed during the PDU session establishment process. It is understood that some steps of the PDU session establishment process can be reused to determine, discover, or select the first core network element. In this case, the determination, discovery, or selection process of the first core network element consumes fewer resources and is more efficient.

[0101] In some embodiments, the message requesting discovery of the first core network element may be implemented based on the first request. The first terminal device may send the first request. The first request may be used to request establishment of a PDU session, and may also be used to request discovery of the first core network element. When a network device (e.g., a second core network element) receives the first request, the network device may select or determine the first core network element for the first terminal device.

[0102] It should be noted that the step of the first terminal device sending the first request can be implemented in conjunction with the step of the first terminal device sending the first information. For example, the first terminal device can send the first request before sending the first information. If the first terminal device receives a response to the first request, the first terminal device can send the first information.

[0103] This application does not limit the message that carries the first request. As an implementation method, the first request can be carried in an uplink (UL) non-access stratum (NAS) transmission message. For example, the first request can be carried in the request type (request type) in the uplink NAS transmission message. That is, the request type can indicate that the first request is used to discover the first core network element. In some embodiments, based on the request type, the AMF can select a suitable SMF. The selected SMF can select a suitable UPF to serve the first terminal device.

[0104] In some embodiments, the first request or the message carrying the first request (such as the uplink NAS transmission message described above) can also be used to indicate the first indication information. The first indication information may be information related to the selection or determination of the first core network element. That is, based on the first indication information, the network device can select or determine a suitable first core network element, thereby optimizing the communication process. For example, when there are multiple optional core network elements for collecting AIoT device information in the network, the network side can further select the core network element for collecting AIoT device information that meets the requirements of the first indication information as the first core network element.

[0105] The first indication information may include, for example, one or more of the following information: an indication of a core network element requesting discovery of terminal device information, an identifier of an AF, an identifier of a service provider, and an identifier of an application.

[0106] In some embodiments, the indication of requesting to discover the core network element that collects the terminal device information can be represented by one bit. As an implementation method, the one bit can be 0 or 1. For example, when the indication of requesting to discover the core network element that collects the terminal device information is 1, the terminal device requests to discover the first core network element through the indication; when the indication of requesting to discover the core network element that collects the terminal device information is 0, the terminal device does not request to discover the first core network element through the indication. Alternatively, when the indication of requesting to discover the core network element that collects the terminal device information is 0, the terminal device requests to discover the first core network element through the indication; when the indication of requesting to discover the core network element that collects the terminal device information is 1, the terminal device does not request to discover the first core network element through the indication.

[0107] It should be noted that, when the first core network element is used to collect AIoT device information, the indication of requesting to discover the core network element for collecting terminal device information can also be called the core network element indication for collecting AIoT device information (AIoT device collection NF indication).

[0108] In some embodiments, the first indication information may be included in a protocol configuration option (PCO) in the first request. During the process of establishing a PDU session by the terminal device, the PCO may indicate to the network side (e.g., an SMF network element) that the terminal device needs to establish an address or connection for discovering and collecting terminal device information from a core network element. Based on the first indication information, the second core network element may send information about the first core network element to the first terminal device.

[0109] In some embodiments, the second core network element may also actively send information of the first core network element to the first terminal device.

[0110] As an implementation, the second core network element may send the information of the first core network element via PCO. For example, when the first indication information is transmitted via PCO, the second core network element may send the information of the first core network element via PCO.

[0111] As another implementation method, the information of the first core network element can be indicated by the parameters for establishing a PDU session. For example, the second core network element can be an AF element. The AF element can configure the parameters for establishing a PDU session to the first terminal device through the PCF. The parameters may include the DNN and / or S-NSSAI of the first core network element. It can be understood that in this way, the establishment of a PDU session corresponding to the core network element that collects terminal device information can be directly indicated during the PDU session establishment process.

[0112] This application does not limit the type of the first core network element. For example, the first core network element can be a core network element specifically configured to collect terminal device information. As a possible example, the first core network element can be different from any of the core network elements shown in Figure 1. A core network element specifically configured to collect terminal device information can make its functions relatively independent, thereby improving its operational efficiency. Alternatively, the first core network element can be any of the types of core network elements described above. In other words, the first core network element can not only be used to collect terminal device information but also perform other functions. On the one hand, this can reduce the number of core network elements required, thereby reducing the network deployment costs of the communication system. On the other hand, the first core network element can be the core network element selected during the PDU session establishment process. It will be appreciated that the first core network element can be determined simultaneously during the PDU session establishment process, thereby simplifying the process of discovering or determining the first core network element.

[0113] Optionally, the first core network element may be a UPF element. The first core network element may be determined by a UPF selection process during the PDU session establishment process. For example, during the PDU session establishment process, the SMF selects a UPF that needs to have a terminal device information collection function.

[0114] In some embodiments, the UPF may be determined based on the first indication information and / or the second information. The description of the first indication information and the second information can be found above and will not be repeated here.

[0115] For ease of understanding, the present application is described in detail below through Example 1 and Example 2.

[0116] Example 1

[0117] Figure 5 is a schematic flowchart of a method for communication provided in Example 1. The method shown in Figure 5 can be performed by tags, a terminal device serving as a reader / writer for the tags (represented by a UE in Figure 5 ), a gNB, an AMF, an SMF, an UPF, a core network element that collects AIoT device information, and an AF.

[0118] The method shown in FIG. 5 may include steps S510 - S540 .

[0119] Step S510: The UE establishes a PDU session. The process of establishing a PDU session may include at least one of the following first to third operations. The first to third operations are described below.

[0120] The first operation: The UE sends an uplink NAS transmission message to the AMF. The request type indication in the uplink NAS transmission message is the core network element indication for collecting AIoT device information (AIoT device collection NF indication). The AMF can select a suitable SMF according to the request type. Then, the SMF can select a suitable UPF to serve the UE. Among them, the core network element indication for collecting AIoT device information can be 0 or 1. The core network element indication for collecting AIoT device information or the uplink NAS transmission message may include one or more of the following information: AF information (for example, including the AF ID and / or the service provider ID), the application ID, etc.

[0121] Second operation: The AF configures the parameters for establishing a PDU session to the UE through the PCF. These parameters may include the DNN and / or S-NSSAI corresponding to the core network element that collects AIoT device information. In other words, during the PDU session establishment process, the AF can directly carry the DNN and / or S-NSSAI to indicate the establishment of a PDU session corresponding to the core network element that collects AIoT device information.

[0122] The third operation: During the process of establishing a PDU session, the UE indicates to the SMF through the PCO that the address or connection of the core network element for collecting AIoT device information needs to be established. According to the instruction, the SMF can directly send the address or FQDN of the core network element for collecting AIoT device information to the UE through the PCO. In addition, the PCO sent by the UE to the SMF may also include one or more of the following information: AF information (for example, including the AF ID and / or the service provider ID), the application ID, etc.

[0123] Step S520: The UE obtains tag information, which may include tag identification information.

[0124] In step S530, the UE reports the tag identification information to the core network element that collects AIoT device information through a user plane message.

[0125] The address of the core network element that collects AIoT device information can be obtained through the PCO method in step S510, or the FQDN of the core network element that collects AIoT device information can be directly constructed for DNS resolution.

[0126] In step S540, the core network element that collects AIoT device information decides to which AF to report the tag data based on the tag identification information.

[0127] Through the method provided in Example 1, the UE can obtain the core network element deployed in the operator network to collect AIoT device information, thereby realizing the unbinding between the UE and the tag, and then realizing communication between UEs and tags manufactured by different manufacturers.

[0128] Example 2

[0129] Figure 6 is a schematic flow chart of a communication method provided in the second embodiment of the present invention. The method shown in Figure 6 can be performed by tags (represented by tags in Figure 6), terminal devices serving as tag readers (represented by UE in Figure 6), 3GPP networks, UPFs, and AFs. 3GPP networks are used to indicate the network devices involved in this method. For example, the 3GPP network may include the gNB, AMF, and SMF shown in Figure 5.

[0130] The method shown in Figure 6 may include steps S610 to S640. The difference between the second embodiment and the first embodiment is that the UPF integrates the function of collecting AIoT device information.

[0131] Step 610: The UE establishes a PDU session. The process of establishing a PDU session may include at least one of the following fourth to sixth operations. The first to third operations are described below.

[0132] Fourth operation: UE sends an uplink NAS transmission message to AMF. AMF can select a suitable SMF according to the request type. Then, SMF can select a suitable UPF to serve the UE. Among them, the core network element indication for collecting AIoT device information can be 0 or 1. The core network element indication or uplink NAS transmission message for collecting AIoT device information may include one or more of the following information: AF information (for example, including the AF ID and / or the service provider ID), application ID, etc. It should be noted that when SMF selects UPF, it is necessary to select a UPF that supports the function of collecting AIoT device information.

[0133] The fifth operation: Or the AF configures the parameters for establishing a PDU session to the UE through the PCF. The parameters may include: the DNN and / or S-NSSAI corresponding to the core network element that collects AIoT device information. That is, during the PDU session establishment process, the AF can directly carry the DNN and / or S-NSSAI to indicate the establishment of a PDU session corresponding to the core network element that collects AIoT device information.

[0134] It should be noted that during the establishment of a PDU session, SMF needs to select a UPF that supports the function of collecting AIoT device information based on S-NSSAI.

[0135] The sixth operation: During the UE establishment of the PDU session, the UE indicates to the SMF through the PCO that the UE needs to select the UPF that supports the function of collecting AIoT device information. During the PDU session establishment process, the SMF can notify the UE through the PCO that the UPF that has selected the function of collecting AIoT device information has been selected.

[0136] Step S620: The UE obtains tag information, where the tag information may include tag identification information.

[0137] Step S630: The UE reports the identification information of the tag to the UPF via a user plane message.

[0138] In step S640, the UPF determines to which AF to report the tag data according to the tag identification information.

[0139] Through the method provided in Example 2, the UE can learn that by deploying the UPF in the operator network to collect AIoT device information, the UE and the tag can be untied, thereby realizing communication between UEs and tags manufactured by different manufacturers.

[0140] The above describes the method embodiment of the present application in detail, and the following describes the device embodiment of the present application in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so for parts not described in detail, reference can be made to the previous method embodiment.

[0141] FIG7 is a schematic structural diagram of a terminal device 700 provided in an embodiment of the present application. The terminal device 700 is a first terminal device and includes a first sending unit 710 .

[0142] The first sending unit 710 is used to send first information to the first core network element through a user plane message; wherein the first information is used to indicate information of the second terminal device.

[0143] In some embodiments, the first core network element is determined during the PDU session establishment process.

[0144] In some embodiments, the terminal device 700 is specifically used to send a first request to establish a PDU session; wherein the first request is also used to request discovery of a first core network element.

[0145] In some embodiments, the first request is carried in an uplink non-access stratum (NAS) transmission message.

[0146] In some embodiments, the first request or the message carrying the first request is used to indicate first indication information, and the first indication information includes one or more of the following information: an indication of a core network element requesting discovery of terminal device information; an identifier of the AF; an identifier of the service provider; an identifier of the application.

[0147] In some embodiments, the first indication information is included in a PCO in the first request.

[0148] In some embodiments, the terminal device 700 further includes: a first receiving unit, configured to receive information of the first core network element sent by the second core network element.

[0149] In some embodiments, the PDU establishment process includes the first terminal device sending second information, and the second information is used to indicate information of the first core network network element.

[0150] In some embodiments, the terminal device 700 further includes: an acquisition unit, configured to acquire parameters for establishing a PDU session; wherein the parameters are used to indicate information of the first core network element.

[0151] In some embodiments, the first core network element is a UPF element or a core network element that collects terminal device information.

[0152] In some embodiments, when the first core network element is a UPF element, the first core network element is determined by the UPF selection process during the PDU session establishment process.

[0153] In some embodiments, the UPF is determined based on first indication information and / or second information, the first indication information is used to indicate a request to discover information of the first core network element, and the second information is used to indicate information of the first core network element.

[0154] In some embodiments, the second terminal device is an AIoT device, and the first terminal device is a reader / writer of the AIoT device.

[0155] FIG8 is a schematic structural diagram of a core network element 800 provided in the present application. The core network element 800 is a first core network element and includes a second receiving unit 810.

[0156] The second receiving unit 810 is used to receive first information sent by the first terminal device through a user plane message; wherein the first information is used to indicate information of the second terminal device.

[0157] In some embodiments, the first core network element is determined during the PDU session establishment process.

[0158] In some embodiments, the first core network element is a UPF element or a core network element used to collect terminal device information.

[0159] In some embodiments, when the first core network element is a UPF element, the first core network element is determined by the UPF selection process during the PDU session establishment process.

[0160] In some embodiments, the information of the first core network element is sent by the second core network element to the first terminal device during the PDU session establishment process.

[0161] In some embodiments, the second terminal device is an AIoT device, and the first terminal device is a reader / writer of the AIoT device.

[0162] FIG9 is a schematic structural diagram of a core network element 900 provided in an embodiment of the present application. The core network element 900 is a second core network element and includes a second sending unit 910.

[0163] The second sending unit 910 is used to send information of the first core network element to the first terminal device; wherein, the first core network element is used to receive the first information through a user plane message, and the first information is used to indicate information of the second terminal device.

[0164] In some embodiments, the first core network element is determined during the PDU session establishment process.

[0165] In some embodiments, the core network element 900 is specifically used to: receive a first request to establish a PDU session; wherein the first request is also used to request discovery of a first core network element.

[0166] In some embodiments, the first request is carried in an uplink NAS transmission message.

[0167] In some embodiments, the first request or the message carrying the first request is used to indicate first indication information, and the first indication information includes one or more of the following information: an indication of a core network element requesting discovery of terminal device information; an identifier of the AF; an identifier of the service provider; an identifier of the application.

[0168] In some embodiments, the first indication information is included in a PCO in the first request.

[0169] In some embodiments, the PDU establishment process includes the second core network element receiving second information, where the second information is used to indicate information of the first core network element.

[0170] In some embodiments, the first core network element is a UPF element or a core network element used to collect terminal device information.

[0171] In some embodiments, when the first core network element is a UPF element, the first core network element is determined by the UPF selection process during the PDU session establishment process.

[0172] In some embodiments, the UPF is determined based on first indication information and / or second information, the first indication information is used to indicate a request to discover information of the first core network element, and the second information is used to indicate information of the first core network element.

[0173] In some embodiments, the second terminal device is an AIoT device, and the first terminal device is a reader / writer of the AIoT device.

[0174] In an optional embodiment, the first sending unit 710, the second receiving unit 810 or the second sending unit 910 may be a transceiver 1030. The terminal device 700, the core network element 800 or the core network element 900 may further include a memory 1020 and / or a processor 1010, as specifically shown in FIG10 .

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

[0176] The device 1000 may include one or more processors 1010. The processor 1010 may support the device 1000 to implement the method described in the method embodiment above. The processor 1010 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.

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

[0178] The apparatus 1000 may further include a transceiver 1030. The processor 1010 may communicate with other devices or chips via the transceiver 1030. For example, the processor 1010 may transmit and receive data with other devices or chips via the transceiver 1030.

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

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

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

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

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

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

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

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

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

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

[0189] 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."

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

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

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

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

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

[0195] 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 the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for communication, characterized in that The method comprises: The first terminal device sends the first information to the first core network element through a user plane message; The first information is used to indicate information of the second terminal device.

2. The method according to claim 1, characterized in that The method further comprises: The first terminal device sends a first request to establish a protocol data unit (PDU) session; The first request is also used to request discovery of the first core network element.

3. The method according to claim 2, characterized in that The first request is carried in an uplink non-access layer NAS transmission message.

4. The method according to claim 2 or 3, characterized in that: The first request or the message carrying the first request is used to indicate first indication information, where the first indication information includes one or more of the following information: An instruction to request discovery of a core network element that collects terminal device information; Identification of application function AF; The identification of the service provider; The ID of the application.

5. The method according to claim 4, characterized in that The first indication information is included in a protocol configuration option PCO in the first request.

6. The method according to claims 1-5, characterized in that: Also includes: The first terminal device receives information of the first core network element sent by the second core network element.

7. The method according to claim 1, characterized in that The method further comprises: The first terminal device sends second information; The second information is used to indicate information of the first core network element.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: The first terminal device obtains parameters for establishing a PDU session; The parameter is used to indicate information of the first core network element.

9. The method according to any one of claims 1 to 8, characterized in that The first core network element is a user plane function UPF element or a core network element that collects terminal device information.

10. The method according to claim 9, characterized in that In the case where the first core network element is the UPF element, the first core network element is determined by the UPF selection process during the PDU session establishment process.

11. The method according to claim 10, characterized in that The UPF is determined based on first indication information and / or second information, wherein the first indication information is used to indicate a request to discover information of the first core network element, and the second information is used to indicate information of the first core network element.

12. The method according to any one of claims 1 to 11, characterized in that The second terminal device is an environment collection Internet of Things (AIoT) device, and the first terminal device is a reader / writer of the AIoT device.

13. The method according to any one of claims 1 to 12, characterized in that The first core network element is determined during the PDU session establishment process.

14. A method for communication, characterized in that The method comprises: The first core network element receives the first information sent by the first terminal device through a user plane message; The first information is used to indicate information of the second terminal device.

15. The method according to claim 14, characterized in that The first core network network element is a user plane function UPF network element or a core network network element used to collect terminal device information.

16. The method according to claim 15, characterized in that In the case where the first core network element is the UPF network element, the first core network element is determined by the UPF selection process during the protocol data unit PDU session establishment process.

17. The method according to claim 16, characterized in that The information of the first core network element is sent by the second core network element to the first terminal device during the PDU session establishment process.

18. The method according to any one of claims 14 to 17, characterized in that: The second terminal device is an environment collection Internet of Things (AIoT) device, and the first terminal device is a reader / writer of the AIoT device.

19. The method according to any one of claims 14 to 18, characterized in that The first core network element is determined during the PDU session establishment process.

20. A method for communication, characterized in that The method comprises: The second core network network element sends information of the first core network network element to the first terminal device; The first core network element is used to receive first information via a user plane message, and the first information is used to indicate information of a second terminal device.

21. The method according to claim 20, characterized in that The method further comprises: The second core network element receives a first request to establish a protocol data unit (PDU) session; The first request is also used to request discovery of the first core network element.

22. The method according to claim 21, characterized in that The first request is carried in an uplink non-access layer NAS transmission message.

23. The method according to claim 21 or 22, characterized in that The first request or the message carrying the first request is used to indicate first indication information, where the first indication information includes one or more of the following information: An instruction to request discovery of a core network element that collects terminal device information; Identification of application function AF; The identification of the service provider; The ID of the application.

24. The method according to claim 23, characterized in that The first indication information is included in a protocol configuration option PCO in the first request.

25. The method according to claim 20, characterized in that The method further comprises: The second core network element receives second information; The second information is used to indicate information of the first core network element.

26. The method according to any one of claims 20 to 25, characterized in that The first core network network element is a user plane function UPF network element or a core network network element used to collect terminal device information.

27. The method according to claim 26, characterized in that In the case where the first core network element is the UPF element, the first core network element is determined by the UPF selection process during the PDU session establishment process.

28. The method according to claim 27, characterized in that The UPF is determined based on first indication information and / or second information, wherein the first indication information is used to indicate a request to discover information of the first core network element, and the second information is used to indicate information of the first core network element.

29. The method according to any one of claims 20 to 28, characterized in that The second terminal device is an environment collection Internet of Things (AIoT) device, and the first terminal device is a reader / writer of the AIoT device.

30. The method according to any one of claims 20 to 29, characterized in that The first core network element is determined during the PDU session establishment process.

31. A terminal device, characterized in that: The terminal device is a first terminal device, and the terminal device includes: A first sending unit, configured to send first information to a first core network element through a user plane message; The first information is used to indicate information of the second terminal device.

32. The terminal device according to claim 31, characterized in that: The terminal device is specifically used for: Sending a first request to establish a protocol data unit (PDU) session; The first request is also used to request discovery of the first core network element.

33. The terminal device according to claim 32, characterized in that: The first request is carried in an uplink non-access layer NAS transmission message.

34. The terminal device according to claim 32 or 33, characterized in that: The first request or the message carrying the first request is used to indicate first indication information, where the first indication information includes one or more of the following information: An instruction to request discovery of a core network element that collects terminal device information; Identification of application function AF; The identification of the service provider; The ID of the application.

35. The terminal device according to claim 34, characterized in that: The first indication information is included in a protocol configuration option PCO in the first request.

36. The terminal device according to claims 31-35, characterized in that: Also includes: The first receiving unit is used to receive information of the first core network element sent by the second core network element.

37. The terminal device according to claim 31, characterized in that: The PDU establishment process includes the first terminal device sending second information, and the second information is used to indicate information of the first core network network element.

38. The terminal device according to any one of claims 31 to 37, characterized in that: Also includes: An acquisition unit, used for acquiring parameters for establishing a PDU session; The parameter is used to indicate information of the first core network element.

39. The terminal device according to any one of claims 31 to 38, characterized in that: The first core network element is a user plane function UPF element or a core network element that collects terminal device information.

40. The terminal device according to claim 39, characterized in that: In the case where the first core network element is the UPF element, the first core network element is determined by the UPF selection process during the PDU session establishment process.

41. The terminal device according to claim 40, characterized in that: The UPF is determined based on first indication information and / or second information, wherein the first indication information is used to indicate a request to discover information of the first core network element, and the second information is used to indicate information of the first core network element.

42. The terminal device according to any one of claims 31 to 41, characterized in that: The second terminal device is an environment collection Internet of Things (AIoT) device, and the first terminal device is a reader / writer of the AIoT device.

43. The terminal device according to any one of claims 31-42, characterized in that: The first core network element is determined during the PDU session establishment process.

44. A core network element, characterized in that: The core network element is a first core network element, and the core network element includes: A second receiving unit, configured to receive first information sent by a first terminal device through a user plane message; The first information is used to indicate information of the second terminal device.

45. The core network element according to claim 44, characterized in that: The first core network network element is a user plane function UPF network element or a core network network element used to collect terminal device information.

46. ​​The core network element according to claim 45, characterized in that: In the case where the first core network element is the UPF network element, the first core network element is determined by the UPF selection process during the protocol data unit PDU session establishment process.

47. The core network element according to claim 46, characterized in that: The information of the first core network element is sent by the second core network element to the first terminal device during the PDU session establishment process.

48. The core network element according to any one of claims 44 to 47, characterized in that: The second terminal device is an environment collection Internet of Things (AIoT) device, and the first terminal device is a reader / writer of the AIoT device.

49. The core network element according to any one of claims 44 to 48, characterized in that: The first core network element is determined during the PDU session establishment process.

50. A core network element, characterized in that: The core network element is a second core network element, and the core network element includes: A second sending unit, configured to send information about a first core network element to a first terminal device; The first core network element is used to receive first information via a user plane message, and the first information is used to indicate information of a second terminal device.

51. The core network element according to claim 50, characterized in that: The core network element is specifically used for: Receiving a first request to establish a protocol data unit (PDU) session; The first request is also used to request discovery of the first core network element.

52. The core network element according to claim 51, characterized in that: The first request is carried in an uplink non-access layer NAS transmission message.

53. The core network element according to claim 51 or 52, characterized in that: The first request or the message carrying the first request is used to indicate first indication information, where the first indication information includes one or more of the following information: An instruction to request discovery of a core network element that collects terminal device information; Identification of application function AF; The identification of the service provider; The ID of the application.

54. The core network element according to claim 53, characterized in that: The first indication information is included in a protocol configuration option PCO in the first request.

55. The core network element according to claim 50, characterized in that: The core network element is specifically used for: receiving second information; The second information is used to indicate information of the first core network element.

56. The core network element according to any one of claims 50-55, characterized in that: The first core network network element is a user plane function UPF network element or a core network network element used to collect terminal device information.

57. The core network element according to claim 56, characterized in that: In the case where the first core network element is the UPF element, the first core network element is determined by the UPF selection process during the PDU session establishment process.

58. The core network element according to claim 57, characterized in that: The UPF is determined based on first indication information and / or second information, wherein the first indication information is used to indicate a request to discover information of the first core network element, and the second information is used to indicate information of the first core network element.

59. The core network element according to any one of claims 50-58, characterized in that: The second terminal device is an environment collection Internet of Things (AIoT) device, and the first terminal device is a reader / writer of the AIoT device.

60. The core network element according to any one of claims 50-59, characterized in that: The first core network element is determined during the PDU session establishment process.

61. A terminal device, characterized in that: The method comprises 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 terminal device executes the method according to any one of claims 1 to 13.

62. A core network element, characterized in that: It includes a memory and a processor, the memory is used to store a program, and the processor is used to call the program in the memory so that the core network element executes the method as described in any one of claims 14-30.

63. A device, characterized in that The device comprises a processor, configured to call a program from a memory so as to enable the device to execute the method according to any one of claims 1 to 30.

64. A chip, characterized in that: The device 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 30.

65. A computer-readable storage medium, characterized in that A program is stored thereon, and the program enables a computer to execute the method according to any one of claims 1 to 30.

66. 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 30.

67. A computer program, characterized in that The computer program enables a computer to execute the method according to any one of claims 1 to 30.

Images