Communication method, network equipment and terminal equipment

Abstract

The invention relates to a communication method, network equipment, terminal equipment, a computer readable storage medium, a computer program product and a computer program. The method comprises the following steps: an access network device receives uplink data information sent by a terminal device; the access network device determines a first core network device based on first information in the uplink data information; and the access network equipment sends the uplink data information to the first core network equipment.

Description

Communication method, network device and terminal device Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method, a network device, a terminal device, a computer-readable storage medium, a computer program product, and a computer program. Background Art

[0002] With the development of 5G systems, the 3rd Generation Partnership Project (3GPP) standards have included a requirement for 5G systems to support zero-power device access. Zero-power communication systems can be used in scenarios such as wireless industrial sensing networks, smart agriculture, smart warehousing and logistics, and smart homes. However, in 5G systems, how to avoid complex communication processes for zero-power devices and thus reduce signaling overhead has become a challenge.

[0003] Summary of the Invention

[0004] Embodiments of the present application provide a communication method, a network device, a terminal device, a computer-readable storage medium, a computer program product, and a computer program.

[0005] An embodiment of the present application provides a communication method, including:

[0006] The access network device receives uplink data information sent by the terminal device;

[0007] The access network device determines a first core network device based on the first information in the uplink data information;

[0008] The access network device sends the uplink data information to the first core network device.

[0009] An embodiment of the present application provides a communication method, including:

[0010] The first core network device receives uplink data information;

[0011] The first core network device determines a target server based on the first information in the uplink data information;

[0012] The first core network device sends the uplink data information to the target server.

[0013] An embodiment of the present application provides a communication method, including:

[0014] The terminal device sends uplink data information; wherein, the first information in the uplink data information is used to determine the first core network device and / or the target server.

[0015] An embodiment of the present application provides an access network device, including:

[0016] The first communication unit is configured to receive uplink data information sent by a terminal device; and send the uplink data information to the first core network device;

[0017] The first processing unit is configured to determine a first core network device based on first information in the uplink data information.

[0018] An embodiment of the present application provides a first core network device, including:

[0019] The second communication unit is configured to receive uplink data information and send the uplink data information to a target server;

[0020] The second processing unit is configured to determine a target server based on the first information in the uplink data information.

[0021] An embodiment of the present application provides a terminal device, including:

[0022] The third communication unit is used to send uplink data information; wherein, the first information in the uplink data information is used to determine the first core network device and / or the target server.

[0023] An embodiment of the present application provides an access network device, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the above method.

[0024] An embodiment of the present application provides a first core network device, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the above method.

[0025] An embodiment of the present application provides a terminal device, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the above method.

[0026] The embodiment of the present application provides a chip for implementing the above method.

[0027] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above method.

[0028] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a device to perform the above method when the computer program is executed by the device.

[0029] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above method.

[0030] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above method.

[0031] The solution provided by the embodiment of the present application allows the network-side device to determine the target server for data transmission based on the uplink data information sent by the terminal device, and directly send the uplink data information to the target server. This can reduce the terminal device's need to perform complex communication processes to transmit data to the network side, as well as reduce the signaling overhead caused by complex communication processes. In particular, in the scenario of zero-power terminals, it can better adapt to the low complexity characteristics of zero-power terminals. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0033] FIG2 is a schematic diagram of the composition structure of a zero-power communication system according to an embodiment of the present application.

[0034] FIG3 is a schematic flowchart 1 of a communication method according to an embodiment of the present application.

[0035] FIG4 is a second schematic flowchart of a communication method according to an embodiment of the present application.

[0036] FIG5 is a third schematic flowchart of a communication method according to an embodiment of the present application.

[0037] 6 to 9 are flowcharts of various examples of communication methods according to embodiments of the present application.

[0038] FIG10 is a schematic block diagram of an access network device according to an embodiment of the present application.

[0039] FIG11 is a schematic block diagram of a first core network device according to an embodiment of the present application.

[0040] FIG12 is a schematic block diagram of a terminal device according to an embodiment of the present application.

[0041] FIG13 is a schematic block diagram of a communication device according to an embodiment of the present application.

[0042] FIG14 is a schematic block diagram of a chip according to an embodiment of the present application.

[0043] FIG15 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0044] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0045] 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, 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, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0046] 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, etc. The embodiments of the present application can also be applied to these communication systems.

[0047] In one possible implementation, 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.

[0048] In one possible implementation, 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 an unshared spectrum.

[0049] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0050] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0051] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as a ship, etc.); it can also be deployed in the air (for example, on an airplane, balloon, and satellite, etc.).

[0052] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0053] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0054] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0055] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0056] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0057] FIG1 exemplarily illustrates a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one possible implementation, the communication system 100 may include multiple network devices 110, and each network device 110 may include a different number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application.

[0058] In one possible implementation, the communication system 100 may further include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which is not limited in this embodiment of the present application.

[0059] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment can be an evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB), etc. in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0060] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system shown in Figure 1 as an example, the communication device may include a network device and a terminal device having a communication function. The network device and the terminal device may be specific devices in the embodiments of the present application and will not be described in detail here. The communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

[0061] To facilitate understanding of the embodiments of the present application, the following briefly describes the basic processes and basic concepts involved in the embodiments of the present application. It should be understood that the basic processes and basic concepts introduced below do not limit the embodiments of the present application.

[0062] Zero-power communication technology is a wireless communication technology suitable for short-range, low-rate communications. As shown in Figure 2, a zero-power communication system can be composed of a reader and a tag; the tag is a zero-power device. This zero-power device (the tag in Figure 2) primarily combines RF energy harvesting, backscatter communication, and low-power computing technologies to achieve the advantage of device nodes not carrying a power supply. 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 sensor devices, completing functions and applications such as modulation and transmission of backscattered signals and collection and processing of sensor information.

[0063] With the development of 5G systems, the 3rd Generation Partnership Project (3GPP) standard has introduced the requirement for 5G systems to support zero-power devices to access the network. The main scenarios targeted have the following characteristics: extreme environments that are not suitable for ordinary terminals; terminals with very low power consumption and cost; and battery-free terminals. Zero-power communication systems can be used in scenarios such as wireless industrial sensing networks, smart agriculture, smart warehousing and logistics, and smart homes. Based on the energy source and usage of zero-power devices, zero-power devices can be divided into the following types:

[0064] 1) Passive Zero-Power Devices. These devices require no internal battery. When they are close to a network device (such as an RFID reader), they are within the near-field radiation generated by the device's antenna. Consequently, the antenna of the passive zero-power device generates an induced current through electromagnetic induction, which drives the device's low-power chip circuitry. This performs tasks such as demodulating forward link signals and modulating reverse link signals. For backscatter links, the passive zero-power device uses backscattering to transmit signals. As can be seen, passive zero-power devices require no internal battery for either the forward or reverse link, making them truly zero-power devices. Their RF and baseband circuits are very simple, requiring no components such as an LNA (Low Noise Amplifier), PA (Power Amplifier), crystal oscillator, or ADC (Analog-to-Digital Converter). Consequently, they offer numerous advantages, including small size, light weight, very low price, and long service life.

[0065] 2) Semi-passive zero-power devices do not have conventional batteries installed on them, but can use radio frequency energy harvesting modules 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 drive the low-power chip circuit of the zero-power device. It can realize tasks such as demodulation of forward link signals and modulation of reverse link signals. For backscatter links, zero-power devices use backscattering to transmit signals. It can be seen that semi-passive zero-power devices do not require built-in batteries to drive either the forward link or the reverse link. Although energy stored in capacitors is used in operation, the energy comes from radio energy harvested by the energy harvesting module, making it a true zero-power device. Semi-passive zero-power devices inherit many of the advantages of passive zero-power devices, and therefore have many advantages such as small size, light weight, very low price, and long service life.

[0066] 3) Active zero-power devices. This type of terminal can have a built-in battery, which is used to drive the low-power chip circuit of the active zero-power device. It realizes the demodulation of the forward link signal and the modulation of the backward link signal. However, for the backscatter link, the active zero-power device uses the backscatter implementation method to transmit the signal. Therefore, this type of active zero-power device is mainly reflected in the fact that the signal transmission of the reverse link does not require the terminal's own power, but uses the backscatter method. Active zero-power devices have built-in batteries to power the radio frequency identification (RFID) chip to increase the reading and writing distance of the tag and improve the reliability of communication. Therefore, it can be used in some scenarios with relatively high requirements on communication distance, reading delay, etc.

[0067] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0068] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0069] In the description of 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 being indicated, configuration and being configured, etc.

[0070] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0071] FIG3 is a schematic flow chart of a communication method according to an embodiment of the present application. The method can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents.

[0072] S310: The access network device receives uplink data information sent by the terminal device;

[0073] S320: The access network device determines a first core network device based on the first information in the uplink data information;

[0074] S330: The access network device sends the uplink data information to the first core network device.

[0075] FIG4 is a schematic flow chart of a communication method according to an embodiment of the present application. The method can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents.

[0076] S410: The first core network device receives uplink data information;

[0077] S420: The first core network device determines a target server based on the first information in the uplink data information;

[0078] S430: The first core network device sends the uplink data information to the target server.

[0079] FIG5 is a schematic flow chart of a communication method according to an embodiment of the present application. The method can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents.

[0080] S510: The terminal device sends uplink data information; wherein, the uplink data information is used to determine the first core network device and / or the target server.

[0081] The terminal device may be a zero-power device. The access network device may be a radio access network (RAN) device. The RAN device may be a base station, a gNB, an eNB, or the like. The first core network device may be a first AMF (Access and Mobility Management Function) entity. The target server may be an Internet of Things (AIoT) server, or may be an energy harvesting-based Ambient Power Enabled Internet of Things (AIoT) server.

[0082] The terminal device may perform the process of S510 by sending the uplink data information to the access network device via the access layer AS connection between the access network devices. Alternatively, the terminal device may send the uplink data information to the first core network device. The following are respectively:

[0083] In one possible implementation, before the terminal device executes the aforementioned S510, wherein the terminal device is connected through the access layer AS between the access network devices and sends the uplink data information to the access network device, at least one of the following information may be pre-configured: routing-related information. The routing-related information includes at least one of the following: a routing-related identifier and routing path information.

