CN109905894B

CN109905894B - Data processing method and network equipment

Info

Publication number: CN109905894B
Application number: CN201711296158.8A
Authority: CN
Inventors: 李小娟; 杨皓睿; 金辉; 欧阳国威; 窦凤辉
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-12-08
Filing date: 2017-12-08
Publication date: 2021-02-12
Anticipated expiration: 2037-12-08
Also published as: CN109905894A; WO2019109865A1

Abstract

The application discloses a data processing method and network equipment. Wherein, the method comprises the following steps: the network equipment receives data; the network equipment determines that the data is data of a session corresponding to a Local Area Data Network (LADN); the network equipment determines that the terminal moves out of the LADN service area, and discards the data; wherein, the terminal is in a radio resource connection inactive state RRC inactive state. By adopting the method and the device, the LADN data of the terminal leaving the LADN service area can be processed, and the system overhead can be reduced.

Description

Data processing method and network equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a data processing method and a network device.

Background

Radio Resource Control (RRC) inactive state (inactive state) means that an IDLE state (IDLE state) exists between a User Equipment (UE) and a base station, and a connected state (connected state) exists between the base station and a core network. In addition, with the development of wireless communication technology, a concept of Local Area Data Network (LADN), which is a Data Network that a UE can access only in a specific Area, i.e., a service Area, is introduced. That is, the UE can establish and use a Protocol Data Unit (PDU) session of DNN whose Data Network Name (DNN) is the LADN only when the UE is located within the service area of the LADN.

If the UE in the RRC inactive state moves away from the LADN service area, if there is downlink LADN data of the UE, the core network still sends the data to the base station where the UE resides before. After receiving the LADN data, the base station sends the data related to the LADN to the UE. The UE in the RRC inactive state will continue to receive the LADN data. However, the UE leaving the area served by the LADN cannot process the received LADN data, for example, the UE may present the LADN data, but the user clicks the content at the application level, and there is no reaction, which results in a poor experience for the user. Moreover, the LADN data that cannot be processed by these UEs is transmitted in the system, which also increases the system overhead.

Disclosure of Invention

The embodiment of the invention provides a data processing method and network equipment, which are beneficial to realizing the processing of the LADN data of the UE leaving the LADN service area and reducing the system overhead.

In a first aspect, an embodiment of the present invention provides a data processing method, including: the network equipment receives data; determining the data as the data of the session corresponding to the LADN; determining that the UE (also referred to as a terminal or other name) moves out of the LADN service area, the network device discarding the data; wherein, the UE is in an RRC inactive state (RRC inactive state). Optionally, the network device may be a UE, or may be a network side device such as a base station. The data is data from the application server, and specifically may be data sent by the application server through the network side, for example, the network device may receive data sent by the application server through a core network entity of the network side. Therefore, the method is beneficial to realizing the processing of the LADN data of the UE leaving the LADN service area and reducing the system overhead.

The method and the device for determining the data are not limited in the sequence of determining whether the data are the data of the session corresponding to the LADN and determining whether the UE moves out of the LADN service area, and when the data are the data of the session corresponding to the LADN and the UE moves out of the LADN service area, the network device can discard the data.

In one possible design, the UE may be connected with a first base station and the UE may also be connected with a second base station. Wherein, the first base station belongs to the LADN service area, and the second base station does not belong to the LADN service area; the first base station may be a base station corresponding to a network accessed by the UE before moving, and the second base station may be a base station corresponding to a network accessed by the UE after moving. That is, the UE is moving from a first base station to a second base station. Optionally, the first base station belonging to the LADN service Area may refer to that a Tracking Area identity (Tracking Area identity, abbreviated as TAI) of the first base station or a Tracking Area (Tracking Area, abbreviated as TA) corresponding to the first base station belongs to the LADN service Area, or that a cell of the first base station belongs to the LADN service Area. Correspondingly, that the second base station does not belong to the LADN service area may mean that the TAI of the second base station or the TA corresponding to the second base station does not belong to the LADN service area, or that the cell of the second base station does not belong to the LADN service area. There may be one or more cells under one base station, and the cells may belong to the same TA or different TAs.

In a possible design, the network device may be the UE, and the network device receives data, which may specifically be: and the UE receives data sent by the first base station through the second base station, wherein the data carries a first session identifier. The data may be sent to the first base station by a network side, such as a core network entity, so that the first base station can determine a session identifier corresponding to the data according to a channel of the data, that is, a first session identifier, and can send the data carrying the first session identifier to the second base station, and the second base station sends the data carrying the first session identifier to the UE.

In a possible design, the UE may store a second session identifier, where the second session identifier is a session identifier corresponding to the LADN. The determining, by the network device, that the data is data of a session corresponding to the LADN may specifically be: and when the first session identifier and the second session identifier are the same, the UE determines that the data is data of a session corresponding to the LADN. That is to say, the network device, such as the UE, may determine whether the data is data of a session corresponding to the LADN by determining whether a first session identifier corresponding to the received data is the same as a second session identifier corresponding to the stored LADN data, and may specifically determine that the data is data of a session corresponding to the LADN when the first session identifier is the same as the second session identifier.

In a possible design, the session identifier, such as the first session identifier and the second session identifier, may be a Data Network Name (DNN) or a session ID, and the like, and the present application is not limited thereto.

In a possible design, the network device may be a first base station, and the first base station is a base station accessed by the UE before moving, that is, a base station corresponding to the LADN service area, or referred to as that the first base station belongs to the LADN service area. Further, before the network device determines that the UE moves out of the LADN service area and the network device discards the data, the first base station may receive a first request message sent by the second base station, where the first request message may be sent by the second base station after receiving a second request message, and the second request message may be sent to the second base station after the UE receives paging requests of the first base station and the second base station. Wherein the second base station does not belong to the LADN service area, and the first request message may include an indication message, which may be used to indicate that the UE moves out of the LADN service area. The network device determines that the UE moves out of the LADN service area, which may specifically be: and the first base station determines that the UE moves out of the LADN service area according to the indication message.

In one possible design, the first request message further includes a second session identifier, where the second session identifier is a session identifier corresponding to the LADN. The determining, by the network device, that the data is data of a session corresponding to the LADN may specifically be: and when the first session identifier corresponding to the data is the same as the second session identifier, the first base station determines that the data is the data of the session corresponding to the LADN. The first session identifier may be determined by the first base station according to a channel for receiving the data, for example, the first session identifier may be a session identifier corresponding to a channel for transmitting the data by a network side, such as a core network entity.

In a possible design, the network device may be a second base station, where the second base station does not belong to the LADN service area, and the second base station is a base station corresponding to a network to which the UE is accessed after moving. Further, before the network device determines that the UE moves out of the LADN service area and the network device discards the data, the second base station may further receive a third request message sent by the UE, where the third request message may include an indication message, and the indication message may be used to indicate that the UE moves out of the LADN service area. Further, the determining, by the network device, that the UE moves out of the LADN service area may specifically be: and the second base station determines that the UE moves out of the LADN service area according to the indication message.

In one possible design, the third request message may include a second session identifier, where the second session identifier is a session identifier corresponding to the LADN. The determining, by the network device, that the data is data of a session corresponding to the LADN may specifically be: and when the first session identifier corresponding to the data is the same as the second session identifier, the second base station determines that the data is the data of the session corresponding to the LADN.

