Wireless communication method, terminal device, and network device

Abstract

Provided are a wireless communication method, a terminal device, and a network device. The wireless communication method comprises: a terminal device sending a first message to a first network element by means of a service-based interface; and / or the terminal device receiving, by means of the service-based interface, a second message sent by the first network element, wherein the first message and / or the second message is / are transmitted on a user plane by means of a first session.

Description

Method, terminal device and network device for wireless communication TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and more particularly, to a method, a terminal device and a network device for wireless communication. BACKGROUND

[0002] In order to reduce the overhead of access stratum (AS) messages required for transmitting non access stratum (NAS) messages between a terminal device and a core network, in some communication systems (such as a 6G system), the terminal device can interact with other network elements (such as network elements in the core network) through a service based interface (SBI). In this scenario, how the terminal device interacts with other network elements through the service based interface is a problem to be solved.

[0003] SUMMARY

[0004] The present application provides a method, a terminal device and a network device for wireless communication. The various aspects of the present application are described below.

[0005] In a first aspect, a method for wireless communication is provided, comprising: sending, by a terminal device, a first message to a first network element through a service based interface; and / or receiving, by the terminal device, a second message sent by the first network element through the service based interface; wherein the first message and / or the second message is transmitted in a user plane through a first session.

[0006] In a second aspect, a method for wireless communication is provided, comprising: receiving, by a first network element, a first message sent by a terminal device through a service based interface; and / or sending, by the first network element, a second message to the terminal device through the service based interface; wherein the first message and / or the second message is transmitted in a user plane through a first session.

[0007] In a third aspect, a method for wireless communication is provided, comprising: receiving, by a second network element, a third message sent by a terminal device, the third message being used to determine a first network element; wherein the terminal device interacts with the first network element through a service based interface, and messages exchanged between the terminal device and the first network element are transmitted in a user plane through a first session.

[0008] In a fourth aspect, a method for wireless communication is provided, comprising: receiving, by a third network element, a first NAS message sent by a terminal device, the first NAS message being used to trigger establishment of a first session; wherein messages exchanged between the terminal device and a first network element are transmitted in a user plane through the first session, and the terminal device interacts with the first network element through a service based interface.

[0009] In a fifth aspect, a terminal device is provided, comprising: a first sending module configured to send a first message to a first network element via a service-based interface; and / or a first receiving module configured to receive a second message sent by the first network element via the service-based interface; wherein the first message and / or the second message are transmitted in a user plane via a first session.

[0010] In a sixth aspect, a network device is provided, the network device being a first network element, the network device comprising: a first receiving module configured to receive a first message sent by a terminal device via a service-based interface; and / or a first sending module configured to send a second message to the terminal device via the service-based interface; wherein the first message and / or the second message are transmitted in a user plane via a first session.

[0011] In a seventh aspect, a network device is provided, the network device being a second network element, the network device comprising: a first receiving module configured to receive a third message sent by a terminal device, the third message being used to determine a first network element; wherein the terminal device interacts with the first network element via a service-based interface, and messages exchanged between the terminal device and the first network element are transmitted in a user plane via a first session.

[0012] In an eighth aspect, a network device is provided, the network device being a third network element, the network device comprising: a first receiving module configured to receive a first NAS message sent by a terminal device, the first NAS message being used to trigger establishment of a first session; wherein messages exchanged between the terminal device and a first network element are transmitted in a user plane via the first session, and the terminal device interacts with the first network element via a service-based interface.

[0013] In a ninth aspect, a terminal device is provided, comprising a processor, a memory, and a communication interface, the memory being configured to store one or more computer programs, and the processor being configured to invoke the computer programs in the memory to cause the terminal device to perform some or all of the steps in the method of the first aspect.

[0014] In a tenth aspect, a network device is provided, comprising a processor, a memory, and a communication interface, the memory being configured to store one or more computer programs, and the processor being configured to invoke the computer programs in the memory to cause the network device to perform some or all of the steps in the method of any one of the second aspect to the fourth aspect.

[0015] In a eleventh aspect, an embodiment of the present application provides a communication system, which comprises the terminal device and / or the network device described above. In another possible design, the system can further comprise other devices interacting with the terminal device or the network device in the solution provided by an embodiment of the present application.

[0016] In a twelfth aspect, an embodiment of the present application provides a computer readable storage medium, which stores a computer program. The computer program causes a computer to perform some or all of the steps of the method in any of the aspects described above.

[0017] In a thirteenth aspect, an embodiment of the present application provides a computer program product. The computer program product includes a non-transitory computer-readable storage medium storing a computer program. The computer program is operable to cause a computer to perform some or all of the steps of the method in any of the aspects described above. In some implementations, the computer program product can be a software installation package.

[0018] In a fourteenth aspect, an embodiment of the present application provides a chip. The chip includes a memory and a processor. The processor can invoke and run a computer program from the memory, to implement some or all of the steps described in the method in any of the aspects described above.

[0019] In an embodiment of the present application, the message (such as the first message and / or the second message) transmitted between the terminal device and the first network element can be transmitted in the user plane through the first session, so as to realize the interaction between the terminal device and other network elements through the service-based interface. Compared with the traditional solution of carrying the NAS message through the AS message, the transmission overhead of the AS message can be reduced. BRIEF DESCRIPTION OF DRAWINGS

[0020] FIG. 1 is an example diagram of a system architecture of a 5G system.

[0021] FIG. 2 is another example diagram of a system architecture of a 5G system.

[0022] FIG. 3 is an example diagram of a protocol stack adopted when interacting based on a service-based interface.

[0023] FIG. 4 is an example diagram of a system architecture of a wireless communication system to which embodiments of the present application are applicable.

[0024] FIG. 5 is an example diagram of a protocol stack to which embodiments of the present application are applicable.

[0025] FIG. 6 is a flow diagram of a method of wireless communication provided by an embodiment of the present application.

[0026] FIG. 7 is a flow diagram of a method of determining a first network element by a terminal device provided by an embodiment of the present application.

[0027] FIG. 8 is a flow diagram of a method for a first network element to determine a terminal device, according to embodiments of the present disclosure.

[0028] FIG. 9 is a flow diagram of a method for establishing a first session, according to embodiments of the present disclosure.

[0029] FIG. 10 is a flow diagram of a method for wireless communication, according to another embodiment of the present disclosure.

[0030] FIG. 11 is a flow diagram of a method for wireless communication, according to yet another embodiment of the present disclosure.

[0031] FIG. 12 is a flow diagram of a method for wireless communication, according to still another embodiment of the present disclosure.

[0032] FIG. 13 is a schematic diagram of a terminal device, according to embodiments of the present disclosure.

[0033] FIG. 14 is a schematic diagram of a network device, according to an embodiment of the present disclosure.

[0034] FIG. 15 is a schematic diagram of a network device, according to another embodiment of the present disclosure.

[0035] FIG. 16 is a schematic diagram of a network device, according to yet another embodiment of the present disclosure.

[0036] FIG. 17 is a schematic diagram of a communication apparatus, according to embodiments of the present disclosure. DETAILED DESCRIPTION

[0037] The technical solutions in the present disclosure will be described below with reference to the accompanying drawings.

[0038] FIG. 1 and FIG. 2 are schematic diagrams of a communication system architecture to which embodiments of the present disclosure are applicable. The communication system can include a terminal device, an access network (AN) device, and a network element in a core network.

[0039] It should be understood that the technical solutions of the embodiments of the present disclosure can be applied to various communication systems, such as a 5th generation (5G) system or new radio (NR), a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD), and the like. The technical solutions provided by the present disclosure can also be applied to future communication systems, such as a 6th generation mobile communication system, a satellite communication system, and the like.

[0040] The terminal device in the embodiments of the present application can also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station (MS), an MT, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless terminal, a user agent or a user apparatus. The terminal device in the embodiments of the present application can refer to a device providing voice and / or data connectivity for a user, and can be used to connect people, things and machines, such as handheld devices with wireless connection function, vehicle-mounted devices, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer (Pad), a notebook computer, a palm computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a scheduling entity, which provides sidelink signals between terminal devices in vehicle-to-everything (V2X) or device to device (D2D), etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and the smart home device communicate with each other without relaying the communication signals through the base station.