[0084] The routing-related identifier may include at least one of the following: an identifier of the routing information and an identifier of the target server. The routing information may include at least a target address; the target address may be the address of the target server. Specifically, the target address may be any one of a target IP (Internet Protocol) address and a destination Layer 2 address, which are not limited herein. The identifier of the target server may be pre-configured on the terminal device, or may be configured for the terminal device by a network device (e.g., a first core network device).

[0085] The routing path information may include the addresses of one or more devices between the terminal device (excluding the terminal device) and the target server (including the target server). The address of any device may be any one of an IP address, a layer 2 address, etc., which are not exhaustive.

[0086] The pre-configured information may also include at least one of the following: device manufacturer identification, service provider identification, and terminal device identification. The device manufacturer identification refers to the device manufacturer ID (Identity) of the terminal device. The service provider identification refers to the SP (Service Provider) ID that provides service support for the terminal device. The terminal device identification refers to the ID of the terminal device itself. The above-mentioned terminal device identification may be something that must be pre-configured on the terminal device, for example, it may be something that is configured on the terminal device when the terminal device leaves the factory. The above-mentioned routing-related identification, device manufacturer identification, service provider identification, and target area may be specified as something that must be configured on the terminal device in advance, or may be specified as something that is configured on the terminal device according to actual conditions, or may not be configured on the terminal device.

[0087] The manner of establishing an AS connection between the terminal device and the access network device may include: when the terminal device is located in a target area, the terminal device establishes an AS connection with the access network device; wherein the target area is preconfigured.

[0088] Here, the target area may be the service area of ​​the terminal device, and the target area may be pre-configured, that is, the service area of ​​the terminal device is pre-configured. The target area refers to the service area of ​​the terminal device; the service area may be represented by one or more target cell identifiers, or may be represented by one or more tracking area identifiers (TAI), or may be represented by longitude and latitude coordinate information. In one example, the target area is represented by one or more target cell identifiers, that is, the target area may be composed of one or more target cells; wherein, the identifier of any one of the one or more target cells may be represented by a cell identifier (CI, Cell Identity). More specifically, CI may be NR Cell Global Identifier (NCGI, NR Cell Global Identifier), or NCI (NR Cell Identifier, NR Cell Identifier), etc., and all possible representations of CI are not exhaustively enumerated here. In another example, the target area is represented by coordinate information; wherein, the coordinate information may specifically include longitude and latitude information in a geographic coordinate system.

[0089] The method for determining whether the terminal device is located in the target area may be: the terminal device obtains the current location based on its own location sensor, and based on the coordinate information corresponding to the pre-configured target area, determines whether the current location is within the target area; if so, it is determined to be located in the target area; otherwise, it is determined not to be located in the target area. The location sensor may specifically be a Global Positioning System (GPS) sensor.

[0090] Alternatively, the method for determining whether the terminal device is located in the target area may be: the terminal device obtains the current cell identity (Cell Identity) from the currently received system message, and determines whether the current cell identity matches the target cell identity corresponding to its own pre-configured target area; if so, it is determined to be located in the target area; otherwise, it is determined not to be located in the target area.

[0091] The access network device specifically refers to the access network device in the target area; that is, when the terminal device is located in the target area, the terminal device establishes an AS connection with the access network device, which can be specifically: when the terminal device is determined to be located in the target area, the terminal device establishes an AS connection with the access network device in the target area. The process of establishing an AS connection between the terminal device and the access network device can include: after the terminal device performs public land mobile network (PLMN) selection, cell selection, wireless resource management and other processing, it establishes an AS connection with the access network device; wherein, the processing of wireless resource management can include: Radio Resource Control (RRC) connection establishment process, etc. The specific process of establishing an AS connection between the terminal device and the access network device will not be repeated here.

[0092] Optionally, after the terminal device completes the establishment of the AS connection with the access network device, if the terminal device has uplink data information that needs to be sent, the uplink data information can be sent to the access network device through the AS connection.

[0093] Optionally, if the access network device detects that the terminal device is in an inactive state, the access network device may also release the AS connection between the terminal device and the terminal device. In this scenario, if the terminal device has uplink data information that needs to be sent, the terminal device and the access network device need to re-establish the AS connection, and then the terminal device sends the uplink data information to the access network device through the AS connection. Among them, the access network device may determine that the terminal device is in an inactive state when it detects that the duration for which the terminal device has not transmitted uplink data reaches a preset duration. The preset duration can be preset according to actual conditions, for example, it can be 1 minute, 10 minutes, or longer or shorter, which is not limited here. That is, the access network device determines that the terminal device is in an inactive state when it determines that the duration from the moment the terminal device completed the last transmission of uplink data information to the current moment reaches or exceeds the preset duration.

[0094] The terminal device may generate the uplink data information based on the current data to be transmitted, wherein the current data to be transmitted may be service data that the terminal device currently needs to report, and the specific content is not limited in this embodiment.

[0095] The first information includes: routing related information. And / or, the first information may also include at least one of the following: a device manufacturer identifier, a service provider identifier, and a terminal device identifier.

[0096] The routing-related information includes at least one of the following: a routing-related identifier and routing path information. The routing-related identifier may include at least one of the following: an identifier of routing information and an identifier of a target server.

[0097] The aforementioned uplink data information includes an uplink data container; the uplink data container may specifically be a data container obtained by encapsulating the uplink data information currently to be transmitted. Exemplarily, the uplink data container may be an uplink (UL) Internet of Things (IoT) data container, and more specifically, the uplink data container may be a UL Ambient Power Enabled Internet of Things (AIoT) data container.

[0098] The uplink data container includes a header portion and a data portion. The header portion can be specifically represented as a header portion. The header portion of the uplink data information can be within or outside the data portion. For example, the data portion of the uplink data information, i.e., the data portion, can be specifically a UL AIoT data container; the header portion can be within the UL AIoT data container, or can be outside the UL AIoT data container, such as a header portion added before the UL AIoT data container.

[0099] The first information is carried by the header portion of the uplink data container, and / or the first information is carried by the data portion of the uplink data container. In a preferred example, the terminal device identifier in the first information is carried by the data portion; and the routing-related information, device manufacturer identifier, and service provider identifier in the first information are carried by the header portion.

[0100] In one case, at least one of the routing-related identifier, the device manufacturer identifier, and the service provider identifier is pre-configured, that is, pre-configured in the terminal device.

[0101] In this case, the uplink data information, ie, the header portion of the uplink data container, may carry at least one of the routing-related identifier, the device manufacturer identifier, and the service provider identifier in the first information.

[0102] That is to say, if the terminal device side is pre-configured with at least one of the routing-related identifier, the device manufacturer identifier, and the service provider identifier, then when the terminal device generates uplink data information, at least one of the routing-related identifier, the device manufacturer identifier, and the service provider identifier can be carried in the first information of the uplink data information.

[0103] For example, if a routing-related identifier is pre-configured on the terminal device side, then when the terminal device generates an uplink data container, the routing-related identifier of the first information is carried in the header of the uplink data container. For another example, if the terminal device does not have a routing-related identifier pre-configured, but has a device manufacturer identifier and / or a service provider identifier pre-configured, then when the terminal device generates an uplink data container, the device manufacturer identifier and / or the service provider identifier of the first information is carried in the header of the uplink data container. For another example, if the terminal device is pre-configured with a device manufacturer identifier, a service provider identifier, and a routing-related identifier, in this case, the terminal device can carry the routing-related identifier of the first information in the header of the uplink data container; or, in this case, the terminal device can carry the device manufacturer identifier, the service provider identifier, and the routing-related identifier of the first information in the header of the uplink data container.

[0104] In another case, the terminal device is not pre-configured with any one of the routing-related identifier, the device manufacturer identifier, and the service provider identifier. The terminal device is only pre-configured with the terminal device identifier.

[0105] In this case, when the terminal device generates an uplink data container, the header of the uplink data container may not carry any one of the routing-related identifier, the device manufacturer identifier, and the service provider identifier.

[0106] It should be understood that if the header part of the uplink data container does not carry any one of the routing-related identifier, the equipment manufacturer identifier, and the service provider identifier, the uplink data container can still have the header part, i.e., the header part, but the header part can be used to carry other predefined related information, but this embodiment does not limit it.

[0107] The uplink data container contains an identifier of the terminal device; the identifier of the terminal device is preconfigured. The identifier of the terminal device can be carried by the data portion of the uplink data container. The identifier of the terminal device can be preconfigured in the terminal device when the terminal device leaves the factory to uniquely identify the terminal device. Therefore, whether the header portion of the uplink data container contains the first information will not affect whether the data portion contains the identifier of the terminal device. In other words, the data portion of the uplink data container can always contain the identifier of the terminal device.

[0108] The data portion of the uplink data container may carry not only the identifier of the terminal device but also the data currently to be transmitted. However, this embodiment does not limit the specific content of the data currently to be transmitted.

[0109] In another scenario, the terminal device is not preconfigured with any of the routing-related identifiers, the device manufacturer identifier, and the service provider identifier. The terminal device is only preconfigured with the terminal device identifier. In this case, the terminal device may also be preconfigured with the target server identifier, or the terminal device may obtain the target server identifier in advance.

[0110] The terminal device may obtain the identifier of the target server in advance through the registration process between the terminal device and the first core network. For example, the identifier of the target server may be carried in the registration acceptance message transmitted during the registration process; that is, the terminal device may obtain the identifier of the target server from the registration acceptance message.

[0111] In this case, the uplink data container includes the identifier of the terminal device and the identifier of the target server. More specifically, the header of the uplink data container may carry the identifier of the target server, and the data portion of the uplink data container may carry the identifier of the terminal device.

[0112] The terminal device sends the uplink data information to the access network device via an access stratum (AS) connection between the terminal device and the access network device. In the aforementioned S310, the access network device receives the uplink data information sent by the terminal device, which may include: the access network device receives the uplink data information sent by the terminal device via an AS connection between the terminal device and the access network device.

[0113] After the access network device receives the uplink data information, S320 may be executed, that is, the access network device determines the first core network device based on the first information in the uplink data information. Specific implementations may include the following:

[0114] In one embodiment, the access network device determines the first core network device based on the first information in the uplink data information, which may include: the access network device determines the first core network device based on the routing related information in the first information in the uplink data information.

