WO2021042398A1

WO2021042398A1 - Communication method and apparatus, network device and terminal device

Info

Publication number: WO2021042398A1
Application number: PCT/CN2019/104806
Authority: WO
Inventors: 许阳
Original assignee: Oppo广东移动通信有限公司
Priority date: 2019-09-06
Filing date: 2019-09-06
Publication date: 2021-03-11
Also published as: CN114287142B; CN114287142A

Abstract

Embodiments of the present application provide a communication method and apparatus, a network device and a terminal device. The method comprises: a network element of a first core network sending first information to a terminal device, wherein the first information carries address information of at least one first server, and the address information of the at least one first server is used for data transmission between the terminal device and the at least one first server by means of a first session.

Description

Communication method and device, network equipment, terminal equipment

Technical field

The embodiments of the present application relate to the field of mobile communication technology, and specifically relate to a communication method and device, network equipment, and terminal equipment.

Background technique

The main function of Edge Computing (EC) is to offload data traffic to local servers. In order to realize the interaction between the terminal device and the local server, the terminal device needs to obtain the address of the local server first. At present, obtaining the address of the local server by the terminal device requires cumbersome interaction between the terminal device and the network side, which causes additional signaling overhead.

Summary of the invention

The embodiments of the present application provide a communication method and device, network equipment, and terminal equipment.

The communication method provided by the embodiment of the present application includes:

The first core network element sends first information to the terminal device, where the first information carries address information of at least one first server, and the address information of the at least one first server is used for the terminal device and the terminal device. At least one first server transmits data through a first session.

The terminal device receives the first information sent by the first core network element, where the first information carries address information of at least one first server, and the address information of the at least one first server is used by the terminal device and all The at least one first server transmits data through a first session.

The communication device provided by the embodiment of the present application includes:

The sending unit is configured to send first information to a terminal device, where the first information carries address information of at least one first server, and the address information of the at least one first server is used for the terminal device and the at least one A first server transmits data through the first session.

The receiving unit is configured to receive first information sent by a first core network element, where the first information carries address information of at least one first server, and the address information of the at least one first server is used for the terminal Data is transmitted between the device and the at least one first server through a first session.

The network device provided by the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the aforementioned communication method.

The terminal device provided in the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the aforementioned communication method.

The chip provided in the embodiment of the present application is used to implement the above-mentioned communication method.

Specifically, the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above-mentioned communication method.

The computer-readable storage medium provided by the embodiments of the present application is used to store a computer program, and the computer program enables a computer to execute the above-mentioned communication method.

The computer program product provided by the embodiments of the present application includes computer program instructions, and the computer program instructions cause a computer to execute the above-mentioned communication method.

The computer program provided in the embodiment of the present application, when it runs on a computer, causes the computer to execute the above-mentioned communication method.

Through the above technical solution, the work of obtaining the address of the first server is realized by the network element of the first core network, which prevents the terminal device from communicating with other servers to obtain the address of the first server, and saves signaling interaction. On the other hand, the technical solutions of the embodiments of the present application make full use of existing processes and mechanisms, have little impact on the existing network, and are easy to implement.

Description of the drawings

The drawings described here are used to provide a further understanding of the application and constitute a part of the application. The exemplary embodiments and descriptions of the application are used to explain the application, and do not constitute an improper limitation of the application. In the attached picture:

FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

Figure 2-1 is a schematic diagram of a coverage area corresponding to a local server provided by an embodiment of the present application;

Figure 2-2 is a first network architecture diagram provided by an embodiment of the present application;

Figure 2-3 is a second network architecture diagram provided by an embodiment of the present application;

FIG. 3 is a schematic flowchart of a communication method provided by an embodiment of this application;

FIG. 4 is a first flowchart of obtaining the address of an access server provided by an embodiment of the present application;

FIG. 5 is a second flowchart of obtaining the address of an access server according to an embodiment of the present application;

6 is a schematic diagram 1 of the structural composition of a communication device provided by an embodiment of the application;

FIG. 7 is a second schematic diagram of the structural composition of a communication device provided by an embodiment of this application;

FIG. 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a chip of an embodiment of the present application;

FIG. 10 is a schematic block diagram of a communication system provided by an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (Time Division Duplex) , TDD), system, 5G communication system or future communication system.