[0041] The access network device can refer to an access device that accesses a terminal device into a wireless network, and is mainly responsible for wireless resource management, quality of service (QoS) management, data compression and encryption, etc. on the air interface side. The access network device can also be referred to as a radio access network (RAN) device, for example, the access network device can be a base station. The base station can broadly cover various names in the following or replace the following names, such as: Node B (NodeB), evolved Node B (eNB), next generation Node B (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master eNB (MeNB), secondary eNB (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The base station can also refer to a communication module, modem or chip used in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs the function of a base station in D2D, V2X, machine-to-machine (M2M) communication, network side device in 6G network, device that performs the function of a base station in future communication system, etc. The base station can support networks of the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the access network element.

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

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

[0044] The type of the network element in the core network can include a user plane function (UPF) network element, an access and mobility management function (AMF) network element, a session management function (SMF) network element, a policy control function (PCF) network element, an application function (AF), a data network (DN), a network slice selection function (NSSF), an authentication server function (AUSF), a unified data management (UDM), a network exposure function (NEF), a network repository function (NRF), and a network slice-specific authentication and authorization function (NSSAAF). Among them, the UPF network element is mainly responsible for the transmission of user data, and other network elements can be referred to as control plane function network elements, which are mainly responsible for authentication, authorization, registration management, session management, mobility management, and policy control, etc. to ensure reliable and stable transmission of user data.

[0045] The UPF network element can be used to forward and receive data of the terminal device. For example, the UPF network element can receive data of a service from a data network through an N6 interface and transmit the data to the terminal device through an access network device, where the UPF network element and the access network device can transmit data through an N3 interface. The UPF network element can also receive user data from the terminal device through the access network device and forward the data to the data network. The transmission resources allocated and scheduled for the terminal device by the UPF network element are managed and controlled by the SMF network element. The bearer between the terminal device and the UPF network element can include a user plane connection between the UPF network element and the access network device, and a channel established between the access network device and the terminal device. The user plane connection is a QoS flow that can be established between the UPF network element and the access network device to transmit data.

[0046] The AMF network element can be used to manage access of the terminal device to the core network, for example, location update, registration network, access control, mobility management of the terminal device, attachment and detachment of the terminal device, and the like. In addition to managing the mobility of the terminal device, the AMF network element is also responsible for forwarding session management related messages between the terminal device and the SMF network element.

[0047] The SMF network element can be used to select a user plane network element for the terminal device, redirect a user plane network element for the terminal device, allocate an internet protocol (IP) address for the terminal device, establish a bearer (also referred to as a session) between the terminal device and the UPF network element, modify the session, release the session, and control QoS. After the terminal device accesses the core network through a Uu interface, the terminal device can establish a protocol data unit (PDU) session for data transmission under the control of the SMF.

[0048] The PCF network element is used to provide policies such as QoS policies and slice selection policies to the AMF network element and the SMF network element. Alternatively, the PCF network element is responsible for formulating policies related to mobility management, session management, and charging of the terminal device.

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

[0050] The DN can provide data services for users, such as IP multi-media service (IMS) networks and the Internet. There can be various application servers in the DN to provide different application services, such as operator services, Internet access, or third-party services, and the like. The application server can implement the function of the AF.

[0051] The NSSF is used for selection of network slices, and supports functions such as: selecting a set of network slice instances to serve a terminal device; determining allowed network slice selection assistance information (NSSAI), and determining mapping to single-network slice selection assistance information (S-NSSAI) of a subscription if necessary; determining configured NSSAI, and determining mapping to S-NSSAI of a subscription if necessary; and determining a set of AMFs that can be queried for a terminal device, or determining a list of candidate AMFs based on configuration.

[0052] The AUSF is used to receive a request for terminal device authentication from an AMF, request a key from a UDM, and forward the delivered key to the AMF for authentication processing.

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

[0054] The NEF is used for capability exposure, that is, based on the NEF, the capabilities of the network can be output to external networks. External non-trusted applications can access internal data of the core network through the NEF to ensure the security of the network. The NEF can provide functions such as external application QoS capability exposure, event subscription, AF request distribution, and the like.

[0055] The NRF is used for registration, management, and state detection of network elements in the core network, thereby enabling automatic management of network elements in the core network. When a network element in the core network starts, it must be registered with the NRF to provide services. Registration information may, for example, include the type, address, and service list of the network element in the core network.

[0056] In addition, some networks (such as 5G networks) also add a network data analysis function (network data analytics function, NWDAF) in the core network. Based on the NWDAF, data can be collected from various network elements, network management systems, and the like in the core network, and big data statistics, analysis, or intelligent data analysis can be performed, thereby obtaining analysis or prediction data on the network side, and further assisting various network elements in more effectively controlling terminal device access based on the data analysis results.

[0057] In some communication systems (such as 5G systems), the network elements in the core network can also be referred to as network functions (network function, NF).

[0058] Each network element in FIG. 1 and FIG. 2 can be a network element in a hardware device, a software function running on a dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). It should be noted that the network elements included in the entire network architecture shown in FIG. 1 and FIG. 2 are merely illustrative. In the embodiments of the present application, the network elements included in the entire network architecture are not limited.

[0059] Those skilled in the art can understand that the network architecture shown in FIG. 1 and FIG. 2 does not constitute a limitation on the network architecture. In actual implementation, the network architecture can include more or fewer network elements than those shown, or some network elements can be combined, etc. It should be understood that the AN or RAN is represented as (R)AN in FIG. 1 and FIG. 2.

[0060] In some scenarios, network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water; and can also be deployed on aircraft, balloons and satellites in the air. The scenarios in which the network devices and terminal devices are located are not limited in the embodiments of the present application.

[0061] By way of example and not limitation, in the embodiments of the present application, the network device can have a mobile characteristic, for example, the network device can be a mobile device. In some embodiments of the present application, the network device can be a satellite, a balloon station. For example, the satellite can 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. In some embodiments of the present application, the network device can also be a base station arranged at a position on land, water, etc.

[0062] In the embodiments of the present application, the network device can serve a cell, and a terminal device communicates with the network device through transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be a cell corresponding to the network device (e.g., a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cell can include a metro cell, a micro cell, a pico cell, a femto cell, etc., which have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.

[0063] The communication system shown in FIG. 1 is a traditional reference point-based system architecture, that is, the network elements in the core network can be connected to each other in pairs through an agreed interface to communicate through the interface. Under this system architecture, the interaction between two network elements is realized through a specially defined reference point. For example, the AF interacts with the PCF through the N5 interface, the PCF interacts with the SMF through the N7 interface, the SMF interacts with the AMF through the N11 interface, and so on. In the reference point-based system architecture, the connection between the network elements in the core network is a one-to-one relationship between two network elements, and cannot be one-to-many or many-to-one. Under this architecture, each network element is specially designed to implement a unique network function, and the software and hardware of the network element are tightly coupled, and the interoperation between network elements is frequent and complex.

[0064] The communication system shown in FIG. 2 can avoid the shortcomings of the communication system shown in FIG. 1. The communication system shown in FIG. 2 draws on the successful experience of the service-based and micro-service-based architecture of IT systems, and realizes the decoupling and integration of network functions through modularization. The decoupled network functions can be independently scaled, independently evolved, and deployed on demand.

[0065] In the communication system shown in FIG. 2, the network elements in the core network can interact based on a service-based interface, and the same service can be called by multiple network functions, thereby reducing the coupling degree caused by interface-based communication between network functions, and ultimately realizing the on-demand customization of the overall network function, and flexibly supporting different business scenarios and requirements.

[0066] FIG. 3 shows a protocol stack used when the network elements in the core network interact based on a service-based interface. As shown in FIG. 3, the protocol stack includes, from high to low, an application layer, a hyper text transfer protocol 2.0 (HTTP / 2) layer, a transmission control protocol (TCP) layer, an Internet protocol (IP) layer, a layer 2 (L2), and a layer 1 (L1). In some embodiments, the protocol stack can also include a transport layer security (TLS) layer. The TLS layer is used to encrypt data to protect the security of data transmission.

[0067] In some embodiments, L2 can also be understood or referred to as a medium access control (MAC) layer. In some embodiments, L1 can also be understood or referred to as a physical layer.

[0068] It can be seen that in the communication system shown in FIG. 2, although the network elements in some core networks can interact based on the service interface, the terminal device and the AMF network element, the access network device and the AMF network element, and the SMF network element and the UPF network element still interact using the traditional reference point. The service-based architecture evolution is not complete, resulting in some problems in the system. For example, in the scenario where the terminal device needs to access the core network from the AMF network element through the N1 interface, the design of the dedicated interface between the terminal device and the AMF network element will be complex, and any interaction between the terminal device and the network element in the core network needs to be carried through the NAS message, and the NAS message needs to be carried through the AS message, resulting in a large transmission overhead of the AS message. Therefore, when designing future networks (for example, 6G network design), the design of the terminal device interacting with other network elements (such as network elements in the core network) through the service interface can be considered.

[0069] For ease of understanding, the system architecture of the communication system in which the terminal device interacts with other network elements through the service interface will be introduced below in conjunction with FIG. 4.

[0070] Referring to the communication system shown in FIG. 4, the communication system can include a terminal device, an access network device, and network elements in a core network. The network elements in the core network can include, for example, a user plane function network element, a mobility management network element, a session management network element, a location management network element, and the like. The communication system can also include an AF network element, a DN, and the like.

[0071] In the communication system shown in FIG. 4, the terminal device can interact with other network elements (such as network elements in the core network, AF network elements, and the like) through the service interface. Among them, the terminal device interacting with other network elements through the service interface can be understood as the terminal device can access the bus similar to the network elements in the 5G core network and interact with other network elements through the service interface. Or in other words, the terminal device can call the services provided by other network elements through the service interface, and / or other network elements can call the services provided by the terminal device through the service interface. Referring to FIG. 4, the service interface provided by the terminal device is Nue, and the terminal device can access the bus and interact with other network elements through the interface Nue.

[0072] Exemplarily, the terminal device can interact with the network elements in the core network through the service interface. For example, the terminal device can access the bus and interact with any network element in the core network through the service interface.

[0073] As an implementation form, the terminal device can be understood as that the terminal device can send a message to the user plane function in an IP packet, and the user plane function routes the IP packet to the bus, so that the terminal device can interact with different network elements respectively. The user plane function can route the data packet to the bus in the user plane.

[0074] It should be noted that the functions of some network elements in the communication system shown in FIG. 4 are the same as or similar to the functions of some network elements in the communication systems shown in FIGS. 1 and 2. For example, the function of the mobility management network element is the same as or similar to the function of the AMF. For another example, the function of the session management network element is the same as or similar to the function of the SMF.

[0075] It should be understood that the terminal device, the access network device, the mobility management network element (also referred to as the "mobility management network element"), the session management network element and the like shown in FIG. 4 are only names, and the names do not constitute a limitation on the devices themselves. In the 6G network and other future networks, the network elements corresponding to the terminal device, the access network device, the mobility management network element and the session management network element can also be other names, and the embodiments of the present application do not make a specific limitation thereon.

[0076] In the scenario that the terminal device interacts with other network elements through the service interface, how the terminal device interacts with the network element in the core network through the service interface becomes a problem to be solved.

[0077] To solve the above problem, the embodiments of the present application provide a method of wireless communication, a terminal device and a network device. The method provided by the embodiments of the present application can transmit messages (such as the first message and / or the second message below) between the terminal device and the first network element in the user plane through the first session, so as to realize the interaction between the terminal device and the first network element through the service interface. Compared with the traditional scheme of carrying the NAS message through the AS message, the transmission overhead of the AS message can be reduced. This is because, when the messages between the terminal device and the first network element are transmitted in the user plane through the first session, these messages are transmitted through the data radio bearer (DRB) in the air interface, so that the signaling interaction of the AS layer can be reduced, and the AS signaling overhead can be reduced.

[0078] In some embodiments, the transmission of the messages between the terminal device and the first network element in the user plane through the first session can be understood as that the messages between the terminal device and the first network element are carried in the first session and transmitted through the IP link. Or, the messages between the terminal device and the first network element are carried in the IP packet, and the IP packet is transmitted through the first session.

[0079] Taking uplink transmission as an example, when the terminal device sends a message to the first network element, the terminal device can invoke a service provided by the first network element, carry the message in IP data, and send the message to the first network element through the first session. Taking downlink transmission as an example, when the first network element sends a message to the terminal device, the first network element can invoke a service provided by the terminal device, carry the message in IP data, and send the message to the terminal device through the first session.

[0080] In some embodiments, the first network element can be a network element in a core network, and therefore, the first network element can also be referred to as a first core network element. For example, the first network element can include one or more of the following: a mobility management network element, a session management network element, a policy control network element, and a location management network element. As an example, the first network element can be a session management network element. For example, the terminal device can request the session management network element to establish a session, modify a session, or delete a session, and the like. As another example, the first network element can be a location management network element. For example, the terminal device can send a message to the location management network element based on a positioning service.

[0081] Of course, the embodiments of the present application are not limited thereto, and the first network element can be any network element in a core network, for example, the first network element can be a network storage function network element (such as NRF), a unified data management network element (such as UDM), an authentication service function network element (such as AUSF), and the like.

[0082] In some embodiments, the first network element can be a network element in an operator network. That is, the first network element can not be limited to a network element in a core network. For example, the first network element can be an AF network element, and the like.

[0083] The above describes the transmission process of the message between the terminal device and the first network element in the embodiments of the present application, and the following describes a protocol stack applicable to the interaction between the terminal device and the first network element in the embodiments of the present application in combination with FIG. 5.

[0084] In some embodiments, the terminal device includes a first protocol layer, and / or the first network element includes the first protocol layer. The first protocol layer is a protocol layer of an application layer, and is mainly responsible for defining how to request and transmit data of the application layer. For example, the first protocol layer can be an HTTP layer or an HTTP / 2 layer. In the example of FIG. 5, the first protocol layer is an HTTP / 2 layer.

[0085] In some embodiments, the terminal device includes a second protocol layer, and / or the first network element includes the second protocol layer. The second protocol layer is below the first protocol layer. The second protocol layer is a protocol layer of a transport layer, and is mainly responsible for ensuring reliable transmission of data in the network. For example, the second protocol layer can be a TCP layer or a UDP layer. In the example of FIG. 5, the second protocol layer is a TCP layer.

[0086] In some embodiments, the terminal device comprises a third protocol layer, and / or the first network element comprises the third protocol layer. The third protocol layer is below the second protocol layer. The third protocol layer is configured to establish an IP connection with the UPF. For example, the third protocol layer can be configured to establish an IP connection between the terminal device and the UPF. For another example, the third protocol layer can be configured to establish an IP connection between the first network element and the UPF. In some embodiments, the third protocol layer can be an IP layer.

[0087] In some embodiments, the terminal device comprises a fourth protocol layer, which is below the third protocol layer. The fourth protocol layer is configured to establish a DRB between the terminal device and the access network device. In some scenarios, the fourth protocol layer can be referred to as a “5G-AN protocol layer”.

[0088] It should be noted that only several protocol layers related to the embodiments of the present application are introduced above, and the embodiments of the present application do not limit other protocol layers included in the terminal device and the first network element. For example, continuing to refer to FIG. 5, the first network element can further comprise one or more protocol layers configured to communicate with the UPF, such as an IP layer, a layer 2, and a layer 1. For another example, FIG. 5 further shows protocol layers related to the access network device and the UPF. For example, the access network device can comprise one or more protocol layers configured to communicate with the UPF, such as a general packet radio service tunneling protocol / user plane (GTP / U) layer, a user datagram protocol / IP (UDP / IP) layer, a layer 2, and a layer 1. Correspondingly, the UPF can further comprise one or more protocol layers configured to communicate with the access network device, such as a GTP / U layer, a UDP / IP layer, a layer 2, and a layer 1.

[0089] The protocol stack applicable to the embodiments of the present application is introduced above in combination with FIG. 5. The method of wireless communication according to the embodiments of the present application is introduced below in combination with FIG. 6. It should be noted that the method shown in FIG. 6 and the protocol stack and the communication system introduced above can be used in combination with each other.

[0090] FIG. 6 is a flow diagram of a method of wireless communication according to an embodiment of the present application. The method shown in FIG. 6 is introduced from the perspective of the terminal device interacting with the first network element. For related description of the terminal device and the first network element, reference can be made to the foregoing description, which will not be repeated here for brevity.

[0091] The method shown in FIG. 6 includes step S610 and / or step S620. For example, the method shown in FIG. 6 includes step S610. For another example, the method shown in FIG. 6 includes step S620. For yet another example, the method shown in FIG. 6 includes step S610 and step S620. These steps are described below.

[0092] In step S610, the terminal device sends a first message to the first network element through a service-based interface.

[0093] That is, in the uplink transmission direction, the terminal device can send the first message to the first network element through the service-based interface. Alternatively, in the uplink transmission direction, the terminal device can invoke a service provided by the first network element through the service-based interface to send the first message to the first network element.

[0094] In some embodiments, the first message is transmitted in the user plane. For example, the first message can be transmitted in the user plane through a first session. Alternatively, the terminal device can invoke a service provided by the first network element to send the first message to the first network element through the first session.

[0095] In some embodiments, the first message can be transmitted through an IP link. For example, the terminal device can carry the first message in a first session and send it to the first network element through an IP link. In other words, the terminal device can carry the first message in an IP packet, which is sent to the first network element through the first session.

[0096] In some embodiments, the transmission of the first message in the user plane through the first session can be understood as follows: the terminal device can carry the first message in an IP packet and send it to the user plane function (such as a UPF) through the first session, and then the user plane function routes the IP packet to a bus, so that the terminal device can interact with the first network element based on the bus.

[0097] In some embodiments, when the terminal device sends the first message to the first network element, the routing mode of the first message can be the same as the routing mode of interaction between network elements in the core network based on the service-based interface. For example, the terminal device can set the uri-host in the HTTP / 2 request message to the information of the first network element.

[0098] The first message is not limited in the embodiments of the present application, and can be any message sent by the terminal device to the first network element. Taking the first network element as a mobility management network element as an example, the first message can be any message sent by the terminal device to the mobility management network element, such as a registration update message. Taking the first network element as a session management network element as an example, the first message can be any message sent by the terminal device to the session management network element, such as a session modification message, a session deletion message, a session establishment message, and the like. Taking the first network element as a location management network element as an example, the first message can be any message sent by the terminal device to the location management network element, such as a positioning request message, a positioning report message, and the like.

[0099] In step S620, the first network element sends a second message to the terminal device through the service-oriented interface.

[0100] That is, in the downlink transmission direction, the first network element can send the second message to the terminal device through the service-oriented interface. Or in the downlink transmission direction, the first network element can invoke the service provided by the terminal device through the service-oriented interface to send the second message to the terminal device.

[0101] In some embodiments, the second message is transmitted in the user plane. For example, the second message can be transmitted in the user plane through the first session. Or the first network element can invoke the service provided by the terminal device to send the second message to the terminal device through the first session.

[0102] In some embodiments, the second message can be transmitted through an IP link. For example, the first network element can carry the second message in the first session and send it to the terminal device through the IP link. In other words, the first network element can carry the second message in an IP packet, and the IP packet is sent to the terminal device through the first session.

[0103] In some embodiments, the transmission of the second message in the user plane through the first session can be understood as that the first network element can carry the second message in an IP packet, and send the IP packet to a user plane function, and then the user plane function sends the IP packet to the terminal device through the first session.

[0104] In some embodiments, when the first network element sends the second message to the terminal device, the routing mode of the second message can be the same as the routing mode based on the service-oriented interface between the network elements in the core network. For example, the first network element can set the uri-host in the HTTP / 2 request message to the information of the terminal device.

[0105] The second message is not limited in the embodiments of the present application, and can be any message sent by the first network element to the terminal device. Taking the first network element as a mobility management network element as an example, the second message can be any message sent by the mobility management network element to the terminal device, such as a registration response message. Taking the first network element as a session management network element as an example, the second message can be any message sent by the session management network element to the terminal device, such as a session modification response message, a session deletion response message, a session establishment response message, and the like. Taking the first network element as a location management network element as an example, the second message can be any message sent by the location management network element to the terminal device, such as a positioning configuration message, and the like.

[0106] In some embodiments, the interaction between the terminal device and the first network element through the service-based interface can be understood as that, above the user plane (i.e., the IP layer), the terminal device and the first network element can interact through the service-based interface, and on the user plane, the terminal device and the first network element can interact through the first session.

[0107] In some embodiments, when the terminal device wants to send a message to the first network element through the service-based interface, if the terminal device knows the information of the first network element, the terminal device can directly send the message on the user plane through the first session. For example, the terminal device can directly invoke the service provided by the first network element to send the message on the user plane through the first session. Similarly, when the first network element wants to send a message to the terminal device through the service-based interface, if the first network element knows the IP address of the terminal device in the first session, the first network element can directly invoke the service provided by the terminal device to send the message on the user plane through the first session. As an example, in the first session establishment process, the terminal device can learn the information of the mobility management network element A and / or the session management network element A, and the mobility management network element A and / or the session management network element A can also learn the IP address of the terminal device in the first session, then the terminal device can subsequently interact with the mobility management network element A or the session management network element A directly.

[0108] However, for other network elements, the terminal device currently does not need to know which other network elements (such as the session management network element B, the policy control network element, and the like) exist in the core network, and the mobility management network element shields the information of the other network elements in the core network from the terminal device, so that the terminal device cannot obtain the information of the other network elements and cannot interact with the other network elements in the core network through the service-based interface. In this case, when the terminal device sends a first message to the first network element through the service-based interface, the terminal device needs to determine the first network element (i.e., knows the information of the first network element) first, so as to invoke the service provided by the first network element to realize the interaction. Similarly, when the first network element sends a second message to the terminal device through the service-based interface, the first network element needs to determine the terminal device (i.e., knows the IP address of the terminal device in the first session) first, so as to invoke the service provided by the terminal device to realize the interaction.

[0109] Taking the first network element as the session management network element B as an example, the terminal device needs to determine the session management network element B, so as to call the service provided by the session management network element B to request to newly establish (or modify, delete, etc.) a session, or in other words, the terminal device needs to determine the session management network element B, so as to call the service provided by the session management network element B to start the control flow of newly establishing (or modifying, deleting, etc.) a session.

[0110] Taking the first network element as the location management network element A as an example, the location management network element A needs to determine the terminal device, so as to call the service provided by the terminal device to request the terminal device to report location information and the like.

[0111] The information of the first network element is not limited in the embodiments of the present application, as long as it can be used for the terminal device to call the service provided by the first network element. Exemplarily, the information of the first network element can include one or more of the following: an identifier of the first network element, a fully qualified domain name (FQDN) of the first network element, an IP address of the first network element.

[0112] The implementation manner of the terminal device determining the first network element and / or the implementation manner of the first network element determining the terminal device are introduced below.

[0113] FIG. 7 is a flow diagram of a method for the terminal device to determine the first network element according to an embodiment of the present application. The method shown in FIG. 7 includes step S710 and step S720.

[0114] In step S710, the terminal device sends a third message to the second network element, and the third message is used to determine the first network element.

[0115] In some embodiments, the second network element is a network element in the core network. Exemplarily, the second network element can include one or more of the following network elements: a network storage function network element, a unified data management network element, and a mobility management network element. As an example, the second network element is a network element with a data storage function in the core network, such as a network storage function network element or a unified data management network element. As another example, the second network element is a mobility management network element.

[0116] In some embodiments, the network storage function network element can refer to a network element with the same or similar function as the NRF. In some embodiments, the unified data management network element can refer to a network element with the same or similar function as the UDM.

[0117] In some embodiments, the terminal device is configured with information of the second network element. As an implementation, the information of the second network element is pre-configured to the terminal device, for example, the manufacturer can configure the information of the second network element to the terminal device when the terminal device is manufactured. As another implementation, the information of the second network element is configured to the terminal device by a network element in the core network, for example, the network element in the core network can configure the information of the second network element to the terminal device before the terminal device sends the third message to the second network element. Taking the network storage function network element or the unified data management network element as an example, the manufacturer can configure the information of the network storage function network element or the unified data management network element to the terminal device when the terminal device is manufactured, or the network element (such as the mobility management network element) in the core network can configure the information of the network storage function network element or the unified data management network element to the terminal device before the terminal device sends the third message.

[0118] In some embodiments, the third message can include first indication information, which can be used to determine the type of the first network element (i.e., the network element type).

[0119] As an implementation, the first indication information can be used to indicate the type of the first network element. For example, the first indication information can indicate that the type of the first network element is the location management network element type (i.e., the first network element is a location management network element). For another example, the first indication information can indicate that the type of the first network element is the session management network element type (i.e., the first network element is a session management network element) when the terminal device wants to establish a new session.

[0120] As another implementation, the first indication information can be used to indicate the purpose of the interaction between the terminal device and the first network element, so that the second network element determines the type of the first network element according to the purpose of the interaction. For example, the first indication information can be used to indicate that the terminal device needs to be positioned, in which case the second network element can determine that the type of the first network element is the location management network element type. For another example, the first indication information can be used to indicate that the terminal device wants to establish a new session, in which case the second network element can determine that the type of the first network element is the session management network element type.

[0121] In some embodiments, the third message can be transmitted in the user plane. For example, the third message can be transmitted in the user plane through the first session. That is, the terminal device can invoke the service provided by the second network element through the service interface. As an example, when the second network element is the network storage function network element or the unified data management network element, the third message can be transmitted in the user plane through the first session. As another example, when the second network element is the mobility management network element, the third message can be transmitted in the user plane through the first session.

[0122] In some embodiments, the third message can be transmitted over the control plane through an access layer message, or in other words, the third message can be carried in an access layer control plane message for transmission. For example, the third message can be transmitted over the control plane through a radio resource control (RRC) message. As an example, when the second network element is a mobility management network element, the third message can be transmitted over the control plane through an access layer message.

[0123] In some embodiments, the third message can be transmitted over the control plane through an N1 interface. In other words, the third message can be transmitted over the control plane through a reference point. As an example, when the second network element is a mobility management network element, the third message can be transmitted over the control plane through an N1 interface.

[0124] In step S720, the second network element sends a response message of the third message to the terminal device.

[0125] In some embodiments, the response message of the third message can indicate information of one or more network elements. In this case, the terminal device needs to determine the first network element based on the information of the one or more network elements.

[0126] In other words, in some embodiments, step S720 can be replaced by: the second network element sends information of one or more network elements to the terminal device. In this case, after step S720, the terminal device further needs to perform the following step: determine (e.g., select) the first network element based on the information of the one or more network elements indicated by the second network element.

[0127] For example, in the case where the second network element is a network storage function network element, the second network element can indicate information of one or more network elements to the terminal device, and the terminal device can determine the first network element based on the information of the one or more network elements. This is because, when a network element in the core network is started, it needs to be registered in the network storage function network element, and therefore, the network storage function network element can provide information of each network element in the core network. In addition, when network elements in the core network currently interact based on a service interface, the target network element for communication is also determined by querying the network storage function network element, and therefore, the terminal device querying the network storage function network element to determine the first network element helps to reduce the complexity of design.

[0128] In some embodiments, the type of the one or more network elements indicated by the second network element to the terminal device is the same. Taking the case where the terminal device indicates the type of the first network element in the third message as a location management network element type as an example, the second network element can indicate information of one or more location management network elements to the terminal device. Taking the case where the terminal device indicates the type of the first network element in the third message as a session management network element type as an example, the second network element can indicate information of one or more session management network elements to the terminal device.

[0129] The embodiments of the present application do not limit the information of the one or more network elements indicated by the second network element. Exemplarily, the information of the one or more network elements can include, but is not limited to, one or more of the following: an identifier of the one or more network elements, a type of the one or more network elements, an FQDN of the one or more network elements, an IP address of the one or more network elements, capability information of the one or more network elements, load information of the one or more network elements, a location where the one or more network elements provide services (i.e., a location served by the network elements or a service area of the network elements), a time when the one or more network elements provide services (i.e., a valid time of service of the network elements).

[0130] In some embodiments, the information of the one or more network elements indicated by the second network element can be a list of profile information of the one or more network elements. Exemplarily, the list of profile information of each network element can include, but is not limited to, one or more of the following: an identifier of the network element, a type of the network element, an FQDN of the network element, an IP address of the network element, capability information of the network element, load information of the network element, a location where the network element provides services, a time when the network element provides services.

[0131] The embodiments of the present application do not limit the implementation manner of the terminal device for determining the first network element based on the information of the one or more network elements. Exemplarily, the terminal device can determine the first network element based on one or more of the following information: capability information of the network element, load information of the network element, a location where the network element provides services, a time when the network element provides services.

[0132] In some embodiments, the terminal device can determine the first network element based on one of the above information.

[0133] As an example, the terminal device can determine the first network element based on the capability information of the network element. For example, the terminal device can determine the network element with the strongest capability in the plurality of network elements as the first network element. Taking the example that the second network element indicates the information of a plurality of location management network elements to the terminal device, the terminal device can determine the location management network element with the strongest capability in the plurality of location management network elements as the first network element.

[0134] As another example, the terminal device can determine the first network element based on the load information of the network element. For example, the terminal device can determine the network element with the smallest load in the plurality of network elements as the first network element. Taking the example that the second network element indicates the information of a plurality of location management network elements to the terminal device, the terminal device can determine the location management network element with the smallest load in the plurality of location management network elements as the first network element.

[0135] As a further example, the terminal device can determine the first network element based on the location where the network element provides the service. For example, the terminal device can determine the network element closest to the terminal device among the multiple network elements as the first network element. Taking the example where the second network element indicates to the terminal device the information of the multiple location management network elements, the terminal device can determine the location management network element closest to the terminal device among the multiple location management network elements as the first network element.

[0136] In some embodiments, the terminal device can determine the first network element based on multiple kinds of the above information.

[0137] As an example, the terminal device can determine the first network element based on the load information of the network element and the time when the network element provides the service. For example, in the case where the multiple network elements can effectively provide the service, the terminal device can determine the network element with the smallest load among the multiple network elements as the first network element.

[0138] As another example, the terminal device can determine the first network element based on the capability information of the network element and the location where the network element provides the service. For example, in the case where the terminal device is at the same or similar distance from the multiple network elements, the terminal device can determine the network element with the strongest capability among the multiple network elements as the first network element.

[0139] As a further example, the terminal device can determine the first network element based on the load information of the network element, the location where the network element provides the service and the time when the network element provides the service.

[0140] The above enumeration is only an example, and multiple kinds of the above information can be combined in any manner, which will not be described herein for the sake of brevity.

[0141] In some embodiments, when the terminal device determines the first network element based on multiple kinds of the above information, the priority of different information can be different. For example, the terminal device can preferentially determine the first network element based on the location where the network element provides the service, and if there are multiple first network elements meeting the location requirement, the terminal device can determine the first network element based on the load information of the network element.

[0142] In some embodiments, the response message of the third message can indicate the information of the first network element. In this case, the terminal device can directly interact with the first network element based on the information of the first network element. That is, in some embodiments, step S720 can be replaced by: the second network element sends the information of the first network element to the terminal device. In other words, the second network element can determine (e.g., select) the first network element for the terminal device, which is conducive to reducing the implementation complexity of the terminal device. For example, in the case where the second network element is a mobility management network element, the second network element can indicate the information of the first network element to the terminal device.

[0143] The embodiments of the present application do not limit the information of the first network element indicated by the second network element. Exemplarily, the information of the first network element can include, but is not limited to, one or more of the following: an identifier of the first network element, an FQDN of the first network element, and an IP address of the first network element.

[0144] In some embodiments, after receiving the third message sent by the terminal device, the second network element needs to query the information of the first network element from other network elements. For example, when the second network element is a mobility management network element, the mobility management network element needs to query the information of the first network element from other network elements.

[0145] As an implementation manner, the second network element can send a sixth message to a network storage function network element. The sixth message is used to request the information of one or more network elements. Then, the second network element can determine the information of the first network element based on the information of the one or more network elements, and send the information of the first network element to the terminal device.

[0146] In some embodiments, the second network element can send the sixth message to the network storage function network element based on a service-oriented interface.

[0147] In some embodiments, the sixth message can include third indication information, and the third indication information can be used to determine the type of the first network element. As an implementation manner, the third indication information can be used to indicate the type of the first network element. For example, the third indication information can indicate that the type of the first network element is a location management network element type. For another example, when the terminal device wants to establish a new session, the third indication information can indicate that the type of the first network element is a session management network element type.

[0148] In some embodiments, the type of the one or more network elements returned by the network storage function network element to the second network element is the same. For example, the network storage function network element can return the information of one or more location management network elements to the second network element. For another example, the network storage function network element can return the information of one or more session management network elements to the second network element.

[0149] The embodiments of the present application do not limit the information of the one or more network elements indicated by the network storage function network element to the second network element. Exemplarily, the information of the one or more network elements can include, but is not limited to, one or more of the following: an identifier of the one or more network elements, a type of the one or more network elements, an FQDN of the one or more network elements, an IP address of the one or more network elements, capability information of the one or more network elements, load information of the one or more network elements, a location at which the one or more network elements provide services, and a time at which the one or more network elements provide services. For details of the information of the one or more network elements, refer to the description of the information of the one or more network elements indicated by the second network element to the terminal device, which will not be described herein again for the sake of brevity.

[0150] In some embodiments, the second network element can determine the first network element based on the information of one or more network elements indicated by the network storage function network element. For example, the second network element can determine the first network element based on one or more of the following information: capability information of the network element, load information of the network element, location where the network element provides services, time when the network element provides services. The description about how the second network element determines the first network element based on the above information is similar to the way the terminal device determines the first network element based on the information, and therefore, the description about how the second network element determines the first network element based on the above information can be referred to the foregoing description and will not be repeated here.

[0151] The implementation of the terminal device determining the first network element is described above in combination with FIG. 7. The implementation of the first network element determining the terminal device is described below in combination with FIG. 8.

[0152] FIG. 8 is a flowchart of a method for the first network element to determine the terminal device according to an embodiment of the present application. The method shown in FIG. 8 includes step S810 and step S820.

[0153] In step S810, the first network element sends a fifth message to the second network element. The fifth message is used to request the IP address of the terminal device in the first session.

[0154] In some embodiments, the fifth message can include the identifier of the terminal device, so that the second network element determines the IP address of the terminal device in the first session according to the identifier.

[0155] In step S820, the second network element sends a response message of the fifth message to the first network element. The response message of the fifth message is used to indicate the IP address of the terminal device in the first session.

[0156] In some embodiments, the first network element and the second network element can interact through a service interface. That is, the first network element can send the fifth message through the service interface, and / or the second network element can send the response message of the fifth message through the service interface.

[0157] In some embodiments, the method shown in FIG. 8 can further include step S805. In step S805, the terminal device sends a fourth message to the second network element. In some embodiments, the fourth message includes (or carries) the IP address of the terminal device in the first session. In some embodiments, the fourth message is used to request (or indicate) to store the IP address of the terminal device in the first session. Thereafter, the second network element can store the IP address of the terminal device in the first session, so as to subsequently send the IP address of the terminal device in the first session to the first network element. Taking the second network element as a network storage function network element or a unified data management network element for example, the terminal device can send the fourth message to the network storage function network element or the unified data management network element, so that the network storage function network element or the unified data management network element subsequently sends the IP address of the terminal device in the first session to the first network element.

[0158] However, the embodiments of the present application are not limited thereto, and the second network element can also obtain the IP address of the terminal device in the first session through other manners. For example, the fourth network element can send a seventh message to the second network element, and the seventh message is used to indicate the IP address of the terminal device in the first session. The fourth network element is a session management network element for managing the first session, such as an SMF or a network element having the same or similar function as the SMF. Taking the second network element as a mobility management network element for example, the fourth network element can send the IP address of the terminal device in the first session to the mobility management network element after controlling the establishment of the first session. In this way, the terminal device does not need to send its IP address in the first session to the mobility management network element, thereby saving signaling overhead.

[0159] It should be noted that the method shown in FIG. 7 and / or FIG. 8 can be used in combination with the method shown in FIG. 6. For example, after the terminal device determines the first network element through the method shown in FIG. 7, the terminal device can send the first message to the first network element based on the process shown in FIG. 6. For another example, after the first network element determines the terminal device through the method shown in FIG. 8, the first network element can send the second message to the terminal device based on the process shown in FIG. 6.

[0160] It is mentioned above that the messages (such as the first message and / or the second message) between the terminal device and the first network element are transmitted through the first session. The first session is introduced as follows.

[0161] In some embodiments, the first session can be used to carry user plane data.

[0162] In some embodiments, the first session can be a PDU session, or the first session can be a session having the same or similar function as the PDU session.

[0163] In some embodiments, the terminal device can perform service-based interface interaction with other network elements (e.g., network elements in a core network) in a user plane through the first session. For example, the terminal device can invoke a service provided by the other network element through the first session, or the other network element can invoke a service provided by the terminal device through the first session.

[0164] In some embodiments, the first session is dedicated to carrying messages received and / or sent by the terminal device through the service-based interface. That is, when the terminal device receives and / or sends messages through the service-based interface, these messages are all transmitted through the first session. Of course, the first session can also carry other messages in addition to carrying messages received and / or sent by the terminal device through the service-based interface, and the embodiments of the present application are not limited in this regard.

[0165] In some embodiments, the first session can be used to transmit messages between the terminal device and the user plane function network element. In other words, after the terminal device accesses the network, the terminal device can establish the first session with the user plane function network element for transmitting IP data.

[0166] The establishment process of the first session will be described below in conjunction with FIG. 9. FIG. 9 is a flowchart of establishing the first session according to an embodiment of the present application. The method shown in FIG. 9 includes steps S910 to S940.

[0167] At step S910, the terminal device sends a first NAS message to a third network element. The first NAS message is used to trigger establishment of the first session.

[0168] In some embodiments, the third network element is a network element in a core network. For example, the third network element is a mobility management network element.

[0169] The first NAS message is not limited in the embodiments of the present application. For example, the first NAS message can include one or more of the following: a registration request message, a session establishment request message.

[0170] In some embodiments, the first NAS message can be carried in an AS layer message (e.g., an RRC message) and transmitted in the control plane. For example, the first NAS message can be carried in an AS layer message and transmitted through an N1 interface. As an implementation manner, the terminal device can send an AS layer message to an access network device, and the AS layer message carries the first NAS message. Then, the access network device sends the first NAS message to the third network element.

[0171] In some embodiments, the first NAS message being used to trigger the establishment of the first session can comprise: the first NAS message being used to request the establishment of the first session. For example, the terminal device sends a session establishment request message to the third network element to request the establishment of the first session. However, the embodiments of the present application are not limited thereto. Taking the first NAS message as a registration request message as an example, the third network element can trigger the establishment of the first session according to the capability report of the terminal device. For example, the terminal device indicates that it supports communication with other network elements through a service interface when reporting the capability, and then the third network element can automatically trigger the establishment of the first session.

[0172] In some embodiments, the first NAS message being used to trigger the establishment of the first session can mean that the first NAS message is used to trigger the third network element to establish the first session. Taking the first NAS message as a session establishment request message as an example, the terminal device can send the first NAS message to the third network element to request the third network element to establish the first session. Then, the third network element triggers the process of establishing the first session, i.e., the third network element can request the fourth network element to establish the first session. Taking the first NAS message as a registration request message as an example, after the terminal device sends the first NAS message to the third network element, the third network element determines that the terminal device supports communication through a service interface, and then the third network element can automatically trigger the establishment of the first session, i.e., the third network element can automatically request the fourth network element to establish the first session.

[0173] In some embodiments, the first NAS message can comprise second indication information. The second indication information can be used to indicate one or more of the following: the terminal device supports communication with other network elements (such as network elements in the core network) through a service interface, and the terminal device requests communication with other network elements through a service interface.

[0174] In some embodiments, the second indication information can explicitly indicate that the terminal device supports communication with other network elements through a service interface and / or the terminal device requests communication with other network elements through a service interface. For example, the second indication information can comprise a first bit, and the value of the first bit is a first value, which means that the terminal device supports communication with other network elements through a service interface and / or the terminal device requests communication with other network elements through a service interface; the value of the first bit is a second value, which means that the terminal device does not support communication with other network elements through a service interface and / or the terminal device does not request communication with other network elements through a service interface.

[0175] The first bit can be one bit or multiple bits, and embodiments of the present application do not limit this. As an implementation manner, the first bit can be one bit. For example, the first bit taking a value of "1" indicates that the terminal device supports communication with other network elements through the service-based interface and / or the terminal device requests communication with other network elements through the service-based interface; the first bit taking a value of "0" indicates that the terminal device performs non-service-based access (i.e., traditional access). Alternatively, the first bit taking a value of "0" indicates that the terminal device supports communication with other network elements through the service-based interface and / or the terminal device requests communication with other network elements through the service-based interface; the first bit taking a value of "1" indicates that the terminal device performs non-service-based access. As another implementation manner, the first bit can be two bits. For example, the first bit taking a value of "00" indicates that the terminal device performs non-service-based access; the first bit taking a value of "01" indicates that the terminal device directly performs service-based access; the first bit taking a value of "10" indicates that the terminal device performs service-based access through a proxy network element. Alternatively, for example, the first bit taking a value of "00" indicates that the terminal device directly performs service-based access; the first bit taking a value of "01" indicates that the terminal device performs service-based access through a proxy network element; the first bit taking a value of "10" indicates that the terminal device performs non-service-based access. It should be noted that the proxy network element can refer to a network element set in the core network to simulate a virtual terminal device.

[0176] In some embodiments, the second indication information can implicitly indicate that the terminal device supports communication with other network elements through the service-based interface and / or the terminal device requests communication with other network elements through the service-based interface. For example, the second indication information can include a first access point name (APN). The first APN can be used to indicate that the terminal device requests communication with other network elements through the service-based interface.

[0177] In some embodiments, after receiving the first NAS message, the third network element can determine whether to allow the terminal device to perform service-based access. For example, if the third network element determines not to allow the terminal device to perform service-based access, the third network element can directly send a response message of the first NAS message to the terminal device, where the response message of the first NAS message is used to indicate rejection of the terminal device to perform service-based access. For another example, if the third network element determines to allow the terminal device to perform service-based access, the first network element can request to establish the first session, i.e., the third network element can perform subsequent steps S920 to S940.

[0178] In step S920, the third network element sends a second NAS message to a fourth network element. The second NAS message is used to request to establish the first session.

[0179] In some embodiments, after the fourth network element establishes the first session, the terminal device can subsequently perform service-based interface-based interaction with other network elements in a user plane through the first session.

[0180] At step S930, the fourth network element sends a response message of the second NAS message to the third network element. The response message of the second NAS message can be used to indicate the establishment of the first session, such as the successful establishment of the first session.

[0181] In some embodiments, the response message of the second NAS message can carry information of the fourth network element.

[0182] In some embodiments, the response message of the second NAS message can carry an IP address of the terminal device in the first session. In this way, the third network element and / or the fourth network element can actively interact with the terminal device based on the service-based interface.

[0183] At step S940, the third network element sends a response message of the first NAS message to the terminal device. In some embodiments, the response message of the first NAS message can be used to indicate the establishment of the first session, such as the successful establishment of the first session.

[0184] The embodiments of the present application do not limit the response message of the first NAS message. For example, the response message of the first NAS message can include one or more of the following: a registration request response message, a session establishment response message. For example, the first NAS message is a registration request message, and the response message of the first NAS message is a registration request response message. For another example, the first NAS message is a session establishment request message, and the response message of the first NAS message is a session establishment response message.

[0185] In some embodiments, the response message of the first NAS message can carry one or more of the following: information of the third network element, information of the fourth network element. In this way, the terminal device can subsequently directly interact with the third network element and / or the fourth network element. However, the embodiments of the present application are not limited thereto. For example, in the case where the response message of the first NAS message does not carry information of the third network element and / or the fourth network element, the terminal device can obtain the information of the third network element and / or the fourth network element by querying the second network element.

[0186] The embodiments of the present application do not limit the information of the third network element and / or the information of the fourth network element carried in the response message of the first NAS message. For example, the information of the third network element and / or the information of the fourth network element can include one or more of the following: an identifier of the network element, an FQDN of the network element, an IP address of the network element.

[0187] After the first session is established, the terminal device can perform service-based interface interaction with other network elements (such as a mobility management network element, a session management network element, and the like) in a user plane through the first session. In this way, data exchanged between the terminal device and the other network elements is transmitted in the user plane, and is transmitted through a DRB in the air interface, which can reduce signaling interaction of an AS layer and signaling overhead.

[0188] For ease of understanding, the flow of the method of the present application is schematically introduced below in combination with embodiments. It should be noted that the embodiments below are only examples, and are not intended to limit the scope of the embodiments of the present application. For example, in the actual application of the scheme of the present application, the steps performed may only include part of the steps in the embodiments, or may include more steps than those listed in the embodiments.

[0189] It should also be noted that the content not introduced in detail in the embodiments below can be referred to the introduction above, such as the first NAS message, the first session, the first indication information, the second indication information, and the like.

[0190] It should also be noted that the embodiments below can be used alone or in combination. For example, embodiment 1 and embodiment 2 can be used in combination.

[0191] It should also be noted that the present application does not limit the execution order between the steps introduced in the embodiments below. For example, in embodiment 1, steps S1007 to S1010 can be executed before step S1005 and / or step S1006, step S1006 can be executed before step S1005, and the like. For example, in embodiment 2, step S1107 can be executed before step S1105 and / or step S1106, step S1106 can be executed before step S1105, and the like. For example, in embodiment 3, steps S1207 to S1211 can be executed before step S1205 and / or step S1206, step S1206 can be executed before step S1205, and the like.

[0192] Embodiment 1:

[0193] In embodiment 1, the second network element can be a network storage function network element or a unified data management network element.

[0194] FIG. 10 is a flow diagram of a method of wireless communication provided by another embodiment of the present application. The method shown in FIG. 10 includes steps S1001 to S1010. It should be noted that the solid line in FIG. 10 represents message interaction through a control plane (such as a message passing through the N1 path shown in FIG. 4), and the dashed line represents message interaction through a user plane (such as a message passing through the Nue path shown in FIG. 4).

[0195] At step S1001, the terminal device sends a first NAS message to a third network element. The first NAS message is used to trigger establishment of a first session.

[0196] In some embodiments, the first NAS message can be transmitted over a control plane through an access layer message.

[0197] In some embodiments, the first NAS message can comprise second indication information.

[0198] At step S1002, the third network element sends a second NAS message to a fourth network element. The second NAS message is used to request establishment of the first session. Subsequently, the terminal device can interact with other network elements based on a service-based interface over a user plane based on the first session.

[0199] At step S1003, the fourth network element sends a response message of the second NAS message to the third network element. The response message of the second NAS message carries information of the fourth network element.

[0200] At step S1004, the third network element sends a response message of the first NAS message to the terminal device. The response message of the first NAS message carries information of the third network element and / or the fourth network element.

[0201] In some embodiments, if the third network element rejects service-based access of the terminal device, the third network element can indicate rejection of service-based access of the terminal device at step S1004. In this scenario, steps S1002 and S1003 can be omitted.

[0202] After step S1004, if the terminal device knows information of the first network element, the terminal device can directly interact with the first network element based on a service-based interface over a user plane through the first session. For example, the terminal device can invoke a service provided by the first network element, and a specific routing manner can be, for example, that the terminal device sets uri-host in an HTTP / 2 request message to the information of the first network element. Or the first network element can invoke a service provided by the terminal device, and a specific routing manner can be, for example, that the first network element sets uri-host in an HTTP / 2 request message to the information of the terminal device. For example, at steps S1005 and S1006, the terminal device can interact with the third network element and / or the fourth network element (in this scenario, the third network element and / or the fourth network element can also be referred to as the first network element).

[0203] At step S1005, the terminal device interacts with the third network element based on a service-based interface.

[0204] For example, in the case that the terminal device needs to perform registration update due to location movement or the terminal device performs periodic registration update, the terminal device can invoke the service provided by the third network element to perform registration update. The terminal device invoking the service provided by the third network element is based on the interaction of the service interface. For example, the terminal device can send a first message to the user plane function through a first session, and route the first message to the third network element through the user plane function.

[0205] At step S1006, the terminal device interacts with the fourth network element based on the service interface.

[0206] For example, when the terminal device needs to modify the first session (e.g., modify the QoS parameter used by the first session), the terminal device can invoke the service provided by the fourth network element to modify the session. The terminal device invoking the service provided by the fourth network element is based on the interaction of the service interface. For example, the terminal device can send a first message to the user plane function through the first session, and route the first message to the fourth network element through the user plane function.

[0207] After step S1004, if the terminal device does not know the information of the first network element, the terminal device needs to query the second network element to obtain the information of the first network element. Then, the terminal device can interact with the first network element based on the obtained information of the first network element through the service interface. The interaction between the terminal device and the first network element based on the service interface is described below in steps S1007 to S1010 (the first network element in steps S1007 to S1010 is described in other network elements of FIG. 10). The information of the second network element can be pre-configured to the terminal device, or configured to the terminal device by a network element (e.g., the third network element) in the core network.

[0208] At step S1007, the terminal device sends a third message to the second network element. The third message is used to determine the first network element.

[0209] In some embodiments, the third message is sent through the service interface, i.e., the terminal device can invoke the service provided by the second network element through the service interface. Alternatively, the third message is transmitted in the user plane through the first session.

[0210] At step S1008, the second network element sends the information of one or more network elements to the terminal device.

[0211] In some embodiments, the second network element can return the information of multiple network elements of the same type to the terminal device. For example, the second network element can return the information of multiple session management network elements to the terminal device when the terminal device queries the session management network element. For example, the second network element can return the information of multiple location management network elements to the terminal device when the terminal device queries the location management network element.

[0212] At step S1009, the terminal device determines the first network element based on the information of one or more network elements.

[0213] For example, the terminal device can determine the first network element based on one or more of the following information: load information of the network element, location where the network element provides services, capability information of the network element, time when the network element provides services, and the like. For example, the terminal device can determine a session management network element from multiple session management network elements, so as to request the session management network element to newly establish a session. Alternatively, the terminal device can determine a location management network element from multiple location management network elements, so as to interact with the location management network element.

[0214] At step S1010, the terminal device sends a first message to the first network element through a service-based interface.

[0215] For example, the terminal device can transmit the first message through the user plane by using the first session. Alternatively, the terminal device can invoke a service provided by the first network element through the first session. As an example, the terminal device can take the session management network element B as the first network element, request the session management network element B to establish a new session for interacting with the Internet, and further request the session management network element B to modify or delete the session. As another example, the terminal device can take a selected location management network element as the first network element, and request the location management network element to perform positioning services.

[0216] In embodiment 1, the terminal device first establishes the first session. After the first session is established, the terminal device can interact with other network elements (such as a mobility management network element, a session management network element, a location management network element, and the like) through the user plane by using the first session based on the service-based interface. Since the data exchanged between the terminal device and the network element is transmitted through the user plane, the data is transmitted through the DRB in the air interface, thereby reducing the AS layer signaling interaction and reducing the signaling overhead.

[0217] Embodiment 2

[0218] In embodiment 2, the second network element can be a network storage function network element or a unified data management network element.

[0219] In embodiment 2, the terminal device can actively register an IP address of the terminal device in the first session to the second network element, so that other network elements can interact with the terminal device through the first session based on the service-based interface.

[0220] FIG. 11 is a flow diagram of a method of wireless communication, according to another embodiment of the present disclosure. The method shown in FIG. 11 includes steps S1101 to S1109. It should be noted that the solid line in FIG. 11 represents message interaction through the control plane (for example, the message passes through the N1 path shown in FIG. 4), and the dashed line represents message interaction through the user plane (for example, the message passes through the Nue path shown in FIG. 4).

[0221] At step S1101, the terminal device sends a first NAS message to a third network element. The first NAS message is used to trigger establishment of a first session.

[0222] In some embodiments, the first NAS message can be transmitted over the control plane through an access layer message.

[0223] In some embodiments, the first NAS message can comprise second indication information.

[0224] At step S1102, the third network element sends a second NAS message to a fourth network element. The second NAS message is used to request establishment of the first session. Subsequently, the terminal device can interact with other network elements based on the service-based interface over the user plane based on the first session.

[0225] At step S1103, the fourth network element sends a response message of the second NAS message to the third network element. The response message of the second NAS message carries information of the fourth network element.

[0226] In some embodiments, the response message of the second NAS message can carry an IP address of the terminal device in the first session. In this way, after step S1104, the third network element and / or the fourth network element can actively interact with the terminal device based on the service-based interface through the first session, for example, invoking a service provided by the terminal device.

[0227] At step S1104, the third network element sends a response message of the first NAS message to the terminal device. The response message of the first NAS message carries information of the third network element and / or the fourth network element.

[0228] In some embodiments, if the third network element rejects the service-based access of the terminal device, the third network element can indicate rejection of the service-based access of the terminal device in step S1104. In this scenario, steps S1102 and S1103 can be omitted.

[0229] After step S1104, if the terminal device knows the information of the first network element, the terminal device can directly interact with the first network element based on the service-based interface over the user plane through the first session. If the first network element knows the IP address of the terminal device in the first session, the first network element can also actively interact with the terminal device based on the service-based interface. For example, in steps S1105 and S1106, the terminal device can interact with the third network element and / or the fourth network element (in this scenario, the third network element and / or the fourth network element can also be referred to as the first network element).

[0230] At step S1105, the terminal device interacts with the third network element based on the service-based interface.

[0231] For example, in the case that the terminal device needs to perform registration update due to location movement or the terminal device performs periodic registration update, the terminal device can invoke the service provided by the third network element to perform registration update. The invocation of the service provided by the third network element by the terminal device is based on the interaction of the service-based interface. Illustratively, the terminal device can send a first message to the user plane function through a first session, and route the first message to the third network element through the user plane function.

[0232] At step S1106, the terminal device interacts with the fourth network element based on the service-based interface.

[0233] For example, when the terminal device needs to modify the first session (e.g., modify the QoS parameter used by the first session), the terminal device can invoke the service provided by the fourth network element to modify the session. The invocation of the service provided by the fourth network element by the terminal device is based on the interaction of the service-based interface. Illustratively, the terminal device can send a first message to the user plane function through the first session, and route the first message to the fourth network element through the user plane function.

[0234] At step S1107, the terminal device sends a fourth message to the second network element. The fourth message includes the IP address of the terminal device in the first session.

[0235] In some embodiments, the fourth message can be used to request the second network element to store the IP address of the terminal device in the first session.

[0236] In some embodiments, the fourth message is sent through the service-based interface, i.e., the terminal device can invoke the service provided by the second network element through the service-based interface. Alternatively, the fourth message is transmitted in the user plane through the first session.

[0237] After step S1104, if the first network element does not know the IP address of the terminal device in the first session, the IP address of the terminal device in the first session can be obtained through step S1108, and then the first network element interacts with the terminal device through the service-based interface (the first network element in steps S1108 to S1109 refers to other network elements in FIG. 11).

[0238] At step S1108, the first network element sends a fifth message to the second network element. The fifth message is used to request the IP address of the terminal device in the first session.

[0239] Based on the request, the second network element can indicate the IP address of the terminal device in the first session to the first network element.

[0240] At step S1109, the first network element sends a second message to the terminal device through the service-based interface.

[0241] For example, the first network element can invoke the service provided by the terminal device to transmit the second message in the user plane through the first session. As an example, when the first network element invokes the service provided by the terminal device, the specific routing manner can be to set the uri-host in the HTTP / 2 request message to the information of the terminal device.

[0242] In embodiment 2, the terminal device first establishes the first session. After the first session is established, the third network element and / or the fourth network element can interact with the terminal device based on the service-based interface in the user plane through the first session. In addition to the third network element and the fourth network element, other network elements can also interact with the terminal device based on the service-based interface in the user plane through the first session by querying the second network element to obtain the IP address of the terminal device in the first session. Since the data exchanged between the terminal device and the network element is transmitted in the user plane, it is transmitted through the DRB in the air interface, so that the AS layer signaling interaction can be reduced and the signaling overhead can be reduced.

[0243] Embodiment 3:

[0244] In embodiment 3, the second network element can be a mobility management network element. That is, in embodiment 3, the second network element and the third network element are the same network element.

[0245] FIG. 12 is a flow diagram of a method of wireless communication, according to another embodiment of the present disclosure. The method shown in FIG. 12 includes steps S1201 to S1212. It should be noted that the solid line in FIG. 12 represents message interaction through the control plane (e.g., the message passes through the N1 path shown in FIG. 4), the dashed line represents message interaction through the user plane (e.g., the message passes through the Nue path shown in FIG. 4), and the dotted line represents message interaction through both the control plane and the user plane.

[0246] In step S1201, the terminal device sends a first NAS message to the third network element. The first NAS message is used to trigger establishment of a first session.

[0247] In some embodiments, the first NAS message can be transmitted in the control plane through an access layer message.

[0248] In some embodiments, the first NAS message can include second indication information.

[0249] In step S1202, the third network element sends a second NAS message to the fourth network element. The second NAS message is used to request establishment of a first session. Subsequently, the terminal device can interact with other network elements based on a service-based interface in the user plane based on the first session.

[0250] In step S1203, the fourth network element sends a response message of the second NAS message to the third network element. The response message of the second NAS message carries information of the fourth network element.

[0251] In some embodiments, the response message of the second NAS message can carry an IP address of the terminal device in the first session. In this way, after step S1204, the third network element and / or the fourth network element can actively interact with the terminal device based on the service-based interface through the first session, for example, invoking a service provided by the terminal device.

[0252] In step S1204, the third network element sends a response message of the first NAS message to the terminal device. The response message of the first NAS message carries information of the third network element and / or the fourth network element.

[0253] In some embodiments, if the third network element rejects the service-based access of the terminal device, the third network element can indicate the rejection of the service-based access of the terminal device in step S1204. In this case, steps S1202 and S1203 can be omitted.

[0254] After step S1204, if the terminal device knows the information of the first network element, the terminal device can directly interact with the first network element based on the service-based interface in the user plane through the first session. For example, the terminal device can invoke a service provided by the first network element, and the specific routing manner can be, for example, that the terminal device sets the uri-host in the HTTP / 2 request message to the information of the first network element. Or the first network element can invoke a service provided by the terminal device, and the specific routing manner can be, for example, that the first network element sets the uri-host in the HTTP / 2 request message to the information of the terminal device. For example, in steps S1205 and S1206, the terminal device can interact with the third network element and / or the fourth network element (in this case, the third network element and / or the fourth network element can also be referred to as the first network element).

[0255] In step S1205, the terminal device interacts with the third network element based on the service-based interface.

[0256] For example, in the case that the terminal device needs to perform registration update due to location movement or the terminal device performs periodic registration update, the terminal device can invoke a service provided by the third network element to perform registration update. The invocation of the service provided by the third network element by the terminal device is based on the service-based interface. For example, the terminal device can send a first message to the user plane function through the first session, and route to the third network element through the user plane function.

[0257] In step S1206, the terminal device interacts with the fourth network element based on the service-based interface.

[0258] For example, when the terminal device needs to modify the first session (e.g., modify a QoS parameter used by the first session), the terminal device can invoke the service provided by the fourth network element to modify the session. The terminal device invokes the service provided by the fourth network element is based on the interaction of the service-based interface. For example, the terminal device can send a first message to the user plane function through the first session, and route the first message to the fourth network element through the user plane function.

[0259] After step S1204, if the terminal device does not know the information of the first network element, the terminal device needs to query the second network element to know the information of the first network element. Then, the terminal device can interact with the first network element through the service-based interface based on the known information of the first network element. This is described below in steps S1207 to S1211 (the first network element in steps S1207 to S1211 is described with reference to other network elements in FIG. 12).

[0260] In step S1207, the terminal device sends a third message to the second network element. The third message is used to determine the first network element.

[0261] In some embodiments, the third message is sent through the service-based interface, i.e., the terminal device can invoke the service provided by the second network element through the service-based interface. Alternatively, the third message is transmitted in the user plane through the first session.

[0262] In some embodiments, the third message is sent through the access layer message in the control plane.

[0263] In step S1208, the second network element sends a sixth message to the network storage function network element. The sixth message is used to request the information of one or more network elements.

[0264] For example, the second network element can invoke the service provided by the network storage function network element through the service-based interface.

[0265] In some embodiments, the network storage function network element can send the information of one or more network elements to the second network element.

[0266] In some embodiments, the network storage function network element can return the information of multiple network elements of the same type to the second network element. For example, the network storage function network element can return the information of multiple session management network elements to the second network element when the type of the network element queried by the second network element is the session management network element. For example, the network storage function network element can return the information of multiple location management network elements to the second network element when the type of the network element queried by the second network element is the location management network element.

[0267] In step S1209, the second network element determines the first network element based on the information of one or more network elements.

[0268] For example, the second network element can determine the first network element based on one or more of the following information: load information of the network element, location where the network element provides service, capability information of the network element, time when the network element provides service, and the like. For example, the second network element can determine a session management network element serving the terminal device from a plurality of session management network elements. Alternatively, the second network element can determine a location management network element serving the terminal device from a plurality of location management network elements.

[0269] At step S1210, the second network element sends information of the first network element to the terminal device.

[0270] In some embodiments, the second network element can send the information of the first network element to the terminal device through a service-based interface, for example, the third message is sent through the service-based interface, and the information of the first network element can also be sent through the service-based interface. In some embodiments, the second network element can send the information of the first network element to the terminal device through an access layer message in the control plane, for example, the third message is sent through the access layer message in the control plane, and the information of the first network element can also be sent through the access layer message in the control plane.

[0271] At step S1211, the terminal device sends a first message to the first network element through a service-based interface.

[0272] For example, the terminal device can transmit the first message through the first session in the user plane. Alternatively, the terminal device can invoke a service provided by the first network element through the first session. As an example, the terminal device can take session management network element B as the first network element, request session management network element B to establish a new session for interaction with the Internet, and subsequently request session management network element B to modify or delete the session. As another example, the terminal device can take a selected location management network element as the first network element, and request the location management network element to perform positioning service.

[0273] When a new network element needs to interact with the terminal device, a fifth message can be sent to the second network element to request the IP address of the terminal device in the first session. Subsequently, the new network element can interact with the terminal device in the user plane through the first session based on the service-based interface.

[0274] In embodiment 3, the terminal device first establishes a first session. After the establishment of the first session, the third network element and / or the fourth network element can interact with the terminal device based on the service-oriented interface in the user plane through the first session. The terminal device can obtain information of other network elements except the third network element and the fourth network element by querying the second network element, or the other network elements can obtain the IP address of the terminal device in the first session by querying the second network element, and then the terminal device and the other network elements can also interact with the terminal device based on the service-oriented interface in the user plane through the first session. Since the data exchanged between the terminal device and the network element is transmitted in the user plane, it is transmitted through the DRB in the air interface, so that the AS layer signaling interaction can be reduced and the signaling overhead can be reduced.

[0275] The method embodiments of the present application are described in detail above in combination with FIG. 1 to FIG. 12, and the device embodiments of the present application are described in detail below in combination with FIG. 13 to FIG. 17. It should be understood that the description of the method embodiments corresponds to the description of the device embodiments, and therefore, the parts not described in detail can be referred to the foregoing method embodiments.

[0276] FIG. 13 is a structural schematic diagram of a terminal device provided by an embodiment of the present application. The terminal device 1300 shown in FIG. 13 can include a first sending module 1310 and / or a first receiving module 1320. The first sending module 1310 can be configured to send a first message to a first network element through a service-oriented interface. The first receiving module 1320 can be configured to receive a second message sent by the first network element through the service-oriented interface. The first message and / or the second message are transmitted in the user plane through a first session.

[0277] In some embodiments, the terminal device further includes a second sending module configured to send a third message to a second network element, the third message being used to determine the first network element.

[0278] In some embodiments, the third message includes first indication information, the first indication information being used to determine the type of the first network element.

[0279] In some embodiments, the terminal device further includes a second receiving module configured to receive information of one or more network elements sent by the second network element, and a determining module configured to determine the first network element based on the information of the one or more network elements.

[0280] In some embodiments, the information of the one or more network elements comprises one or more of: an identity of the one or more network elements; a type of the one or more network elements; an FQDN of the one or more network elements; an IP address of the one or more network elements; capability information of the one or more network elements; load information of the one or more network elements; a location where the one or more network elements provide services; a time when the one or more network elements provide services.

[0281] In some embodiments, the third message is transmitted in user plane through the first session.

[0282] In some embodiments, the second network element comprises one or more of: a network repository function network element, a unified data management network element.

[0283] In some embodiments, the information of the second network element is pre-configured to the terminal device, or the information of the second network element is configured to the terminal device by a network element in a core network.

[0284] In some embodiments, the terminal device further comprises a third sending module configured to send a fourth message to the second network element, the fourth message comprising an IP address of the terminal device in the first session.

[0285] In some embodiments, the terminal device further comprises a third receiving module configured to receive the information of the first network element sent by the second network element.

[0286] In some embodiments, the information of the first network element comprises one or more of: an identity of the first network element; an FQDN of the first network element; an IP address of the first network element.

[0287] In some embodiments, the third message is transmitted in user plane through the first session, or the third message is transmitted in control plane through an access stratum message.

[0288] In some embodiments, the second network element is a mobility management network element.

[0289] In some embodiments, the terminal device further comprises a fourth sending module configured to send a first NAS message to a third network element, the first NAS message being used to trigger establishment of the first session.

[0290] In some embodiments, the first NAS message comprises second indication information, the second indication information being used to indicate one or more of: the terminal device supports communication with a network element in a core network through a service-based interface, the terminal device requests communication with a network element in a core network through a service-based interface.

[0291] In some embodiments, the second indication information comprises a first access point name, and the first access point name is used to indicate that the terminal device requests to communicate with a network element in a core network through a service interface.

[0292] In some embodiments, the first NAS message comprises one or more of the following: a registration request message, a session establishment request message.

[0293] In some embodiments, the terminal device further comprises a fourth receiving module, configured to receive a response message of the first NAS message sent by the third network element, wherein the response message carries information of the third network element and / or information of a fourth network element, and the fourth network element is a session management network element used to manage the first session.

[0294] In some embodiments, the information of the third network element and / or the information of the fourth network element comprises one or more of the following: an identifier of a network element, an FQDN of a network element, and an IP address of a network element.

[0295] In some embodiments, the third network element is a mobility management network element.

[0296] In some embodiments, the first session is used to carry messages received and / or sent by the terminal device through the service interface.

[0297] In some embodiments, the first sending module 1310 and / or the first receiving module 1320 can be a transceiver 1730. The terminal device 1300 can further include a processor 1710 and a memory 1720, as shown in FIG. 17.

[0298] FIG. 14 is a structural schematic diagram of a network device according to an embodiment of the present application. The network device 1400 shown in FIG. 14 can be any first network element described above. The network device 1400 can include a first receiving module 1410 and / or a first sending module 1420. The first receiving module 1410 can be configured to receive a first message sent by a terminal device through a service interface. The first sending module 1420 can be configured to send a second message to the terminal device through the service interface. The first message and / or the second message are transmitted in a user plane through a first session.

[0299] In some embodiments, the network device further comprises a second sending module, configured to send a fifth message to a second network element, wherein the fifth message is used to request an IP address of the terminal device in the first session; and a second receiving module, configured to receive a response message of the fifth message sent by the second network element, wherein the response message is used to indicate the IP address of the terminal device in the first session.

[0300] In some embodiments, the second network element comprises one or more of: a network repository function network element, a unified data management network element, a mobility management network element.

[0301] In some embodiments, the first session is dedicated to carrying messages received and / or sent by the terminal device through the service-based interface.

[0302] In some embodiments, the first receiving module 1410 and / or the first sending module 1420 can be a transceiver 1730. The network device 1400 can further include a processor 1710 and a memory 1720, as shown in FIG. 17.

[0303] FIG. 15 is a structural schematic diagram of a network device provided by another embodiment of the present application. The network device 1500 shown in FIG. 15 can be any of the second network elements described above. The network device 1500 can include a first receiving module 1510. The first receiving module 1510 can be configured to receive a third message sent by a terminal device, the third message being used to determine a first network element; wherein the terminal device interacts with the first network element through a service-based interface, and messages exchanged between the terminal device and the first network element are transmitted through a first session in a user plane.

[0304] In some embodiments, the third message includes first indication information, the first indication information being used to determine a type of the first network element.

[0305] In some embodiments, the network device further includes a first sending module configured to send information of one or more network elements to the terminal device; wherein the information of the one or more network elements is used to determine the first network element.

[0306] In some embodiments, the information of the one or more network elements comprises one or more of: an identifier of the one or more network elements; a type of the one or more network elements; an FQDN of the one or more network elements; an IP address of the one or more network elements; capability information of the one or more network elements; load information of the one or more network elements; a location at which the one or more network elements provide services; a time at which the one or more network elements provide services.

[0307] In some embodiments, the third message is transmitted through the first session in the user plane.

[0308] In some embodiments, the second network element comprises one or more of: a network repository function network element, a unified data management network element.

[0309] In some embodiments, the information of the second network element is pre-configured to the terminal device, or the information of the second network element is configured to the terminal device by a network element in a core network.

[0310] In some embodiments, the network device further includes a second receiving module, configured to receive a fourth message sent by the terminal device, the fourth message comprising an IP address of the terminal device in the first session.

[0311] In some embodiments, the network device further includes a third receiving module, configured to receive a fifth message sent by the first network element, the fifth message being used to request an IP address of the terminal device in the first session; and a second sending module, configured to send a response message of the fifth message to the first network element, the response message being used to indicate the IP address of the terminal device in the first session.

[0312] In some embodiments, the network device further includes a third sending module, configured to send information of the first network element to the terminal device.

[0313] In some embodiments, the information of the first network element comprises one or more of the following: an identifier of the first network element; an FQDN of the first network element; an IP address of the first network element.

[0314] In some embodiments, the third message is transmitted in a user plane through the first session, or the third message is transmitted in a control plane through an access layer message.

[0315] In some embodiments, the network device further includes a fourth sending module, configured to send a sixth message to a network storage function network element, the sixth message being used to request information of one or more network elements; and a determining module, configured to determine the information of the first network element based on the information of the one or more network elements.

[0316] In some embodiments, the information of the one or more network elements comprises one or more of the following: an identifier of the one or more network elements; a type of the one or more network elements; an FQDN of the one or more network elements; an IP address of the one or more network elements; capability information of the one or more network elements; load information of the one or more network elements; a location where the one or more network elements provide services; a time when the one or more network elements provide services.

[0317] In some embodiments, the sixth message comprises third indication information, the third indication information being used to determine the type of the first network element.

[0318] In some embodiments, the network device further includes a fourth receiving module, configured to receive a seventh message sent by a fourth network element, the seventh message being used to indicate an IP address of the terminal device in the first session, the fourth network element being a session management network element used to manage the first session.

[0319] In some embodiments, the second network element is a mobility management network element.

[0320] In some embodiments, the first session is dedicated to carrying messages received and / or sent by the terminal device through the service-based interface.

[0321] In some embodiments, the first receiving module 1510 can be the transceiver 1730. The network device 1500 can further include a processor 1710 and a memory 1720, as shown in FIG. 17.

[0322] FIG. 16 is a structural schematic diagram of a network device provided by another embodiment of the present application. The network device 1600 described in FIG. 16 can be any of the third network elements described above. The network device 1600 can include a first receiving module 1610. The first receiving module 1610 can be configured to receive a first NAS message sent by a terminal device, the first NAS message being used to trigger establishment of a first session, wherein messages exchanged between the terminal device and a first network element are transmitted in a user plane through the first session, and the terminal device and the first network element are configured to exchange messages through a service-based interface.

[0323] In some embodiments, the first NAS message includes second indication information, the second indication information being used to indicate one or more of the following: the terminal device supports communication with a network element in a core network through a service-based interface, and the terminal device requests to communicate with a network element in a core network through a service-based interface.

[0324] In some embodiments, the second indication information includes a first access point name, the first access point name being used to indicate that the terminal device requests to communicate with a network element in a core network through a service-based interface.

[0325] In some embodiments, the first NAS message includes one or more of the following: a registration request message, a session establishment request message.

[0326] In some embodiments, the network device further includes a first sending module configured to send, to the terminal device, a response message of the first NAS message, the response message of the first NAS message carrying information of the third network element and / or information of a fourth network element, wherein the fourth network element is a session management network element configured to manage the first session.

[0327] In some embodiments, the network device further comprises a second sending module, configured to send a second NAS message to a fourth network element, the second NAS message being used to request establishment of the first session; and a second receiving module, configured to receive a response message of the second NAS message sent by the fourth network element, the response message of the second NAS message carrying information of the fourth network element.

[0328] In some embodiments, the information of the third network element and / or the information of the fourth network element comprises one or more of the following information: an identifier of the network element, a fully qualified domain name (FQDN) of the network element, and an IP address of the network element.

[0329] In some embodiments, the third network element is a mobility management network element.

[0330] In some embodiments, the first session is dedicated to carrying messages received and / or sent by the terminal device through a service interface.

[0331] In some embodiments, the first receiving module 1610 can be a transceiver 1730. The network device 1600 can further include a processor 1710 and a memory 1720, as shown in FIG. 17.

[0332] FIG. 17 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application. The dashed line in FIG. 17 indicates that the unit or module is optional. The apparatus 1700 can be used to implement the method described in the above method embodiments. The apparatus 1700 can be a chip, a terminal device, or a network device.

[0333] The apparatus 1700 can include one or more processors 1710. The processor 1710 can support the apparatus 1700 to implement the method described in the above method embodiments. The processor 1710 can be a general purpose processor or a dedicated processor. For example, the processor can be a central processing unit (CPU). Alternatively, the processor can also be other general purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, etc. The general purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0334] The apparatus 1700 can further include one or more memories 1720. The memories 1720 store a program for execution by the processor 1710, such that the processor 1710 performs the methods described in the foregoing method embodiments. The memories 1720 can be independent of the processor 1710 or integrated in the processor 1710.

[0335] The apparatus 1700 can further include a transceiver 1730. The processor 1710 can communicate with other devices or chips through the transceiver 1730. For example, the processor 1710 can perform data transceiving with other devices or chips through the transceiver 1730.

[0336] The embodiments of the present application also provide a computer readable storage medium for storing a program. The computer readable storage medium can be applied to the terminal device or the network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the terminal device or the network device in the embodiments of the present application.

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

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

[0339] It should be understood that the terms "system" and "network" can be used interchangeably in the present application. In addition, the terms used in the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third", and "fourth" and the like in the specification and claims of the present application and the drawings are used to distinguish different objects, and are not used to describe a particular order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion.

[0340] In the embodiments of the present application, the "indication" mentioned can be direct indication, or indirect indication, or can be an indication with an associated relationship. For example, A indicates B, which can mean that B can be obtained by A directly; or A indirectly indicates B, for example, A indicates C, and B can be obtained by C; or A and B have an associated relationship.

[0341] In the embodiments of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that the determination of B according to A does not mean that B is determined only according to A, but B can also be determined according to A and / or other information.

[0342] In the embodiments of the present application, the term "corresponding" can represent a direct or indirect corresponding relationship between the two, can also represent an associated relationship between the two, and can also indicate a relationship with the indicated, configured and configured.

[0343] In the embodiments of the present application, "including" mentioned can mean direct inclusion, or indirect inclusion. Alternatively, "including" mentioned in the embodiments of the present application can be replaced by "indicating" or "for determining". For example, A includes B can be replaced by A indicating B, or A for determining B.

[0344] In the embodiments of the present application, "predefined" or "preconfigured" can be realized by pre-saving corresponding codes, tables or other means for indicating related information in devices (for example, including terminal devices and network devices), and the specific implementation manner of the present application is not limited. For example, predefinition can refer to definition in a protocol.

[0345] In the embodiments of the present application, the "protocol" can refer to a standard protocol in the communication field, for example, it can include LTE protocol, NR protocol and related protocols applied in future communication systems, and the present application is not limited to this.

[0346] In the embodiments of the present application, the term "and / or" is only a description of the association relationship between the associated objects, which means that there can be three relationships, for example, A and / or B can mean that A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in this paper generally represents a "or" relationship between the associated objects before and after it.

[0347] In various embodiments of the present application, the size of the serial number of the above processes does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0348] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented by other manners. For example, the above-described device embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and in actual implementation, another division manner can be adopted, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0349] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, i.e., can be located in one place or distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

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