[0115] Specifically, it may be that: when the first information in the uplink data information includes the routing related information, the access network device determines the first core network device based on the routing related information.

[0116] As described above, the routing-related information may be at least one of: a routing-related identifier and routing path information. The routing-related identifier includes at least one of: an identifier of routing information and an identifier of a target server.

[0117] Optionally, when the first information in the uplink data information includes the identifier of the routing information, the access network device determines the routing information based on the identifier of the routing information, and determines the first core network device based on the routing information. The routing information may include one or more IP addresses, and the one or more IP addresses at least include the next-hop IP address and the IP address of the target server; the routing information may be included in a routing table (Routing Table) preset by the access network device. For example, when the access network device receives the uplink data information sent by the terminal device, it extracts the identifier of the routing information from the uplink data information, and then performs a routing query in its own pre-stored routing table according to the identifier of the routing information, looking for routing information (or routing entry) that matches the identifier of the routing information. If matching routing information is found, the access network device uses the core network device corresponding to the outgoing interface and the next-hop IP address contained in the routing information as the first core network device. For another example, the routing information may also be represented in other ways, which are not limited here; accordingly, when the access network device receives the uplink data information sent by the terminal device, it extracts the identifier of the routing information from the uplink data information, and performs a routing query in its own pre-saved routing table (Routing Table) based on the identifier of the routing information, looking for routing information (or routing entries) that matches the identifier of the routing information. If matching routing information is found, the access network device uses the core network device corresponding to the outgoing interface and the next-hop address (which can be the next-hop IP address or the next-hop layer 2 address, without limitation) contained in the routing information as the first core network device.

[0118] Optionally, when the first information in the uplink data information includes the identifier of the target server, the access network device determines the first core network device based on the identifier of the target server. When the access network device receives the uplink data information sent by the terminal device, it extracts the identifier of the target server from the uplink data information, determines the target address based on the identifier of the target server, performs a routing query in its own pre-stored routing table based on the target address, and searches for routing information that matches the routing-related identifier. If matching routing information is found, the access network device uses the core network device corresponding to the outgoing interface and next-hop address contained in the routing information as the first core network device.

[0119] Optionally, when the first information in the uplink data information includes the routing path information, the access network device determines the first core network device based on the routing path information. The routing path information may include the addresses of one or more devices between the terminal device (excluding the terminal device) and the target server (including the target server). The one or more devices may include one or more network devices, and the one or more network devices may include at least a core network device. The address of any device may be any one of an IP address, a layer 2 address, etc., and they are not exhaustively listed. Specifically, when the access network device receives the uplink data information sent by the terminal device, it extracts the routing path information from the uplink data information, and determines the core network device corresponding to the next hop address according to the routing path information as the first core network device.

[0120] Optionally, if there is only one candidate core network device in the current system, the access network device directly selects the candidate core network device as the first core network device. The candidate core network device is specifically a candidate AMF; this situation is generally applicable to a standalone non-public network (SNPN).

[0121] Optionally, the process of the access network device selecting the first core network device from the one or more candidate core network devices may specifically be: the access network device arbitrarily selects one from the one or more candidate core network devices as the first core network device; or, the access network device selects the one with the smallest load from the one or more candidate core network devices as the first core network device; or, the access network device selects one or more candidate core network devices with the smallest load from the one or more candidate core network devices, and arbitrarily selects one from the one or more candidate core network devices with the smallest load as the first core network device.

[0122] Optionally, when the first information includes at least one of the following: a device manufacturer identifier, a service provider identifier, and a terminal device identifier; the access network device determines the first core network device based on the first information in the uplink data information, including: the access network device determines the first core network device based on the first information in the uplink data information and the first pre-configuration information. The first pre-configuration information includes: parameters of the candidate device corresponding to the candidate server supported by each candidate core network among one or more candidate core network devices; the parameters of the candidate device corresponding to the candidate server include at least one of the following: a candidate device manufacturer identifier, a candidate service provider identifier, and a candidate device identifier.

[0123] Among them, at least one of the candidate device manufacturer identifier, candidate service provider identifier, and candidate device identifier supported by the candidate server corresponding to each candidate core network device can be pre-configured in each candidate core network device and can also be pre-configured in the access network device. That is to say, a candidate core network device can be associated with one or more candidate servers, and each candidate server reports in advance to the candidate core network device at least one of the candidate device manufacturer identifier, candidate service provider identifier, and candidate device identifier supported by it. In addition, each candidate server can simultaneously pre-configure at least one of the candidate device manufacturer identifier, candidate service provider identifier, and candidate device identifier supported by the candidate server in the access network device; or, each candidate core network device can receive at least one of the candidate device manufacturer identifier, candidate service provider identifier, and candidate device identifier supported by the candidate core network device and synchronously save them in the access network device. For example, there are two candidate core network devices in the system, namely candidate core network device 1 and candidate core network device 2. Candidate core network device 1 is associated with two candidate servers, namely candidate server 1 and candidate server 2. Candidate server 1 supports a candidate device manufacturer identifier of 01, a candidate service provider identifier of 02, and a candidate device identifier of 001. Candidate server 2 supports a candidate device manufacturer identifier of 03, a candidate service provider identifier of 04, and a candidate device identifier of 002. Assuming that the first information received by the access network device includes the candidate device manufacturer identifier 03, the access network device can determine that candidate core network device 1 is the first core network device based on the device manufacturer identifier.

[0124] The aforementioned candidate core network device may specifically refer to a candidate AMF entity.

[0125] After the access network device completes the aforementioned process of selecting the first core network device, the access network device may execute S330, where the access network device sends the uplink data information to the first core network device. Accordingly, the first core network device may execute S410, where the first core network device receives the uplink data information; this may specifically include: the first core network device receiving the uplink data information sent by the access network device.

[0126] In another possible implementation, the terminal device executes the aforementioned S510, specifically: the terminal device sends uplink data information to the first core network device. Correspondingly, the first core network device executes S410, specifically including: the first core network device receives the uplink data information sent by the terminal device.

[0127] In this implementation, before the terminal device executes S510, it may include: the terminal device establishes a NAS connection with the first core network device; correspondingly, the first core network device establishes a NAS connection with the terminal device.

[0128] The way to establish a NAS connection between the terminal device and the first core network may be to establish a NAS connection through a registration process between the terminal device and the first core network, or to establish a NAS connection by sending a control plane service request message from the terminal device to the first core network device, or to establish a NAS connection through other processes (such as a service request process).

[0129] Specifically, establishing a NAS connection through the registration process between the terminal device and the first core network may include: the terminal device sends a registration request message to the first core network device through the access network device; the terminal device receives a registration acceptance message sent by the first core network device through the access network device; the registration acceptance message is used to indicate that the terminal device and the first core network device have completed establishing a NAS connection; the terminal device returns a registration completion message to the first core network device through the NAS connection.

[0130] Correspondingly, the first core network device establishes a NAS connection with the terminal device, which may specifically include: the first core network device receives a registration request message sent by the terminal device through the access network device; the first core network device sends a registration acceptance message to the terminal device through the access network device; the registration acceptance message is used to indicate that the terminal device and the first core network device have completed the establishment of a NAS connection; the first core network device receives a registration completion message sent by the terminal device through the NAS connection.

[0131] The terminal device establishes an RRC connection with the access network device, sends a registration request message to the access network device via the RRC connection, and the access network device sends the registration request message to the first core network device. The registration request message may be carried by a NAS message within the RRC message. The registration request message may include an identifier of the terminal device and a registration type. Similar to the aforementioned embodiment, the identifier of the terminal device may be pre-configured when the terminal device leaves the factory.

[0132] Here, the terminal device may establish an RRC connection with an access network device to which it can currently be connected, and send a registration request message to the access network device through the RRC connection.

[0133] The first core network device may be selected by the access network device from one or more candidate core network devices. For example, if there is only one candidate core network device, the candidate core network device is directly selected as the first core network device. For example, if there are multiple candidate core network devices, the access network device selects any one of the multiple candidate core network devices as the first core network device. Alternatively, the access network device selects the one with the lowest load from the multiple candidate core network devices based on their load conditions.

[0134] After receiving the registration request message, the first core network device can establish a NAS connection with the terminal device. When the NAS connection is established, a registration acceptance message can be sent to the terminal device through the access network device. In the registration acceptance message, a 5G Globally Unique Temporary Identifier (5G-GUTI) can be carried. The 5G-GUTI can be an identifier assigned to the terminal device by the first core network device, that is, the first Access and Mobility Management Function (AMF) entity; 5G-GUTI is a clear identifier of the terminal device provided in the 5G system, which will not disclose the permanent identity of the terminal device, and allows it to be used to identify the AMF and the network. It can be used to establish the identity of the terminal device during the signaling between the network and the terminal device in 5GS.

[0135] The registration acceptance message may also carry the identifier of the target server. The target server may specifically be the target IOT server, and more specifically may be the target AIoT server (Server). That is, the registration acceptance message may carry the target AIoT Server ID. The identifier of the target server specifically refers to the destination identifier for the terminal device to send the second uplink data. As mentioned above, the identifier of the target server may be pre-configured, or may be carried in the registration acceptance message. That is, the identifier of the target server may be carried in the registration acceptance message, that is, the identifier of the target server may be sent by the first core network device to the terminal device. As mentioned above, the registration acceptance message may not carry the identifier of the target server; accordingly, in this case, the identifier of the target server is pre-configured, for example, it may be preset in the terminal device when the terminal device leaves the factory.

[0136] After the terminal device receives the aforementioned registration acceptance message, it can send a registration completion message to the first core network device through the currently established NAS connection.

[0137] Through the above processing, the registration process of the terminal device is completed, and while completing the registration process of the terminal device, a NAS connection between the terminal device and the first core network device is established.

[0138] It should be pointed out that the aforementioned registration acceptance message may carry the identifier of the target server, or may not carry the identifier of the target server. In the case where the registration acceptance message does not carry the identifier of the target server, the aforementioned process is only used to complete the registration of the terminal device and establish a NAS connection; in the case where the registration acceptance message carries the identifier of the target server, the aforementioned process can also be used to indicate the destination address of the uplink data sent by the terminal device, that is, the destination identifier of the target server. Whether the registration acceptance message carries the identifier of the target server can be determined by the first core network device according to a pre-configured processing policy. For example, its policy can be pre-configured so that the registration acceptance message can carry the identifier of the target server, or it can be pre-configured so that the registration acceptance message does not carry the identifier of the target server. All possible configuration methods are not exhaustively enumerated here.

