Wireless communication method and communication device

Abstract

Provided are a wireless communication method and a communication device. The method comprises: a first device receiving first information sent by a second device, wherein the first information is used for indicating information of a data plane device capable of serving the first device. On the basis of first information, a first device can discover a suitable data plane device serving the first device, so as to acquire an efficient data service. For example, for data plane devices with a distributed deployment, on the basis of first information, a first device can discover a data plane device closer to the first device, thereby reducing the latency for the first device with regard to requesting a data service operation.

Description

Wireless communication method and communication device TECHNICAL FIELD

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

[0002] With the development of technology, a network architecture based on a data plane (DP) service is proposed. There are some aspects to be improved in the communication based on the data plane.

[0003] SUMMARY

[0004] The present application provides a kind of, terminal device and network equipment. The aspects related to the present application are introduced as follows.

[0005] In a first aspect, a wireless communication method is provided, the method comprising: receiving, by a first device, first information transmitted by a second device; wherein the first information is used to indicate information of a data plane device capable of serving the first device.

[0006] In a second aspect, a wireless communication method is provided, the method comprising: transmitting, by a second device, first information; wherein the first information is used to indicate information of a data plane device capable of serving a first device.

[0007] In a third aspect, a wireless communication method is provided, the method comprising: transmitting, by a data plane device, registration information to a network repository function (NRF); wherein the registration information is used to register the data plane device to the NRF.

[0008] In a fourth aspect, a wireless communication method is provided, the method comprising: receiving, by a control plane device, a first request; wherein the first request is used to request to discover a data plane device serving a first device.

[0009] In a fifth aspect, a wireless communication method is provided, the method comprising: receiving, by a third device, first query information transmitted by a second device; wherein the third device is used to obtain an address of a data plane device capable of serving a first device from a DNS server, and the first query information is used to request to query the address of the data plane device.

[0010] In a sixth aspect, a wireless communication method is provided, the method comprising: receiving, by an access network device, first information transmitted by a second device; wherein the first information is used to indicate information of a data plane device capable of serving a first device and / or the access network device.

[0011] In a seventh aspect, a communication device is provided, the communication device being a first device, the communication device comprising: a first receiving unit, configured to receive first information sent by a second device; wherein the first information is used to indicate information of a data plane device capable of serving the first device.

[0012] In an eighth aspect, a communication device is provided, the communication device being a second device, the communication device comprising: a first sending unit, configured to send first information; wherein the first information is used to indicate information of a data plane device capable of serving a first device.

[0013] In a ninth aspect, a communication device is provided, the communication device being a data plane device, the communication device comprising: a second sending unit, configured to send registration information to a network repository function (NRF); wherein the registration information is used to register the data plane device to the NRF.

[0014] In a tenth aspect, a communication device is provided, the communication device being a control plane device, the communication device comprising: a second receiving unit, configured to receive a first request; wherein the first request is used to request to discover a data plane device capable of serving a first device.

[0015] In an eleventh aspect, a communication device is provided, the communication device being a third device, the communication device comprising: a third receiving unit, configured to receive first query information sent by a second device; wherein the third device is used to obtain an address of a data plane device capable of serving a first device from a target domain name system (DNS) server, and the first query information is used to request to query the address of the data plane device.

[0016] In a twelfth aspect, a communication device is provided, the communication device being an access network device, the communication device comprising: a fourth receiving unit, configured to receive first information sent by a second device; wherein the first information is used to indicate information of a data plane device capable of serving the first device and / or the access network device.

[0017] In a thirteenth aspect, a communication device is provided, comprising a processor and a memory, the memory being used to store one or more computer programs, and the processor being used to invoke the computer programs in the memory to cause the communication device to perform some or all of the steps in the methods of the various aspects described above.

[0018] In a fourteenth aspect, an embodiment of the present application provides a communication system, which comprises the communication device described above. In another possible design, the system can further comprise other devices interacting with the communication device in the solutions provided by the embodiments of the present application.

[0019] In a fifteenth aspect, an embodiment of the present application provides a computer readable storage medium, which stores a computer program. The computer program causes a communication device to perform some or all of the steps of the methods in the various aspects described above.

[0020] In a sixteenth 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 communication device to perform some or all of the steps of the methods in the various aspects described above. In some implementations, the computer program product can be a software installation package.

[0021] In a seventeenth 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 methods in the various aspects described above.

[0022] Based on the first information, the first device can discover a suitable data plane device serving it, thereby obtaining efficient data service. For example, for a distributed deployment of data plane devices, based on the first information, the first device can discover a data plane device close to the first device, thereby reducing the latency of the first device requesting data service operation. BRIEF DESCRIPTION OF DRAWINGS

[0023] FIG. 1 is a schematic diagram of a wireless communication system to which embodiments of the present application can be applied.

[0024] FIG. 2 is a schematic diagram of a network architecture.

[0025] FIG. 3 is a schematic diagram of a network architecture to which embodiments of the present application can be applied.

[0026] FIG. 4 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.

[0027] FIG. 5 is a schematic flowchart of another wireless communication method according to an embodiment of the present application.

[0028] FIG. 6 is a schematic flowchart of another wireless communication method according to an embodiment of the present application.

[0029] FIG. 7 is a schematic flowchart of another wireless communication method according to an embodiment of the present application.

[0030] FIG. 8 is a schematic flowchart of another wireless communication method according to an embodiment of the present application.

[0031] FIG. 9 is a schematic flowchart of another wireless communication method according to an embodiment of the present application.

[0032] FIG. 10 is a schematic flow chart of another method of wireless communication provided by embodiments of the present application.

[0033] FIG. 11 is a schematic block diagram of a communication device provided by embodiments of the present application.

[0034] FIG. 12 is a schematic block diagram of another communication device provided by embodiments of the present application.

[0035] FIG. 13 is a schematic block diagram of another communication device provided by embodiments of the present application.

[0036] FIG. 14 is a schematic block diagram of another communication device provided by embodiments of the present application.

[0037] FIG. 15 is a schematic block diagram of another communication device provided by embodiments of the present application.

[0038] FIG. 16 is a schematic block diagram of another communication device provided by embodiments of the present application.

[0039] FIG. 17 is a schematic block diagram of an apparatus for communication provided by embodiments of the present application. DETAILED DESCRIPTION

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

[0041] Communication system

[0042] FIG. 1 is a wireless communication system 100 to which embodiments of the present application are applied. The wireless communication system 100 can include communication devices. The communication devices can include a network device 110 and a terminal device 120. The network device 110 can be a device that communicates with the terminal device 120.

[0043] FIG. 1 exemplarily shows one network device and two terminals. Optionally, the wireless communication system 100 can include multiple network devices and each network device can include other number of terminal devices within its coverage, which is not limited in the embodiments of the present application.

[0044] Optionally, the wireless communication system 100 can further include a network controller, a mobile management entity, and other network entities, which are not limited in the embodiments of the present application.

[0045] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, for example: 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) system, and the like. The technical solutions provided in the present application can also be applied to future communication systems, such as a 6th generation mobile communication system, a satellite communication system, and the like.

[0046] 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), a mobile terminal (MT), a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. The terminal device in the embodiments of the present application can refer to a device that provides 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 functions, vehicle-mounted devices, and the like. 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, and the like. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in vehicle-to-everything (V2X) or device to device (D2D), and the like. 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.

[0047] The network device in the embodiments of the present application can be a device for communicating with a terminal device. The network device can also include an access network device. The access network device can provide communication coverage for a specific geographic area and can communicate with terminal devices 120 located within the coverage area. The access network device can also be referred to as a radio access network device or a base station, etc. The access network device in the embodiments of the present application can refer to a radio access network (RAN) node (or device) that accesses a terminal device to a wireless network. The access network device can broadly cover or be replaced by various names as follows, such as: Node B (NodeB), evolved Node B (eNB), next generation Node B (gNB), relay station, 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, a network side device in a 6G network, a device that performs the function of a base station in a 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 device.

[0048] 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, a helicopter or a drone can be configured to serve as a device that communicates with another base station.

[0049] The communication devices involved in the wireless communication system can include not only access network devices and terminal devices, but also core network elements. The core network elements can be implemented by devices, that is, the core network elements are core network devices. It can be understood that the core network device can also be a kind of network device.

[0050] The core network element in the embodiment of the present application can include a network element that processes and forwards signaling and data of a user. For example, the core network device can include core network access and mobility management function (core access and mobility management function, AMF), session management function (session management function, SMF), and user plane gateway, location management function (location management function, LMF), and other core network devices. Among them, the user plane gateway can be a server with functions of mobility management, routing, forwarding, etc. for user plane data, generally located on the network side, such as serving gateway (serving gateway, SGW) or packet data network gateway (packet data network gateway, PGW) or user plane function entity (user plane function, UPF) and the like. Of course, other network elements can also be included in the core network, which are not listed here.

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

[0052] The network device and the terminal device can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; can also be deployed on the water surface; can also be deployed on airplanes, balloons and satellites in the air. The scenario in which the network device and the terminal device are located is not limited in the embodiment of the present application.

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

[0054] Mobile network system architecture

[0055] FIG. 2 is a schematic diagram of a network architecture. The network architecture can include a terminal device, an access network (access network, AN) network element, and a core network element.

[0056] The type of the core network element 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.

[0057] The UPF network element can be used to forward and receive data of the terminal. For example, the UPF network element can receive service data from a data network and transmit the data to the terminal through the access network device; the UPF network element can also receive user data from the terminal through the access network device and forward the data to the data network. Among them, the transmission resource allocated and scheduled by the UPF network element for the terminal is managed and controlled by the SMF network element. The bearer between the terminal 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. Among them, the user plane connection is a QoS flow that can be established between the UPF network element and the access network device to transmit data.