In a possible design, the data may be sent by a first base station to the second base station, where the data carries the first session identifier, the first base station is a base station corresponding to a network accessed by the UE before moving, and the first base station belongs to the LADN service area. Or, the data may be sent by the core network entity to the second base station, where the first session identifier is determined by the second base station according to a channel for receiving the data, and the second base station is a base station corresponding to a network accessed by the UE before and after moving, that is, the base stations accessed by the UE before and after moving are the same (for example, the first base station and the second base station are the same base station); at this time, the cells under the second base station may include cells belonging to the LADN service area and cells not belonging to the LADN service area.

In a possible design, the first Request message may include a user Context Retrieval Request, i.e., a UE Context Retrieval Request, such as a Retrieve UE Context Request or a UE Context Retrieval Request, and the second Request message and/or the third Request message may be an RRC message, such as an RRC message, an RRC connection response, an RRC response Request, or the like.

In a second aspect, an embodiment of the present invention further provides a network device, where the network device has a function of implementing the behavior of the network device in the foregoing method example. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more units or modules corresponding to the above functions. Optionally, the network device may be the UE, the first base station, or the second base station.

In one possible design, the network device may include a communication unit and a processing unit in a structure, and the processing unit is configured to support the network device to execute the corresponding functions in the method. The communication unit is used for supporting communication between the network equipment and other equipment. The network device may also include a storage unit, coupled to the processing unit, that stores program instructions (operating instructions) and data necessary for the network device. As an example, the processing unit may be a processor, the communication unit may be a transceiver, and the storage unit may be a memory.

In a third aspect, an embodiment of the present invention provides a communication system, where the system includes the user equipment, the first base station, the second base station, and/or the core network entity in the foregoing aspects. In another possible design, the system may further include other devices that interact with the above-described device in the solution provided by the embodiment of the present invention.

In a fourth aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the network device, which includes a program for executing the method according to the above aspects.

In a fifth aspect, the present invention provides a computer program, which comprises instructions that, when run on a computer, cause the computer to perform the method of the above aspects.

In a sixth aspect, the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the above aspects.

In a seventh aspect, the present application provides a chip system, which includes a processor for enabling a network device to implement the functions referred to in the above aspects, for example, to process data and/or information referred to in the above methods. In one possible design, the system-on-chip further includes a memory for storing program instructions and data necessary for the network device. The chip system may be formed by a chip, or may include a chip and other discrete devices.

In the technical scheme claimed in the application, when the UE in the RRC inactive state leaves the LADN service area and moves to a non-LADN service area, the network device may receive data from the network side, and then determine that the data belongs to the LADN data, and when determining that the UE leaves the LADN service area, the network device may directly discard the data, thereby implementing processing of the LADN data of the UE leaving the LADN service area, reducing system overhead, and enhancing user experience.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments or the background art of the present invention, the drawings required to be used in the embodiments or the background art of the present invention will be described below.

Fig. 1 is an application scenario diagram of a communication system according to an embodiment of the present invention;

FIG. 2 is an interaction diagram of a data processing method according to an embodiment of the present invention;

FIG. 3 is an interaction diagram of another data processing method according to an embodiment of the present invention;

FIG. 4 is an interaction diagram of another data processing method according to an embodiment of the present invention;

FIG. 5 is an interaction diagram of another data processing method according to an embodiment of the present invention;

FIG. 6 is an interaction diagram of another data processing method according to an embodiment of the present invention;

FIG. 7 is an interaction diagram of another data processing method according to an embodiment of the present invention;

fig. 8 is a schematic structural diagram of a network device according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of another network device provided in the embodiment of the present invention;

fig. 10 is a schematic structural diagram of another network device according to an embodiment of the present invention.

Detailed Description

The embodiments of the present invention will be described below with reference to the drawings.