[0139] Optionally, after completing the above processing, the terminal device executes S510. Specifically, if the terminal device is currently in a connected state, the terminal device sends uplink data information to the first core network device through the NAS connection between the terminal device and the first core network device. The uplink data information can be carried by an uplink NAS transport (TRANSPORT) message. Accordingly, the first core network device executes S410, and the first core network device receives the uplink data information sent by the terminal device.

[0140] In one implementation, the first core network device receives uplink data information carried by an uplink NAS transmission message sent by the terminal device.

[0141] This processing is typically applicable when the terminal device is in a connected state, i.e., the NAS connection remains established, after the NAS connection is established through the aforementioned registration process or after another method is used. Because the terminal device still maintains a NAS connection with the first core network device, the terminal device can directly send uplink data information carried in an uplink NAS transmission message to the first core network device through the NAS connection with the first core network device.

[0142] In one embodiment, the first core network device receives uplink data information carried by a control plane service request message sent by a terminal device.

[0143] This process typically occurs when the terminal device disconnects from the NAS connection after a period of time, after establishing a NAS connection through the aforementioned registration process or by other means. This means the terminal device is currently in a disconnected state. Because the NAS connection between the terminal device and the first core network device has been disconnected, the terminal device uses a control plane service request message carrying the uplink data information to restore the NAS connection between the terminal device and the first core network device.

[0144] In this embodiment, the first message of the uplink data information necessarily carries the identifier of the target server. Based on the foregoing description, it can be understood that the identifier of the target server can be preconfigured by the terminal device, or can be carried in a registration acceptance message during the registration process. If the uplink data information is an uplink data container, the identifier of the target server can preferably be carried in the header of the uplink data container, but it can also be carried in the data portion of the uplink data container.

[0145] It should be pointed out that in this embodiment, in addition to the identifier of the target server, the first information of the uplink data information may also include at least one of the routing-related identifiers, equipment manufacturer identifiers, service provider identifiers, target areas, and terminal device identifiers in the aforementioned embodiments. The specific carrying method is the same as that in the aforementioned embodiments, so it will not be repeated.

[0146] On the side of the first core network device, the uplink data information may be received from the access network device, or directly from the terminal device; regardless of which of the above methods is used, when the first core network device receives the uplink data information, S420 may be executed, and the first core network device determines the target server based on the first information in the uplink data information.

[0147] Optionally, the first core network device determines the target server based on the first information in the uplink data information, which may include: the first core network device determines the target server based on the routing related information in the first information in the uplink data information.

[0148] Specifically, when the first information includes routing-related information, the first core network device determines routing information based on the routing-related information; and determines the target server based on the routing information.

[0149] For example, when the first core network device receives uplink data information, it extracts the identifier of the routing information from the uplink data information, and then performs a routing query in its own pre-stored routing table based on the identifier of the routing information to search for routing information (or routing entry) that matches the routing-related identifier. If matching routing information is found, the first core network device uses the server corresponding to the outgoing interface and the next-hop IP address contained in the routing information as the target server. For another example, the routing information may also be represented in other ways, which are not limited here. Accordingly, when the first core network device receives uplink data information, it extracts the identifier of the routing information from the uplink data information, and then performs a routing query in its own pre-stored routing table based on the identifier of the routing information to search for routing information (or routing entry) that matches the identifier of the routing information. If matching routing information is found, the first core network device uses the server corresponding to the outgoing interface and the next-hop destination address (which may be a destination IP address or a destination Layer 2 address, which is not limited here) contained in the routing information as the target server.

[0150] Optionally, when the first information in the uplink data information includes the identifier of the target server, the first core network device determines the target server based on the identifier of the target server. When the first core network device receives the uplink data information, it extracts the identifier of the target server from the uplink data information, determines the target address based on the identifier of the target server, performs a routing query in its own pre-stored routing table based on the target address, and searches for routing information that matches the routing-related identifier. If matching routing information is found, the first core network device uses the server corresponding to the outgoing interface and next-hop address contained in the routing information as the target server.

[0151] Optionally, when the first information in the uplink data information includes the routing path information, the first core network device determines the first core network device based on the routing path information. The routing path information may include the addresses of one or more devices between the terminal device (excluding the terminal device) and the target server (including the target server). The address of any device can be any one of an IP address, a layer 2 address, etc., and they are not exhaustively listed. Specifically, when the first core network device receives the uplink data information, it extracts the routing path information from the uplink data information, and determines the server corresponding to the next hop address according to the routing path information as the target server.

[0152] Optionally, the first core network device determines the target server based on the first information in the uplink data information, which may include: the first core network device determines the target server based on the first information in the uplink data information and second pre-configuration information.

[0153] Specifically, when the first information in the uplink data information includes at least one of the device manufacturer identifier, the service provider identifier, and the terminal device identifier, the first core network device selects the target server from one or more candidate servers based on the first information and the second pre-configuration information.

[0154] The second pre-configuration information is shared by one or more candidate core network devices, and the one or more candidate core network devices include the first core network device;

[0155] The second pre-configuration information includes: parameters of the candidate device corresponding to each candidate server among the one or more candidate servers; wherein the parameters of the candidate device include at least one of the following: an identifier of the candidate device, a service area of ​​the candidate device, an identifier of a manufacturer of the candidate device, and an identifier of a candidate service provider.

[0156] The service area of ​​the candidate device may be represented by one or more cell identifiers, may be represented by one or more tracking area identifiers, or may be identified by latitude and longitude information.

[0157] The second pre-configuration information may specifically be the information contained in a shared database; the shared database may refer to one or more candidate core network devices shared by the network side. The aforementioned embodiment has already explained that the candidate core network device may specifically refer to a candidate AMF entity; that is, the second pre-configuration information in the shared database can be used in common between the candidate AMF entities. The shared database may be set in any network element of the core network, or may be set in a separate server. For example, the shared database may be set in the AMF of the core network, in the UDM (Unified Data Management), or in any other network element, which are not exhaustively listed here. For example, if the shared database is set in a separate server, the server may have a communication interface with at least each core network element so that each core network element can read the contents of the shared database.

[0158] Among them, among the one or more candidate servers, different candidate servers may correspond to different candidate devices. The candidate device corresponding to any candidate server refers to one or more zero-power devices managed or provided by any candidate server. That is, the pre-configuration information may include parameters of one or more zero-power devices corresponding to each candidate server among all candidate servers. The aforementioned terminal device can be any zero-power device among all zero-power devices corresponding to all candidate servers in the pre-configuration information.

[0159] It should be pointed out that, among the aforementioned one or more candidate core network devices, any candidate core network device can pre-acquire and save the parameters of the candidate device reported by one or more candidate servers, and different candidate core network devices can obtain the parameters of one or more candidate devices reported by different candidate servers. For example, candidate core network device 1 obtains the parameters of the candidate devices reported by candidate server 1 and candidate server 2, and saves the parameters of the candidate devices corresponding to candidate server 1 and candidate server 2 in the pre-configuration information, so that all candidate core network devices can share; similarly, the candidate core network device obtains the parameters of the candidate devices reported by candidate server 3 and candidate server 4, and saves the parameters of the candidate devices corresponding to candidate server 3 and candidate server 4 in the pre-configuration information, so that all candidate core network devices can also share.

[0160] Taking the identification of the terminal device included in the first information as an example, the first core network device obtains the identification of the device included in the parameters of the device corresponding to one or more candidate servers from the second pre-configuration information, and obtains the identification of the terminal device from the first information of the uplink data information; the candidate server where the identification of the device matching the identification of the terminal device is located is used as the target server. For example, the pre-configuration information includes 3 candidate servers, namely candidate server 1 and candidate server 2; the pre-configuration information also includes the parameters of the device corresponding to each candidate server, such as the parameters of the device corresponding to device a1 of candidate server 1 include the identification of device a1, the parameters of the device corresponding to device a2 include the identification of device a2, the parameters of the device corresponding to device b1 of candidate server 2 include the identification of device b1, and the parameters of the device corresponding to device b2 include the identification of device b2; the identification of the terminal device included in the uplink data information is the identification of device a2, then it can be determined that the aforementioned candidate server 1 is selected as the target server this time.

[0161] Taking the example of the device manufacturer identifier included in the first information, the first core network device obtains the candidate device manufacturer identifier included in the parameters of the device corresponding to one or more candidate servers from the second pre-configuration information, and obtains one or more bits in the identifier of the terminal device from the uplink data information; the candidate server where the candidate device manufacturer identifier that matches the one or more bits in the identifier of the terminal device is located is used as the target server. In this case, the one or more bits of the terminal device can be one or more bits at a specified number and a specified position, such as the first 8 bits of the terminal device are used to represent the device manufacturer identifier and / or the service provider identifier. Accordingly, based on the specific content of the one or more bits, the candidate device manufacturer identifier contained in the current second pre-configuration information is matched, and the candidate server where the matched candidate device manufacturer identifier is located is used as the target server.

[0162] After completing the above processing, the first core network device may execute the above S430, and the first core network device sends the uplink data information to the target server.

[0163] Optionally, the first core network device sends the uplink data information to the target server, which may be the first core network device, that is, the first AMF entity directly sends the uplink data information to the target server.

[0164] Optionally, the first core network device sends the uplink data information to the target server, which can be: the first core network device sends the uplink data information to the target server through the second core network device. The second core network device can be a NEF (Network Exposure Function) entity. This method is mainly applicable to when the target server does not belong to the operator, that is, a server provided by a third party. In order to ensure data security, the first core network device, i.e., the first AMF, is controlled to send the uplink data information to the target server through the NEF.

[0165] It should be noted that the aforementioned target server may specifically be a target service server (SP, Service Provider); the target server specifically refers to the server corresponding to the terminal device, or may refer to an SP that provides service support or service processing for the terminal device. The aforementioned candidate server may be a candidate service SP.

[0166] After completing the above processing, the process of sending the uplink data information of the terminal device to the target server through the access network device, the first core network device (or the first core network device and the second core network device) is completed.