[0058] The AMF network element can be used to manage the terminal access to the core network, for example: location update of the terminal, registration network, access control, mobility management of the terminal, attachment and detachment of the terminal, etc. The AMF network element can also provide storage resources for the control plane of the session for the terminal in the case of providing services for the session, to store the session identifier, the SMF network element identifier associated with the session identifier, etc.

[0059] The SMF network element can be used to select a user plane network element for the terminal, redirect a user plane network element for the terminal, allocate an internet protocol (IP) address for the terminal, establish a bearer (also referred to as a session) between the terminal and the UPF network element, modify the session, release, and QoS control.

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

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

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

[0063] The NSSF is used for network slice selection, and the supported functions include: selecting a set of network slice instances to serve the UE; determining the allowed network slice selection assistance information (NSSAI), and determining the mapping to the single network slice selection assistance information (S-NSSAI) of the subscription when needed; determining the configured NSSAI, and determining the mapping to the S-NSSAI of the subscription when needed; determining a set of AMFs that can be queried for the UE, or determining a list of candidate AMFs based on configuration.

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

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

[0066] 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 untrusted 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.

[0067] The NRF is used for core network element registration, management, and state detection, so as to realize automatic management of the core network elements. When the core network element is started, it must be registered in the NRF to provide services. The registration information may include, for example, the type, address, and service list of the core network element.

[0068] It should be noted that in some communication systems (for example, a 5G system), the core network element can also be referred to as a network function (NF).

[0069] With the development of technology, the functions of the network elements are more diversified.

[0070] For example, some communication protocols or proposals (for example, 3GPP Rel-18, 3GPP TS 23.288) define network data analysis functions (NWDAF), data collection coordination functions (DCCF), and analytics data repository functions (ADRF) and other network elements. Based on the NWDAF, devices can collect data from various network elements, network management systems, and the like of the core network, and perform big data statistics, analysis, or intelligent data analysis, thereby obtaining network-side analysis or prediction data, and further assisting various network elements in more effectively controlling terminal device access according to the data analysis results.

[0071] For another example, some communication protocols or proposals (for example, 3GPP TS 28.104, TS 28.537, and TS 28.622) define a data service capability and management data analysis framework, including a management data analytics function (MDAF). It focuses on collecting data and providing data analysis reports for data consumers.

[0072] According to the practical experience of intelligent communication network, it is very difficult to obtain data and the quality of data is difficult to guarantee. The data collection based on network management also has the problems of less data types, long collection period (for example, 15 minutes), non-uniform data format, naming and calculation method of different manufacturers, and difficulty in opening network management data. In addition, it is more difficult to collect data from terminal devices because there are a large number of privacy and security problems in collecting data from terminal devices. How to ensure that the data collected from terminal devices can be processed by trusted nodes so as to not disclose the privacy of users, and how to track the collected data in the whole life cycle and ensure that the use of any data by any data consumer will be recorded, are problems that need to be solved urgently.

[0073] In view of the above problems, a network architecture based on data plane service is proposed.

[0074] The data elements in the data plane will cover internal and external data of the network, which can specifically include business data, user data, network data, perception data, external data and the like. The basic data services of the data plane can include one or more of data collection, data preprocessing, data storage, data access, data sharing and collaboration and the like. The basic data services of the data plane can have the following technical features: supporting trusted authentication, authorization and access, efficient data storage and management, on-demand data collection, data preprocessing, external data opening and the like.

[0075] In addition, "trusted" will become an important requirement of users for data services. Data services mainly reflect in the stages of data collection, data storage, data access, data sharing and the like. How to ensure the trustworthiness and traceability of data at each stage becomes a key problem that needs to be solved by the data plane.

[0076] It should be noted that "data plane" is only an example of name. The "data plane" can also be called "data plane", "user data plane", "distributed data plane" and the like.

[0077] The data plane service can be implemented through a data plane network element. The data plane network element can be used for one or more of the following functions: data collection, data storage, data access, data sharing, data tracking, data opening and the like.

[0078] The following set of FIG. 3 illustrates the data plane network element.

[0079] As shown in FIG. 3, the data plane network element can include a data plane access controller (DPAC). The DPAC can implement one or more of the following functions: data collection, management of data sources and / or data consumers (e.g., management of IDs), verification of data sources and / or data consumers (e.g., verification of IDs), data processing, data exposure, interaction with a data plane repository, data tracking, and / or the like.

[0080] For example, when the data plane of the core network performs data collection once towards a terminal device, the terminal device can be considered as a data source, and a data transaction is performed between the terminal device and the data plane of the core network once. The terminal device can send a data transaction request to the DPAC, and the data transaction request can carry a data source ID, source data itself, data description information, and / or the like. The DPAC can verify the data source ID according to the data transaction request sent by the terminal device, and after verification, the DPAC can send the data source ID, source data itself, data description information, and / or the like to the data plane repository.

[0081] Optionally, the DPAC can be a newly defined network element. Alternatively, the DPAC can be obtained by enhancing the function of a network element in the related art. For example, the DPAC can be obtained by enhancing the DCCF.

[0082] It should be noted that the DPAC is only an example of the name of the network element, and the network element can also be referred to as other names. For example, the network element can be referred to as a data plane management network element, a data plane interface, a data plane control network element, and / or the like.

[0083] In some embodiments, the data plane network element can include a data plane repository. The data plane repository can be used to store data of data sources. The data plane repository can include, for example, the data plane repository infrastructure shown in FIG. 3.

[0084] It should be noted that each network element in FIG. 3 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).

[0085] It should be noted that in the network architecture shown in the above FIG. 3, only the network elements included in the entire network architecture are exemplarily illustrated. In the embodiments of the present application, the network elements included in the entire network architecture are not limited.

[0086] Those skilled in the art can understand that the network architecture shown in FIG. 3 does not constitute a limitation on the network architecture, and in actual implementation, the network architecture can include more or fewer network elements than FIG. 3, or combine certain network elements, etc. In addition, it should be understood that the AN or RAN in FIG. 3 is represented as (R)AN.

[0087] The data plane network element can not only be used to perform operations related to core network element data, but also be used to perform operations related to data of a communication device such as a terminal device. Therefore, the data plane can implement more flexible and dedicated functions to collect data from devices such as terminal devices. The collected data can be used for next-generation AI / ML and sensing operations, thereby improving the performance of the entire communication system.

[0088] Optionally, the data plane network element can be distributedly deployed. In the case of distributed deployment, multiple data plane network elements of the same type can serve the same data plane. Among them, multiple data plane network elements of the same type can be distributed in different geographical locations. The data plane network element can be represented by the address of the data plane network element. Among them, the address can be an IP address. Taking the DPAC distributed deployment as an example, multiple DPACs can serve the same data plane. Multiple DPACs can be represented by the IP address of the DPAC.

[0089] FIG. 4 is a schematic flowchart of a wireless communication method provided by an embodiment of the present application. The method shown in FIG. 4 can be performed by at least two of a first device, a second device, and an access network device. The first device may, for example, include a terminal device. The second device may, for example, include an access network device and a core network device. Among them, the core network device may, for example, include one or more of the following: a control plane device, a user plane device. Among them, the control plane device may, for example, include an SMF. The user plane device may, for example, include a UPF.

[0090] The method shown in FIG. 4 can include step S410. In step S410, the second device sends first information.

[0091] The receiver of the first information can be the first device and / or the access network device. For example, step S410 can include step S411. In step S411, the first device can receive the first information. For another example, step S410 can include step S412. In step S412, the access network device can also receive the first information.

[0092] Exemplarily, the first information can be sent by the core network device to the first device, and the access network device can receive the first information sent by the core network device and forward the first information to the first device as the second device.

[0093] The first information can be used to indicate information of a data plane device capable of serving the first device and / or the access network device. For example, for step S411, the first information received by the first device can be used to indicate information of a data plane device capable of serving the first device. That is, the first device can discover a data plane device suitable for itself based on the first information. For another example, for step S412, the first information received by the access network device can indicate information of a data plane device capable of serving the access network device and / or the first device. That is, the access network device can discover a data plane device suitable for itself based on the first information, and / or, the access network device can discover a data plane device capable of serving the first device based on the first information. It can be understood that, in the case that the first information received by the access network device indicates a data plane device capable of serving the access network device, the access network device can be understood as a kind of first device, that is, the access network device can receive the first information indicating a data plane device capable of serving itself as a first device.

[0094] The data plane device can include the data plane network element described above. For example, the data plane device can include a DPAC. In other words, the first information can be used to indicate information of a DPAC capable of serving the first device.

[0095] It can be understood that, based on the first information, the first device can discover a data plane device capable of serving itself, thereby obtaining efficient data service. For example, for a DPAC deployed in a distributed manner, based on the first information, the first device can discover a DPAC close to the first device, thereby reducing the latency of the first device requesting a data service operation.

[0096] In the case that the first information is obtained through the user plane device, that is, the second device includes the user plane device, the technical solution provided in the present application can be referred to as a "data plane device discovery process based on the user plane". In the case that the first information is obtained through the control plane device, that is, the second device includes the control plane device, the technical solution provided in the present application can be referred to as a "data plane device discovery process based on the control plane".

[0097] In some embodiments, the information of the data plane device can include one or more of the following: an address of the data plane device, an instance ID of the data plane device.

[0098] In the present application, the address of a device can include the IP address of the device. Therefore, the address of the data plane device can include the IP address of the data plane device. As described above, for a data plane device deployed in a distributed manner, each data plane device can be represented by an address. Therefore, based on the address of the data plane device, the first information can indicate which data plane device or data plane devices are capable of serving the first device.