Exemplarily, the communication system 100 applied in the embodiment of the present application is shown in FIG. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or called a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminals located in the coverage area. Optionally, the network device 110 may be an evolved base station (Evolutional Node B, eNB, or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or The network equipment can be a mobile switching center, a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network side device in a 5G network, or a network device in a future communication system, etc.

The communication system 100 also includes at least one terminal 120 located within the coverage area of the network device 110. The "terminal" used here includes, but is not limited to, connection via a wired line, such as via a public switched telephone network (PSTN), digital subscriber line (Digital Subscriber Line, DSL), digital cable, and direct cable connection; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM Broadcast transmitter; and/or another terminal's device configured to receive/send communication signals; and/or Internet of Things (IoT) equipment. A terminal set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a "wireless terminal" or a "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio telephone transceivers Electronic device. Terminal can refer to access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user Device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks, or terminals in the future evolution of PLMN, etc.

Optionally, direct terminal connection (Device to Device, D2D) communication may be performed between the terminals 120.

Optionally, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.

FIG. 1 exemplarily shows one network device and two terminals. Optionally, the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminals. This embodiment of the present application There is no restriction on this.

Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.

It should be understood that the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 and a terminal 120 with communication functions, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here; communication The device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.

It should be understood that the terms "system" and "network" in this article are often used interchangeably in this article. The term "and/or" in this article is only an association relationship describing the associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, exist alone B these three situations. In addition, the character "/" in this text generally indicates that the associated objects before and after are in an "or" relationship.

In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the technical solutions related to the embodiments of the present application are described below.

Edge computing

A typical edge computing is Mobile Edge Computing (EMC). It should be noted that the edge computing involved in the embodiments of the present application is also applicable to mobile edge computing.

The main function of edge computing is to offload data traffic to a local server. Because the local server is close to the user, it has the characteristics of low data transmission delay and obvious bandwidth savings for wired networks. As shown in Figure 2-1, different areas can be covered by different local servers, for example, local server-1 covers area 1, local server-2 covers area 2, and local server-3 covers area 3. When the terminal device moves to a different area, it can access the local server corresponding to that area for some or all of the services. When the terminal device is not in a specific area (referring to the area covered by the local server), the terminal device can still access the remote server (that is, the non-local server).

For the coverage areas of different local servers in Figure 2-1, it can be considered that the data transmitted in each coverage area corresponds to a network slice, that is, the PDU session for data transmission in each area can be through at least S-NSSAI and/or DNN. Differentiated. Optionally, S-NSSAI is composed of slice/service type (Slice/Service Type, SST) and slice differential (Slice Differentiator, SD). Since they are both edge computing services, they correspond to areas 1, 2, and 3. The value of SST is the same, but the value of SD is different, and DNN can also be used to select the location of the egress gateway (ie, UPF).

It should be noted that the remote server is relative to the local server. The local server is used to process part or all of the services in a specific area, and after the terminal device moves out of the area covered by the local server, the part or all of the services The processing of the business needs to interact with the remote server. The remote server has no absolute relationship with the distance, but by contrast, the local server will be closer to the user in a specific area.

Figure 2-2 shows a network architecture through which the connection relationship between the local server and remote server and other network elements in the network can be determined. As shown in Figure 2-2, the network architecture involves The equipment includes: terminal equipment, base station, user plane function network element (User Plane Function, UPF), access and mobility management function network element (Access and Mobility Management Function, AMF), session management function network element (Session Management Function, SMF), Domain Name System (DNS). It can be seen that the local server and the remote server are respectively connected to two different UPFs. The terminal device can simultaneously establish a Protocol Data Unit (PDU) session with the remote server and a PDU session with the local server.

It should be noted that the local server involved in the embodiment of the present application may also be referred to as an access server or an EC server or an MEC server.

UE strategy

Figure 2-3 shows a 5G network architecture, as shown in Figure 2-3, the equipment involved in the 5G network architecture includes: UE, Radio Access Network (RAN), UPF, and data network (Data Network, DN), AMF, SMF, Policy Control Function (PCF), Application Function (AF), Authentication Server Function (AUSF), unified Data management network element (Unified Data Management, UDM). Among them, the network elements related to the strategy are mainly PCF, AMF, SMF, RAN, and UE. Among them, SMF is mainly responsible for the execution of policies related to the session, AMF is mainly responsible for the execution of policies related to access and UE policies, and the policy issuance and update on the two network elements (AMF and SMF) are all controlled by the PCF.

Specific to the UE policy, the PCF and the UE monitor the information related to the UE policy through a container (Container), including the content of the UE policy, the UE policy identifier, and so on. In the upstream direction, the container is sent by the UE to the AMF through NAS messages, and the AMF continues to transmit (not aware or modify) to the PCF. In the downstream direction, the PCF sends the container to the AMF, and the AMF then transmits through the NAS message. Pass to UE.

In order to be able to bind specific business data (or application data) to a specific PDU session for transmission (especially in the edge computing scenario, bind specific business data to the PDU session corresponding to the local server for transmission), Need to use UE strategy to achieve. The UE policy may be a UE Route Selection Policy (URSP), which is used to determine the binding relationship between service data and the PDU session, and also determines what PDU session the UE needs to establish to satisfy this binding relationship. The URSP strategy can be sent to the AMF via the container (Container) through the core network element PCF in Figure 2-2 and then transparently transmitted to the UE via the AMF, or it can be a strategy configured locally by the UE.

The URSP policy includes multiple policy rules (referred to as URSP Rules), and each URSP Rule is composed of a traffic descriptor (Traffic Descriptor) and a set of routing selectors (Route Selection Descriptor, RSD). The service descriptor in URSP is used to describe a specific service. For example, the microblog service can be described in the range of IP@1-9, and the IMS service can be described by IMS DNN. Then, there can be one or more RSDs under a service descriptor. The value of Single-Network Slice Selection Assistant Information (S-NSSAI) and the value of Data Network Name (DNN) in an RSD can be one or more. The values of other parameters are only Include one. Therefore, each RSD can correspond to one or more sets of parameter combinations. Each set of parameter combinations is used to define the characteristics of a PDU session. The service data corresponding to the service descriptor can be carried out in the PDU session corresponding to a certain set of parameter combinations of the RSD. transmission. When the service data described by the service descriptor appears, the UE can select a set of parameter combinations according to the corresponding RSD and initiate a PDU session establishment request. Each time the UE initiates a PDU session establishment request, it adds a set of parameter combinations to the request message. The related content of URSP is shown in Table 1 and Table 2. Table 1 is the content of URSP Rule, and Table 2 is the content of RSD:

Table 1

Table 2

The UE associates the application data (or service data) with the corresponding PDU session for transmission based on the URSP strategy. The mechanism is as follows:

When data appears at the application layer, the UE uses the URSP rule in the URSP policy to check whether the characteristics of the application data match the Traffic Descriptor of a rule in the URSP rule, and the viewing order is based on the priority in the Traffic Descriptor in the URSP rule (Precedence) to determine, that is, the UE sequentially checks the matching situation based on the order of priority. When a URSP rule is matched, the RSD list under the URSP rule is used to bind the PDU session.

The above process of finding a suitable PDU session for application data is called "evaluation", that is, finding or establishing a suitable PDU session binding. The RSD in the URSP rule used by the UE is considered to be a valid RSD only if the following conditions are met and used to perform the above evaluation process:

-If there is S-NSSAI in RSD, and S-NSSAI must belong to one of Allowed NSSAI (corresponding to non-roaming situation) or Mapping of Allowed NSSAI (corresponding to roaming situation);

-If there is a DNN in the RSD and it is a LADN DNN, the UE must be in the valid area corresponding to the LADN;

-If there is an access type preference (Access Type Prefrence) in the RSD and it is set to Multi-Access, the UE must support the ATSSS function;

-If there is a Timer Window and/or Location Criteria in the RSD, the UE must meet the required time and/or location conditions.

Otherwise, the UE will not use the RSD for data flow binding or PDU session establishment. Specifically, the UE only considers valid RSDs or ignores invalid RSDs. Based on this, the valid conditions of a specific PDU session and the service data that can be transmitted can be limited according to the URSP mechanism.

Based on Figure 2-2, in order for a terminal device to find the address of the local server, it usually needs to establish a connection with the remote server to interact with it, and then interact with the local server after obtaining the address of the local server. In this way, the terminal device needs to establish at least two PDU sessions, one for remote server interaction and one for local server interaction. This causes additional signaling overhead, especially in order to interact with the remote server to obtain the address of the local server, and it is very redundant for the terminal device to establish a PDU session corresponding to the remote server. For this reason, the technical solution of the embodiment of the present application proposes a solution for establishing only one PDU session and obtaining the address of the local server during the establishment or modification of the PDU session.

As shown in Figure 2-2, for specific business data (or application data), the terminal device can directly communicate with the local server, which helps to improve communication efficiency. In order to enable the terminal device to obtain the address of the local server during the establishment of a PDU session communicating with the local server, the following technical solutions of the embodiments of the present application are proposed.

FIG. 3 is a schematic flowchart of a communication method provided by an embodiment of the application. As shown in FIG. 3, the communication method includes the following steps:

Step 301: The first core network element sends first information to the terminal device, and the terminal device receives the first information sent by the first core network element, where the first information carries address information of at least one first server, so The address information of the at least one first server is used to transmit data between the terminal device and the at least one first server through a first session.

In an optional implementation manner of the present application, the network element of the first core network includes SMF and/or UPF.

In the embodiments of the present application, the realization of the first information can be but not limited to the following ways:

Manner 1: Implementation based on a UE Configuration Update (UCU) process. Specifically, the first information is carried in a downlink NAS message (that is, a UCU message) sent by the first core network element.

Further, optionally, the first information is carried in a first container, the first container is sent by the PCF to the AMF, and the AMF sends the first container to the terminal device through a downlink NAS message.

Manner 2: Implementation based on the session establishment or modification process. Specifically, the first information is carried in a first response message, and the first response message is the first core network element received by the first core network element sent by the terminal device. A response message after a request message, where the first request message is used to request the establishment or modification of the first session.

In an optional implementation manner of the present application, the first request message is a session establishment request message or a session modification request message.

In the embodiment of the present application, the first session is a session that needs to be established or modified. Optionally, the first session is a PDU session.

The content carried in the first request message is described below.

Optionally, the first request message carries a first session attribute parameter, and the first session attribute parameter is used for at least one of the following:

The network element of the first core network determines the service type;

Determining, by the first core network element, whether to obtain the address information of the at least one first server from a second server;

The first core network element determines the first route of the second server, and obtains the address information of the at least one first server from the second server according to the first route.

In an optional implementation manner, the first session attribute parameter includes at least one of the following: S-NSSAI, DNN.

Optionally, the first request message carries first indication information; the first indication information is used to indicate whether to request to obtain the address information of the first server.

In an optional implementation manner, the first indication information is carried in a first container, and the first container is carried in the first request message; the first core network element transfers the first container to Send (or transparently transmit) to the second server without any modification (or insensitivity).

Optionally, the first request message carries a first route identifier; the first route identifier is used by the first core network element to address a second server and obtain the at least one route from the second server Address information of the first server.

Optionally, the first request message carries at least one first service identifier; the at least one first service identifier is used by the first core network element to determine at least one service and obtain the at least one service from a second server Address information of at least one first server corresponding to one service.

In an optional implementation manner, the at least one first service identifier is carried in a first container; the first container is carried in the first request message; and the first core network element receives from the first container; After obtaining the first container in a request message, the first container is sent to the second server; the first core network element receives the second container sent by the second server, and the second The container carries address information of at least one first server corresponding to the at least one first service identifier; the first core network element carries the second container in the first response message and sends it to the terminal equipment.

In another optional implementation manner, after acquiring the at least one first service identifier from the first request message, the first core network element sends the at least one first service identifier to the first The second server, or generate at least one second service identifier based on the at least one first service identifier, and send the at least one second service identifier to the second server; the first core network element receives the The address information of the at least one first server corresponding to the at least one first service identifier sent by the second server; the first core network element carries the address information of the at least one first server in the first A response message is sent to the terminal device.

It should be noted that the content carried in the first request message may be any combination of the above content. The following describes the content carried in the first request message with several optional examples.

Example 1: The first request message carries the first session attribute parameter.

Example 2: The first request message carries a first session attribute parameter and at least one of the following: first indication information and a first route identifier.

Example 3: The first request message carries at least one first service identifier.

Example 4: The first request message carries at least one first service identifier and at least one of the following: first indication information and a first routing identifier.

The above examples are only examples, and the content carried in the first request message is not limited to the above examples, and may also be a combination of other content.

In the embodiment of the present application, the first core network element addresses the second server according to at least one of the following: a first route identifier, indication information from the second core network element, local configuration information, and at least one first A service identifier; and then obtain the address information of the at least one first server from the second server.

In an optional implementation manner of this application, the second server is a Dynamic Host Configuration Protocol (DHCP) server and/or a Domain Name System (DNS) server, and the second server may also It is called an external server.

During specific implementation, the network side may, but is not limited to, search for the address information of the first server (ie, local server, or access server, or EC server, or MEC server) for the terminal device in the following manner.

The task of triggering the search for the address of the first server can be executed by the first core network element (SMF or UPF) (which can happen without the container in the second mode), or by the second server (can be executed in the second mode). It can happen in the case of using the container), or the terminal can be executed through a user-plane PDU session (it can happen in the case of mode 1). The technical solution of the embodiment of the present application does not limit the method of finding the address of the first server. One possible search method is:

Taking the first core network element triggering the search for the address of the first server as an example, the first core network element queries the DHCP server (which may be the DHCP server in the second server) according to the parameters in the first request message to obtain the first If the domain name and/or address of the server is the obtained domain name of the first server, the DNS server may be further asked for the address (for example, IP address) of the first server. Here, the DHCP server and/or DNS service may all belong to the second server, that is, the second server may include two actually used servers.

Take the second server triggering the search for the address of the first server as an example. The search triggered by the second server is basically similar to the search triggered by the first core network element. The difference is that the DHCP server and/or DNS server can be a server other than the second server. .

Taking the terminal device triggering the search for the address of the first server as an example, the terminal device queries the second server according to the FQDN information in the first information, so as to obtain the address of the first server.

In the embodiment of the present application, the first response message is a response message for the first request message, and the first response message carries address information of at least one first server. For example, the first response message carries address information of one first server or address information of multiple first servers.

Further, optionally, the first server includes at least an edge computing server. Here, the edge computing server can also become a local server or an access server.

A) In an optional implementation manner of the present application, in the case of at least one service, the data stream of the at least one service is bound and transmitted on the first session; correspondingly, the address of the at least one first server The information is used by the terminal device to transmit the data stream of the at least one service bound on the first session to the at least one first server, and/or receive binding from the at least one first server The data flow of the at least one service on the first session. B) In another optional implementation manner of the present application, the first response message carries address information of a first server, and the address information of the first server is used by the terminal device to bind to the first server. Part or all of the data stream on a session is transmitted to the one first server, and/or part or all of the data stream bound on the first session is received from the one first server.

In an optional implementation manner of the present application, before the terminal device initiates session establishment or modification, the first core network element sends a first rule to the terminal device, and the terminal device receives the first core network element. The first rule for meta sending, the first rule is used by the terminal device to determine the content carried in the first request message; wherein, the first rule includes at least one of the following:

First indication information corresponding to at least one service identifier, where the first indication information is used to indicate whether to request to obtain address information of the first server;

A first session attribute parameter corresponding to at least one service identifier, where the first session attribute parameter is used to describe the first session.

For example: the first rule is a URSP rule; the service identifier is represented by a service descriptor in the URSP rule; the first indication information is carried in the RSD under the URSP rule; A session attribute parameter is carried in the RSD under the URSP rule. Further, optionally, the first rule further includes an effective condition, and the effective condition includes at least one of the following: effective time, effective duration, and effective area.

In the technical solution of the embodiment of the present application, when a terminal device needs to send a service data packet, if there is no corresponding PDU session to bind, it needs to create a new corresponding PDU session (whether there is a corresponding PDU session can be determined by URSP rules or local rules Judgment), the process of establishing a session can obtain its own address (that is, the session address, or the address of the terminal device). For this reason, the terminal device also requests the address of the access server corresponding to the service when establishing or modifying the session, so that the subsequent terminal device can directly communicate with the access server. After the session is successfully established, if the PDU session corresponding to other subsequent service data packets is also the session, the access server address can also be used to communicate with the access server.

The following describes the technical solutions of the embodiments of the present application with examples in conjunction with the interaction flowcharts shown in Figs. In Figures 4 and 5, SMF/UPF corresponds to the first core network element of the embodiment of this application, the external server corresponds to the second server (such as the DNS server) of the embodiment of this application, and the access server corresponds to the implementation of this application. Example of the first server (such as EC server, or application server, or local server). Among them, the external server is used to interact with the core network element (ie SMF/UPF) to obtain the address of the access server.

Referring to Fig. 4, Fig. 4 is the first flow chart of obtaining the address of the access server provided by an embodiment of the application. The flow includes the following steps:

Step 401: The terminal device sends a PDU session establishment or modification request message to the SMF/UPF. The PDU session establishment or modification request message carries the PDU session attribute parameter, and optionally carries the first indication information and/or the first route identifier.

Here, the PDU session attribute parameter is used to determine the first PDU session.

In an optional implementation manner, the PDU session establishment or modification request message only carries PDU session attribute parameters, and SMF/UPF can determine whether step 402 needs to be triggered according to the PDU session attribute parameters.

Here, the PDU session attribute parameter includes but is not limited to at least one of the following: S-NSSAI, DNN. It should be noted that the S-NSSAI and DNN itself are used to select the core network gateway, because a specific gateway corresponds to the access server, so it can be determined whether step 402 needs to be triggered according to the PDU session attribute parameters.

In another optional implementation manner, the PDU session establishment or modification request message not only carries the PDU session attribute parameter, but also carries the first indication information and/or the first route identifier.

Wherein, the first indication information is used to indicate whether to request to obtain the address information of the access server. For example, the first indication information is used to indicate that it is necessary to request to obtain the address information of the access server.