[0167] In one embodiment, when the target server has downlink data that needs to be sent to the terminal device, the following processing may also be performed:

[0168] The first core network device receives downlink data information sent by the target server; wherein the downlink data information is response information of the uplink data information;

[0169] The first core network device sends the downlink data information.

[0170] The downlink data information sent by the aforementioned target server to the first core network can serve as confirmation information (or confirmation part) of the uplink data information. That is, the target server does not actively send downlink data to the terminal device. Only after receiving the uplink data information sent by the terminal device, when the target server needs to send downlink data information, the downlink data information will be sent as confirmation information of the uplink data information.

[0171] The downlink data information includes relevant information of the terminal device. The relevant information of the terminal device can be used to uniquely identify the terminal device. For example, the relevant information of the terminal device may include: an identifier of the terminal device; for another example, the relevant information of the terminal device may include user information of the terminal device, and the user information may be a user identifier, etc., which are not exhaustive here.

[0172] The downlink data information is specifically a downlink (DL) data container. The terminal device-related information may be carried in the data portion of the downlink data information. Furthermore, the downlink data information may include service-related information that the target server needs to transmit to the terminal device, although this embodiment does not limit its content.

[0173] The aforementioned first core network device receives the downlink data information sent by the target server, which may be: the first core network device directly receives the downlink data information sent by the target server. Alternatively, it may be: the first core network device receives the downlink data information sent by the target server through a second core network device. Similarly, the second core network device may be an NEF entity.

[0174] In one embodiment, the aforementioned first core network device sending the downlink data information includes: the first core network device sending the downlink data information to an access network device.

[0175] The first core network device may determine an access network device based on relevant information of the terminal device, and send downlink data information to the terminal device through the access network device.

[0176] Accordingly, the operation of the access network device may include: the access network device receiving downlink data information sent by the first core network device; the access network device sending the downlink data information to the terminal device. Accordingly, the terminal device receives the downlink data information sent by the access network device.

[0177] Here, the access network device can simultaneously connect to or manage one or more terminal devices. Therefore, after receiving the downlink data information, the access network device can parse the downlink data information and, based on the relevant information of the terminal device in the downlink data information, determine to which terminal device the downlink data information is to be sent, and then send the downlink data information to the corresponding terminal device.

[0178] In one embodiment, the aforementioned first core network device sends the downlink data information, including: the first core network device sends the downlink data information to the terminal device.

[0179] When a first core network device sends downlink data information to a terminal device, the downlink data information may be carried in a downlink NAS transmission message. That is, the first core network device sends the downlink data information carried in a downlink NAS transmission message to the terminal device. Correspondingly, the terminal device receives the downlink data information sent by the first core network device.

[0180] Furthermore, the first core network device may have multiple registered terminal devices. Since the downlink data information sent by the target server to the first core network carries relevant information of the terminal device, the corresponding NAS connection can be determined based on the relevant information of the terminal device, and then the downlink data information carried by the downlink NAS transmission message can be sent to the terminal device through the NAS connection.

[0181] 6 , the method provided in the above embodiment will be exemplarily described by taking the above terminal device as a device (Device) as an example:

[0182] S601: The target server provides parameters of a candidate device to a core network device.

[0183] The core network device may be any one of one or more candidate core network devices, and the candidate core network device may be a candidate AMF. Specifically, this step may include: the target server may send parameters of the device it manages to any one of the one or more candidate AMFs, and the candidate AMF that receives the device parameters sent by the target server updates the preconfiguration information. The preconfiguration information may be stored in a shared database, so that one or more AMFs share the preconfiguration information.

[0184] It should be pointed out that the above description only uses the target server to perform the processing of S601. In actual processing, there may be one or more candidate servers. Accordingly, the above pre-configuration information may include the parameters of the candidate device corresponding to each candidate server in the one or more candidate servers; wherein, the parameters of the candidate device corresponding to each candidate server are configured by each candidate server to one of the one or more candidate core network devices; the parameters of the candidate device are the same as those in the above embodiment and will not be repeated here.

[0185] S602: The core network device saves the device parameters in the pre-configuration information, and the pre-configuration information is shared among different core network devices.

[0186] S603. The device is pre-configured with at least one of the following information: routing related information, device manufacturer identifier, service provider identifier, and terminal device identifier.

[0187] The specific description of the routing related information, the device manufacturer identifier, the service provider identifier, and the terminal device identifier is the same as that in the above embodiment and will not be repeated here.

[0188] The processing of S603 is the same as that of the previous embodiment and will not be repeated here. In addition, the execution timing of S603 and the execution timing of S601-S602 can be different. They can be executed simultaneously, or S601-S602 can be executed first and then S603; or S603 can be executed first and then S601-S602.

[0189] After completing the above processing, the device can send uplink data information to the gNB when it needs to send service data. Specifically, in conjunction with Figure 7, the terminal device is the device (Device) and the first core network device is the first AMF as an example for explanation:

[0190] S701. When the device is located in the target area, the device establishes an AS connection with the gNB.

[0191] S702. The device sends uplink data information to the gNB.

[0192] Specifically, the device sends uplink data information to the gNB via an AS connection established with the gNB. The uplink data information may be an uplink data container, specifically a UL AIoT data container. The header portion of the UL AIoT data container may include at least one of the following first information: a routing-related identifier, a device manufacturer identifier, and a service provider identifier. The specific description of the first information is the same as in the previous embodiment and is not repeated here.

[0193] S703. The gNB determines the first AMF based on the first information in the uplink data information.

[0194] Specifically, when the gNB carries at least one of the routing-related identifier, the device manufacturer identifier, and the service provider identifier of the first information in the header part of the uplink data container, the first AMF may be selected based on at least one of the routing-related identifier, the device manufacturer identifier, and the service provider identifier in the first information;

[0195] If the header portion of the uplink data container does not carry at least one of the routing-related identifier, device manufacturer identifier, and service provider identifier of the first information, the gNB arbitrarily selects an AMF as the first AMF. Furthermore, similar to the aforementioned embodiment, if the header portion of the uplink data container does not carry at least one of the routing-related identifier, device manufacturer identifier, and service provider identifier of the first information, the gNB may select an AMF as the first AMF based on the device identifier carried in the data portion. The specific processing method is the same as that of the aforementioned embodiment and is not further described.

[0196] S704, the gNB sends the uplink data information to the first AMF.

[0197] Specifically, the gNB sends the UL AIoT data container to the first AMF.

[0198] S705: The first AMF determines the target server based on the first information in the uplink data information.

[0199] The manner in which the first AMF determines the target server has been described in detail in the preceding embodiment and will not be repeated here.

[0200] S706: The first AMF sends the uplink data information to the target server.

[0201] Here, although not shown in the figure, in one case, the first AMF can send the uplink data information to the target server through the NEF.

[0202] S707: The target server sends downlink data information to the first AMF.

[0203] Specifically, the downlink data information is a response to the uplink data information; the downlink data information may include a device identifier. The downlink data information may be encapsulated as a DL data container; that is, when the target server has DL data to send to the device, the target server may send the DL data container to the first AMF.

[0204] Here, although not shown in the figure, in one case, the target SP can send downlink data information to the first AMF through the NEF.

[0205] S708. The first AMF sends downlink data information to the gNB.

[0206] S709: The gNB sends downlink data information to the device.

[0207] The following uses a terminal device as a device, an access network device as a gNB, and a first core network device as a first AMF as an example. In conjunction with FIG8 , an exemplary description of the communication method of this embodiment is provided, including:

[0208] S801: The device sends a registration request message to the first AMF through the gNB.

[0209] The process of establishing a NAS connection between the device and the first AMF begins with S1001. S1001 may include establishing an RRC connection between the device and the gNB, and including a NAS message in the RRC message. The NAS message in this case is a registration request message, which includes the device ID, registration type, and other information.

[0210] S802: The device receives a registration accept message sent by the first AMF through the gNB. The registration accept message carries the identifier of the target server.

[0211] Specifically, after the first AMF obtains the user data of the device, the first AMF returns a registration acceptance message to the device. The message may carry 5G-GUTI and the identifier of the target server. The identifier of the target server can be expressed as AIoT server ID; AIoT server ID is used to indicate the destination identifier (i.e., the identifier of the target server) for the device to send AIoT data.

[0212] It should be understood that in S802, the registration acceptance message may not carry the identifier of the target server. The identifier of the target server may be pre-configured in the terminal device (ie, Device).

[0213] S803: The device returns a registration completion message to the first AMF through the NAS connection.

[0214] S804: The device sends uplink data information carried by the uplink NAS transport message to the first AMF.

[0215] That is, when the device is in a connected state, a UL NAS TRANSPORT (uplink NAS transport message) message is sent on the NAS connection, and the message includes uplink data information (specifically, AIoT data); the uplink data information may also include an identifier of the target server. The identifier of the target server may be the content contained in the routing information in the uplink data information. Similar to the above example, the uplink data information may be an uplink data container, and the uplink data container may specifically be a UL AIoT data container. In the header part of the UL AIoT data container, the identifier of the target server of the first information may be included. The specific description of the first information is the same as that in the above embodiment and will not be repeated here.

[0216] S805: The first AMF sends the uplink data information to the target server.

[0217] Specifically, the first AMF sends the uplink data information to the appropriate server according to the identifier of the target server (which can be expressed as AIoT server ID) contained in the first information of the uplink data information carried in the uplink NAS transmission message.

[0218] The steps for sending downlink data are as follows:

[0219] S806. The target server sends downlink data information to the first AMF.

[0220] The downlink data information is the DL data container carried in the DL Transport message, and the downlink data information also needs to carry a device identifier.

[0221] S807. The first AMF sends the downlink data information carried by the downlink NAS transmission message to the device.

[0222] That is, the first AMF carries the downlink data information in a DL NAS TRANSPORT message (downlink NAS transport message) and sends it to the device. The message carries the downlink data information (specifically, it can be an AIoT data container).

[0223] The following uses a terminal device as a device, an access network device as a gNB, and a first core network device as a first AMF as an example, and combines FIG9 to further illustrate another exemplary communication method provided in this embodiment, including:

[0224] S901: The device sends uplink data information carried by a control plane service request message to the first AMF.