[0099] The instance identifier of the data plane device can represent a data plane network element instance. An IP address of a data plane network element can be associated with one or more data plane network element instances. Therefore, the IP address of the data plane network element can be determined based on the data plane network element instance.

[0100] In some embodiments, the first information can further comprise information indicative of the first device. For example, the first information can further comprise one or more of: an identifier of the first device, an address of the first device. For example, the first information can comprise: an identifier of the first device, information of a data plane device capable of serving the first device. For another example, the first information can comprise: an address of the first device, information of a data plane device capable of serving the first device. For another example, the first information can comprise: an address of the first device, an identifier of the first device, information of a data plane device capable of serving the first device.

[0101] It can be understood that the first information received by different first devices can be different, i.e., the data plane devices capable of serving different first devices can be different. Therefore, the first information comprising information of the first device can indicate which first device or which first devices the first information is for, so that the first device can obtain the first information corresponding to the first device.

[0102] In some embodiments, the first information can be carried in the connection establishment request receiving message. That is, the discovery of the data plane device can be implemented in the connection establishment process. For example, the first information can be carried in the connection establishment request receiving message for the data plane.

[0103] In some embodiments, the first information can be carried in the data packet of the user plane. That is, the discovery of the data plane device can be implemented in the data interaction process between the terminal device and the user plane. Optionally, the address of the first device indicated by the first information can be indicated by the destination address of the data packet.

[0104] In some embodiments, the first device can send a first request. The first request can be used to request to discover the data plane device. In other words, through the first request, the first device can request to obtain the data plane device capable of serving the first device. That is, based on the first request, the first device can trigger the discovery process of the data plane device.

[0105] For example, the first request can be used to request to discover the IP address of the data plane device. Correspondingly, the first information fed back based on the first request can comprise the IP address of the data plane device. If the IP address of the data plane device is obtained through the DNS server, the first request can be carried in the DNS query information. For another example, the first request can be used to request to discover the instance of the data plane device. Correspondingly, the first information fed back based on the first request can comprise the instance ID of the data plane device.

[0106] In some embodiments, the first request can also be referred to as a data plane discovery request. In the case where the first request is used to request discovery of a DPAC, the first request can also be referred to as a DPAC discovery request.

[0107] In some embodiments, the first device can send the first request when the first device needs to interact with the data plane, or invoke a service of the data plane.

[0108] In some embodiments, the receiver of the first request can be the second device. For example, the method shown in FIG. 4 can include step S405. In step S405, the second device can receive the first request sent by the first device. In response to receiving the first request, the second device can perform step S412, i.e., sending the first information.

[0109] In some embodiments, the receiver of the first request can include devices other than the second device. For example, in the case where the second device includes a user plane device, the receiver of the first request can include a control plane device and / or the user plane device. Among them, the user plane device can send the first information to the first device based on the first request. The control plane device can perform other operations related to data plane device discovery based on the first request (e.g., can include the process of discovering a third device described later).

[0110] In some embodiments, the first request can include information related to the requested data plane device. For example, the first request can be used to indicate which condition or conditions need to be met by the data plane device requested by the first device to be discovered.

[0111] Optionally, the first request can include one or more of the following: a fully qualified domain name (FQDN) corresponding to the requested data plane device, a data network name (DNN) corresponding to the requested data plane device, single-network slice selection assistance information (S-NSSAI) corresponding to the requested data plane device, and a network function type corresponding to the requested data plane device.

[0112] The FQDN corresponding to the data plane device can be used to represent the organization that owns or manages the data plane device. For example, the FQDN corresponding to the data plane device can indicate the operator to which the data plane device belongs. For another example, the FQDN corresponding to the data plane device can indicate the manufacturer to which the data plane device belongs. For example, the first request can indicate that the FQDN corresponding to the requested data plane device is OPPO. The format of this FQDN can be DP.OPPO.COM, for example.

[0113] In some embodiments, the FQDN corresponding to the data plane device requested by the first device can be pre-configured on the first device. Alternatively, in the case that the first device comprises a terminal device, the network device can send the FQDN to the terminal device after the terminal device makes a registration request to the network.

[0114] The first request indicates the FQDN corresponding to the requested data plane device, which can enable the first device to request a data plane device that meets its needs. Illustratively, the FQDN corresponding to the data plane device capable of serving the first device indicated by the first information needs to be consistent with the FQDN corresponding to the data plane device requested in the first request.

[0115] The first request can include capability information of the first device for discovering the data plane device. Based on the capability information, the data plane device can be discovered through a discovery method that meets the capability of the first device. For example, the first request can include one or more of a first capability and a second capability. The first capability can be used to indicate whether the first device is capable of discovering the data plane device based on the user plane. The second capability can be used to indicate whether the first device is capable of discovering the data plane device based on the control plane.

[0116] As one possible implementation, if the first device is capable of discovering the data plane device based on the user plane, the first request can include a user plane query indication. The user plane query indication can indicate that the first device requests to discover the data plane device based on the user plane, i.e., the first device requests to perform a data plane device discovery process based on the user plane.

[0117] As one possible implementation, if the first device is capable of discovering the data plane device based on the control plane, the first request can include a control plane query indication. The control plane query indication can indicate that the first device requests to discover the data plane device based on the control plane, i.e., the first device requests to perform a data plane device discovery process based on the control plane.

[0118] In some embodiments, the first request can include an identity of the first device. The identity of the first device can indicate that the first request is for requesting a data plane device capable of serving which device.

[0119] In some embodiments, the first request can include a location of the first device. Based on the location of the first device, a data plane device close to the location of the first device can be discovered.

[0120] In some embodiments, the first request can comprise information of the third device. For example, the first request can comprise one or more of an identity, an address, etc. of the third device. The third device can be used to assist in discovering a data plane device capable of serving the first device. Based on the information of the third device, the second device receiving the first request can determine through which third device to obtain the data plane device capable of serving the first device.

[0121] In some embodiments, the first request can be carried in a connection establishment request message.

[0122] Optionally, the connection establishment request message can comprise a connection establishment request for a data plane. Correspondingly, the first information can be carried in a connection establishment request reply for a data plane. In this case, the first device can obtain the first information, i.e. complete the discovery of the data plane device, in the connection establishment procedure for a data plane. It can be appreciated that in this scheme, the data plane connection establishment procedure is multiplexed, i.e. the data plane device is discovered, so that the interaction between the first device and the second device can be reduced to a certain extent.

[0123] For ease of understanding, the following will be described taking the embodiment shown in FIG. 5 as an example. In FIG. 5, the first device can comprise a terminal device, and the second device can comprise a control plane device. As shown in FIG. 5, in step S510, the terminal device sends a data plane connection establishment request message (i.e. a connection establishment request for a data plane) to the control plane device. The connection establishment request in step S510 can comprise a specific DNN and S-NSSAI to identify that the connection establishment request is for establishing a connection dedicated to a data plane. The data plane connection establishment request message can comprise the first request. The data plane connection establishment request message can comprise the FQDN of the requested data plane device and a control plane query indication. For example, the request carries one or more of the following: an indication of the second capability, the FQDN corresponding to the requested data device, the DNN and the S-NSSAI.

[0124] Optionally, the connection establishment request message can comprise a general connection establishment request. That is, the connection establishment request can not be for a data plane. In this case, the connection establishment request can carry multiple FQDNs. The multiple FQDNs can correspond to data plane devices capable of or about to be requested by the first device.

[0125] In the case where the first request is carried in the connection establishment request message, the receiver of the first request can comprise the control plane device. The control plane device can feed back the first information to the first device as the second device, or the control plane device can perform other operations related to data plane device discovery (e.g. can comprise the process of discovering the third device described later) based on the first request.

[0126] For ease of understanding, the following will be described in conjunction with FIG. 6. In FIG. 5, the first device can include a terminal device, and the second device can include a UPF. In step S601, the terminal device sends a connection establishment request to the control plane device. The connection establishment request is not necessarily for the data plane. The connection establishment request message can include the FQDN of the requested data plane device and a user plane query indication. The connection establishment request in step S601 can include a first request. Based on the first request, the control plane device can perform steps S602-S605 (which will be described in detail later).

[0127] In some embodiments, the first request can be carried in a data packet of the user plane. The address of the first device indicated by the first request can be indicated by the source address of the data packet. The address of the third device indicated by the first request can be indicated by the destination address of the data packet. The content of the data packet can include a DNS query message. The DNS query message can include the identifier of the terminal device and the FQDN of the requested data plane device.

[0128] Continuing to refer to FIG. 6, in step S606, the terminal device can send DNS query information to the UPF. The DNS query information can include the first request. The DNS query information can be used to request to discover the IP address of the data plane device, and is contained in a data packet. In step S611, the UPF can send a DNS query message reply to the terminal device to reply to the DNS query information in step S606. The DNS query message reply can include first information, for example, including the IP address of the data plane device capable of serving the terminal device. The DNS query message reply can be contained in a data packet.

[0129] It should be noted that the connection establishment request message in step S601 can carry multiple FQDNs. Therefore, in step S606, the terminal device has established a connection, and can perform discovery of the data plane devices corresponding to multiple FQDNs through the same user plane connection.

[0130] In some embodiments, the first request can be carried in a network element discovery request message sent to the NRF. In some embodiments, the first information can be carried in a network element discovery response message sent by the NRF.

[0131] For example, the interface of the first device can support a service-based architecture (SBA), and the first device can interact with the NRF. For another example, the interface of the access network device can support the SBA, and the access network device can interact with the NRF. In the above cases, the second device can include the NRF. For this case, the first request can be carried in a network element discovery request message sent to the NRF; and / or the first information can be carried in a network element discovery response request message sent by the NRF.