Wherein, the first routing identifier is used for the SMF/UPF to address the external server. Specifically, the first routing identifier is used to notify the SMF/UPF of the routing information of the external server, so that the SMF/UPF can be based on the first routing identifier. Find the corresponding external server, and ask the external server for the address information of the access server required by the terminal device. Optionally, the first route identifier may be a uniform resource locator (Uniform Resource Locators, URL), a server address, or the like. In addition, PDU session attribute parameters (such as DNN and/or S-NSSAI) may be used as the first route identifier.

It should be noted that the first indication information and the first routing identifier may not be carried in the PDU session establishment or modification request message, and the SMF/UPF may determine whether step 402 needs to be triggered according to the PDU session attribute parameters.

Optionally, in the case that the first indication information is carried in the PDU session establishment or modification request message, the terminal device may encapsulate the first indication information in a container, carry the container in the PDU session establishment or modification request message, and send it to SMF/UPF, SMF/UPF sends the container directly to the external server, that is, SMF/UPF does not perceive or process the container and directly transmits it to the external server.

Step 402: The SMF/UPF interacts with the external server according to the content carried in the PDU session establishment or modification request message to obtain the address information of the access server.

Specifically, SMF/UPF addresses the access server according to at least one of the following: PDU session attribute parameters, first route identifier, indication information of other network elements, local configuration information, interacts with external servers, and sends relevant information to external servers To get the address information of the access server.

Here, the interaction form between SMF/UPF and the external server is not specifically limited. Its purpose is to obtain the address information of the access server required by the terminal device from the external server, so that the terminal device can directly communicate with the access server through the user interface (such as with The access server establishes an HTTP connection for communication).

Here, the address information for accessing the server includes, but is not limited to, an IP address, a MAC address, and so on.

It should be noted that the SMF can contact the external server or the SMF informs the UPF to contact the external server, so as to obtain the address information of the access server.

Step 403: The SMF/UPF sends a PDU session establishment or modification response message to the terminal device. The PDU session establishment or modification response message carries the address information of the access server.

Here, the PDU session establishment or modification response message may carry address information of one access server, or may carry address information of multiple access servers. If the address information of an access server is carried, it means that all service data bound on the first PDU session needs to access the access server.

Optionally, the address information for accessing the server may be carried by a container, and the container is transparently transmitted to the terminal device through SMF/UPF, that is, the SMF/UPF does not perceive or modify the container. Further, if the external server receives a container (for example, the terminal device sends the container in step 401), the external server also replies to the container, and the SMF/UPF transparently transmits the container to the terminal device through a NAS message (specifically, a downlink NAS message).

Step 404: The terminal device transmits the data bound to the first PDU session between the user plane and the access server according to the address information of the access server.

Here, the terminal device establishes an HTTP connection with the access server according to the address information of the access server, and transmits the data bound to the first PDU session through the HTTP connection.

Specifically, during the establishment or modification of the PDU session, the terminal device can obtain the PDU session address (that is, the address of the terminal device), and at the same time can also obtain the address of the access server. In this way, the terminal device binds the service data to the first PDU session according to the UE local policy or the URSP policy. For the service data bound to the first PDU session, the terminal device uses the source address=PDU session for the data packets it sends Address, destination address = access server address; correspondingly, the data packet received by the terminal device should normally be source address = access server address, destination address = PDU session address. Considering security and other issues, if the source address of the data packet received by the terminal device is not the address of the access server, the terminal device can discard the data packet.

For the case where the first PDU session corresponds to an address for accessing the server, after completing the PDU session establishment or modification process through the above steps, the terminal device sets the target addresses of all service data bound to the first PDU session as the access server address.

In an optional implementation manner, in order for the terminal device to select appropriate PDU session attribute parameters, the terminal device receives the correspondence between the service identifier from the network side and the PDU session attribute parameters (that is, the first rule), as shown in Table 3 below :

table 3

The above-mentioned first rule can be implemented through the URSP rule. In actual deployment, for the services that need to access the local server, these services can be described by the Traffic Descriptor in the URSP rule, and the specific S-NSSAI is configured in the corresponding RSD And DNN, the S-NSSAI and DNN are used for the first PDU session of the local offload. In this way, after a service establishes the first PDU session for local offloading, if other service data appears, it can also be bound to the first PDU session according to the matched URSP rule, and then access the local server. The URSP rules and their corresponding RSDs are shown in Table 4 and Table 5 below. Among them, the Traffic Descriptor in the URSP rules can be used as a service identifier to describe service-related information. Optionally, the RSD can carry first indication information. An indication information is used to indicate whether to request to obtain the address information of the access server.

Table 4

table 5

Referring to FIG. 5, FIG. 5 is the second flowchart of obtaining the address of the access server according to an embodiment of the application. The process includes the following steps:

Step 501: The terminal device sends a PDU session establishment or modification request message to the SMF/UPF. The PDU session establishment or modification request message carries a service identifier, and optionally the first indication information and/or the first route identifier.

By default, the PDU session establishment or modification request message also carries PDU session attribute parameters. Here, the PDU session attribute parameters are used to determine the first PDU session.

In an optional implementation manner, the PDU session establishment or modification request message only carries a service identifier.

In another optional implementation manner, the PDU session establishment or modification request message not only carries the service identifier, but also carries the first indication information and/or the first route identifier.

Wherein, the service identifier is used to identify the service, and the SMF/UPF can know the address information of the access server corresponding to which service needs to be requested according to the service identifier. The form of the service identifier may be URL, domain name, IP address, application identifier (Application Id) defined within 3GPP, and so on. In addition, PDU session attribute parameters (such as DNN and/or S-NSSAI) can be used as the service identifier.

Wherein, the first routing identifier is used for the SMF/UPF to address the external server. Specifically, the first routing identifier is used to notify the SMF/UPF of the routing information of the external server, so that the SMF/UPF can be based on the first routing identifier. Find the corresponding external server, and ask the external server for the address information of the access server required by the terminal device. Optionally, the first route identification may be a URL, or a server address, or the like. In addition, PDU session attribute parameters (such as DNN and/or S-NSSAI) may be used as the first route identifier.

It should be noted that the first indication information and the first routing identifier may not be carried in the PDU session establishment or modification request message, and the SMF/UPF may determine whether step 502 needs to be triggered according to the PDU session attribute parameters.

Optionally, when the PDU session establishment or modification request message carries the service identifier and/or the first indication information, the terminal device may encapsulate the service identifier and/or the first indication information in a container, and carry the container in The PDU session establishment or modification request message is sent to the SMF/UPF, and the SMF/UPF sends the container directly to the external server, that is, the SMF/UPF does not perceive or process the container and directly transmits it to the external server.

Step 502: The SMF/UPF interacts with the external server according to the content carried in the PDU session establishment or modification request message to obtain the address information of the access server.

Specifically, SMF/UPF addresses the access server according to at least one of the following: PDU session attribute parameters, first route identifier, indication information of other network elements, local configuration information, interacts with external servers, and sends relevant information to external servers To get the address information of the access server. Not limited to this, SMF/UPF can also address the access server according to the service ID (it should be noted that the first routing ID is a more direct indication of the address of the external server, and the service ID can also be used to know the address of the external server. ).

Here, the form of interaction between SMF/UPF and the external server is not specifically limited, and its purpose is to obtain the address information of the access server required by the terminal device from the external server (that is, the address information of the access server corresponding to the service identifier indicated by the terminal device). Enable the terminal device to directly communicate with the access server through the user interface (for example, establish an HTTP connection with the access server for communication).