[0351] In the above embodiments, all or part can be realized by software, hardware, firmware or any combination thereof. When realized by software, all or part can be realized 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, all or part of the processes or functions described in the embodiments of the present application are generated. 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 transferred from one computer readable storage medium to another, for example, the computer instructions can be transferred from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer readable storage medium can be any available medium readable by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media. The available media can be magnetic media (such as floppy disk, hard disk, magnetic tape), optical media (such as digital video disc (DVD)) or semiconductor media (such as solid state disk (SSD)) and the like.

[0352] The above descriptions are only the specific embodiments of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of the changes or replacements within the technical range disclosed by the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method of wireless communication, comprising: The method comprises: The terminal device sends a first message to a first network element through a service interface; and / or The terminal device receives a second message sent by the first network element through the service interface; The first message and / or the second message are transmitted in a user plane through a first session.

2. The method of claim 1, wherein, The method further comprises: The terminal device sends a third message to a second network element, the third message being used to determine the first network element.

3. The method of claim 2, wherein, The third message comprises first indication information, the first indication information being used to determine a type of the first network element.

4. The method according to claim 2 or 3, characterized in that, The method further comprises: The terminal device receives information of one or more network elements sent by the second network element; The terminal device determines the first network element based on the information of the one or more network elements.

5. The method of claim 4, wherein, The information of the one or more network elements comprises one or more of: identifiers of the one or more network elements; types of the one or more network elements; fully qualified domain names (FQDNs) of the one or more network elements; IP addresses of the one or more network elements; capability information of the one or more network elements; load information of the one or more network elements; locations at which the one or more network elements provide services; times at which the one or more network elements provide services.