[0132] By SBA of the interface between the first device and the access network device, it is realized that the first device can discover the data plane device through the NRF like other core network elements, which not only saves signaling, but also is simpler in logic.

[0133] The network element discovery request message carrying the first request can include a data plane network element discovery request message. Correspondingly, the first information can be carried in a data plane network element discovery response message. The data plane network element discovery request message is represented as Nnrf_NFDiscovery_Request message for example. The NF type that the Nnrf_NFDiscovery_Request message can include can be the type of the data plane network element (for example, DPAC), so as to request discovery of the data plane network element. The data plane network element discovery response message can be represented as Nnrf_NFDiscovery_Response message for example. The Nnrf_NFDiscovery_Response message can include the address of the data plane device or the identification of the instance of the data plane device. The following is described in combination with the embodiment shown in FIG. 7.

[0134] The method shown in FIG. 7 can be performed by the RAN and the NRF (that is, including steps S731 and S741), and / or the method shown in FIG. 7 can be performed by the terminal device and the NRF (that is, including steps S732 and S742). As shown in FIG. 7, the interface between the terminal device and the RAN supports SBA.

[0135] In step S731, the RAN sends an Nnrf_NFDiscovery_Request message to the NRF to request discovery of a DPAC capable of serving the RAN.

[0136] In step S741, the NRF sends an Nnrf_NFDiscovery_Response message to the RAN to feed back the DPAC capable of serving the RAN.

[0137] In step S732, the UE sends an Nnrf_NFDiscovery_Request message to the NRF to request discovery of a DPAC capable of serving the UE.

[0138] In step S742, the NRF sends an Nnrf_NFDiscovery_Response message to the UE to feed back the DPAC capable of serving the UE.

[0139] As described above, the access network device can forward the first information sent by the core network device to the first device. Correspondingly, the access network device can receive the first request sent by the first device and forward the first request to the second device.

[0140] The access network device can forward the first information and / or the first request through an RRC message. For example, the terminal device can send an RRC message to the access network device to send the first request. The RRC message can carry a NAS DM container. The NAS DM container can include the first request. Illustratively, the NAS DM container parameters can include one or more of the following: ID of the terminal device, location of the terminal device, DNN, S-NSSAI, NR type (e.g., DPAC), service operation, etc. As another example, the access network device can send an RRC message to the terminal device to send the first information. The RRC message can carry a NAS DM container. The NAS DM container can include the first information. The following is described with reference to FIG. 8.

[0141] The method shown in FIG. 8 can be performed by a UE, a RAN, and a NRF.

[0142] As shown in FIG. 8, at step S830, the UE sends an RRC message to the RAN, which can include a NAS DM container, and the NAS DM container includes a DPAC discovery request, the parameters can be UE ID, location of the UE, DNN, S-NSSAI, NF type (DPAC), service operation.

[0143] At step S840, the RAN invokes a service operation of the NRF through a service interface, i.e., sends an Nnrf_NFDiscovery_Request to the NRF. The UE's DPAC discovery request is passed to the NRF.

[0144] At step S850, the NRF determines the eligible DPACs according to the parameters in step S840 and the parameters of the stored DPAC profiles, and sends the information of the DPACs to the RAN through an Nnrf_NFDiscovery_Response. The DPAC information is the IP address of the DPAC or the instance ID of the DPAC.

[0145] At step S860, the RAN sends an RRC message to the UE. The RRC message carries a NAS DM container, and the NAS DM container includes a DPAC discovery request reply, the parameters are the IP address of the DPAC or the instance ID of the DPAC.

[0146] In order for the NRF to determine the data plane device serving the first device, the present application provides a data plane device registration method shown in FIG. 9. FIG. 9 is a schematic flowchart of another wireless communication method provided by the embodiments of the present application. The method shown in FIG. 9 can be performed by a data plane device and an NRF.

[0147] The method shown in FIG. 9 can include step S910.

[0148] In step S910, the data plane device sends registration information to the NRF. The registration information is used to register the data plane device to the NRF. The registration information can be carried in the profile of the data plane device.

[0149] The registration information can include one or more of the following: a service area of the data plane device, a network function type corresponding to the data plane device, an address of the data plane device, an FQDN corresponding to the data plane device, an instance identifier of the data plane device, a service operation supported by the data plane device, a DNN supported by the data plane device, and an S-NSSI supported by the data plane device.

[0150] By way of example, the service operation supported by the data plane device can include one or more of the following: data storage, data retrieval, data plane access authentication, and the like.

[0151] The network function type can be used to indicate the type of the data plane device. For example, the network function type can indicate that the type of the data plane device is DPAC.

[0152] The NRF can authorize the registration information of the data plane device and mark the data plane device as valid, i.e., the corresponding network element is a valid network element.

[0153] In some embodiments, the NRF can send a registration acceptance message to the data plane device. The registration acceptance message can be used to indicate that the NRF marks the data plane device as valid, or the NRF authorizes the registration information of the data plane device.

[0154] In the case where the NRF marks a certain data plane device as valid, other devices can discover the data plane device through the NRF. In other words, in the case where the second device includes the NRF, the data plane device capable of serving the first device fed back by the first information must be a data plane device marked as valid by the NRF. If the data plane device fails to register with the NRF or does not register with the NRF, the NRF cannot feed back that the data plane device is capable of serving the first device, i.e., the first device will not be able to discover the data plane device, and the first information cannot indicate the data plane device.

[0155] With reference back to FIG. 7 or FIG. 8. In step S710 or step S810, the DPAC can register to the NRF, and the DPAC profile can be carried in the registration message, and the DPAC profile can include one or more of the service area of the DPAC, the NF type, the DPAC IP address, the FQDN corresponding to the DPAC, the DPAC instance ID, the service operation supported by the DPAC, the DNN supported by the DPAC, and the S-NSSAI. The service operation can include, for example, data storage, data retrieval, data plane access authentication, etc. In step S720 or S820, the NRF can authorize the registration request of the DPAC, mark the DPAC as a valid network element, and send a registration acceptance message to the DPAC.

[0156] The above describes a technical solution for the first device to discover the data plane device based on the NRF. The following describes a solution for the first device to discover the data plane device based on the third device.

[0157] The third device can assist the first device to discover the data plane device capable of serving the first device. For example, the third device can be used to obtain the address of the data plane device capable of serving the first device from the target DNS server. The network element corresponding to the third device can be referred to as a data plane discovery function (DPDF).

[0158] In some embodiments, the control plane device can determine a suitable third device according to the situation of the first device, i.e., discover the third device. For example, the control plane device can determine the third device according to the location of the first device and / or the information carried in the first request.

[0159] The third device can register to the NRF for subsequent discovery by the control plane device. For example, the third device can send one or more of the address of the third device, the instance identifier of the third device, the FQDN supported by the third device, the DNN, and the S-NSSAI to the NRF for registration. The NRF can store the corresponding NF profile. The NF profile of the third device can include one or more of the address of the third device, the instance identifier of the third device, the FQDN supported by the third device, the DNN, and the S-NSSAI.

[0160] After the third device registers to the NRF, the third device can be discovered based on the NRF. For example, the control plane device can send the information carried in the first request and / or the location of the first device to the NRF to discover the third device that meets the conditions. The NRF can feed back the address and / or instance identifier of the third device that meets the conditions to the control plane device.

[0161] The third device and the second device can perform the method shown in FIG. 10 to discover, by the third device, a data plane device capable of serving the first device.

[0162] The method shown in FIG. 10 can include step S1010. In step S1010, the third device receives first query information sent by the second device.

[0163] The first query information can be used to request querying a data plane device capable of serving the first device. For example, the first query information can be used to request querying an address of a data plane device capable of serving the first device. It can be understood that through the first query information, the second device can request the third device to assist the second device to obtain the address of the data plane device.

[0164] Optionally, the first query information can be carried in a DNS query request message. The DNS query request message can be used to request the third device to query the address of the data plane device on a target DNS server.

[0165] The target DNS server can be used to query the address of the data plane device capable of serving the first device. The target DNS server can be a DNS server closer to the terminal device. In the case where the target DNS server is a DNS server closer to the terminal device, the target DNS server can also be referred to as a local DNS server.

[0166] The control plane device can determine the target DNS server. For example, the control plane device can determine a DNS server closer to the location of the first device as the target DNS server according to the location of the first device. The location of the first device can be determined by a tracking area identity (TAI). After determining the target DNS server, the control plane device can send information of the target DNS server to other devices (such as the first device, the third device, etc.).

[0167] In some embodiments, the first query information can include one or more of the following: a FQDN corresponding to the requested data plane device; a DNN corresponding to the requested data plane device; an S-NSSAI corresponding to the requested data plane device; a location of the first device; an identifier of the first device; an address of the target DNS server.

[0168] The third device can send the second query information to the target DNS server to request querying an address of a data plane device capable of serving the first device. In a case where the first query information comprises the address of the target DNS server, the third device can determine the target DNS server according to the first query information and send the second query information. In a case where the first query information does not comprise the address of the target DNS server, the third device can determine the target DNS server according to the relevant information (e.g., third information described below) of the DNS server stored by the third device.

[0169] It should be noted that the location information of the first device can be provided by the first request or provided by other manners. For example, the first device can provide the location information of the first device in a network registration process, and thus the network can obtain the location information of the first device before receiving the first request.

[0170] In some embodiments, in response to receiving the first request, the second device can send the first query information to the third device. The first query information can be determined based on the first request.