In an optional implementation manner, SMF/UPF can directly use the service ID sent by the terminal device to send the service ID to an external server to request the address information for accessing the server; or, SMF/UPF can be based on the service ID sent by the terminal device Generate a new service ID by itself (for example, generate a URL based on the Application ID sent by the terminal device), and send the new service ID to an external server to request access to the server's address information.

Step 503: The SMF/UPF sends a PDU session establishment or modification response message to the terminal device. The PDU session establishment or modification response message carries the address information of the access server.

Here, the PDU session establishment or modification response message may carry address information of one access server, or may carry address information of multiple access servers.

If the PDU session establishment or modification request message carries multiple service identifiers in step 501, the PDU session establishment or modification response message may carry the correspondence between the multiple service identifiers and the address information of multiple access servers; or, The PDU session establishment or modification response message carries the address information of an access server, which means that all service data bound on the first PDU session needs to access the access server.

Step 504: The terminal device transmits the data bound to the first PDU session between the user plane and the access server according to the address information of the access server.

In an optional implementation manner, in order for the terminal device to select a suitable service identifier and/or first indication information (the first indication information is used to indicate whether to request access to the server address information), the terminal device receives the information from the network side The corresponding relationship between the service identifier and the first indication information (that is, the first rule) is shown in Table 6 below:

Table 6

It should be noted that the PDU session attribute parameters involved in the embodiments of this application are not limited to S-NSSAI and/or DNN, and may also include SSC mode (SSC Mode), PDU session type (PDU Session Type), and non-seamless Offload indication (Non-Seamless Offload indication), access preference (Access Preference), etc.

The above-mentioned first rule can be implemented through the URSP rule. In actual deployment, for the services that need to access the server, these services can be described by the Traffic Descriptor in the URSP rule, and the specific S-NSSAI is configured in the corresponding RSD And DNN, the S-NSSAI and DNN are used for the first PDU session of the local offload. In this way, after a service establishes the first PDU session of the local offload, if other service data appears, it can also be bound to the first PDU session according to the matched URSP rule, and then access the access server. The URSP rules and their corresponding RSDs are shown in Table 7 and Table 8 below. Among them, the Traffic Descriptor in the URSP rule can be used as a service identifier to describe service-related information, and the RSD carries first indication information, and the first indication information is used for Indicates whether to request access to the server's address information.

Table 7

Table 8

In an optional implementation manner of the present application, the terminal device can obtain the address of the access server in the following manner: the network side sends a first message to the terminal device, the first message includes a first rule, and the first rule includes a service Identifies and corresponds to the address of the access server or the FQDN (or URL) information of the access server, as shown in Table 9 below. If the terminal device obtains the address of the access server, it means that all the data packets corresponding to the service identifier are sent to the server at that address; if the terminal device obtains the full domain name (Fully Qualified Domain Name, FQDN) of the access server , The terminal device uses the FQDN to interact with the second server to obtain the address of the access server, and then uses the address to communicate with the data packet corresponding to the service identifier.

业务标识Business identity	访问服务器的地址/FQDNAccess server address/FQDN	(可选)地点/时间(Optional) location/time
业务标识-1Business ID-1	IP地址-1IP address-1	区域-1Area-1
业务标识-2Business ID-2	IP地址-1IP address-1	区域-1Area-1
业务标识-3Business ID-3	FQDN-1FQDN-1	区域-1Area-1

Table 9

After establishing the PDU session, the terminal device obtains the address of the access server through the PDU session according to the FQDN information. Here, if the address of the access server already exists, the terminal device directly communicates with the access server according to the address of the access server. That is to say, the PDU session establishment or modification process does not need to be enhanced, but the terminal device itself directly communicates with the external server and/or the access server through the established PDU session.

In an implementation manner, the address or FQDN information of the access server is added to the RSD of the URSP rule, such as the RSD shown in Table 10 below, and the terminal device obtains the address or FQDN information of the access server by obtaining the URSP rule. The "service identifier" can correspond to the parameters in the Traffic Descriptor in the URSP rules.

Table 10

In an optional manner, the address/FQDN information of the access server can be sent to the terminal device through a NAS message triggered by the core network side. For example, the PCF triggers the UCU message to send the URSP rule containing the access server address/FQDN information to the terminal device. Here, the URSP rule is encapsulated in a container, and the container is sent by the PCF to the AMF, and the AMF sends the container to the terminal device through a downlink NAS message.

Further, optionally, in addition to the first rule indicating the address or FQDN of the access server, the first rule may also indicate the address or FQDN of the second server, and the terminal communicates with the second server according to the information to determine the address of the access server .

The technical solutions of the embodiments of this application can not only be applied to the scenario of obtaining the address of a local server (such as an EC server), but also can be used in other scenarios, that is, the terminal device can use the technical solutions of the embodiments of this application to discover any specific The address of the application server corresponding to the service.

The technical solution of the embodiment of the present application can be combined with a PDU session control related mechanism to control a terminal device to access a local server for a specific service in a specific area. For example, a mechanism (such as the LADN mechanism) is used to control the activation of the PDU session in a specific area (area covered by the local server) before the business can access the local server. When the terminal device moves out of a specific area, the original PDU session will be deactivated or deleted, and a new PDU session will be established to access the non-local server (that is, the remote server).

In the technical solution of the embodiment of the present application, the PDU session establishment or modification response sent by the network side to the terminal device may not only carry the address information of the access server, but also information such as the port number and protocol type of the access server.

The technical solutions of the embodiments of the present application can be used not only for communication with the access server under the 5G network, but also for communication with the access server under the 4G network.

FIG. 6 is a schematic diagram 1 of the structural composition of a communication device provided by an embodiment of the application. As shown in FIG. 6, the communication device includes:

The sending unit 601 is configured to send first information to a terminal device, where the first information carries address information of at least one first server, and the address information of the at least one first server is used for the terminal device and the At least one first server transmits data through a first session.

In an optional implementation manner, the first information is carried in a downlink NAS message sent by the first core network element.

In an optional implementation manner, the first information is carried in a first container, the first container is sent by the PCF to the AMF, and the AMF sends the first container to the terminal device through a downlink NAS message .

In an optional implementation manner, the first information is carried in a first response message, and the first response message is a response after the first core network element receives the first request message sent by the terminal device Message, the first request message is used to request the establishment or modification of the first session.

In an optional implementation manner, the first request message carries a first session attribute parameter, and the first session attribute parameter is used for at least one of the following:

The network element of the first core network determines the service type;

In an optional implementation manner, the first request message carries first indication information;

The first indication information is used to indicate whether to request to obtain the address information of the first server.

In an optional implementation manner, the first indication information is carried in a first container, and the first container is carried in the first request message;

The sending unit 601 is further configured to send the first container to the second server without any modification.

In an optional implementation manner, the first request message carries a first route identifier;

The first route identifier is used by the first core network element to address a second server and obtain address information of the at least one first server from the second server.

In an optional implementation manner, the first request message carries at least one first service identifier;

The at least one first service identifier is used by the first core network element to determine at least one service, and obtain address information of at least one first server corresponding to the at least one service from a second server.

In an optional implementation manner, the at least one first service identifier is carried in a first container; the first container is carried in the first request message;

The sending unit 601 is further configured to send the first container to the second server;

The device further includes: a receiving unit 602, configured to receive a second container sent by the second server, the second container carrying address information of at least one first server corresponding to the at least one first service identifier;

The sending unit 601 is further configured to carry the second container in the first response message and send it to the terminal device.