6. The method according to claim 4 or 5, characterized in that, The third message is transmitted in the user plane through the first session.

7. The method according to any one of claims 4-6, characterized in that, The second network element comprises one or more of: a network storage function network element, a unified data management network element.

8. The method according to any one of claims 4-7, characterized in that, The information of the second network element is pre-configured to the terminal device, or the information of the second network element is configured to the terminal device by a network element in a core network.

9. The method according to any one of claims 4-8, characterized in that, The method further comprises: The terminal device sends a fourth message to the second network element, the fourth message comprising an IP address of the terminal device in the first session.

10. The method of claim 2 or 3, wherein, The method further comprises: The terminal device receives information of the first network element sent by the second network element.

11. The method of claim 10, wherein, The information of the first network element comprises one or more of: an identifier of the first network element; an FQDN of the first network element; an IP address of the first network element.

12. The method according to claim 10 or 11, characterized in that, The third message is transmitted in the user plane through the first session, or the third message is transmitted in a control plane through an access layer message.

13. The method according to any one of claims 10-12, characterized in that, The second network element is a mobility management network element.

14. The method of any one of claims 1-13, wherein, The method further comprises: The terminal device sends a first non-access stratum (NAS) message to a third network element, the first NAS message being used to trigger establishment of the first session.

15. The method of claim 14, wherein, The first NAS message comprises second indication information, the second indication information being used to indicate one or more of: the terminal device supports communication with a network element in a core network through a service interface, the terminal device requests communication with a network element in a core network through a service interface.