[0171] In some embodiments, in a case where the second device comprises a control plane device, the second device can indicate the address of the target DNS server in the first query information. With reference to FIG. 5, at step S530, the control plane device as the second device can send the address of the target DNS server to the DPDF in a DNS query request.

[0172] In some embodiments, the control plane device can send third information to the third device. For example, in response to receiving the first request, the control plane device can send the third information to the third device. The third information is used to indicate a correspondence between one or more DNS servers and one or more first devices. The DNS server corresponding to the first device can be the target DNS server.

[0173] It should be noted that the correspondence between the DNS server and the first device can be one-to-one, one-to-many, many-to-one or many-to-many. That is, one DNS server can correspond to one first device, or one DNS server can correspond to multiple first devices, or multiple DNS servers can correspond to one first device, or multiple DNS servers can correspond to multiple first devices.

[0174] The third information can be determined by the control plane device. For example, in a case where the first device discovers the data plane device based on the user plane device, the user plane device can be difficult to determine the target DNS server, and thus the third device can determine the target DNS server according to the third information and send the second query information to the target DNS server.

[0175] In response to receiving the third information, the third device can feed back to the control plane device. For example, the third information can be carried in a DNS context setup request message. After receiving the DNS context setup request message, the third device can send a DNS context setup reply message to indicate whether the third information is received and / or recorded by the third device.

[0176] Optionally, the third information may, for example, include one or more of the following: an identifier of the first device, an address of the first device, a DNS processing rule. The DNS processing rule can be used to indicate a correspondence between one or more DNS servers and one or more first devices. Based on the DNS processing rule, when the third device receives the first query information, it can determine which DNS server to send the second query information to (i.e., a determination rule of the target DNS server). Taking the first device including a terminal device as an example, the DNS processing rule can include the information in Table 1.

[0177] Table 1

[0178] Based on the indication of Table 1, a correspondence between the UE ID or the UE IP address and the IP address of the target DNS server can be determined. It should be noted that Table 1 is only an example. The second row of Table 1 exemplarily shows a correspondence between one UE ID or one UE IP address and one IP address of the target DNS server. The correspondence in Table 1 can also include one or more of the following: a correspondence between one UE ID or one UE IP address and multiple target DNS addresses; a correspondence between multiple UE IDs or multiple UE IP addresses and one target DNS address; a correspondence between multiple UE IDs or multiple UE IP addresses and multiple target DNS addresses.

[0179] In some embodiments, the third device can determine the target DNS server based on the information of the first device and the third information. For example, based on the correspondence between the terminal device and the DNS server in Table 1 and the ID or IP of the terminal device, it can be determined that the terminal device can request which target DNS server or servers to obtain the address of the data plane device.

[0180] Continuing to refer to FIG. 6. In step S603, in response to receiving the connection setup request in step S601, the control plane device sends a DNS context setup request to the DPDF. The DNS context setup request can include the content shown in Table 1. In step S604, in response to receiving the DNS context setup request, the DPDF sends a DNS context setup reply to the control plane device to reply that it has received and recorded the content of Table 1.

[0181] The target DNS server can feed back the fourth information to the third device. The fourth information can be used to indicate the address of the data plane device determined by the target DNS server to serve the first device. Illustratively, the address of the data plane device fed back by the DNS can be the address of the data plane device closest to the first device. For example, the address of the data plane device and the first device have some same IP fields, thereby identifying that both are in the same area.

[0182] The third device can send the second information to the second device. The second information can be used to indicate the address of the data plane device capable of serving the first device. Wherein, the second information can be determined based on the fourth information.

[0183] The second device can feed back the first information to the first device, which can be determined based on the second information.

[0184] In order to facilitate understanding of the present application, the following will be described in detail in combination with FIG. 5 and FIG. 6.

[0185] The embodiment shown in FIG. 5 is an example diagram of a DPAC discovery process based on a control plane. The first device includes a UE. The second device includes a control plane device. The third device includes a DPDF.

[0186] The DPAC discovery process shown in FIG. 5 can include steps S510-S570.

[0187] Step S510, the UE sends a connection establishment request for a data plane to a control plane network element (for example, SMF). The request can include a specific DNN and S-NSSAI for the data plane, to indicate that the connection request is to establish a connection dedicated to the access user plane. The request carries a second capability indication. The second capability indication is the capability of the UE to perform DPAC discovery based on the control plane. In addition, the request can carry the FQDN, DNN and S-NSSAI of the data plane.

[0188] Step S520, the control plane network element discovers the DPDF according to the location of the UE, for example, TAI, and the FQDN and DNN-SNSSAI carried in the request of step S510.

[0189] The main function of the DPDF is to assist the UE to discover the DPAC IP address. The location information of the UE can be provided by the UE in step S510. Alternatively, the location information of the UE can be provided by the UE in the previous registration process to the network, that is, the network can have the location information of the UE related before step S510.

[0190] It should be noted that in this step, the DPDF has registered its information in the NRF, and the NRF can store the corresponding NF profile of the DPDF. The corresponding NF profile of the DPDF can include one or more of the following: DPDF IP address, DPDF instance ID, FQDN supported by the DPDF, DNN and S-NSSAI. Therefore, after receiving the request of the UE, the control plane network element can send a discovery request to the NRF according to the FQDN, DNN and S-NSSAI carried in the request, so as to discover the DPDF meeting the condition. The NRF can return the DPDF IP address and instance ID meeting the condition to the SMF.

[0191] In step S530, the control plane network element sends a UE DNS query request to the selected DPDF. The request includes the UE IP address, UE ID, FQDN and IP address of the local DNS server. The local DNS server is the IP address of the DNS server determined by the control plane network element according to the UE location.

[0192] In step S540, the DPDF receives the query request and sends a DNS query request to the local DNS server according to the IP address of the local DNS server in the request. The DNS query request includes the UE IP address and FQDN.

[0193] In step S550, the DNS server returns an IP address of a DPAC according to the UE IP address and FQDN. The IP address of the DPAC is the nearest IP address to the UE. For example, the DPAC and the UE have some same IP fields, indicating that they are in the same area.

[0194] In step S560, the DPDF returns the IP address of the DPAC to the control plane network element. The message carries the UE ID, UE IP address and DPAC IP address.

[0195] In step S570, the control plane network element sends a connection establishment receiving message to the UE. The message carries the UE ID, UE IP address and IP address of the DPAC.

[0196] The embodiment shown in FIG. 6 is an example diagram of a user plane-based data plane device discovery process. In FIG. 6, the first device includes a UE. The second device includes a UPF, and the third device includes a DPDF. The method shown in FIG. 6 can include steps S601-S611.

[0197] Step S601, the UE sends a connection establishment request to a control plane network element (for example, SMF). The request is a general request, which can not be a connection establishment request for the data plane. The first capability is carried in the request. The first capability indicates the capability of the UE to discover the DPAC based on the user plane. The FQDN, DNN and S-NSSAI of the data plane are carried in the request.

[0198] Step S602, similar to step S520, the control plane network element determines the IP address of the DPDF.

[0199] Step S603, in order to realize the IP address query of the DPCA based on the user plane, the control plane network element sends a DNS query context establishment request to the DPDF. The request includes the UE ID, the UE IP address and the DNS message processing rule. The DNS processing rule is that when the DPDF receives the DNS query request related to the UE, it needs to send the query request to which local DNS server. The DNS message processing rule can be as shown in Table 1.

[0200] Step S604, the DPDF sends a DNS context establishment reply to the control plane network element.

[0201] Step S605, the control plane network element sends the IP address of the DPDF to the UE through the connection establishment receiving reply.

[0202] Step S606, the UE sends a DNS query request to the DPDF through the UPF, taking the IP address of the DPDF as the address of the DNS server. The source address of the data packet sent to the user plane by the UE is the IP address of the UE, and the destination address is the IP address of the DPDF. The content of the data packet includes the DNS query message, which includes the UE ID and the FQDN.

[0203] Step S607, after receiving the data packet, the UPF forwards the data packet to the DPDF according to the destination address.

[0204] Steps S608-S609, the DPDF determines the IP address of the local DNS server according to the DNS message processing rule configured in advance.

[0205] Steps S610-S611, the DPDF sends the IP address of the DPAC to the UE through the UPF.

[0206] It should be noted that the communication network to which the present application is applicable can be a communication network in the related art or a future communication network (for example, a 6G network). The node capable of accessing the network can be a terminal device, a base station, a core network element or a third party server.

[0207] It should be noted that the present application does not limit the data service performed by the terminal device and the data plane. For example, the data service performed by the two can be applied to various services of the future communication system.

[0208] The method embodiments of the present application are described in detail above, and the device embodiments of the present application are described in detail below. 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.

[0209] FIG. 11 is a schematic structural diagram of a communication device 1100 provided by an embodiment of the present application. The communication device 1100 can include a first receiving unit 1110.

[0210] The first receiving unit 1110 can be configured to receive first information sent by a second device; wherein the first information is used to indicate information of a data plane device capable of serving the first device.

[0211] In some embodiments, the information of the data plane device includes one or more of the following: an address of the data plane device; an instance identifier of the data plane device.

[0212] In some embodiments, the first information further includes one or more of the following: an identifier of the first device; an address of the first device.

[0213] In some embodiments, the communication device 1100 is further configured to: send a first request; wherein the first request is used to request to discover the data plane device.

[0214] In some embodiments, the first request includes one or more of the following: a FQDN corresponding to a requested data plane device; a DNN corresponding to the requested data plane device; an S-NSSAI corresponding to the requested data plane device; a location of the first device; an identifier of the first device; a network function type corresponding to the requested data plane device; a first capability used to indicate whether the first device is capable of discovering the data plane device based on a user plane device; a second capability used to indicate whether the first device is capable of discovering the data plane device based on a control plane device.