[0225] This step is different from the above-mentioned exemplary description in that the registration process of S801 to S803 may have been completed before executing S901. However, the current device is in an idle state (or non-connected state). At this time, if the device has AIoT data (i.e., uplink data information) to send, the device can directly send a control plane service request message to the first AMF (this message can make the device enter a connected state). The control plane service request message includes AIoT data (i.e., uplink data information); the uplink data information can also include the identifier of the target server. It is the same as the above-mentioned exemplary description and will not be repeated here.

[0226] S902: The first AMF sends the uplink data information to the target server.

[0227] Specifically, the first AMF sends the uplink data information to the appropriate server according to the identifier of the target server (which can be expressed as AIoT server ID) contained in the uplink data information carried in the uplink NAS transmission message.

[0228] The steps for sending downlink data are as follows:

[0229] S903, the target server sends downlink data information to the first AMF.

[0230] S904: The first AMF sends the downlink data information carried by the downlink NAS transmission message to the device.

[0231] Here, the processing of S903 and S904 is the same as the specific processing of S806 and S807 in the above example, and will not be repeated.

[0232] As can be seen, by adopting the above solution, the network-side device can determine the target server for data transmission based on the uplink data information sent by the terminal device, and send the uplink data information directly to the target server. This can reduce the terminal device's need to perform complex communication processes to transmit data to the network side, as well as the signaling overhead caused by complex communication processes. In particular, in the scenario of zero-power terminal application, it can better adapt to the low complexity characteristics of zero-power terminal.

[0233] FIG10 is a schematic block diagram of an access network device according to an embodiment of the present application. The access network device may include:

[0234] The first communication unit 1001 is configured to receive uplink data information sent by a terminal device; and send the uplink data information to the first core network device;

[0235] The first processing unit 1002 is configured to determine a first core network device based on the first information in the uplink data information.

[0236] The first information includes: routing related information.

[0237] The routing-related information includes at least one of the following: routing-related identifiers and routing path information.

[0238] The routing-related identifier includes at least one of the following: an identifier of routing information, an identifier of a target server.

[0239] The first information includes at least one of the following: a device manufacturer identifier, a service provider identifier, and a terminal device identifier.

[0240] The uplink data information includes an uplink data container.

[0241] The first information is carried by a header portion of the uplink data container, or the first information is carried by a data portion of the uplink data container.

[0242] The first processing unit 1002 is configured to determine the first core network device based on routing related information in the first information of the uplink data information.

[0243] The first processing unit 1002 is configured to determine the first core network device based on the first information of the uplink data information and the first pre-configuration information.

[0244] The first pre-configuration information includes: parameters of the candidate device corresponding to the candidate server supported by each candidate core network in one or more candidate core network devices; the parameters of the candidate device corresponding to the candidate server include at least one of the following: candidate device manufacturer identifier, candidate service provider identifier, and candidate device identifier.

[0245] The first communication unit 1001 is configured to receive the uplink data information sent by the terminal device through an access layer AS connection with the terminal device.

[0246] The first communication unit 1001 is used to receive downlink data information sent by the first core network device; wherein the downlink data information is response information of the uplink data information; and send the downlink data information to the terminal device.

[0247] The downlink data information includes relevant information of the terminal device.

[0248] The downlink data information includes a downlink data container.

[0249] The terminal device is a zero-power device, and / or the first core network device is a first access and mobility management function AMF entity.

[0250] FIG11 is a schematic block diagram of a first core network device according to an embodiment of the present application. The device may include:

[0251] The second communication unit 1101 is configured to receive uplink data information and send the uplink data information to a target server;

[0252] The second processing unit 1102 is configured to determine a target server based on the first information in the uplink data information.

[0253] The first information includes: routing related information.

[0254] The routing-related information includes at least one of the following: routing-related identifiers and routing path information.

[0255] The routing-related identifier includes at least one of the following: an identifier of routing information, an identifier of a target server.

[0256] The first information includes at least one of the following: a device manufacturer identifier, a service provider identifier, and a terminal device identifier.

[0257] The uplink data information is an uplink data container.

[0258] The first information is carried by a header portion of the uplink data container, or the first information is carried by a data portion of the uplink data container.

[0259] The second processing unit is configured to determine the target server based on the routing related information in the first information of the uplink data information.

[0260] The second processing unit is configured to determine the target server based on the first information of the uplink data information and second pre-configuration information.

[0261] The second pre-configuration information is shared by one or more candidate core network devices, where the one or more candidate core network devices include the first core network device;

[0262] The second pre-configuration information includes: parameters of the candidate device corresponding to each candidate server among the one or more candidate servers; wherein the parameters of the candidate device include at least one of the following: an identifier of the candidate device, a service area of ​​the candidate device, an identifier of a manufacturer of the candidate device, and an identifier of a candidate service provider.

[0263] The second communication unit is used to receive uplink data information sent by the access network device.

[0264] The second communication unit is used to receive uplink data information sent by the terminal device.

[0265] The second communication unit is used to receive uplink data information carried by an uplink NAS transmission message sent by a terminal device; or, to receive uplink data information carried by a control plane service request message sent by a terminal device.

[0266] The second communication unit is used to establish a non-access stratum NAS connection with the terminal device.

[0267] The second communication unit is used to receive a registration request message sent by the terminal device through the access network device; send a registration acceptance message to the terminal device through the access network device; the registration acceptance message is used to indicate that the terminal device has completed the establishment of a NAS connection with the first core network device; and receive a registration completion message sent by the terminal device through the NAS connection.

[0268] The registration acceptance message carries the identifier of the target server.

[0269] The second communication unit is used to send the uplink data information to the target server through the second core network device.

[0270] The second communication unit is configured to receive downlink data information sent by the target server; wherein the downlink data information is response information to the uplink data information; and send the downlink data information.

[0271] The downlink data information includes relevant information of the terminal device.

[0272] The downlink data information is a downlink data container.

[0273] The second communication unit is used to receive downlink data information sent by the target server through the second core network device.

[0274] The second core network device is a network open function NEF entity.

[0275] The second communication unit is used to send the downlink data information to the access network device.

[0276] The second communication unit is used to send the downlink data information to the terminal device.

[0277] The second communication unit is used to send the downlink data information carried by the downlink NAS transmission message to the terminal device.

[0278] The terminal device is a zero-power device, and / or the first core network device is a first AMF entity.

[0279] FIG12 is a schematic block diagram of a terminal device according to an embodiment of the present application. The terminal device may include:

[0280] The third communication unit 1201 is configured to send uplink data information; wherein the first information in the uplink data information is used to determine the first core network device and / or the target server.

[0281] The first information includes: routing related information.

[0282] The routing-related information includes at least one of the following: a routing-related identifier, an identifier of a target server, and routing information.

[0283] The first information includes at least one of the following: an identifier of a device manufacturer, an identifier of a service provider, and an identifier of the terminal device.

[0284] The routing related information is pre-configured; and / or at least one of the device manufacturer identifier, the service provider identifier, and the terminal device identifier is pre-configured.

[0285] The uplink data information includes an uplink data container.

[0286] The first information is carried by a header portion of the uplink data container, or the first information is carried by a data portion of the uplink data container.

[0287] The third communication unit is configured to send the uplink data information to the access network device through an access layer AS connection between the access network devices.

[0288] The third communication unit is used to establish an AS connection with the access network device when the terminal device is located in a target area; wherein the target area is preconfigured.

[0289] The third communication unit is used to send uplink data information to the first core network device.

[0290] The uplink data information is carried by an uplink NAS transmission message, or by a control plane service request message.

[0291] The third communication unit is used to establish a non-access stratum NAS connection with the first core network device.

[0292] The third communication unit is used to send a registration request message to the first core network device through the access network device; receive a registration acceptance message sent by the first core network device through the access network device; the registration acceptance message is used to indicate that the terminal device and the first core network device have completed the establishment of a NAS connection; and return a registration completion message to the first core network device through the NAS connection.

[0293] The registration acceptance message carries the identifier of the target server.

[0294] The third communication unit is configured to receive downlink data information; wherein the downlink data information is response information to the uplink data information.

[0295] The third communication unit is used to receive downlink data information sent by the access network device.

[0296] The third communication unit is used to receive downlink data information sent by the first core network device.

[0297] The downlink data information is carried by a downlink NAS transmission message.

[0298] The downlink data information includes relevant information of the terminal device.

[0299] The downlink data information includes a downlink data container.

[0300] The terminal device is a zero-power device, and / or the first core network device is a first AMF entity.

[0301] It should be understood that in addition to the above-mentioned third communication unit, the terminal device may also include a third processing unit, which can perform processing such as generating uplink data information in the aforementioned communication method, which will not be described in detail here.

[0302] Figure 13 is a schematic structural diagram of a communication device 1300 according to an embodiment of the present application. The communication device 1300 includes a processor 1310, which can call and execute a computer program from a memory to enable the communication device 1300 to implement the method in the embodiment of the present application.

[0303] In a possible implementation, the communication device 1300 may further include a memory 1320. The processor 1310 may call and execute a computer program from the memory 1320 to enable the communication device 1300 to implement the method in the embodiment of the present application.

[0304] The memory 1320 may be a separate device independent of the processor 1310 , or may be integrated into the processor 1310 .

[0305] In one possible implementation, the communication device 1300 may further include a transceiver 1330 , and the processor 1310 may control the transceiver 1330 to communicate with other devices. Specifically, the transceiver 1330 may send information or data to other devices, or receive information or data sent by other devices.

[0306] The transceiver 1330 may include a transmitter and a receiver. The transceiver 1330 may further include an antenna, and the number of antennas may be one or more.

[0307] In one possible implementation, the communication device 1300 may be the access network device of the embodiment of the present application, and the communication device 1300 may implement the corresponding processes implemented by the access network device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0308] In one possible implementation, the communication device 1300 may be the first core network device of an embodiment of the present application, and the communication device 1300 may implement the corresponding processes implemented by the first core network device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0309] In one possible implementation, the communication device 1300 may be a terminal device of an embodiment of the present application, and the communication device 1300 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0310] 14 is a schematic structural diagram of a chip 1400 according to an embodiment of the present application. The chip 1400 includes a processor 1410, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

[0311] In a possible implementation, the chip 1400 may further include a memory 1420. The processor 1410 may call and execute a computer program from the memory 1420 to implement the method executed by the terminal device or the access network device in the embodiment of the present application.