16. The method of claim 15, wherein, The second indication information comprises a first access point name, the first access point name being used to indicate that the terminal device requests communication with a network element in a core network through a service interface.

17. The method according to any one of claims 14-16, characterized by, The first NAS message comprises one or more of: a registration request message, a session establishment request message.

18. The method according to any one of claims 14-17, characterized by, The method further comprises: The terminal device receives a response message of the first NAS message sent by the third network element, and the response message carries information of the third network element and / or information of a fourth network element, where the fourth network element is a session management network element for managing the first session.

19. The method of claim 18, wherein, The information of the third network element and / or the information of the fourth network element includes one or more of the following: an identifier of the network element, an FQDN of the network element, and an IP address of the network element.

20. The method of any one of claims 14-19, wherein, The third network element is a mobility management network element.

21. The method of any one of claims 1-20, wherein, The first session is dedicated to carrying messages received and / or sent by the terminal device through a service interface.

22. A method of wireless communication, comprising: Comprise: The first network element receives a first message sent by a terminal device through a service interface; And / or The first network element sends a second message to the terminal device through a service interface; Wherein, the first message and / or the second message is transmitted in the user plane through the first session.

23. The method of claim 22, wherein, The method further comprises: The first network element sends a fifth message to a second network element, and the fifth message is used to request an IP address of the terminal device in the first session; The first network element receives a response message of the fifth message sent by the second network element, and the response message is used to indicate the IP address of the terminal device in the first session.