[0215] In some embodiments, the first request is carried in one or more of the following messages: a connection establishment request message; a network element discovery request message sent to a network repository function (NRF).

[0216] In some embodiments, the connection establishment request message includes a connection establishment request message for a data plane.

[0217] In some embodiments, the first device includes a terminal device.

[0218] In some embodiments, the second device comprises one or more of: an access network device, a control plane device, a user plane device.

[0219] In some embodiments, the second device comprises a NRF, and the interface of the first device supports a service-based architecture.

[0220] In optional embodiments, the first receiving unit 1110 can be a transceiver 1730. The communication device 1100 can further include a processor 1710 and a memory 1720, as shown in FIG. 17.

[0221] FIG. 12 is a schematic structural diagram of a communication device 1200 provided by an embodiment of the present application. The communication device 1200 can include a first sending unit 1210.

[0222] The first sending unit 1210 is configured to send first information; wherein the first information is used to indicate information of a data plane device capable of serving a first device.

[0223] In some embodiments, the information of the data plane device comprises one or more of: an address of the data plane device; an instance identifier of the data plane device.

[0224] In some embodiments, the first information further comprises one or more of: an identifier of the first device; an address of the first device.

[0225] In some embodiments, the communication device is further configured to: receive a first request sent by the first device; wherein the first request is used to request discovery of the data plane device.

[0226] In some embodiments, the first request comprises one or more of: a FQDN corresponding to a requested data plane device; a DNN corresponding to the requested data plane device; an S-NSSAI corresponding to the requested data plane device; a location of the first device; an identifier of the first device; a network function type corresponding to the requested data plane device; a first capability, used to indicate whether the first device is capable of discovering the data plane device based on a user plane device; a second capability, used to indicate whether the first device is capable of discovering the data plane device based on a control plane device.

[0227] In some embodiments, the first request is carried in one or more of: a connection establishment request message; a network element discovery request sent to a NRF.

[0228] In some embodiments, the connection establishment request message comprises a connection establishment request message for a data plane.

[0229] In some embodiments, the communication device is further configured to: in response to receiving the first request, send first query information to a third device, wherein the third device is configured to obtain the address of the data plane device from a target domain name system (DNS) server, and the first query information is used to request to query the address of the data plane device.

[0230] In some embodiments, the first query information comprises one or more of: a FQDN corresponding to the requested data plane device; a DNN corresponding to the requested data plane device; an S-NSSAI corresponding to the requested data plane device; a location of the first device; an identifier of the first device; an address of the target DNS server.

[0231] In some embodiments, the communication device is further configured to: receive second information sent by the third device, wherein the second information is used to indicate the address of the data plane device.

[0232] In some embodiments, the first information is determined based on the second information.

[0233] In some embodiments, the first device comprises a terminal device.

[0234] In some embodiments, the second device comprises one or more of: an access network device, a control plane device, and a user plane device.

[0235] In some embodiments, the second device comprises an NRF, and an interface of the first device supports a service-based architecture.

[0236] In some embodiments, the communication device is further configured to: receive registration information sent by the data plane device, wherein the registration information is used to register the data plane device to the NRF.

[0237] In some embodiments, the registration information comprises one or more of: a service area of the data plane device; a network function type corresponding to the data plane device; an address of the data plane device; a FQDN corresponding to the data plane device; an instance identifier of the data plane device; a service operation supported by the data plane device; a DNN supported by the data plane device; and an S-NSSAI supported by the data plane device.

[0238] In optional embodiments, the first sending unit 1210 can be a transceiver 1730. The communication device 1200 can further include a processor 1710 and a memory 1720, as shown in FIG. 17.

[0239] FIG. 13 is a schematic structural diagram of a communication device 1300 provided by an embodiment of the present application. The communication device 1300 is a data plane device, and the communication device 1300 can include a second sending unit 1310.

[0240] The second sending unit 1310 is configured to send registration information to an NRF, and the registration information is used to register the data plane device to the NRF.

[0241] In some embodiments, the registration information includes one or more of the following: a service area of the data plane device; a network function type corresponding to the data plane device; an address of the data plane device; an FQDN corresponding to the data plane device; an instance identifier of the data plane device; a service operation supported by the data plane device; a DNN supported by the data plane device; and an S-NSSAI supported by the data plane device.

[0242] In optional embodiments, the second sending unit 1310 can be a transceiver 1730. The communication device 1300 can further include a processor 1710 and a memory 1720, as shown in FIG. 17.

[0243] FIG. 14 is a schematic structural diagram of a communication device 1400 provided by an embodiment of the present application. The communication device 1400 is a control plane device, and the communication device 1400 can include a second receiving unit 1410.

[0244] The second receiving unit 1410 is configured to receive a first request, and the first request is used to request to discover a data plane device serving a first device.

[0245] In some embodiments, the first request includes one or more of the following: an FQDN corresponding to a requested data plane device; a DNN corresponding to the requested data plane device; an S-NSSAI corresponding to the requested data plane device; a location of the first device; an identifier of the first device; a network function type corresponding to the requested data plane device; a first capability indicating whether the first device is capable of discovering the data plane device based on a user plane device; and a second capability indicating whether the first device is capable of discovering the data plane device based on a control plane device.

[0246] In some embodiments, the communication device is further configured to: in response to receiving the first request, send third information to a third device, and the third device is used to obtain an address of the data plane device from a target domain name system (DNS) server, and the third information is used to indicate a correspondence between one or more DNS servers and one or more of the first devices.

[0247] In some embodiments, the third device is determined by the control plane device based on the first request.

[0248] In some embodiments, the communication device is further configured to: send fourth information; wherein the fourth information is used to indicate the third device determined by the control plane device.

[0249] In optional embodiments, the second receiving unit 1410 can be a transceiver 1730. The communication device 1400 can further include a processor 1710 and a memory 1720, as shown in FIG. 17.

[0250] FIG. 15 is a schematic structural diagram of a communication device 1500 provided by an embodiment of the present application. The communication device 1500 is a third device, and the communication device 1500 can include a third receiving unit 1510.

[0251] The third receiving unit 1510 is configured to receive first query information sent by a second device; wherein the third device is configured to obtain, from a target domain name system (DNS) server, an address of a data plane device capable of serving a first device, and the first query information is used to request to query the address of the data plane device.

[0252] In some embodiments, the first query information includes one or more of the following: a FQDN corresponding to a requested data plane device; a DNN corresponding to the requested data plane device; an S-NSSAI corresponding to the requested data plane device; a location of the first device; an identifier of the first device; and an address of the target DNS server.

[0253] In some embodiments, the communication device is further configured to: send second query information to the target DNS server; wherein the second query information is used to request the target DNS server to query the address of the data plane device capable of serving the first device.

[0254] In some embodiments, the communication device is further configured to: receive, by the third device, fourth information sent by the target DNS server; wherein the fourth information is used to indicate the address of the data plane device.

[0255] In some embodiments, the communication device is further configured to: send second information to the second device; wherein the second information is used to indicate the address of the data plane device, and the second information is determined based on the fourth information.

[0256] In some embodiments, the communication device is further configured to: receive third information sent by a control plane device; wherein the third information is used to indicate a correspondence between one or more DNS servers and one or more first devices.

[0257] In some embodiments, the communication device is further configured to determine the target DNS server based on the information of the first device and the third information.

[0258] In optional embodiments, the third receiving unit 1510 can be a transceiver 1730. The communication device 1500 can further include a processor 1710 and a memory 1720, as shown in FIG. 17.

[0259] FIG. 16 is a schematic structural diagram of a communication device 1600 according to an embodiment of the present application. The communication device 1600 is an access network device, and the communication device 1600 can include a fourth receiving unit 1610.

[0260] The fourth receiving unit 1610 is configured to receive first information sent by a second device, wherein the first information is used to indicate information of a data plane device capable of serving a first device and / or the access network device.

[0261] In some embodiments, the second device includes an NRF, and an interface of the access network device supports a service-based architecture.

[0262] In some embodiments, in a case where the first information is used to indicate information of a data plane device capable of serving the first device, the communication device is further configured to send the first information to the first device through a radio resource control (RRC) message.

[0263] In optional embodiments, the fourth receiving unit 1610 can be a transceiver 1730. The communication device 1600 can further include a processor 1710 and a memory 1720, as shown in FIG. 17.

[0264] FIG. 17 is a schematic structural diagram of an apparatus for communication 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 methods described in the above method embodiments. The apparatus 1700 can be a chip, a terminal device, or a network device.

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

[0266] The apparatus 1700 can also include one or more memories 1720. The memory 1720 stores a program that can be executed by the processor 1710, so that the processor 1710 performs the methods described in the foregoing method embodiments. The memory 1720 can be independent of the processor 1710 or integrated in the processor 1710.

[0267] The apparatus 1700 can also 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.

[0268] 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 or network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the terminal or network device in the various embodiments of the present application.

[0269] 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 or network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the terminal or network device in the various embodiments of the present application.

[0270] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or 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 or network device in the various embodiments of the present application.

[0271] It should be understood that the terms "system" and "network" can be used interchangeably in this application. In addition, the terms used in this application are only used to explain the specific embodiments of the application, and are not intended to limit the application. The terms "first", "second", "third", and "fourth" and the like in the specification and claims of the 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.

[0272] In embodiments of the present application, the term "indicate" can be direct indication or indirect indication, or can represent an associated relationship. For example, A indicates B, which can mean that B can be obtained through A; or A indirectly indicates B, for example, A indicates C, and B can be obtained through C; or A and B have an associated relationship.

[0273] In 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 determining 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.