[0312] The memory 1420 may be a separate device independent of the processor 1410 , or may be integrated into the processor 1410 .

[0313] In a possible implementation, the chip 1400 may further include an input interface 1430. The processor 1410 may control the input interface 1430 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0314] In a possible implementation, the chip 1400 may further include an output interface 1440. The processor 1410 may control the output interface 1440 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0315] In one possible implementation, the chip can be applied to the access network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the access network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0316] In one possible implementation, the chip can be applied to the first core network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first core network device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0317] In one possible implementation, the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0318] The chips used in the access network device and the terminal device may be the same chip or different chips.

[0319] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0320] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0321] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM).

[0322] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0323] FIG15 is a schematic block diagram of a communication system 1500 according to an embodiment of the present application. The communication system 1500 includes a terminal device 1510 and a network device 1520 .

[0324] The terminal device 1510 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1520 may be used to implement the corresponding functions implemented by the network device (access network device and / or first core network device) in the above method. For the sake of brevity, these will not be described in detail here.

[0325] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, 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 in accordance with 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 devices. 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 a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0326] It should be understood that in the 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.

[0327] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0328] 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 modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within 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 communication method, comprising: The access network device receives uplink data information sent by the terminal device; The access network device determines a first core network device based on the first information in the uplink data information; The access network device sends the uplink data information to the first core network device.

2. The method according to claim 1, wherein The first information includes: routing related information.

3. The method according to claim 2, wherein: The routing-related information includes at least one of the following: routing-related identifiers and routing path information.

4. The method according to claim 3, wherein: The routing-related identifier includes at least one of the following: an identifier of routing information, an identifier of a target server.

5. The method according to claim 1, wherein The first information includes at least one of the following: a device manufacturer identifier, a service provider identifier, and a terminal device identifier.

6. The method according to any one of claims 2 to 5, wherein: The uplink data information includes an uplink data container.

7. The method according to claim 6, wherein: The first information is carried by a header portion of the uplink data container, or the first information is carried by a data portion of the uplink data container.

8. The method according to claim 2, wherein: The access network device determines, based on the first information in the uplink data information, a first core network device, including: The access network device determines the first core network device based on the routing related information in the first information of the uplink data information.

9. The method according to claim 5, wherein: The access network device determines, based on the first information in the uplink data information, a first core network device, including: The access network device determines the first core network device based on the first information in the uplink data information and the first pre-configuration information.

10. The method according to claim 9, wherein: The first pre-configuration information includes: parameters of the candidate device corresponding to the candidate server supported by each candidate core network in one or more candidate core network devices; the parameters of the candidate device corresponding to the candidate server include at least one of the following: candidate device manufacturer identifier, candidate service provider identifier, and candidate device identifier.

11. The method according to any one of claims 1 to 10, wherein: The access network device receives uplink data information sent by the terminal device, including: The access network device receives the uplink data information sent by the terminal device through the access layer AS connection between the access network device and the terminal device.

12. The method according to claim 1, wherein The method further comprises: The access network device receives downlink data information sent by the first core network device; wherein the downlink data information is response information to the uplink data information; The access network device sends the downlink data information to the terminal device.

13. The method according to claim 12, wherein: The downlink data information includes relevant information of the terminal device.

14. The method according to claim 12 or 13, wherein: The downlink data information includes a downlink data container.

15. The method according to any one of claims 1 to 14, wherein: The terminal device is a zero-power device, and / or the first core network device is a first access and mobility management function AMF entity.

16. A communication method, comprising: The first core network device receives uplink data information; The first core network device determines a target server based on the first information in the uplink data information; The first core network device sends the uplink data information to the target server.

17. The method according to claim 16, wherein The first information includes: routing related information.

18. The method according to claim 17, wherein The routing-related information includes at least one of the following: routing-related identifiers and routing path information.

19. The method according to claim 18, wherein The routing-related identifier includes at least one of the following: an identifier of routing information, an identifier of a target server.

20. The method according to claim 16, wherein The first information includes at least one of the following: a device manufacturer identifier, a service provider identifier, and a terminal device identifier.

21. The method according to any one of claims 17 to 20, wherein: The uplink data information is an uplink data container.

22. The method according to claim 21, wherein The first information is carried by a header portion of the uplink data container, or the first information is carried by a data portion of the uplink data container.

23. The method according to claim 17, wherein The first core network device determines a target server based on first information in the uplink data information, including: The first core network device determines the target server based on the routing related information in the first information of the uplink data information.

24. The method according to claim 20, wherein The first core network device determines a target server based on the first information in the uplink data information, including: The first core network device determines the target server based on the first information and second pre-configuration information in the uplink data information.

25. The method according to claim 24, wherein The second pre-configuration information is shared by one or more candidate core network devices, where the one or more candidate core network devices include the first core network device; The second pre-configuration information includes: parameters of the candidate device corresponding to each candidate server among the one or more candidate servers; wherein the parameters of the candidate device include at least one of the following: an identifier of the candidate device, a service area of ​​the candidate device, an identifier of a manufacturer of the candidate device, and an identifier of a candidate service provider.

26. The method according to any one of claims 16 to 25, wherein: The first core network device receives uplink data information, including: The first core network device receives uplink data information sent by the access network device.

27. The method according to any one of claims 16 to 25, wherein: The first core network device receives uplink data information, including: The first core network device receives uplink data information sent by the terminal device.

28. The method according to claim 27, wherein The first core network device receives uplink data information sent by the terminal device, including: The first core network device receives uplink data information carried by an uplink NAS transmission message sent by the terminal device; Alternatively, the first core network device receives uplink data information carried by a control plane service request message sent by the terminal device.

29. The method according to claim 28, wherein Also includes: The first core network device establishes a non-access layer NAS connection with the terminal device.

30. The method according to claim 29, wherein The first core network device establishes a non-access stratum (NAS) connection with the terminal device, including: The first core network device receives the registration request message sent by the terminal device through the access network device; The first core network device sends a registration acceptance message to the terminal device through the access network device; the registration acceptance message is used to indicate that the terminal device has completed the establishment of a NAS connection with the first core network device; The first core network device receives the registration completion message sent by the terminal device through the NAS connection.

31. The method according to claim 30, wherein The registration acceptance message carries the identifier of the target server.

32. The method according to any one of claims 16 to 31, wherein: The first core network device sending the uplink data information to the target server includes: The first core network device sends the uplink data information to the target server through the second core network device.

33. The method of claim 16, wherein: The method further comprises: The first core network device receives downlink data information sent by the target server; wherein the downlink data information is response information of the uplink data information; The first core network device sends the downlink data information.

34. The method according to claim 33, wherein The downlink data information includes relevant information of the terminal device.

35. The method according to claim 33 or 34, wherein The downlink data information includes a downlink data container.

36. The method according to any one of claims 33 to 35, wherein: The first core network device receives downlink data information sent by the target server, including: The first core network device receives the downlink data information sent by the target server through the second core network device.

37. The method according to claim 32 or 36, wherein The second core network device is a network open function NEF entity.

38. The method of claim 33, wherein: The first core network device sending the downlink data information includes: The first core network device sends the downlink data information to the access network device.

39. The method of claim 33, wherein: The first core network device sending the downlink data information includes: The first core network device sends the downlink data information to the terminal device.

40. The method of claim 39, wherein The first core network device sending the downlink data information to the terminal device includes: The first core network device sends the downlink data information carried by the downlink NAS transmission message to the terminal device.

41. The method according to any one of claims 27 to 30, 34, 39, and 40, wherein: The terminal device is a zero-power consumption device.

42. The method according to any one of claims 16 to 41, wherein: The first core network device is the first AMF entity.

43. A communication method comprising: The terminal device sends uplink data information; wherein, the first information in the uplink data information is used to determine the first core network device and / or the target server.

44. The method according to claim 43, wherein The first information includes: routing related information.

45. The method of claim 44, wherein: The routing-related information includes at least one of the following: routing-related identifiers and routing path information.

46. ​​The method of claim 45, wherein The routing-related identifier includes at least one of the following: an identifier of a target server and routing information.

47. The method of claim 43, wherein The first information includes at least one of the following: a device manufacturer identifier, a service provider identifier, and a terminal device identifier.

48. The method according to any one of claims 44 to 47, wherein: The routing related information is pre-configured; And / or, at least one of the device manufacturer identifier, the service provider identifier, and the terminal device identifier is preconfigured.

49. The method according to any one of claims 44 to 47, wherein: The uplink data information includes an uplink data container.

50. The method of claim 49, wherein The first information is carried by a header portion of the uplink data container, or the first information is carried by a data portion of the uplink data container.

51. The method according to any one of claims 43 to 50, wherein: The terminal device sends uplink data information, including: The terminal device sends the uplink data information to the access network device through the access layer AS connection between the access network devices.

52. The method of claim 51, wherein The method further comprises: When the terminal device is located in a target area, the terminal device establishes an AS connection with the access network device; wherein the target area is preconfigured.

53. The method according to any one of claims 43 to 50, wherein: The terminal device sends uplink data information, including: The terminal device sends uplink data information to the first core network device.

54. The method of claim 53, wherein: The uplink data information is carried by an uplink NAS transmission message, or by a control plane service request message.

55. The method of claim 54, further comprising: The terminal device establishes a non-access layer NAS connection with the first core network device.

56. The method of claim 55, wherein: The terminal device establishes a NAS connection with the first core network device, including: The terminal device sends a registration request message to the first core network device through the access network device; The terminal device receives, through the access network device, a registration acceptance message sent by the first core network device; the registration acceptance message is used to indicate that the terminal device has completed establishing a NAS connection with the first core network device; The terminal device returns a registration completion message to the first core network device through the NAS connection.

57. The method of claim 56, wherein The registration acceptance message carries the identifier of the target server.

58. The method of claim 43, wherein The method further comprises: The terminal device receives downlink data information; wherein the downlink data information is response information to the uplink data information.

59. The method of claim 58, wherein The terminal device receives downlink data information, including: The terminal device receives downlink data information sent by the access network device.

60. The method of claim 58, wherein The terminal device receives downlink data information, including: The terminal device receives downlink data information sent by the first core network device.