24. The method of claim 23, wherein, The second network element includes one or more of the following: a network storage function network element, a unified data management network element, and a mobility management network element.

25. The method of any one of claims 22-24, wherein, The first session is dedicated to carrying messages received and / or sent by the terminal device through a service interface.

26. A method of wireless communication, comprising: Comprise: The second network element receives a third message sent by a terminal device, and the third message is used to determine a first network element; Wherein, the terminal device interacts with the first network element through a service interface, and messages exchanged between the terminal device and the first network element are transmitted in the user plane through a first session.

27. The method of claim 26, wherein, The third message includes first indication information, and the first indication information is used to determine the type of the first network element.

28. The method of claim 26 or 27, wherein, The method further comprises: The second network element sends information of one or more network elements to the terminal device; Wherein, the information of the one or more network elements is used to determine the first network element.

29. The method of claim 28, wherein, The information of the one or more network elements includes one or more of the following: An identifier of the one or more network elements; A type of the one or more network elements; A fully qualified domain name (FQDN) of the one or more network elements; An IP address of the one or more network elements; Capability information of the one or more network elements; Load information of the one or more network elements; A location where the one or more network elements provide services; A time when the one or more network elements provide services.

30. The method of claim 28 or 29, wherein, The third message is transmitted in the user plane through the first session.