[0274] In embodiments of the present application, the term "corresponding" can represent a direct or indirect corresponding relationship between the two, or can represent an associated relationship between the two, or can represent an indication and being indicated, configuration and being configured, and the like.

[0275] In embodiments of the present application, "predefined" or "preconfigured" can be implemented by pre-saving corresponding codes, tables or other information that can be used to indicate related information in devices (such as terminal devices and network devices), and the specific implementation manner is not limited in the present application. For example, predefinition can refer to definition in a protocol.

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

[0277] In embodiments of the present application, the term "and / or" is only used to describe the associated relationship between the associated objects, which means that there can be three relationships, for example, A and / or B, which can mean that A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in this paper generally represents an "or" relationship between the front and rear associated objects.

[0278] In the embodiments of the present application, the "comprising" can mean directly comprising or indirectly comprising. Alternatively, the "comprising" mentioned in the embodiments of the present application can be replaced by "indicating" or "for determining". For example, A comprising B can be replaced by A indicating B, or A for determining B.

[0279] In various embodiments of the present application, the size of the serial number of the above processes does not mean the order of execution, the execution order of each process 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.

[0280] In several embodiments provided by the present application, it should be understood that the disclosed system, device and method can be implemented by other means. For example, the above-described device embodiments are only illustrative, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, 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 displayed or discussed each other can be through some interface, device or unit indirectly coupled or communicated, which can be electrical, mechanical or other forms.

[0281] 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, that is, they can be located in one place, or can be distributed on multiple network units. According to actual needs, part or all of the units can be selected to achieve the purpose of the present embodiment.

[0282] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically independently, or two or more units can be integrated into one unit.

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

[0284] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered within 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, the method comprising: Comprising: A first device receives first information sent by a second device; Wherein, the first information is used to indicate information of a data plane device capable of serving the first device.

2. The method of claim 1, wherein, The information of the data plane device comprises one or more of: An address of the data plane device; An instance identifier of the data plane device.

3. The method according to claim 1 or 2, characterized in that, The first information further comprises one or more of: An identifier of the first device; An address of the first device.

4. The method according to any one of claims 1-3, characterized in that, The method further comprises: The first device sends a first request; Wherein, the first request is used to request discovery of the data plane device.

5. The method of claim 4, wherein, The first request comprises one or more of: A fully qualified domain name (FQDN) corresponding to the requested data plane device; A data network name (DNN) corresponding to the requested data plane device; Single network slice selection assistance information (S-NSSAI) corresponding to the requested data plane device; A location of the first device; An identifier of the first device; A network function type corresponding to the requested data plane device; A first capability indicating whether the first device is capable of discovering the data plane device based on a user plane device; A second capability indicating whether the first device is capable of discovering the data plane device based on a control plane device.

6. The method according to claim 4 or 5, characterized in that, The first request is carried in one or more of: A connection setup request message; A network element discovery request message sent to a network repository function (NRF).

7. The method of claim 6, wherein, The connection setup request message comprises a connection setup request message for a data plane.

8. The method according to any one of claims 1-7, characterized in that, The first device comprises a terminal device.

9. The method according to any one of claims 1-8, characterized in that, The second device comprises one or more of: an access network device, a control plane device, and a user plane device.

10. The method according to any one of claims 1-8, characterized in that, The second device comprises an NRF, and an interface of the first device supports a service-based architecture.

11. A method of wireless communication, the method comprising: Comprising: A second device sends first information; Wherein, the first information is used to indicate information of a data plane device capable of serving a first device.

12. The method of claim 11, wherein, The information of the data plane device comprises one or more of: An address of the data plane device; An instance identifier of the data plane device.

13. The method according to claim 11 or 12, characterized in that, The first information further comprises one or more of: An identifier of the first device; An address of the first device.

14. The method according to any one of claims 11-13, characterized in that, The method further comprises: The second device receives a first request sent by the first device; Wherein, the first request is used to request discovery of the data plane device.

15. The method of claim 14, wherein, The first request comprises one or more of: A fully qualified domain name (FQDN) corresponding to the requested data plane device; A data network name (DNN) corresponding to the requested data plane device; Single network slice selection assistance information (S-NSSAI) corresponding to the requested data plane device; A location of the first device; An identifier of the first device; A network function type corresponding to the requested data plane device; A first capability indicating whether the first device is capable of discovering the data plane device based on a user plane device; A second capability indicating whether the first device is capable of discovering the data plane device based on a control plane device.

16. The method according to claim 14 or 15, characterized in that The first request is carried in one or more of: A connection setup request message; A network element discovery request sent to an NRF.

17. The method of claim 16, wherein, The connection establishment request message includes a connection establishment request message for a data plane.

18. The method according to any one of claims 14-17, characterized by, The method further includes: In response to receiving the first request, the second device sends first query information to a third device; The third device is configured to obtain an address of the data plane device from a target domain name system (DNS) server, and the first query information is configured to request to query the address of the data plane device.

19. The method of claim 18, wherein, The first query information includes one or more of the following: a FQDN corresponding to the requested data plane device; a DNN corresponding to the requested data plane device; an S-NSSAI corresponding to the requested data plane device; a location of the first device; an identifier of the first device; an address of the target DNS server.

20. The method of claim 18 or 19, wherein, The method further includes: The second device receives second information sent by the third device; The second information is configured to indicate the address of the data plane device.

21. The method of claim 20, wherein, The first information is determined based on the second information.

22. The method of any one of claims 11-21, wherein, The first device includes a terminal device.

23. The method of any one of claims 11-22, wherein, The second device includes one or more of the following: an access network device, a control plane device, and a user plane device.

24. The method of any one of claims 11-17, wherein, The second device includes a network repository function (NRF), and an interface of the first device supports a service-based architecture.

25. The method of claim 24, wherein, The method further includes: The NRF receives registration information sent by the data plane device; The registration information is configured to register the data plane device to the NRF.

26. The method of claim 25, wherein, The registration information includes one or more of the following: a service area of the data plane device; a network function type corresponding to the data plane device; an address of the data plane device; a FQDN corresponding to the data plane device; an instance identifier of the data plane device; a service operation supported by the data plane device; a DNN supported by the data plane device; an S-NSSAI supported by the data plane device.

27. A method of wireless communication, the method comprising: The method includes: A data plane device sends registration information to a network repository function (NRF); The registration information is configured to register the data plane device to the NRF.

28. The method of claim 27, wherein, The registration information includes one or more of the following: a service area of the data plane device; a network function type corresponding to the data plane device; an address of the data plane device; a fully qualified domain name (FQDN) corresponding to the data plane device; an instance identifier of the data plane device; a service operation supported by the data plane device; a data network name (DNN) supported by the data plane device; a single network slice selection assistance information (S-NSSAI) supported by the data plane device.

29. A method of wireless communication, the method comprising: The method includes: A control plane device receives a first request; The first request is configured to request to discover a data plane device serving a first device.

30. The method of claim 29, wherein, The first request includes one or more of the following: a fully qualified domain name (FQDN) corresponding to a requested data plane device; a data network name (DNN) corresponding to the requested data plane device; a single network slice selection assistance information (S-NSSAI) corresponding to the requested data plane device; a location of the first device; an identifier of the first device; a network function type corresponding to the requested data plane device; A first capability indicating whether the first device is capable of discovering the data plane device based on a user plane device; A second capability indicating whether the first device is capable of discovering the data plane device based on a control plane device.

31. The method of claim 29 or 30, wherein, The method further includes: In response to receiving the first request, the control plane device sends third information to a third device; The third device is configured to obtain an address of the data plane device from a target domain name system (DNS) server, and the third information is configured to indicate a correspondence between one or more DNS servers and one or more first devices.

32. The method of claim 31, wherein, The third device is determined by the control plane device based on the first request.

33. The method of any one of claims 29-32, wherein, The method further includes: The control plane device sends fourth information; The fourth information is configured to indicate the third device determined by the control plane device.

34. A method of wireless communication, the method comprising: The method further includes: The third device receives first query information sent by a second device; The third device is configured to obtain an address of a data plane device capable of serving a first device from a target domain name system (DNS) server, and the first query information is configured to request to query the address of the data plane device.

35. The method of claim 34, wherein, The first query information includes one or more of the following: A full qualified domain name (FQDN) corresponding to a requested data plane device; A data network name (DNN) corresponding to the requested data plane device; Single network slice selection assistance information (S-NSSAI) corresponding to the requested data plane device; A location of the first device; An identifier of the first device; An address of the target DNS server.

36. The method of claim 34 or 35, wherein, The method further includes: The third device sends second query information to the target DNS server; The second query information is configured to request the target DNS server to query an address of a data plane device capable of serving a first device.

37. The method of any one of claims 34-36, wherein, The method further includes: The third device receives fourth information sent by the target DNS server; The fourth information is configured to indicate the address of the data plane device.

38. The method of any one of claims 34-37, wherein, The method further includes: The third device sends second information to the second device; The second information is configured to indicate the address of the data plane device, and the second information is determined based on the fourth information.

39. The method of any one of claims 34-38, wherein, The method further includes: The third device receives third information sent by a control plane device; The third information is configured to indicate a correspondence between one or more DNS servers and one or more first devices.

40. The method of claim 39, wherein, The method further includes: The third device determines the target DNS server based on information of the first device and the third information.

41. A method for wireless communication, comprising: The method further includes: An access network device receives first information sent by a second device; The first information is configured to indicate information of a data plane device capable of serving a first device and / or the access network device.

42. The method of claim 41, wherein, The second device includes a network repository function (NRF), and an interface of the access network device supports a service-based architecture.