61. The method of claim 60, wherein: The downlink data information is carried by a downlink NAS transmission message.

62. The method according to any one of claims 58 to 61, wherein: The downlink data information includes relevant information of the terminal device.

63. The method according to any one of claims 58 to 62, wherein: The downlink data information includes a downlink data container.

64. The method according to any one of claims 43 to 63, wherein: The terminal device is a zero-power device, and / or the first core network device is a first AMF entity.

65. An access network device comprising: A first communication unit, configured to receive uplink data information sent by a terminal device; Sending the uplink data information to the first core network device; The first processing unit is configured to determine a first core network device based on first information in the uplink data information.

66. The access network device according to claim 65, wherein: The first information includes: routing related information.

67. The access network device according to claim 66, wherein: The routing-related information includes at least one of the following: routing-related identifiers and routing path information.

68. The access network device according to claim 67, wherein: The routing-related identifier includes at least one of the following: an identifier of routing information, an identifier of a target server.

69. The access network device according to claim 65, wherein: The first information includes at least one of the following: a device manufacturer identifier, a service provider identifier, and a terminal device identifier.

70. The access network device according to any one of claims 66 to 69, wherein: The uplink data information includes an uplink data container.

71. The access network device according to claim 70, wherein: The first information is carried by a header portion of the uplink data container, or the first information is carried by a data portion of the uplink data container.

72. The access network device according to claim 66, wherein: The first processing unit is configured to determine the first core network device based on routing related information in the first information of the uplink data information.

73. The access network device according to claim 69, wherein: The first processing unit is configured to determine the first core network device based on the first information of the uplink data information and the first pre-configuration information.

74. The access network device according to claim 73, wherein: The first pre-configuration information includes: parameters of the candidate device corresponding to the candidate server supported by each candidate core network in one or more candidate core network devices; the parameters of the candidate device corresponding to the candidate server include at least one of the following: candidate device manufacturer identifier, candidate service provider identifier, and candidate device identifier.

75. The access network device according to any one of claims 65 to 74, wherein: The first communication unit is used to receive the uplink data information sent by the terminal device through an access layer AS connection with the terminal device.

76. The access network device according to claim 65, wherein: The first communication unit is used to receive downlink data information sent by the first core network device; wherein the downlink data information is response information of the uplink data information; and send the downlink data information to the terminal device.

77. The access network device according to claim 76, wherein: The downlink data information includes relevant information of the terminal device.

78. The access network device according to claim 76 or 77, wherein: The downlink data information includes a downlink data container.

79. The access network device according to any one of claims 65 to 78, wherein: The terminal device is a zero-power device, and / or the first core network device is a first access and mobility management function AMF entity.

80. A first core network device, comprising: A second communication unit, configured to receive uplink data information; Sending the uplink data information to a target server; The second processing unit is configured to determine a target server based on the first information in the uplink data information.

81. The first core network device according to claim 80, wherein: The first information includes at least one of the following: routing related information.

82. The first core network device according to claim 81, wherein: The routing-related information includes at least one of the following: routing-related identifiers and routing path information.

83. The first core network device according to claim 82, wherein: The routing-related identifier includes at least one of the following: an identifier of routing information, an identifier of a target server.

84. The first core network device according to claim 80, wherein: The first information includes at least one of the following: a device manufacturer identifier, a service provider identifier, and a terminal device identifier.

85. The first core network device according to any one of claims 81 to 84, wherein: The uplink data information is an uplink data container.

86. The first core network device according to claim 85, wherein: The first information is carried by a header portion of the uplink data container, or the first information is carried by a data portion of the uplink data container.

87. The first core network device according to claim 81, wherein: The second processing unit is configured to determine the target server based on the routing related information in the first information of the uplink data information.

88. The first core network device according to claim 84, wherein: The second processing unit is configured to determine the target server based on the first information of the uplink data information and second pre-configuration information.

89. The first core network device according to claim 88, wherein: The second pre-configuration information is shared by one or more candidate core network devices, where the one or more candidate core network devices include the first core network device; The second pre-configuration information includes: parameters of the candidate device corresponding to each candidate server among the one or more candidate servers; wherein the parameters of the candidate device include at least one of the following: an identifier of the candidate device, a service area of ​​the candidate device, an identifier of a manufacturer of the candidate device, and an identifier of a candidate service provider.

90. The first core network device according to any one of claims 80 to 89, wherein: The second communication unit is used to receive uplink data information sent by the access network device.

91. The first core network device according to any one of claims 80 to 89, wherein: The second communication unit is used to receive uplink data information sent by the terminal device.

92. The first core network device according to claim 91, wherein: The second communication unit is configured to receive uplink data information carried by an uplink NAS transmission message sent by a terminal device; Alternatively, receive uplink data information carried by a control plane service request message sent by the terminal device.

93. The first core network device according to claim 92, wherein: The second communication unit is used to establish a non-access stratum NAS connection with the terminal device.

94. The first core network device according to claim 93, wherein: The second communication unit is used to receive a registration request message sent by the terminal device through the access network device; send a registration acceptance message to the terminal device through the access network device; the registration acceptance message is used to indicate that the terminal device has completed the establishment of a NAS connection with the first core network device; and receive a registration completion message sent by the terminal device through the NAS connection.

95. The first core network device according to claim 94, wherein: The registration acceptance message carries the identifier of the target server.

96. The first core network device according to any one of claims 80 to 95, wherein: The second communication unit is used to send the uplink data information to the target server through the second core network device.

97. The first core network device according to claim 80, wherein: The second communication unit is configured to receive downlink data information sent by the target server; wherein the downlink data information is response information to the uplink data information; and send the downlink data information.

98. The first core network device according to claim 97, wherein: The downlink data information includes relevant information of the terminal device.

99. The first core network device according to claim 97 or 98, wherein: The downlink data information includes a downlink data container.

100. The first core network device according to any one of claims 97 to 99, wherein: The second communication unit is used to receive downlink data information sent by the target server through the second core network device.

101. The first core network device according to claim 96 or 100, wherein: The second core network device is a network open function NEF entity.

102. The first core network device according to claim 97, wherein: The second communication unit is used to send the downlink data information to the access network device.

103. The first core network device according to claim 97, wherein: The second communication unit is used to send the downlink data information to the terminal device.

104. The first core network device according to claim 103, wherein: The second communication unit is used to send the downlink data information carried by the downlink NAS transmission message to the terminal device.

105. The method according to any one of claims 91-94, 98, 103, and 104, wherein: The terminal device is a zero-power consumption device.

106. The method according to any one of claims 80 to 105, wherein: The first core network device is the first AMF entity.

107. A terminal device comprising: The third communication unit is used to send uplink data information; wherein, the first information in the uplink data information is used to determine the first core network device and / or the target server.

108. The terminal device according to claim 107, wherein: The first information includes: routing related information.

109. The terminal device according to claim 108, wherein: The routing-related information includes at least one of the following: routing-related identifiers and routing path information.

110. The terminal device according to claim 109, wherein: The routing-related identifier includes at least one of the following: an identifier of a target server and routing information.

111. The terminal device according to claim 107, wherein: The first information includes at least one of the following: an identifier of a device manufacturer, an identifier of a service provider, and an identifier of the terminal device.

112. The terminal device according to any one of claims 108 to 111, wherein: The routing related information is pre-configured; and / or at least one of the device manufacturer identifier, the service provider identifier, and the terminal device identifier is pre-configured.

113. The terminal device according to any one of claims 108 to 112, wherein: The uplink data information includes an uplink data container.

114. The terminal device according to claim 113, wherein: The first information is carried by a header portion of the uplink data container, or the first information is carried by a data portion of the uplink data container.

115. The terminal device according to any one of claims 108 to 114, wherein: The third communication unit is configured to send the uplink data information to the access network device through an access layer AS connection between the access network devices.

116. The terminal device according to claim 115, wherein: The third communication unit is used to establish an AS connection with the access network device when the terminal device is located in a target area; wherein the target area is preconfigured.

117. The terminal device according to any one of claims 108 to 114, wherein: The third communication unit is used to send uplink data information to the first core network device.

118. The terminal device according to claim 117, wherein: The uplink data information is carried by an uplink NAS transmission message, or by a control plane service request message.

119. The terminal device according to claim 117, wherein: The third communication unit is used to establish a non-access stratum NAS connection with the first core network device.

120. The terminal device according to claim 119, wherein: The third communication unit is configured to send a registration request message to the first core network device through the access network device; Receiving, through the access network device, a registration acceptance message sent by the first core network device; The registration reception message is used to indicate that the terminal device has completed establishing a NAS connection with the first core network device; and return a registration completion message to the first core network device through the NAS connection.

121. The terminal device according to claim 120, wherein: The registration acceptance message carries the identifier of the target server.

122. The terminal device according to claim 107, wherein: The third communication unit is configured to receive downlink data information; wherein the downlink data information is response information to the uplink data information.

123. The terminal device according to claim 122, wherein: The third communication unit is used to receive downlink data information sent by the access network device.

124. The terminal device according to claim 122, wherein: The third communication unit is used to receive downlink data information sent by the first core network device.

125. The terminal device according to claim 124, wherein: The downlink data information is carried by a downlink NAS transmission message.

126. The terminal device according to any one of claims 122 to 125, wherein: The downlink data information includes relevant information of the terminal device.

127. The terminal device according to any one of claims 122 to 126, wherein: The downlink data information includes a downlink data container.

128. The terminal device according to any one of claims 107 to 127, wherein: The terminal device is a zero-power device, and / or the first core network device is a first AMF entity.

129. An access network device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the access network device executes the method according to any one of claims 1 to 15.

130. A first core network device, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory so that the first core network device executes the method as described in any one of claims 16 to 42.

131. A terminal device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory so that the terminal device executes the method as described in any one of claims 43 to 64.

132. A chip comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as described in any one of claims 1 to 15, or 16 to 42, or 43 to 64.

133. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the method as claimed in any one of claims 1 to 15, or 16 to 42, or 43 to 64.

134. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 15, or 16 to 42, or 43 to 64.

135. A computer program causing a computer to perform the method of any one of claims 1 to 15, or 16 to 42, or 43 to 64.

136. A computer program causing a computer to perform the method of any one of claims 1 to 15, or 16 to 42, or 43 to 64.

Images