31. The method of any one of claims 28-30, wherein, The second network element includes one or more of the following: a network storage function network element and a unified data management network element.

32. The method of any one of claims 28-31, wherein, The information of the second network element is pre-configured to the terminal device, or the information of the second network element is configured to the terminal device by a network element in a core network.

33. The method of any one of claims 28-32, wherein, The method further comprises: The second network element receives a fourth message sent by the terminal device, and the fourth message includes an IP address of the terminal device in the first session.

34. The method of any one of claims 28-33, wherein, The method further comprises: The second network element receives a fifth message sent by the first network element, and the fifth message is used to request an IP address of the terminal device in the first session. The second network element sends a response message of the fifth message to the first network element, and the response message is used to indicate the IP address of the terminal device in the first session.

35. The method of claim 26 or 27, wherein, The method further comprises: The second network element sends information of the first network element to the terminal device.

36. The method of claim 35, wherein, The information of the first network element comprises one or more of the following: An identifier of the first network element; An FQDN of the first network element; An IP address of the first network element.

37. The method of claim 35 or 36, wherein, The third message is transmitted in a user plane through the first session, or the third message is transmitted in a control plane through an access layer message.

38. The method of any one of claims 35-37, wherein, The method further comprises: The second network element sends a sixth message to a network storage function network element, and the sixth message is used to request information of one or more network elements; The second network element determines the information of the first network element based on the information of the one or more network elements.

39. The method of claim 38, wherein, The information of the one or more network elements comprises one or more of the following: An identifier of the one or more network elements; A type of the one or more network elements; An FQDN of the one or more network elements; An IP address of the one or more network elements; Capability information of the one or more network elements; Load information of the one or more network elements; A location where the one or more network elements provide services; A time when the one or more network elements provide services.

40. The method of claim 38 or 39, wherein, The sixth message comprises third indication information, and the third indication information is used to determine the type of the first network element.