43. The method of claim 41 or 42, wherein, In a case where the first information is configured to indicate information of a data plane device capable of serving the first device, the method further includes: The access network device sends the first information to the first device through a radio resource control (RRC) message.

44. A communications device, characterized by The communication device is a first device, and the communication device comprises: a first receiving unit configured to receive first information sent by a second device; wherein the first information is used to indicate information of a data plane device capable of serving the first device.

45. The communication device of claim 44, wherein, The information of the data plane device comprises one or more of the following: an address of the data plane device; an instance identifier of the data plane device.

46. The communication device of claim 44 or 45, wherein, The first information further comprises one or more of the following: an identifier of the first device; an address of the first device.

47. The communication device of any of claims 44-46, wherein, The communication device is further configured to: send a first request; wherein the first request is used to request discovery of the data plane device.

48. The communication device of claim 47, wherein, The first request comprises one or more of the following: a full qualified domain name (FQDN) corresponding to a requested data plane device; a data network name (DNN) corresponding to the requested data plane device; single network slice selection assistance information (S-NSSAI) corresponding to the requested data plane device; a location of the first device; an identifier of the first device; a network function type corresponding to the requested data plane device; a first capability used to indicate whether the first device is capable of discovering the data plane device based on a user plane device; a second capability used to indicate whether the first device is capable of discovering the data plane device based on a control plane device.

49. The communication device of claim 47 or 48, wherein, The first request is carried in one or more of the following messages: a connection establishment request message; a network element discovery request message sent to a network repository function (NRF).

50. The communication device of claim 49, wherein, The connection establishment request message comprises a connection establishment request message for a data plane.

51. The communication device of any of claims 44-50, wherein, The first device comprises a terminal device.

52. The communication device of any of claims 44-51, wherein, The second device comprises one or more of the following: an access network device, a control plane device, and a user plane device.

53. The communication device of any of claims 44-52, wherein, The second device comprises an NRF, and an interface of the first device supports a service-based architecture.

54. A communications device, characterized by The communication device is a second device, and the communication device comprises: a first sending unit configured to send first information; wherein the first information is used to indicate information of a data plane device capable of serving a first device.

55. The communication device of claim 54, wherein, The information of the data plane device comprises one or more of the following: an address of the data plane device; an instance identifier of the data plane device.

56. The communication device of claim 54 or 55, wherein, The first information further comprises one or more of the following: an identifier of the first device; an address of the first device.

57. The communication device of any of claims 54-56, wherein, The communication device is further configured to: receive a first request sent by the first device; wherein the first request is used to request discovery of the data plane device.

58. The communication device of claim 57, wherein, The first request comprises one or more of the following: a full qualified domain name (FQDN) corresponding to a requested data plane device; a data network name (DNN) corresponding to the requested data plane device; single network slice selection assistance information (S-NSSAI) corresponding to the requested data plane device; a location of the first device; an identifier of the first device; a network function type corresponding to the requested data plane device; a first capability used to indicate whether the first device is capable of discovering the data plane device based on a user plane device; a second capability used to indicate whether the first device is capable of discovering the data plane device based on a control plane device.

59. The communication device of claim 57 or 58, wherein, The first request is carried in one or more of the following messages: a connection establishment request message; a network element discovery request sent to the NRF.

60. The communication device of claim 59, wherein, The connection establishment request message includes a connection establishment request message for a data plane.

61. The communication device of any of claims 57-60, wherein, The communication device is further configured to in response to receiving the first request, send first query information to a third device; wherein the third device is configured to obtain an address of the data plane device from a target domain name system (DNS) server, and the first query information is used to request to query the address of the data plane device.

62. The communication device of claim 61, wherein, The first query information includes one or more of the following: a FQDN corresponding to the requested data plane device; a DNN corresponding to the requested data plane device; an S-NSSAI corresponding to the requested data plane device; a location of the first device; an identifier of the first device; an address of the target DNS server.

63. The communication device of claim 61 or 62, wherein, The communication device is further configured to: receive second information sent by the third device; wherein the second information is used to indicate the address of the data plane device.

64. The communication device of claim 63, wherein, The first information is determined based on the second information.

65. The communication device of any of claims 54-64, wherein, The first device includes a terminal device.

66. The communication device of any of claims 54-65, wherein, The second device includes one or more of the following: an access network device, a control plane device, and a user plane device.

67. The communication device of any of claims 54-60, wherein, The second device includes a network repository function (NRF), and an interface of the first device supports a service-based architecture.

68. The communication device of claim 67, wherein, The communication device is further configured to: receive registration information sent by the data plane device; wherein the registration information is used to register the data plane device to the NRF.

69. The communication device of claim 68, wherein, The registration information includes one or more of the following: a service area of the data plane device; a network function type corresponding to the data plane device; an address of the data plane device; a FQDN corresponding to the data plane device; an instance identifier of the data plane device; a service operation supported by the data plane device; a DNN supported by the data plane device; an S-NSSI supported by the data plane device.

70. A communications device, characterized by The communication device is a data plane device, and the communication device includes: a second sending unit configured to send registration information to a network repository function (NRF); wherein the registration information is used to register the data plane device to the NRF.

71. The communication device of claim 70, wherein, The registration information includes one or more of the following: a service area of the data plane device; a network function type corresponding to the data plane device; an address of the data plane device; a fully qualified domain name (FQDN) corresponding to the data plane device; an instance identifier of the data plane device; a service operation supported by the data plane device; a data network name (DNN) supported by the data plane device; a single network slice selection assistance information (S-NSSI) supported by the data plane device.

72. A wireless communication device, comprising: The communication device is a control plane device, and the communication device includes: a second receiving unit configured to receive a first request; wherein the first request is used to request to discover a data plane device serving a first device.

73. The communication device of claim 72, wherein, The first request includes one or more of the following: a fully qualified domain name (FQDN) corresponding to a requested data plane device; a data network name (DNN) corresponding to the requested data plane device; The requested data plane device corresponds to single network slice selection assistance information S-NSSAI; The location of the first device; The identity of the first device; The requested data plane device corresponds to a network function type; A first capability, used to indicate whether the first device can discover the data plane device based on a user plane device; A second capability, used to indicate whether the first device can discover the data plane device based on a control plane device.

74. The communication device of claim 72 or 73, wherein, The communication device is further configured to: In response to receiving the first request, send third information to a third device; The third device is used to obtain the address of the data plane device from a target domain name system DNS server, and the third information is used to indicate the correspondence between one or more DNS servers and one or more first devices.

75. The communication device of claim 74, wherein, The third device is determined by the control plane device based on the first request.

76. The communication device of any one of claims 72-75, wherein, The communication device is further configured to: Send fourth information; The fourth information is used to indicate the third device determined by the control plane device.

77. A communications device, characterized by The communication device is a third device, and the communication device comprises: A third receiving unit, configured to receive first query information sent by a second device; The third device is used to obtain the address of a data plane device capable of serving a first device from a target domain name system DNS server, and the first query information is used to request to query the address of the data plane device.

78. The communication device of claim 77, wherein, The first query information comprises one or more of the following: A full qualified domain name FQDN corresponding to the requested data plane device; A data network name DNN corresponding to the requested data plane device; Single network slice selection assistance information S-NSSAI corresponding to the requested data plane device; The location of the first device; The identity of the first device; The address of the target DNS server.

79. The communication device of claim 77 or 78, wherein, The communication device is further configured to: Send second query information to the target DNS server; The second query information is used to request the target DNS server to query the address of a data plane device capable of serving a first device.

80. The communication device of any of claims 77-79, wherein, The communication device is further configured to: The third device receives fourth information sent by the target DNS server; The fourth information is used to indicate the address of the data plane device.

81. The communication device of any of claims 77-80, wherein, The communication device is further configured to: Send second information to a second device; The second information is used to indicate the address of the data plane device, and the second information is determined based on the fourth information.

82. The communication device of any of claims 77-81, wherein, The communication device is further configured to: Receive third information sent by a control plane device; The third information is used to indicate the correspondence between one or more DNS servers and one or more first devices.

83. The communication device of claim 82, wherein, The communication device is further configured to: Determine the target DNS server based on the information of the first device and the third information.

84. A communications device, characterized by The communication device is an access network device, and the communication device comprises: A fourth receiving unit, configured to receive first information sent by a second device; The first information is used to indicate the information of a data plane device capable of serving a first device and / or the access network device.

85. The communication device of claim 84, wherein, The second device comprises a network repository function (NRF), and an interface of the access network device supports a service-based architecture.

86. The communication device of claim 84 or 85, wherein, In a case where the first information is used to indicate information of a data plane device capable of serving the first device, the communication device is further configured to: transmit the first information to the first device through a radio resource control (RRC) message.

87. A communications device, characterized by comprising a transceiver, a memory, and a processor, the memory being configured to store a program, the processor being configured to invoke the program in the memory and control the transceiver to receive or transmit a signal, so that the communication device performs the method according to any one of claims 1-43.

88. An apparatus comprising: comprising a processor configured to invoke a program in a memory, so that the apparatus performs the method according to any one of claims 1-43.

89. A chip, comprising: comprising a processor configured to invoke a program in a memory, so that the apparatus performs the method according to any one of claims 1-43.

90. A computer-readable storage medium, comprising: comprising a processor configured to invoke a program in a memory, so that the apparatus performs the method according to any one of claims 1-43.

91. A computer program product, characterized in that, comprising a processor configured to invoke a program in a memory, so that the apparatus performs the method according to any one of claims 1-43.

92. A computer program, characterized in that, comprising a processor configured to invoke a program in a memory, so that the apparatus performs the method according to any one of claims 1-43. comprising a processor configured to invoke a program in a memory, so that the apparatus performs the method according to any one of claims 1-43.

Images