It should be understood that the solution of the present application may be applied in particular to various communication networks, such as: global System for Mobile communications (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (Long Term Evolution, LTE) networks, etc., and with the continuous development of communication technology, the technical solution of the present application can also be used in future networks, such as 5G networks, also can be called New Radio (NR) networks, or can be used in device D2D (device) networks, device 2M (M2) networks, etc.

In this application, a network device may refer to an entity used to send or receive information, for example, it may be a user equipment, or it may be a base station, or it may be a Transmission Point (TP), a Transmission and Reception Point (TRP), a relay device, or other network devices with a function of a base station.

The core network entity referred to in this application may refer to a User plane network element, such as a User Port Function (UPF), or a User plane network element in a core network of another network, such as a future network, which is not limited in this application.

In the present application, a User Equipment (UE) is a device with communication function, which may also be referred to as a terminal, and may include a handheld device with wireless communication function, a vehicle-mounted device, a wearable device, a computing device or other processing device connected to a wireless modem, and the like. The user devices may be called different names in different networks, for example: a terminal, mobile station, subscriber unit, cellular telephone, personal digital assistant, wireless modem, wireless communication device, handheld device, laptop computer, cordless telephone, wireless local loop station, or the like. The user equipment may be a wireless terminal or a wired terminal. The wireless terminal may refer to a device that provides voice and/or data connectivity to a user, a handheld device having wireless connection capability, or other processing device connected to a wireless modem that may communicate with one or more core networks via a Radio Access Network (RAN).

In this application, a base station may also be referred to as a base station device, which is a device deployed in a radio access network to provide wireless communication functions. The names of the base stations may be different in different radio access systems, for example, the base station is called node B (NodeB) in a UMTS network, the base station is called evolved node B (evolved NodeB) in an LTE network, the base station is called TRP network node or G node B (G-NodeB, gNB) in a future 5G system, and so on, which are not listed here.

Referring to fig. 1, fig. 1 is a block diagram of a communication system according to an embodiment of the present invention. Specifically, as shown in fig. 1, the communication system may include a UE, a first base station, and a second base station. The UE may be connected to a first base station, the first base station belonging to the LADN service area. In addition, the UE may be connected to a second base station that does not belong to the LADN service area. The first base station may be a base station corresponding to a network, such as a RAN, to which the UE accesses before moving, or may be referred to as an "old RAN", or may be referred to as a "source base station", and so on; the second base station may be a base station corresponding to a network, such as a RAN, to which the UE accesses after moving, or may be referred to as a "new RAN", or may be referred to as a "target base station", and the like, which is not limited in this application. The first base station and the second base station may be the same base station or different base stations, for example, the UE moves from the first base station to the second base station. The first base station and the second base station may support an RRC inactive state, that is, the first base station and the second base station are base stations supporting the RRC inactive state. The UE may be a UE supporting an RRC inactive state, and the UE may be in the RRC inactive state while communicating with the first base station. In other words, the first base station and the second base station may enter the RRC inactive state before the UE moves, and may remain in the state after the UE moves. That is to say, the technical solution of the present application is applicable to a scenario in which the UE moves out of the LADN service area to another scenario not belonging to the LADN service area. The communication system may further include a core network entity, which may be a core network entity in a network accessed by the first base station, for example, it may be a UPF. Further, the communication system may further include AMF, SMF, and the like.

When information transmission is performed, since the UE is in an RRC inactive state, the LADN data sent by the network side may be transmitted in an area outside the LADN service area. That is, if the UE moves out of the LADN service area (e.g., LADN service area) of the first base station, the UE is still in the RRC inactive state, and if there is LADN data of the UE, the core network still sends the data to the first base station where the UE resides before. Therefore, the method and the device can process the LADN data by determining whether the UE moves out of the LADN service area, determining whether the received data belongs to the LADN data, and discarding the received data through the UE or the first base station or the second base station when the UE moves out of the LADN service area and the received data belongs to the LADN data.

In this application, that the first base station belongs to the LADN service area may mean that the TAI of the first base station or the TA corresponding to the first base station belongs to the LADN service area, or that the cell of the first base station belongs to the LADN service area. Correspondingly, that the second base station does not belong to the LADN service area may mean that the TAI of the second base station or the TA corresponding to the second base station does not belong to the LADN service area, or that the cell of the second base station does not belong to the LADN service area. There may be one or more cells under one base station, and the cells may belong to the same TA or different TAs.

In this application, the session identifier, such as the first session identifier and the second session identifier, may be a Data Network Name (abbreviated as DNN) or a session ID, and the application is not limited. The session ID may refer to a PDU session ID.

The application discloses a data processing method and network equipment, which are beneficial to realizing the processing of LADN data of UE leaving an LADN service area and reducing the system overhead. The details are described below.

Referring to fig. 2 in conjunction with fig. 1, fig. 2 is an interaction diagram of a data processing method according to an embodiment of the present invention. Specifically, as shown in fig. 2, the data processing method according to the embodiment of the present invention may include the following steps:

201. the network device receives the data.

Optionally, the network device may be a UE; or may be a base station corresponding to the LADN, that is, a base station before the UE moves, that is, a first base station; or may be the base station after the UE moves, i.e., the second base station. Specifically, the data is data from an application server, and the data may be transmitted through a network side, for example, the network device may receive data sent by the application server through a core network entity of the network side.

202. The network device determines that the data is data of a session corresponding to the LADN.

203. And the network equipment determines that the UE moves out of the LADN service area, and discards the data.

Specifically, when receiving data, the network device may determine whether the data is data of a session corresponding to a LADN, and after determining that the data is data of a session corresponding to the LADN, determine whether the UE moves out of a LADN service area (abbreviated as "LADN SA"), and discard the data when determining that the UE moves out of the LADN SA; if the data is determined not to be the data of the session corresponding to the LADN, the judgment or detection of whether the UE moves out of the LADN SA may not be performed. Or, the network device may respectively (simultaneously or non-simultaneously) determine whether the data is data of a session corresponding to a LADN and determine whether the UE moves out of the LADN SA, and may discard the data when determining that the data is data of a session corresponding to the LADN and when determining that the UE moves out of the LADN SA. Or, the network device may determine whether the UE moves out of the LADN SA, determine whether the data is data of a session corresponding to the LADN after determining that the UE moves out of the LADN SA, and discard the data when determining that the data is data of a session corresponding to the LADN. That is to say, the present application does not limit the sequence of determining whether the data is the data of the session corresponding to the LADN and determining whether the UE moves out of the LADN SA, and when the data is the data of the session corresponding to the LADN and the UE moves out of the LADN SA, the data may be discarded.

For example, optionally, the network device may be the UE, and the network device receives data, which may specifically be: and the UE receives data sent by the first base station through the second base station, wherein the data carries a first session identifier. The data may be sent to the first base station by a network side, such as a core network entity, so that the first base station can determine a session identifier corresponding to the data according to a channel of the data, that is, a first session identifier, and can send the data carrying the first session identifier to the second base station, and the second base station sends the data to the UE. It should be understood that the data forwarding process involved in the present application may vary in the header of the data packet in addition to carrying the data itself. For example, when the data received by the second base station and sent by the first base station is an IP data packet, the data sent by the second base station to the UE is still the data in the IP data packet, that is, the data sent by the first base station, and the data itself is not changed, but the packet header of the IP data packet sent by the second base station may be changed according to the difference of the base stations.

Further, a second session identifier may be stored in the UE, where the second session identifier is a session identifier corresponding to the LADN. The determining, by the network device, that the data is data of a session corresponding to the LADN may specifically be: and when the first session identifier and the second session identifier are the same, the UE determines that the data is data of a session corresponding to the LADN. That is, the network device, such as the UE, may determine whether the received data is data of a session corresponding to a LADN (abbreviated as "LADN data") by determining whether a first session identifier corresponding to the data is the same as a second session identifier corresponding to the stored LADN data, and may specifically determine that the data is the LADN data when the first session identifier is the same as the second session identifier; otherwise, if the first session identifier and the second session identifier are different, it may indicate that the data is not the LADN data. Optionally, the session identifier, such as the first session identifier and the second session identifier, may be a Data Network Name (abbreviated as DNN) or a session ID, and the session ID may refer to a PDU session ID.

Alternatively, the network device may be a first base station. Further, before the first base station determines that the UE moves out of the LADN service area and discards the data, the first base station may receive a first request message sent by the second base station, where the first request message may be sent by the second base station after receiving a second request message, the second request message may be sent to the second base station after receiving paging requests of the first base station and the second base station, and the first request message may include an indication message, where the indication message may be used to indicate that the UE moves out of the LADN service area. The network device determines that the UE moves out of the LADN service area, which may specifically be: and the first base station determines that the UE moves out of the LADN service area according to the indication message. Further optionally, the indication message may be a bit message, such as indicating whether the UE moves out of the LADN service area through 1bit, for example, "1" indicates that the UE moves out of the LADN service area, "0" indicates that the UE does not move out of the LADN service area, or vice versa; or, the indication message may be text information, and the UE may obtain whether the UE moves out of the LADN service area by analyzing the text information; alternatively, the indication message may also be generated and carried in the first request message only when the UE moves out of the LADN service area, and the like, which is not limited in this application.

Further, the first request message may further include a second session identifier, where the second session identifier is a session identifier corresponding to the LADN. The determining, by the network device, that the data is data of a session corresponding to the LADN may specifically be: and when the first session identifier corresponding to the data is the same as the second session identifier, the first base station determines that the data is the data of the session corresponding to the LADN. The first session identifier may be determined by the first base station according to a channel for receiving the data, for example, the first session identifier is a session identifier corresponding to a channel for transmitting the data by a network side, such as a core network entity.

Optionally, the network device may be a second base station. Further, before the second base station determines that the UE moves out of the LADN service area and discards the data, the second base station may further receive a third request message sent by the UE, where the third request message may include an indication message, and the indication message may be used to indicate that the UE moves out of the LADN service area. Further, the determining, by the network device, that the UE moves out of the LADN service area may specifically be: and the second base station determines that the UE moves out of the LADN service area according to the indication message. Further optionally, the indication message may be bit information, or may be text information, etc., which is not described herein; alternatively, the indication message may also be generated and carried in the third request message only when the UE moves out of the lan service area, and the like, which is not limited in this application.

Further, the third request message may include a second session identifier, where the second session identifier is a session identifier corresponding to the LADN. The determining, by the network device, that the data is data of a session corresponding to the LADN may specifically be: and when the first session identifier corresponding to the data is the same as the second session identifier, the second base station determines that the data is the data of the session corresponding to the LADN. The first session identifier may be determined by the first base station according to a channel for receiving the data, for example, the first session identifier is a session identifier corresponding to a channel for transmitting the data by a network side, such as a core network entity, and when the first base station sends the data to the second base station, the first session identifier may be carried in the data. Or, the data may be sent by the core network entity to the second base station, the first session identifier is determined by the second base station according to a channel for receiving the data, and the second base station is a base station corresponding to a network accessed before and after the UE moves, that is, the base stations accessed before and after the UE moves are the same; at this time, the cells under the second base station may include cells belonging to the LADN service area and cells not belonging to the LADN service area.

Optionally, in this application, the first Request message may include a user Context Retrieval Request, that is, a UE Context Retrieval Request, such as a Retrieve UE Context Request or a UE Context Retrieval Request, and the second Request message and/or the third Request message may be an RRC message, such as an RRC message, an RRC connection response, an RRC response Request, or any other message with this function.

In the embodiment of the invention, when the UE in the RRC non-activated state leaves the LADN service area and moves to the non-LADN service area, the network equipment can receive the data from the network side, further judge that the data belongs to the LADN data, and directly discard the data when the UE leaves the LADN service area, thereby realizing the processing of the LADN data of the UE leaving the LADN service area, reducing the system overhead and enhancing the user experience.

The following describes in detail an example in which the core network entity is a UPF, the first request message is a UE context retrieval request, and the second request message and the third request message are RRC messages.

Referring to fig. 3, fig. 3 is an interaction diagram of another data processing method according to an embodiment of the present invention. Specifically, the embodiments of the present invention are applicable to a scenario in which a UE moves from a LADN service area (hereinafter referred to as "LADN SA") under one base station (i.e., a first base station) to an area under another base station (i.e., a second base station), that is, in the embodiments of the present invention, the first base station and the second base station are different. As shown in fig. 3, the data processing method according to the embodiment of the present invention may include the following steps:

301. the core network entity transmits data to the first base station.

Specifically, a core network entity such as a UPF may send data, such as downlink LADN data, that an application server needs to send to the UE through a network side to the first base station, and the first base station receives the data sent by the UPF. Furthermore, the first base station may determine, according to the channel receiving the data, a session identifier corresponding to the data, such as a session ID or DNN, that is, a first session identifier, and the session identifier is taken as the session ID for the following description. Optionally, the data may be sent by the UPF to the AMF through the SMF, and further sent to the first base station through the AMF.

302. The first base station sends a paging request to the UE.

303. The second base station sends a paging request to the UE.

Optionally, the first base station may be a base station corresponding to a network, such as ran (old ran), to which the UE accesses before moving, and the first base station belongs to a LADN SA (for example, a TAI or a cell of the first base station belongs to a LADN SA); the second base station may be a base station corresponding to a network, such as ran (new ran), accessed by the UE after moving, and the second base station does not belong to the LADN SA.

Specifically, the UE may be in an RRC inactive state. When receiving a Paging request such as Paging sent by the first base station and the second base station, the UE may enter an RRC connected state (RRC connected state, abbreviated as "connected state") by sending an RRC message.

304. The UE sends an RRC message to the second base station.

Specifically, if the UE receives a Paging request, such as Paging, sent to the UE by the first base station, that is, the old RAN and the second base station, that is, the new RAN, the UE may send an RRC message, that is, the second request message, to the second base station. Optionally, the second Request message may be a message sent by the UE to transition from the RRC inactive state to the RRC connected state, for example, the message may be an RRC message, an RRC connection response, an RRC response Request, or any other message with this function, which is described in the following by way of example. The RRC Resume Request may carry a Resume identifier such as Resume ID. Therefore, the second base station can determine the first base station before the UE moves according to the Resume ID, so that the second base station and the first base station can communicate conveniently.

305. The second base station sends a UE context retrieval request to the first base station.

Specifically, after receiving the RRC message sent by the UE, the second base station, i.e., the new RAN, may send a UE Context Retrieval Request, such as a Retrieve UE Context Request or a UE Context Retrieve Request, to the first base station, i.e., the old RAN, so as to obtain the Context information of the UE. The first base station receives the UE context retrieval request and may obtain information of the second base station to facilitate communication with the second base station. Wherein, the UE Context Retrieval Request, such as Retrieve UE Context Request or UE Context Retrieve Request, may carry the result ID.

306. The first base station returns a UE context retrieval response to the second base station.

Optionally, after receiving the UE Context Retrieval request sent by the second base station, the first base station, that is, the old RAN, may return a UE Context Retrieval Response, such as Retrieve UE Context Response or UE Context Retrieve Response, to the second base station, that is, the new RAN. The UE Context retrieving Response may carry UE Context information, i.e. UE Context, in the Retrieve UE Context Response or the UE Context Retrieve Response. The second base station may thus obtain the context information of the UE, so as to communicate with the core network according to the context information of the UE and to recover or establish an RRC connection between the UE and the second base station.

307. And the first base station forwards data to the second base station, wherein the data carries the session identification.

Optionally, the execution sequence of the steps 306 and 307 is not limited, for example, the step 307 may be executed first, and then the step 306 is executed, or the steps 306 and 307 may be executed simultaneously, which is not limited in this application.

308. And the second base station forwards data to the UE, wherein the data carries the session identification.

When the first base station forwards the received data to the second base station, the data may carry the determined first session identifier, such as the first session ID. Specifically, the first base station, that is, the old RAN, may forward the data carrying the first session identifier to the second base station, that is, the new RAN, and the new RAN may send the data carrying the first session identifier to the UE.

309. And the UE determines the data as the LADN data according to the session identifier carried by the data, and discards the data if the data is moved out of the LADN SA.

Specifically, the UE may determine the type of the received data according to a session identifier, such as a first session ID (i.e., a first session identifier), in the data, for example, whether the data is data of a session corresponding to a LADN (hereinafter, referred to as "LADN data"). Specifically, a session identifier of the LADN data, such as a second session ID (i.e., a second session identifier), may be stored in the UE, so that the UE may compare the first session ID carried in the data with the second session ID of the stored LADN data, and determine that the received data is the LADN data when the first session ID and the second session ID are the same. Further, the UE may also detect whether it moves out of the LADN SA. For example, the UE may determine whether the UE moves out of the LADN SA by acquiring the location information of the UE and determining whether the location indicated by the location information is within the range of the LADN SA, and specifically may indicate that the UE moves out of the LADN SA when it is determined that the location is not within the range of the LADN SA, or may detect whether the UE moves out of the LADN SA in other manners, and the present application is not limited to the manner of determining whether the UE moves out of the LADN SA. Optionally, the UE determines whether the data is the LADN data, and the sequence of determining whether the UE moves out of the LADN SA is not limited, for example, the two may be executed separately (simultaneously or non-simultaneously); or determining whether the data is the LADN data, and determining whether the UE moves out of the LADN SA after determining that the data is the LADN data; or it may be determined whether the UE moves out of the LADN SA first, and then it is determined whether the data is LADN data after it is determined that the UE moves out of the LADN SA, which is not limited in the present application. And the UE can discard the LADN data when the received data is determined to be the LADN data and the UE is determined to move out of the LADN SA, thereby realizing the processing of the LADN data.

Optionally, the second base station may send a Path switching Request, such as a Path Switch Request, to the AMF, where the Path switching Request may carry the location information of the UE. And the AMF may determine whether the UE moves out of the LADN SA according to the location information. Further optionally, after the AMF determines that the UE has moved out of the LADN SA, the AMF may also send a notification message, such as a Namf _ EventExposure _ Notify, to the SMF to Notify the SMF that the UE has moved out of the LADN SA. Further, after the SMF determines that the UE moves out of the LADN SA, a PDU session deactivation procedure may be performed, such as to release the LADN related PDU session, i.e., deactivated the LADN related PDU session. Further, the SMF may also notify the UPF to discard the Data of the PDU session, and/or notify the UPF not to provide a subsequent Data Notification message (not provider resource Data Notification messages). Specifically, the SMF may initiate release of User Plane (UP) connection of the PDU session related to the LADN, and at this time, the base station to which the UE is connected and the core network are in a connected state, and the UPF may stop sending the LADN data to the first base station and the second base station. For example, the subsequent LADN data may be directly discarded by the UPF upon receipt, and as another example, the upd may still receive the LADN data but no longer send (to the SMF) the data to the first base station, old RAN, and the second base station, new RAN.

In the embodiment of the invention, when the UE in the RRC non-activated state leaves the LADN SA under the old RAN and moves to the service area under the new RAN, the network side can send the LADN data to the old RAN, the old RAN can forward the data to the UE through the new RAN after the UE is paged and enters the connected state, and then the UE can judge that the data belongs to the LADN data according to the session ID and directly abandons the LADN data when judging that the UE itself leaves the LADN SA. Therefore, the UE can process the LADN data of the UE leaving the LADN SA, the system overhead is reduced, and the user experience is enhanced.

Referring to fig. 4, fig. 4 is an interaction diagram of another data processing method according to an embodiment of the present invention. Specifically, the embodiment of the present invention is applicable to a scenario in which the UE moves from a LADN service area, such as a LADN SA, under the same base station (a first base station, that is, a second base station) to another area under the base station, that is, in the embodiment of the present invention, the first base station and the second base station are the same. As shown in fig. 4, the data processing method according to the embodiment of the present invention may include the following steps:

401. the core network entity sends data to the base station.

The base station may refer to the first base station or the second base station, where the first base station and the second base station are the same base station, and the base station includes a cell belonging to a LADN SA and a cell not belonging to the LADN SA. Specifically, the step 401 may refer to the related description of the step 301 in the embodiment shown in fig. 3, which is not repeated herein.

402. The base station sends a paging request to the UE.

Specifically, the UE may be in an RRC inactive state. The UE may enter an RRC Connected state when receiving a paging request sent by the base station.

403. The UE sends an RRC message to the base station.

Specifically, if the UE receives a Paging Request, such as Paging, sent by the base station, i.e., RAN to the UE, the UE may send an RRC message, such as RRC Resume Request, to the second base station. The RRC Resume Request may carry a Resume identifier such as Resume ID.

404. And the base station forwards data to the UE, wherein the data carries the session identification.

Specifically, after the UE is paged and enters the connected state, the base station may send the data to the UE, where the data may carry a session identifier such as a session ID (i.e., a first session identifier), and the first session identifier may be determined by the base station according to a channel for receiving the data sent by the network side.

405. And the UE determines the data as LADN data according to the session identifier carried by the data, determines to move out of LADN SA, and discards the data.

Specifically, the description of step 405 may refer to the description related to step 309 in the embodiment shown in fig. 3, and is not repeated herein.

Optionally, the base station may send a location report, such as a location report, to the AMF, where the location report may carry the location information of the UE. Before the base station sends Location Report to the AMF, the AMF sends a Location Report Control message such as Location Reporting Control to the base station. That is, the AMF may request the Location Report by sending the Location Reporting Control to the base station, and the base station may return the Location Report to the AMF after receiving the Location Reporting Control. And the AMF may determine whether the UE moves out of the LADN SA according to the location information. Further optionally, after the AMF determines that the UE has moved out of the LADN SA, the AMF may also send a notification message, such as a Namf _ EventExposure _ Notify, to the SMF to Notify the SMF that the UE has moved out of the LADN SA. Further, after determining that the UE moves out of the LADN SA, the SMF may execute a PDU session deactivation procedure, notify the UPF to discard the data of the PDU session, and/or notify the UPF not to provide a subsequent data notification message any more, and then the UPF may stop sending the LADN data to the base station, and so on.

In the embodiment of the invention, when the UE in the RRC non-activated state leaves the LADN SA and is still in the same RNA, the network side can send the LADN data to the RAN, the RAN can send the data to the UE after the UE is paged and enters the connected state, and the UE can judge that the data belongs to the LADN data according to the session ID carried by the data and directly abandon the LADN data when the UE itself leaves the LADN SA. Therefore, the UE can process the LADN data of the UE leaving the LADN SA, the system overhead is reduced, and the user experience is enhanced.

Referring to fig. 5, fig. 5 is an interaction diagram of another data processing method according to an embodiment of the present invention. Specifically, the embodiments of the present invention are applicable to a scenario where the UE moves from a LADN service area, such as a LADN SA, under one base station (i.e., a first base station) to an area under another base station (i.e., a second base station), that is, in the embodiments of the present invention, the first base station and the second base station are different. As shown in fig. 5, the data processing method according to the embodiment of the present invention may include the following steps:

501. the core network entity transmits data to the first base station.

502. The first base station sends a paging request to the UE.

503. The second base station sends a paging request to the UE.

Specifically, the steps 502-504 can refer to the related description of the steps 301-303 in the embodiment shown in fig. 3, which is not repeated herein.

504. The UE moves out of the LADN SA.

Specifically, the manner of determining that the UE moves out of the LADN SA may refer to the related description of step 309 in the embodiment shown in fig. 3, and the embodiment of the present invention does not limit the manner of determining whether the UE moves out of the LADN SA.

505. And the UE sends an RRC message to the second base station, wherein the RRC message carries a recovery identifier, a second session identifier and an indication message for indicating the UE to move out of the LADN SA.

The second session identifier (e.g., the second session ID) may refer to a session identifier of the stored LADN data.

Optionally, the step 504 is not limited, for example, it may also be performed before the step 502, or before the step 503 or 504, and the like, and the present application is not limited.

Specifically, the UE may detect whether it has moved out of the LADN SA, such as a LADN SA. If the UE detects that the LADN SA is removed, an indication message may be generated to indicate that the UE is removed from the LADN SA. The UE is paged by the first base station and the second base station and determines to move out of the LADN SA, that is, an RRC message such as an RRC Resume Request carrying the indication message may be sent to the second base station. Further, the RRC Resume Request may also carry a recovery identifier, such as a Resume ID, and a second session identifier, such as a session ID of the LADN data.

506. And the second base station sends a UE context retrieval request to the first base station, wherein the UE context retrieval request carries a recovery identifier, a second session identifier and an indication message for indicating that the UE is moved out of the LADN SA.

Specifically, the second base station, i.e., the new RAN, may send a UE Context Retrieval Request, such as a Retrieve UE Context Request or a UE Context Retrieval Request, to the first base station, i.e., the old RAN, and the first base station receives the UE Context Retrieval Request. Wherein, the UE Context Retrieval Request, such as a Retrieve UE Context Request or a UE Context Retrieve Request, may carry a result ID, a session ID of the LADN data, and an indication message for indicating that the UE moves out of the LADN SA.

507. And the first base station determines that the data is the LADN data according to the first session identifier corresponding to the data and the second session identifier carried in the request, determines that the UE moves out of the LADN SA according to the indication message carried in the request, and discards the data.

The first session identifier (e.g., the first session ID) may refer to an identifier of a session to which the data itself belongs, and for example, the first session ID may be determined by the first base station according to a channel for receiving the data.

Specifically, the first base station may compare a first session ID carried by the data with a second session ID in the UE context retrieval request, and determine that the data is the LADN data when the two are the same. And the first base station may discard the LADN data when determining that the received data is the LADN data and determining that the UE moves out of the LADN SA, thereby implementing processing of the LADN data.

508. The first base station returns a UE context retrieval response to the second base station.

Specifically, after receiving the UE Context Retrieval request sent by the second base station, the first base station, that is, the old RAN, may return a UE Context Retrieval Response, such as Retrieve UE Context Response or UE Context Retrieve Response, to the second base station, that is, the new RAN. The UE Context retrieving Response may carry UE Context information, i.e. UE Context, in the Retrieve UE Context Response or the UE Context Retrieve Response. The second base station may thus obtain the context information of the UE, so as to communicate with the core network according to the context information of the UE.

Optionally, the execution sequence of steps 507 and 508 is not limited, for example, step 508 may be executed first, and then step 507 may be executed, or steps 507 and 508 may be executed simultaneously, which is not limited in this application.

Optionally, the second base station may send a Path switching Request, such as a Path Switch Request, to the AMF, where the Path switching Request may carry the location information of the UE. And the AMF may determine whether the UE moves out of the LADN SA according to the location information. Further optionally, after the AMF determines that the UE has moved out of the LADN SA, the AMF may also send a notification message, such as a Namf _ EventExposure _ Notify, to the SMF to Notify the SMF that the UE has moved out of the LADN SA. Further, after determining that the UE moves out of the LADN SA, the SMF may execute a PDU session deactivation procedure, and may further notify the UPF to discard the PDU session data, and/or notify the UPF not to provide a subsequent data notification message any more, and then the UPF may stop sending the LADN data to the first base station and the second base station, and so on, which may specifically refer to the relevant description of the above embodiments and is not described herein again.

In the embodiment of the invention, when the UE in the RRC inactive state leaves the LADN SA under the old RAN and moves to the service area under the new RAN, the network side can send the LADN data to the old RAN, the old RAN receives the session ID and the indication message sent by the new RAN after the UE is paged, and the old RAN directly discards the LADN data when judging that the data belongs to the LADN data according to the session ID and judging that the UE leaves the LADN SA according to the indication message. Therefore, the method can realize the processing of the LADN data of the UE leaving the LADN SA through the old RAN, reduce the system overhead and enhance the user experience.

Referring to fig. 6, fig. 6 is an interaction diagram of another data processing method according to an embodiment of the present invention. Specifically, the embodiments of the present invention are applicable to a scenario where the UE moves from a LADN service area, such as a LADN SA, under one base station (i.e., a first base station) to an area under another base station (i.e., a second base station), that is, in the embodiments of the present invention, the first base station and the second base station are different. As shown in fig. 6, the data processing method according to the embodiment of the present invention may include the following steps:

601. the core network entity transmits data to the first base station.

602. The first base station sends a paging request to the UE.

603. The second base station sends a paging request to the UE.

604. The UE moves out of the LADN SA.

605. And the UE sends an RRC message to the second base station, wherein the RRC message carries a recovery identifier, a second session identifier and an indication message for indicating the UE to move out of the LADN SA.

Optionally, the step 601-605 can refer to the related description of the step 501-505 in the embodiment shown in fig. 5, which is not repeated herein.

Specifically, if the UE receives a Paging Request, such as Paging, sent to the UE by the first base station, that is, old RAN and the second base station, that is, new RAN, and the UE determines to move out of the laddn SA, the UE may send an RRC message, such as RRC Resume Request, to the second base station. The RRC Resume Request may carry a Resume identifier, such as a Resume ID, a session identifier, such as a session ID, and an indication message, which may be used to indicate that the UE moves out of the LADN SA.

606. And the second base station sends a UE context retrieval request to the first base station, wherein the UE context retrieval request carries the recovery identifier.

Specifically, the second base station, i.e., the new RAN, may send a UE Context Retrieval Request, such as a Retrieve UE Context Request or a UE Context Retrieval Request, to the first base station, i.e., the old RAN, and the first base station receives the UE Context Retrieval Request. Wherein the UE Context Retrieval Request, such as a Retrieve UE Context Request or a UE Context Retrieve Request, may carry a recovery identity, such as a Resume ID.

607. The first base station returns a UE context retrieval response to the second base station.

Specifically, the steps 606-607 can refer to the related description of the steps 305-306 in the embodiment shown in fig. 3, which is not repeated herein.

608. And the first base station forwards data to the second base station, wherein the data carries the first session identifier.

The data carries a session identifier, i.e. a first session identifier. The first session identifier (e.g., the first session ID) may refer to an identifier of a session to which the data itself belongs, for example, the first base station may determine the first session ID according to a channel receiving the data. Specifically, the first base station, that is, the old RAN, may forward the data carrying the first session ID to the second base station, that is, the new RAN, so that the second base station processes the data.

609. And the second base station determines that the data is LADN data according to the first session identifier corresponding to the data and the second session identifier in the RRC message, and discards the data if the UE is determined to move out of LADN SA according to the indication message in the RRC message.

Specifically, the second base station may compare the first session ID carried by the data with the second session ID in the RRC message, and determine that the data is the LADN data when the two are the same. And the second base station may discard the LADN data when determining that the received data is the LADN data and determining that the UE moves out of the LADN SA, thereby implementing processing of the LADN data.

In the embodiment of the invention, when the UE in the RRC non-activated state leaves the LADN SA under the old RAN and moves to the service area under the new RAN, the network side can send the LADN data to the old RAN, the old RAN can forward the data to the new RAN after the UE is paged and sends the resume request, and then the new RAN can directly discard the LADN data when judging that the data belongs to the LADN data according to the session ID and judging that the UE leaves the LADN SA according to the indication message. Therefore, the method can realize the processing of the LADN data of the UE leaving the LADN SA through the new RAN, reduce the system overhead and enhance the user experience.

Referring to fig. 7, fig. 7 is an interaction diagram of another data processing method according to an embodiment of the present invention. Specifically, the embodiment of the present invention is applicable to a scenario in which the UE moves from a LADN service area, such as a LADN SA, under the same base station (a first base station, that is, a second base station) to another area under the base station, that is, in the embodiment of the present invention, the first base station and the second base station are the same. As shown in fig. 7, the data processing method according to the embodiment of the present invention may include the following steps:

701. the core network entity sends data to the base station.

The base station may refer to the first base station or the second base station, and the first base station and the second base station are the same base station.

702. The base station sends a paging request to the UE.

Optionally, the UE may enter the connected state when receiving a paging request sent by the base station.

703. The UE moves out of the LADN SA.

Optionally, the execution sequence of the step 703, the step 701, and the step 702 is not limited, for example, the step 703 may be executed first, and then the steps 701 and 702 may be executed, or the steps 703 and 701 may be executed simultaneously, which is not limited in this application.

704. And the UE sends an RRC message to the base station, wherein the RRC message carries a recovery identifier, a second session identifier and an indication message for indicating the UE to move out of the LADN SA.

Specifically, if the UE receives a Paging Request, such as Paging, sent by the base station, i.e., RAN to the UE, and the UE determines to move out of the LADN SA, the UE may send an RRC message, such as RRC Resume Request, to the second base station. The RRC Resume Request may carry a Resume identifier, such as a Resume ID, a second session identifier, such as a session ID, and an indication message for indicating that the UE moves out of the LADN SA.

705. And the base station determines that the data is LADN data according to the first session identifier corresponding to the data and the second session identifier in the RRC message, and discards the data if the UE is determined to move out of the LADN SA according to the indication message in the RRC message.

The first session identifier (e.g., the first session ID) may refer to an identifier of a session to which the data itself belongs, and for example, the base station may determine the first session ID according to a channel receiving the data.

Specifically, the base station may compare the first session ID carried by the data with the second session ID in the RRC message, and determine that the data is the LADN data when the two are the same. And the base station can discard the LADN data when the currently received data is determined to be the LADN data and the UE is determined to move out of the LADN SA, thereby realizing the processing of the LADN data.

Optionally, the base station may send a location report, such as a location report, to the AMF, where the location report may carry the location information of the UE. Before the base station sends Location Report to the AMF, the AMF sends a Location Report Control message such as Location Reporting Control to the base station. That is, the AMF may request the Location Report by sending the Location Reporting Control to the base station, and the base station may return the Location Report to the AMF after receiving the Location Reporting Control. And the AMF may determine whether the UE moves out of the LADN SA according to the location information. Further optionally, the AMF may also send a notification message, such as a Namf _ EventExposure _ Notify, to the SMF to Notify the SMF that the UE has moved out of the LADN SA. Further, after determining that the UE moves out of the LADN SA, the SMF may execute a PDU session deactivation procedure, notify the UPF to discard the data of the PDU session, and/or notify the UPF not to provide a subsequent data notification message any more, and then the UPF may stop sending the LADN data to the first base station, and so on.

In the embodiment of the invention, when the UE in the RRC non-activated state leaves the LADN SA and the UE is still in the same RNA, the network side can send the LADN data to the RAN, and further when the UE is paged and receives a resume request sent by the UE, the RAN can judge that the data belongs to the LADN data according to the session ID, and directly discards the LADN data when the UE leaves the LADN SA according to the indication message carried in the request. Therefore, the base station can process the LADN data of the UE leaving the LADN SA, the system overhead is reduced, and the user experience is enhanced.

The above method embodiments are all illustrations of the data processing method of the present application, and descriptions of various embodiments have respective emphasis, and reference may be made to relevant descriptions of other embodiments for parts that are not described in detail in a certain embodiment.

Fig. 8 shows a schematic diagram of a possible structure of the network device according to the above embodiment, and referring to fig. 8, the network device 800 may include: a communication unit 801 and a processing unit 802. Wherein these units may perform the respective functions of the network device in the above method examples, e.g. the communication unit 801 for receiving data; a processing unit 802, configured to determine whether the data is data of a session corresponding to a local area data network LADN; the processing unit 802 is further configured to discard the data when it is determined that the data is data of a session corresponding to the LADN and it is determined that the user equipment terminal moves out of the LADN service area. Wherein, the terminal is in a radio resource connection inactive state RRC inactive state.

Optionally, the terminal moves from a first base station to a second base station, where the first base station belongs to the LADN service area, and the second base station does not belong to the LADN service area.

Optionally, the network device is the terminal; the communication unit 801 is specifically configured to receive data sent by the first base station through the second base station, where the data carries a first session identifier.

Optionally, a second session identifier is stored in the terminal, where the second session identifier is a session identifier corresponding to the LADN;

the processing unit 802 is specifically configured to determine that the data is data of a session corresponding to the LADN when the first session identifier is the same as the second session identifier.

Optionally, the network device is a first base station;

the communication unit 801 is further configured to receive a first request message sent by a second base station, where the first request message is sent by the second base station after the second base station receives a second request message, the second request message is sent to the second base station after the terminal receives paging requests of the first base station and the second base station, the first request message includes an indication message, and the indication message is used to indicate that the terminal moves out of the LADN service area;

the processing unit 802 is specifically configured to determine that the terminal moves out of the LADN service area according to the indication message.

Optionally, the first request message further includes a second session identifier, where the second session identifier is a session identifier corresponding to the LADN;

the processing unit 802 is specifically configured to determine that the data is data of a session corresponding to the LADN when a first session identifier corresponding to the data is the same as the second session identifier, where the first session identifier is determined by the first base station according to a channel for receiving the data.

Optionally, the network device is a second base station;

the communication unit 801 is further configured to receive a third request message sent by the terminal, where the third request message includes an indication message, and the indication message is used to indicate that the terminal moves out of the LADN service area;

Optionally, the third request message includes a second session identifier, where the second session identifier is a session identifier corresponding to the LADN;

the processing unit 802 is specifically configured to determine that the data is the data of the session corresponding to the LADN when the first session identifier corresponding to the data is the same as the second session identifier.

Optionally, the data is sent by the first base station to the second base station, and the data carries the first session identifier; or, the data is sent to the second base station by a core network entity, and the first session identifier is determined by the second base station according to a channel for receiving the data.

Optionally, the first base station is a base station corresponding to a network accessed by the terminal before moving, and the second base station is a base station corresponding to a network accessed by the terminal after moving.

It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation. Each functional unit in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

In the case of an integrated unit, fig. 9 shows another possible structural diagram of the network device involved in the foregoing embodiments, and as shown in fig. 9, the network device 900 may include: a processing unit 902 and a communication unit 903. Processing unit 902 may be used to control and manage the actions of a network device, e.g., processing unit 902 may be used to support the network device performing the processes in fig. 2, processes 304, 309 in fig. 3, processes 403, 405 in fig. 4, process 507 in fig. 5, process 609 in fig. 6, process 705 in fig. 7, and/or other processes for the techniques described herein. The communication unit 903 is used to support communication between the network device and other network entities, for example, the functional units or network entities shown in fig. 2 to 5. The network device may further include a storage unit 901 for storing program codes (operation instructions) and data of the network device.

The Processing Unit 902 may be a Processor or a controller, such as a Central Processing Unit (CPU), a general-purpose Processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication unit 903 may be a transceiver or be provided separately as a receiver and a transmitter. The storage unit 901 may be a memory.

When the processing unit 902 is a processor, the communication unit 903 is a transceiver, and the storage unit 901 is a memory, the network device according to the embodiment of the present invention may be the network device shown in fig. 10.

Referring to fig. 10, the network device 1000 may include: a processor 1002, a transceiver 1003, a memory 1001, and a bus 1004. The transceiver 1003, the processor 1002, and the memory 1001 are connected to each other through a bus 1004; the bus 1004 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 10, but this is not intended to represent only one bus or type of bus. Wherein the processor 1002 is operable to perform:

invoking the transceiver 1003 to receive data;

determining the data as the data of the session corresponding to the local area data network LADN;

when the terminal is determined to move out of the LADN service area, the data are discarded;

wherein, the terminal is in a radio resource connection inactive state RRC inactive state.

Optionally, the terminal may move from a first base station to a second base station, where the first base station belongs to the LADN service area, and the second base station does not belong to the LADN service area.

Optionally, the network device is the terminal; the processor 1002 calls the transceiver 1003 to receive data, specifically, to:

and invoking the transceiver 1003 to receive data sent by the first base station through the second base station, where the data carries a first session identifier.

Optionally, a second session identifier is stored in the terminal, where the second session identifier is a session identifier corresponding to the LADN; the processor 1002 determines that the data is data of a session corresponding to a LADN, and is specifically configured to:

and when the first session identifier and the second session identifier are the same, determining that the data is the data of the session corresponding to the LADN.

Optionally, the network device is a first base station; the processor 1002 is further configured to, before determining that the terminal moves out of the LADN service area and discards the data, perform:

calling the transceiver 1003 to receive a first request message sent by a second base station, where the first request message is sent by the second base station after receiving a second request message, the second request message is sent to the second base station after the terminal receives paging requests of the first base station and the second base station, the first request message includes an indication message, and the indication message is used to indicate that the terminal moves out of the LADN service area;

the processor 1002 determines that the terminal moves out of the LADN service area, and is specifically configured to:

and determining that the terminal moves out of the LADN service area according to the indication message.

Optionally, the first request message further includes a second session identifier, where the second session identifier is a session identifier corresponding to the LADN; the processor 1002 determines that the data is data of a session corresponding to a LADN, and is specifically configured to:

and when the first session identifier corresponding to the data is the same as the second session identifier, determining that the data is the data of the session corresponding to the LADN, wherein the first session identifier is determined by the first base station according to a channel for receiving the data.

Optionally, the network device is a second base station; the processor 1002 is further configured to, before determining that the terminal moves out of the LADN service area and discards the data, perform:

invoking the transceiver 1003 to receive a third request message sent by the terminal, where the third request message includes an indication message, and the indication message is used to indicate that the terminal moves out of the LADN service area;

Optionally, the third request message includes a second session identifier, where the second session identifier is a session identifier corresponding to the LADN; the processor 1002 determines that the data is data of a session corresponding to a LADN, and is specifically configured to:

and when the first session identifier corresponding to the data is the same as the second session identifier, determining that the data is the data of the session corresponding to the LADN.

The application also provides a communication system, which comprises the UE (terminal), the first base station, the second base station and/or the core network entity. Optionally, the system may further include other devices, such as an AMF, an SMF, an application server, and the like, interacting with the above device in the solution provided by the embodiment of the present invention.

The present application further provides a chip system, which may include a processor for supporting a network device to implement the functions of the network device, such as a UE, a first base station, or a second base station, for example, to process data and/or information involved in the data processing method. Optionally, the system-on-chip may further include a memory for storing program instructions and data necessary for the network device. Further alternatively, the chip system may be formed by a chip, or may include a chip and other discrete devices.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware or in software instructions executed by a processor. The software instructions may be comprised of corresponding software modules or units that may be stored in Random Access Memory (RAM), flash Memory, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, a hard disk, a removable hard disk, a compact disc Read Only Memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a network device. Of course, the processor and the storage medium may reside as discrete components in a network device.

It should be understood that the reference herein to first, second, third and various numerical designations is merely a convenient division to describe and is not intended to limit the scope of embodiments of the present invention.

It should be understood that the term "and/or" herein is merely one type of association relationship that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of the processes should be determined by their functions and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A data processing method, comprising:

the network equipment receives data;

the network equipment determines that the data is data of a session corresponding to a Local Area Data Network (LADN);

the network equipment determines that the terminal corresponding to the data moves out of an LADN service area, and discards the data;

wherein the terminal is in a radio resource connection inactive state RRC inactive state; the terminal is moved from a first base station to a second base station, the first base station belonging to the LADN service area, the second base station not belonging to the LADN service area.

2. The method of claim 1, wherein the network device is the terminal; the network device receives data, including:

and the terminal receives data sent by the first base station through the second base station, wherein the data carries a first session identifier.

3. The method according to claim 2, wherein a second session identifier is stored in the terminal, and the second session identifier is a session identifier corresponding to the LADN;

the network device determines that the data is data of a session corresponding to the LADN, including:

and when the first session identifier is the same as the second session identifier, the terminal determines that the data is the data of the session corresponding to the LADN.

4. The method of claim 1, wherein the network device is a first base station; before the network device determines that the terminal moves out of the LADN service area and the network device discards the data, the method further comprises:

the first base station receives a first request message sent by a second base station, the first request message is sent by the second base station after receiving a second request message, the second request message is sent to the second base station after the terminal receives paging requests of the first base station and the second base station, the first request message comprises an indication message, and the indication message is used for indicating that the terminal moves out of the LADN service area;

the network equipment determines that the terminal moves out of the LADN service area, and the method comprises the following steps:

and the first base station determines that the terminal moves out of the LADN service area according to the indication message.

5. The method of claim 4, wherein the first request message further comprises a second session identifier, and wherein the second session identifier is a session identifier corresponding to the LADN;

and when the first session identifier corresponding to the data is the same as the second session identifier, the first base station determines that the data is the data of the session corresponding to the LADN, and the first session identifier is determined by the first base station according to a channel for receiving the data.

6. The method of claim 1, wherein the network device is a second base station; before the network device determines that the terminal moves out of the LADN service area and the network device discards the data, the method further comprises:

the second base station receives a third request message sent by the terminal, wherein the third request message comprises an indication message, and the indication message is used for indicating that the terminal moves out of the LADN service area;

and the second base station determines that the terminal moves out of the LADN service area according to the indication message.

7. The method of claim 6, wherein the third request message comprises a second session identifier, and wherein the second session identifier is a session identifier corresponding to the LADN;

and when the first session identifier corresponding to the data is the same as the second session identifier, the second base station determines that the data is the data of the session corresponding to the LADN.

8. The method of claim 7, wherein the data is sent from a first base station to the second base station, and the data carries the first session identifier; or,

the data is sent to the second base station by a core network entity, and the first session identifier is determined by the second base station according to a channel for receiving the data.

9. The method according to any of claims 1-8, wherein the first base station is a base station corresponding to a network accessed by the terminal before moving, and the second base station is a base station corresponding to a network accessed by the terminal after moving.

10. A network device, comprising: a communication unit and a processing unit;

the communication unit is used for receiving data;

the processing unit is configured to determine that the data is data of a session corresponding to a Local Area Data Network (LADN), and discard the data when determining that a terminal corresponding to the data moves out of a LADN service area;

11. The device of claim 10, wherein the network device is the terminal;

the communication unit is specifically configured to receive data sent by the first base station through the second base station, where the data carries a first session identifier.

12. The apparatus according to claim 11, wherein a second session identifier is stored in the terminal, and the second session identifier is a session identifier corresponding to the LADN;

the processing unit is specifically configured to determine that the data is data of a session corresponding to the LADN when the first session identifier is the same as the second session identifier.

13. The device of claim 10, wherein the network device is a first base station;

the communication unit is further configured to receive a first request message sent by a second base station, where the first request message is sent by the second base station after receiving a second request message, the second request message is sent to the second base station after the terminal receives paging requests of the first base station and the second base station, the first request message includes an indication message, and the indication message is used to indicate that the terminal moves out of the LADN service area;

the processing unit is specifically configured to determine that the terminal moves out of the LADN service area according to the indication message.

14. The device of claim 13, wherein the first request message further comprises a second session identifier, and wherein the second session identifier is a session identifier corresponding to the LADN;

the processing unit is specifically configured to determine that the data is data of a session corresponding to the LADN when a first session identifier corresponding to the data is the same as the second session identifier, where the first session identifier is determined by the first base station according to a channel through which the data is received.

15. The apparatus of claim 10, wherein the network device is a second base station;

the communication unit is further configured to receive a third request message sent by the terminal, where the third request message includes an indication message, and the indication message is used to indicate that the terminal moves out of the LADN service area;

16. The apparatus of claim 15, wherein the third request message comprises a second session identifier, and wherein the second session identifier is a session identifier corresponding to the LADN;

the processing unit is specifically configured to determine that the data is data of a session corresponding to the LADN when the first session identifier and the second session identifier corresponding to the data are the same.

17. The apparatus of claim 16, wherein the data is sent from a first base station to the second base station, and the data carries the first session identifier; or,

18. The apparatus according to any of claims 10-17, wherein the first base station is a base station corresponding to a network accessed by the terminal before moving, and the second base station is a base station corresponding to a network accessed by the terminal after moving.