In an optional implementation manner, the sending unit 601 is further configured to send the at least one first service identifier to the second server, or generate at least one second service identifier based on the at least one first service identifier. A service identifier, and sending the at least one second service identifier to the second server;

The device further includes: a receiving unit 602, configured to receive address information of at least one first server corresponding to the at least one first service identifier sent by the second server;

The sending unit 601 is further configured to carry the address information of the at least one first server in the first response message and send it to the terminal device.

In an optional implementation manner, the data stream of the at least one service is bound and transmitted on the first session;

The use of the address information of the at least one first server to transmit data corresponding to the first session between the terminal device and the at least one first server includes:

The address information of the at least one first server is used by the terminal device to transmit the data stream of the at least one service bound to the first session to the at least one first server, and/or from all The at least one first server receives the data stream of the at least one service bound to the first session.

In an optional implementation manner, the first response message carries address information of a first server, and the address information of the first server is used for the part that the terminal device binds to the first session Or all data streams are transmitted to the one first server, and/or part or all of the data streams bound to the first session are received from the one first server.

In an optional embodiment, the device further includes:

The addressing unit (not shown in the figure) is used to address the second server according to at least one of the following: a first routing identifier, indication information from a second core network element, local configuration information, at least one first Business identity.

In an optional implementation manner, the sending unit 601 is further configured to send a first rule to the terminal device, where the first rule is used by the terminal device to determine the content carried in the first request message; Wherein, the first rule includes at least one of the following:

In an optional implementation manner, the first rule is a URSP rule;

The service identifier is represented by a service descriptor in the URSP rule;

The first indication information is carried in the RSD under the URSP rule;

The first session attribute parameter is carried in the RSD under the URSP rule.

In an optional implementation manner, the first rule further includes an effective condition, and the effective condition includes at least one of the following: effective time, effective duration, and effective area.

In an optional embodiment, the first server includes at least an edge computing server.

Those skilled in the art should understand that the relevant description of the foregoing communication device in the embodiment of the present application can be understood with reference to the relevant description of the communication method in the embodiment of the present application.

FIG. 7 is a second schematic diagram of the structural composition of a communication device provided by an embodiment of the application. As shown in FIG. 7, the communication device includes:

The receiving unit 701 is configured to receive first information sent by a first core network element, where the first information carries address information of at least one first server, and the address information of the at least one first server is used for the The terminal device and the at least one first server transmit data through a first session.

The first information is carried in a downlink NAS message sent by the first core network element.

The network element of the first core network determines the service type;

In an optional implementation manner, the first indication information is carried in a first container, and the first container is carried in the first request message.

The first response message carries a second container, and the second container carries address information of at least one first server corresponding to the at least one first service identifier.

In an optional implementation manner, the receiving unit 701 is further configured to receive a first rule sent by the first core network element, and the first rule is used by the terminal device to determine the first request message The content carried in; wherein, the first rule includes at least one of the following:

In an optional implementation manner, the first rule is a URSP rule;

The service identifier is represented by a service descriptor in the URSP rule;

The first indication information is carried in the RSD under the URSP rule;

FIG. 8 is a schematic structural diagram of a communication device 800 provided by an embodiment of the present application. The communication device may be a terminal device or a network device. The communication device 800 shown in FIG. 8 includes a processor 810, and the processor 810 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 8, the communication device 800 may further include a memory 820. The processor 810 may call and run a computer program from the memory 820 to implement the method in the embodiment of the present application.

The memory 820 may be a separate device independent of the processor 810, or may be integrated in the processor 810.

Optionally, as shown in FIG. 8, the communication device 800 may further include a transceiver 830, and the processor 810 may control the transceiver 830 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.

Wherein, the transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include an antenna, and the number of antennas may be one or more.

Optionally, the communication device 800 may specifically be a network device in an embodiment of the present application, and the communication device 800 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here. .

Optionally, the communication device 800 may specifically be a mobile terminal/terminal device of an embodiment of the application, and the communication device 800 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the application. For the sake of brevity , I won’t repeat it here.

FIG. 9 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 900 shown in FIG. 9 includes a processor 910. The processor 910 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 9, the chip 900 may further include a memory 920. The processor 910 can call and run a computer program from the memory 920 to implement the method in the embodiment of the present application.

The memory 920 may be a separate device independent of the processor 910, or may be integrated in the processor 910.

Optionally, the chip 900 may further include an input interface 930. The processor 910 can control the input interface 930 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.

Optionally, the chip 900 may further include an output interface 940. The processor 910 can control the output interface 940 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, details are not described herein again.

Optionally, the chip can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application. For the sake of brevity, here No longer.

It should be understood that the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip, etc.

FIG. 10 is a schematic block diagram of a communication system 1000 according to an embodiment of the present application. As shown in FIG. 10, the communication system 1000 includes a terminal device 1010 and a network device 1020.

Wherein, the terminal device 1010 can be used to implement the corresponding function implemented by the terminal device in the above method, and the network device 1020 can be used to implement the corresponding function implemented by the network device in the above method. For brevity, it will not be repeated here. .