41. The method of any one of claims 35-40, wherein, The method further comprises: The second network element receives a seventh message sent by a fourth network element, and the seventh message is used to indicate an IP address of the terminal device in the first session, and the fourth network element is a session management network element used to manage the first session.

42. The method of any one of claims 35-41, wherein, The second network element is a mobility management network element.

43. The method of any one of claims 26-42, wherein, The first session is used to bear messages received and / or sent by the terminal device through a service interface.

44. A method of wireless communication, the method comprising: Comprise: A third network element receives a first non-access stratum (NAS) message sent by a terminal device, and the first NAS message is used to trigger establishment of a first session; Wherein, messages exchanged between the terminal device and a first network element are transmitted in a user plane through the first session, and the terminal device and the first network element are interacted through a service interface.

45. The method of claim 44, wherein, The first NAS message comprises second indication information, and the second indication information is used to indicate one or more of the following: The terminal device supports communication with a network element in a core network through a service interface, The terminal device requests to communicate with the network element in the core network through the service interface.

46. The method of claim 45, wherein, The second indication information comprises a first access point name, and the first access point name is used to indicate that the terminal device requests to communicate with the network element in the core network through the service interface.

47. The method of any one of claims 44-46, wherein, The first NAS message comprises one or more of the following: a registration request message, a session establishment request message.

48. The method of any one of claims 44-47, wherein, The method further comprises: The third network element sends a response message of the first NAS message to the terminal device, and the response message of the first NAS message carries information of the third network element and / or information of a fourth network element, where the fourth network element is a session management network element for managing the first session.

49. The method of any one of claims 44-48, wherein, The method further includes: The third network element sends a second NAS message to a fourth network element, and the second NAS message is used to request establishment of the first session. The third network element receives a response message of the second NAS message sent by the fourth network element, and the response message of the second NAS message carries information of the fourth network element.

50. The method of claim 48 or 49, wherein, The information of the third network element and / or the information of the fourth network element includes one or more of the following: an identifier of a network element, a fully qualified domain name (FQDN) of a network element, and an IP address of a network element.

51. The method of any one of claims 44-50, wherein, The third network element is a mobility management network element.

52. The method of any one of claims 44-51, wherein, The first session is dedicated to carrying messages received and / or sent by the terminal device through a service interface.

53. A terminal device, comprising: includes: A first sending module configured to send a first message to a first network element through a service interface; and / or A first receiving module configured to receive a second message sent by the first network element through the service interface; The first message and / or the second message are transmitted in a user plane through a first session.

54. The terminal device of claim 53, wherein, The terminal device further includes: A second sending module configured to send a third message to a second network element, where the third message is used to determine the first network element.

55. The terminal device of claim 54, wherein, The third message includes first indication information used to determine a type of the first network element.

56. The terminal device of claim 54 or 55, wherein, The terminal device further includes: A second receiving module configured to receive information of one or more network elements sent by the second network element; A determining module configured to determine the first network element based on the information of the one or more network elements.

57. The terminal device of claim 56, wherein, The information of the one or more network elements includes one or more of the following: An identifier of the one or more network elements; A type of the one or more network elements; A fully qualified domain name (FQDN) of the one or more network elements; An IP address of the one or more network elements; Capability information of the one or more network elements; Load information of the one or more network elements; A location at which the one or more network elements provide services; A time at which the one or more network elements provide services.

58. The terminal device of claim 56 or 57, wherein, The third message is transmitted in a user plane through the first session.

59. The terminal device of any one of claims 56-58, wherein, The second network element includes one or more of the following: a network storage function network element and a unified data management network element.

60. The terminal device of any one of claims 56-59, wherein, The information of the second network element is preconfigured to the terminal device, or the information of the second network element is configured to the terminal device by a network element in a core network.

61. The terminal device of any one of claims 56-60, wherein, The terminal device further includes: A third sending module configured to send a fourth message to the second network element, where the fourth message includes an IP address of the terminal device in the first session.

62. The terminal device of claim 54 or 55, wherein, The terminal device further includes: A third receiving module configured to receive information of the first network element sent by the second network element.

63. The terminal device of claim 62, wherein, The information of the first network element includes one or more of the following: An identifier of the first network element; A FQDN of the first network element; An IP address of the first network element.

64. The terminal device of claim 62 or 63, wherein, The third message is transmitted in a user plane through the first session, or the third message is transmitted in a control plane through an access layer message.

65. The terminal device of any one of claims 62-64, wherein, The second network element is a mobility management network element.

66. The terminal device of any one of claims 53-65, wherein, The terminal device further includes: A fourth sending module, configured to send a first non-access stratum (NAS) message to a third network element, the first NAS message being used to trigger establishment of the first session.

67. The terminal device of claim 66, wherein, The first NAS message includes second indication information, the second indication information being used to indicate one or more of the following: The terminal device supports communication with a network element in a core network through a service-based interface, The terminal device requests communication with a network element in a core network through a service-based interface.

68. The terminal device of claim 67, wherein, The second indication information includes a first access point name, the first access point name being used to indicate that the terminal device requests communication with a network element in a core network through a service-based interface.

69. The terminal device of any one of claims 66-68, wherein, The first NAS message includes one or more of the following: a registration request message, a session establishment request message.

70. The terminal device of any one of claims 66-69, wherein, The terminal device further includes: A fourth receiving module, configured to receive a response message of the first NAS message sent by the third network element, the response message carrying information of the third network element and / or information of a fourth network element, wherein the fourth network element is a session management network element used to manage the first session.

71. The terminal device of claim 70, wherein, The information of the third network element and / or the information of the fourth network element includes one or more of the following: an identifier of a network element, a FQDN of a network element, and an IP address of a network element.

72. The terminal device of any one of claims 66-71, wherein, The third network element is a mobility management network element.

73. The terminal device of any one of claims 53-72, wherein, The first session is used to carry messages received and / or sent by the terminal device through a service-based interface.

74. A network device, comprising: The network device is a first network element, and the network device includes: A first receiving module, configured to receive a first message sent by a terminal device through a service-based interface; and / or A first sending module, configured to send a second message to the terminal device through the service-based interface; The first message and / or the second message are transmitted in a user plane through a first session.

75. The network device of claim 74, wherein, The network device further includes: A second sending module, configured to send a fifth message to a second network element, the fifth message being used to request an IP address of the terminal device in the first session; A second receiving module, configured to receive a response message of the fifth message sent by the second network element, the response message being used to indicate the IP address of the terminal device in the first session.

76. The network device of claim 75, wherein, The second network element includes one or more of the following: a network storage function network element, a unified data management network element, and a mobility management network element.

77. The network device of any of claims 74-76, wherein, The first session is used to carry messages received and / or sent by the terminal device through a service-based interface.

78. A network device, comprising: The network device is a second network element, and the network device includes: A first receiving module, configured to receive a third message sent by a terminal device, the third message being used to determine a first network element; The terminal device and the first network element interact through a service-based interface, and messages exchanged between the terminal device and the first network element are transmitted in a user plane through a first session.

79. The network device of claim 78, wherein, The third message includes first indication information, the first indication information being used to determine a type of the first network element.

80. The network device of claim 78 or 79, wherein, The network device further comprises: The first sending module is used for sending information of one or more network elements to the terminal device; The information of the one or more network elements is used for determining the first network element.

81. The network device of claim 80, wherein, The information of the one or more network elements comprises one or more of the following: An identifier of the one or more network elements; A type of the one or more network elements; A fully qualified domain name (FQDN) of the one or more network elements; An IP address of the one or more network elements; Capability information of the one or more network elements; Load information of the one or more network elements; A location where the one or more network elements provide services; A time when the one or more network elements provide services.

82. The network device of claim 80 or 81, wherein, The third message is transmitted in a user plane through the first session.

83. The network device of any of claims 80-82, wherein, The second network element comprises one or more of the following: a network storage function network element, a unified data management network element.

84. The network device of any of claims 80-83, wherein, The information of the second network element is pre-configured to the terminal device, or the information of the second network element is configured to the terminal device by a network element in a core network.

85. The network device of any of claims 80-84, wherein, The network device further comprises: The second receiving module is used for receiving a fourth message sent by the terminal device, wherein the fourth message comprises an IP address of the terminal device in the first session. The network device further comprises:

86. The network device of any of claims 80-85, wherein, The third receiving module is used for receiving a fifth message sent by the first network element, wherein the fifth message is used for requesting the IP address of the terminal device in the first session; The second sending module is used for sending a response message of the fifth message to the first network element, wherein the response message is used for indicating the IP address of the terminal device in the first session. The network device further comprises:

87. The network device of claim 78 or 79, wherein, The third sending module is used for sending information of the first network element to the terminal device. The information of the first network element comprises one or more of the following:

88. The network device of claim 87, wherein, An identifier of the first network element; An FQDN of the first network element; An IP address of the first network element. The third message is transmitted in a user plane through the first session, or the third message is transmitted in a control plane through an access layer message.

89. The network device of claim 87 or 88, wherein, The network device further comprises:

90. The network device of any of claims 87-89, wherein, The fourth sending module is used for sending a sixth message to a network storage function network element, wherein the sixth message is used for requesting information of one or more network elements; The determining module is used for determining the information of the first network element based on the information of the one or more network elements. The information of the one or more network elements comprises one or more of the following:

91. The network device of claim 90, wherein, An identifier of the one or more network elements; A type of the one or more network elements; An FQDN of the one or more network elements; An IP address of the one or more network elements; Capability information of the one or more network elements; Load information of the one or more network elements; A location where the one or more network elements provide services; A time when the one or more network elements provide services. The sixth message comprises third indication information, and the third indication information is used for determining the type of the first network element.

92. The network device of claim 90 or 91, wherein, The network device further comprises:

93. The network device of any of claims 87-92, wherein, ​ a fourth receiving module, configured to receive a seventh message sent by a fourth network element, the seventh message being used to indicate an IP address of the terminal device in the first session, and the fourth network element being a session management network element used to manage the first session.

94. The network device of any of claims 87-93, wherein, The second network element is a mobility management network element.

95. The network device of any of claims 78-94, wherein, The first session is used to carry messages received and / or sent by the terminal device through a service-oriented interface.

96. A network device, comprising: The network device is a third network element, and the network device comprises: a first receiving module, configured to receive a first non-access stratum (NAS) message sent by a terminal device, the first NAS message being used to trigger establishment of a first session; The terminal device and the first network element interact through the first session in a user plane, and the terminal device and the first network element interact through a service-oriented interface.

97. The network device of claim 96, wherein, The first NAS message comprises second indication information, and the second indication information is used to indicate one or more of the following: The terminal device supports communication with a network element in a core network through a service-oriented interface, The terminal device requests to communicate with a network element in a core network through a service-oriented interface.

98. The network device of claim 97, wherein, The second indication information comprises a first access point name, and the first access point name is used to indicate that the terminal device requests to communicate with a network element in a core network through a service-oriented interface.

99. The network device of any of claims 96-98, wherein, The first NAS message comprises one or more of the following: a registration request message, a session establishment request message.

100. The network device of any of claims 96-99, wherein, The network device further comprises: a first sending module, configured to send a response message of the first NAS message to the terminal device, the response message of the first NAS message carrying information of the third network element and / or information of a fourth network element, wherein the fourth network element is a session management network element used to manage the first session. The network device further comprises:

101. The network device of any of claims 96-100, wherein, a second sending module, configured to send a second NAS message to a fourth network element, the second NAS message being used to request establishment of the first session; a second receiving module, configured to receive a response message of the second NAS message sent by the fourth network element, the response message of the second NAS message carrying information of the fourth network element. The information of the third network element and / or the information of the fourth network element comprises one or more of the following information: an identifier of a network element, a fully qualified domain name (FQDN) of a network element, and an IP address of a network element.

102. The network device of claim 100 or 101, wherein, The third network element is a mobility management network element.

103. The network device of any of claims 96-102, wherein, The first session is used to carry messages received and / or sent by the terminal device through a service-oriented interface. 104.The network device of any of claims 96-103, wherein, The terminal device comprises a transceiver, a memory, and a processor, the memory is used to store a program, the processor is used to invoke the program in the memory and control the transceiver to receive or send a signal, so that the terminal device executes the method in any one of claims 1-21.

105. A terminal device, comprising: The network device comprises a transceiver, a memory, and a processor, the memory is used to store a program, the processor is used to invoke the program in the memory and control the transceiver to receive or send a signal, so that the network device executes the method in any one of claims 22-25 or 26-43 or 44-52. 106.A network device, characterized in that, ​ 107. An apparatus, comprising: comprising a processor to call a program from a memory to cause the apparatus to perform the method of any of claims 22-25 or 26-43 or 44-52.

108. A chip, comprising: comprising a processor to call a program from a memory to cause the apparatus to perform the method of any of claims 22-25 or 26-43 or 44-52.

109. A computer readable storage medium, characterized in that, having a program stored thereon, the program causing a computer to perform the method of any of claims 22-25 or 26-43 or 44-52.

110. A computer program product, characterized in that, comprising a program to cause a computer to perform the method of any of claims 22-25 or 26-43 or 44-52.

111. A computer program, characterized in that, the computer program causing a computer to perform the method of any of claims 22-25 or 26-43 or 44-52. the computer program causing a computer to perform the method of any of claims 22-25 or 26-43 or 44-52.

Images