It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (Random Access Memory, RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (Double Data Rate SDRAM, DDR SDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced SDRAM, ESDRAM), Synchronous Link Dynamic Random Access Memory (Synchlink DRAM, SLDRAM) ) And Direct Rambus RAM (DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

It should be understood that the foregoing memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.

The embodiment of the present application also provides a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium can be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application , For the sake of brevity, I won’t repeat it here.

The embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it is not here. Go into details again.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, For the sake of brevity, I will not repeat them here.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the network device in the embodiment of the present application. When the computer program runs on the computer, it causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity , I won’t repeat it here.

Optionally, the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application. When the computer program runs on the computer, the computer executes each method in the embodiment of the present application. For the sake of brevity, the corresponding process will not be repeated here.

A person of ordinary skill in the art may realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

A communication method, the method includes:

The first core network element sends first information to the terminal device, where the first information carries address information of at least one first server, and the address information of the at least one first server is used for the terminal device and the terminal device. At least one first server transmits data through a first session.
The method according to claim 1, wherein the first information is carried in a downlink NAS message sent by the network element of the first core network.
The method according to claim 2, wherein the first information is carried in a first container, the first container is sent to the AMF by the PCF, and the AMF sends the first container to the all through a downlink NAS message述terminal equipment.
The method according to claim 1, wherein the first information is carried in a first response message, and the first response message is a first request message sent by the terminal device received by the first core network element After the response message, the first request message is used to request the establishment or modification of the first session.
The method according to claim 4, wherein the first request message carries a first session attribute parameter, and the first session attribute parameter is used for at least one of the following:

The network element of the first core network determines the service type;

Determining, by the first core network element, whether to obtain the address information of the at least one first server from a second server;

The first core network element determines the first route of the second server, and obtains the address information of the at least one first server from the second server according to the first route.
The method according to claim 5, wherein the first session attribute parameter includes at least one of the following: single network slice selection auxiliary information S-NSSAI, data network name DNN.
The method according to any one of claims 4 to 6, wherein the first request message carries first indication information;

The first indication information is used to indicate whether to request to obtain the address information of the first server.
The method according to claim 7, wherein the first indication information is carried in a first container, and the first container is carried in the first request message; the method further comprises:

The first core network element sends the first container to the second server without any modification.
8. The method according to any one of claims 4 to 8, wherein the first request message carries a first routing identifier;

The first route identifier is used by the first core network element to address a second server and obtain address information of the at least one first server from the second server.
The method according to any one of claims 4 to 9, wherein the first request message carries at least one first service identifier;

The at least one first service identifier is used by the first core network element to determine at least one service, and obtain address information of at least one first server corresponding to the at least one service from a second server.
The method according to claim 10, wherein the at least one first service identifier is carried in a first container; the first container is carried in the first request message; and the method further comprises:

After obtaining the first container from the first request message, the first core network element sends the first container to the second server;

Receiving, by the first core network element, a second container sent by the second server, the second container carrying address information of at least one first server corresponding to the at least one first service identifier;

The first core network element carries the second container in the first response message and sends it to the terminal device.
The method according to claim 10, wherein the method further comprises:

After obtaining the at least one first service identifier from the first request message, the first core network element sends the at least one first service identifier to the second server, or based on the at least one One first service identifier generates at least one second service identifier, and the at least one second service identifier is sent to the second server;

Receiving, by the first core network element, the address information of at least one first server corresponding to the at least one first service identifier sent by the second server;

The first core network element carries the address information of the at least one first server in the first response message and sends it to the terminal device.
The method according to any one of claims 10 to 12, wherein the data stream of the at least one service is bound and transmitted on the first session;

The use of the address information of the at least one first server to transmit data corresponding to the first session between the terminal device and the at least one first server includes:

The address information of the at least one first server is used by the terminal device to transmit the data stream of the at least one service bound to the first session to the at least one first server, and/or from all The at least one first server receives the data stream of the at least one service bound to the first session.
The method according to any one of claims 10 to 12, wherein the first response message carries address information of a first server, and the address information of the first server is used by the terminal device to bind Part or all of the data stream on the first session is transmitted to the one first server, and/or part or all of the data stream bound on the first session is received from the one first server.
The method according to any one of claims 5 to 14, wherein the method further comprises:

The first core network element addresses the second server according to at least one of the following: a first route identifier, indication information from the second core network element, local configuration information, and at least one first service identifier.
The method according to any one of claims 4 to 15, wherein the method further comprises:

The first core network element sends a first rule to the terminal device, where the first rule is used by the terminal device to determine the content carried in the first request message; wherein, the first rule includes the following At least one of:

First indication information corresponding to at least one service identifier, where the first indication information is used to indicate whether to request to obtain address information of the first server;

A first session attribute parameter corresponding to at least one service identifier, where the first session attribute parameter is used to describe the first session.
The method according to claim 16, wherein the first rule is a URSP rule;

The service identifier is represented by a service descriptor in the URSP rule;

The first indication information is carried in the RSD under the URSP rule;

The first session attribute parameter is carried in the RSD under the URSP rule.
The method according to claim 16 or 17, wherein the first rule further includes an effective condition, and the effective condition includes at least one of the following: effective time, effective duration, and effective area.
The method according to any one of claims 1 to 18, wherein the first server includes at least an edge computing server.
A communication method, the method includes:

The terminal device receives the first information sent by the first core network element, where the first information carries address information of at least one first server, and the address information of the at least one first server is used by the terminal device and all The at least one first server transmits data through a first session.
The method according to claim 20, wherein the first information is carried in a downlink NAS message sent by the first core network element.
The method according to claim 21, wherein the first information is carried in a first container, and the first container is sent by the PCF to the AMF, and the AMF sends the first container to the all through a downlink NAS message.述terminal equipment.
The method according to claim 20, wherein the first information is carried in a first response message, and the first response message is a first request message sent by the terminal device received by the first core network element After the response message, the first request message is used to request the establishment or modification of the first session.
The method according to claim 23, wherein the first request message carries a first session attribute parameter, and the first session attribute parameter is used for at least one of the following:

The network element of the first core network determines the service type;

Determining, by the first core network element, whether to obtain the address information of the at least one first server from a second server;

The first core network element determines the first route of the second server, and obtains the address information of the at least one first server from the second server according to the first route.
The method according to claim 24, wherein the first session attribute parameter includes at least one of the following: S-NSSAI, DNN.
The method according to any one of claims 23 to 25, wherein the first request message carries first indication information;

The first indication information is used to indicate whether to request to obtain the address information of the first server.
The method according to claim 26, wherein the first indication information is carried in a first container, and the first container is carried in the first request message.
The method according to any one of claims 23 to 27, wherein the first request message carries a first routing identifier;

The first route identifier is used by the first core network element to address a second server and obtain address information of the at least one first server from the second server.
The method according to any one of claims 23 to 28, wherein the first request message carries at least one first service identifier;

The at least one first service identifier is used by the first core network element to determine at least one service, and obtain address information of at least one first server corresponding to the at least one service from a second server.
The method according to claim 29, wherein the at least one first service identifier is carried in a first container; the first container is carried in the first request message;

The first response message carries a second container, and the second container carries address information of at least one first server corresponding to the at least one first service identifier.
The method according to claim 29 or 30, wherein the data stream of the at least one service is bound for transmission on the first session;

The use of the address information of the at least one first server to transmit data corresponding to the first session between the terminal device and the at least one first server includes:

The address information of the at least one first server is used by the terminal device to transmit the data stream of the at least one service bound to the first session to the at least one first server, and/or from all The at least one first server receives the data stream of the at least one service bound to the first session.
The method according to claim 29 or 30, wherein the first response message carries address information of a first server, and the address information of the first server is used by the terminal device to bind to the first server. Part or all of the data stream on a session is transmitted to the one first server, and/or part or all of the data stream bound on the first session is received from the one first server.
The method according to any one of claims 23 to 32, wherein the method further comprises:

The terminal device receives a first rule sent by the first core network element, where the first rule is used by the terminal device to determine the content carried in the first request message; wherein, the first rule includes At least one of the following:

First indication information corresponding to at least one service identifier, where the first indication information is used to indicate whether to request to obtain address information of the first server;

A first session attribute parameter corresponding to at least one service identifier, where the first session attribute parameter is used to describe the first session.
The method according to claim 33, wherein the first rule is a URSP rule;

The service identifier is represented by a service descriptor in the URSP rule;

The first indication information is carried in the RSD under the URSP rule;

The first session attribute parameter is carried in the RSD under the URSP rule.
The method according to claim 33 or 34, wherein the first rule further includes an effective condition, and the effective condition includes at least one of the following: effective time, effective duration, and effective area.
The method according to any one of claims 20 to 35, wherein the first server includes at least an edge computing server.
A communication device, the device includes:

The sending unit is configured to send first information to a terminal device, where the first information carries address information of at least one first server, and the address information of the at least one first server is used for the terminal device and the at least one A first server transmits data through the first session.
The apparatus according to claim 37, wherein the first information is carried in a downlink NAS message sent by the first core network element.
The device according to claim 38, wherein the first information is carried in a first container, and the first container is sent by the PCF to the AMF, and the AMF sends the first container to the all through a downlink NAS message.述terminal equipment.
The apparatus according to claim 37, wherein the first information is carried in a first response message, and the first response message is a first request message sent by the terminal device received by the first core network element After the response message, the first request message is used to request the establishment or modification of the first session.
The apparatus according to claim 40, wherein the first request message carries a first session attribute parameter, and the first session attribute parameter is used for at least one of the following:

The network element of the first core network determines the service type;

Determining, by the first core network element, whether to obtain the address information of the at least one first server from a second server;

The first core network element determines the first route of the second server, and obtains the address information of the at least one first server from the second server according to the first route.
The apparatus according to claim 41, wherein the first session attribute parameter comprises at least one of the following: S-NSSAI, DNN.
The device according to any one of claims 40 to 42, wherein the first request message carries first indication information;

The first indication information is used to indicate whether to request to obtain the address information of the first server.
The apparatus according to claim 43, wherein the first indication information is carried in a first container, and the first container is carried in the first request message;

The sending unit is further configured to send the first container to the second server without any modification.
The device according to any one of claims 40 to 44, wherein the first request message carries a first routing identifier;

The first route identifier is used by the first core network element to address a second server and obtain address information of the at least one first server from the second server.
The apparatus according to any one of claims 40 to 45, wherein the first request message carries at least one first service identifier;

The at least one first service identifier is used by the first core network element to determine at least one service, and obtain address information of at least one first server corresponding to the at least one service from a second server.
The apparatus according to claim 46, wherein the at least one first service identifier is carried in a first container; the first container is carried in the first request message;

The sending unit is further configured to send the first container to the second server;

The device further includes: a receiving unit, configured to receive a second container sent by the second server, the second container carrying address information of at least one first server corresponding to the at least one first service identifier;

The sending unit is further configured to carry the second container in the first response message and send it to the terminal device.
The device of claim 46, wherein:

The sending unit is further configured to send the at least one first service identifier to the second server, or generate at least one second service identifier based on the at least one first service identifier, and send the at least one Sending the second service identifier to the second server;

The device further includes: a receiving unit configured to receive address information of at least one first server corresponding to the at least one first service identifier sent by the second server;

The sending unit is further configured to carry the address information of the at least one first server in the first response message and send it to the terminal device.
The apparatus according to any one of claims 46 to 48, wherein the data stream of the at least one service is bound and transmitted on the first session;

The use of the address information of the at least one first server to transmit data corresponding to the first session between the terminal device and the at least one first server includes:

The address information of the at least one first server is used by the terminal device to transmit the data stream of the at least one service bound to the first session to the at least one first server, and/or from all The at least one first server receives the data stream of the at least one service bound to the first session.
The apparatus according to any one of claims 46 to 48, wherein the first response message carries address information of a first server, and the address information of the first server is used by the terminal device to bind Part or all of the data stream on the first session is transmitted to the one first server, and/or part or all of the data stream bound on the first session is received from the one first server.
The device according to any one of claims 41 to 50, wherein the device further comprises:

The addressing unit is configured to address the second server according to at least one of the following: a first routing identifier, indication information from a network element of the second core network, local configuration information, and at least one first service identifier.
The apparatus according to any one of claims 40 to 51, wherein the sending unit is further configured to send a first rule to the terminal device, and the first rule is used by the terminal device to determine the first rule Content carried in a request message; wherein, the first rule includes at least one of the following:

First indication information corresponding to at least one service identifier, where the first indication information is used to indicate whether to request to obtain address information of the first server;

A first session attribute parameter corresponding to at least one service identifier, where the first session attribute parameter is used to describe the first session.
The device according to claim 52, wherein the first rule is a URSP rule;

The service identifier is represented by a service descriptor in the URSP rule;

The first indication information is carried in the RSD under the URSP rule;

The first session attribute parameter is carried in the RSD under the URSP rule.
The device according to claim 52 or 53, wherein the first rule further includes an effective condition, and the effective condition includes at least one of the following: effective time, effective duration, and effective area.
The apparatus according to any one of claims 37 to 54, wherein the first server includes at least an edge computing server.
A communication device, the device includes:

The receiving unit is configured to receive first information sent by a first core network element, where the first information carries address information of at least one first server, and the address information of the at least one first server is used for the terminal Data is transmitted between the device and the at least one first server through a first session.
The apparatus according to claim 56, wherein the first information is carried in a downlink NAS message sent by the network element of the first core network.
The apparatus according to claim 57, wherein the first information is carried in a first container, and the first container is sent to the AMF by the PCF, and the AMF sends the first container to the all through a downlink NAS message.述terminal equipment.
The apparatus according to claim 56, wherein the first information is carried in a first response message, and the first response message is a first request message sent by the terminal device received by the first core network element After the response message, the first request message is used to request the establishment or modification of the first session.
The apparatus according to claim 59, wherein the first request message carries a first session attribute parameter, and the first session attribute parameter is used for at least one of the following:

The network element of the first core network determines the service type;

Determining, by the first core network element, whether to obtain the address information of the at least one first server from a second server;

The first core network element determines the first route of the second server, and obtains the address information of the at least one first server from the second server according to the first route.
The apparatus according to claim 60, wherein the first session attribute parameter comprises at least one of the following: S-NSSAI, DNN.
The device according to any one of claims 59 to 61, wherein the first request message carries first indication information;

The first indication information is used to indicate whether to request to obtain the address information of the first server.
The apparatus according to claim 62, wherein the first indication information is carried in a first container, and the first container is carried in the first request message.
The device according to any one of claims 59 to 63, wherein the first request message carries a first routing identifier;

The first route identifier is used by the first core network element to address a second server and obtain address information of the at least one first server from the second server.
The apparatus according to any one of claims 59 to 64, wherein the first request message carries at least one first service identifier;

The at least one first service identifier is used by the first core network element to determine at least one service, and obtain address information of at least one first server corresponding to the at least one service from a second server.
The apparatus according to claim 65, wherein the at least one first service identifier is carried in a first container; the first container is carried in the first request message;

The first response message carries a second container, and the second container carries address information of at least one first server corresponding to the at least one first service identifier.
The device according to claim 65 or 66, wherein the data stream of the at least one service is bound and transmitted on the first session;

The use of the address information of the at least one first server to transmit data corresponding to the first session between the terminal device and the at least one first server includes:

The address information of the at least one first server is used by the terminal device to transmit the data stream of the at least one service bound to the first session to the at least one first server, and/or from all The at least one first server receives the data stream of the at least one service bound to the first session.
The apparatus according to claim 65 or 66, wherein the first response message carries address information of a first server, and the address information of the first server is used by the terminal device to bind to the first server. Part or all of the data stream on a session is transmitted to the one first server, and/or part or all of the data stream bound on the first session is received from the one first server.
The device according to any one of claims 59 to 68, wherein:

The receiving unit is further configured to receive a first rule sent by the first core network element, where the first rule is used by the terminal device to determine the content carried in the first request message; wherein, the The first rule includes at least one of the following:

First indication information corresponding to at least one service identifier, where the first indication information is used to indicate whether to request to obtain address information of the first server;

A first session attribute parameter corresponding to at least one service identifier, where the first session attribute parameter is used to describe the first session.
The device of claim 69, wherein the first rule is a URSP rule;

The service identifier is represented by a service descriptor in the URSP rule;

The first indication information is carried in the RSD under the URSP rule;

The first session attribute parameter is carried in the RSD under the URSP rule.
The device according to claim 69 or 70, wherein the first rule further includes an effective condition, and the effective condition includes at least one of the following: effective time, effective duration, and effective area.
The device according to any one of claims 56 to 71, wherein the first server includes at least an edge computing server.
A network device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 1 to 19 Methods.
A terminal device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 20 to 36 Methods.
A chip comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 19.
A chip comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 20 to 36.
A computer-readable storage medium for storing a computer program that enables a computer to execute the method according to any one of claims 1 to 19.
A computer-readable storage medium for storing a computer program that enables a computer to execute the method according to any one of claims 20 to 36.
A computer program product comprising computer program instructions that cause a computer to execute the method according to any one of claims 1 to 19.
A computer program product comprising computer program instructions that cause a computer to execute the method according to any one of claims 20 to 36.
A computer program that causes a computer to execute the method according to any one of claims 1 to 19.
A computer program that causes a computer to execute the method according to any one of claims 20 to 36.