Communication methods, terminal device, radio access device and core network device

Abstract

Provided are communication methods, a terminal device, a radio access device and a core network device. A communication method comprises: a first terminal device transmitting first data to a first radio access device, wherein the first data is local service data or non-local service data. A first terminal device can transmit local service data or non-local service data to a radio access device; and a base station can execute operations on the local service data and the non-local service data, for example, the radio access device forwards, to a second terminal device and by means of local routing, the local service data transmitted by the first terminal device, so that the forwarding of local service data at a radio access device level is realized, without the need for forwarding at the level of network elements, such as a UPF, thereby reducing the transmission latency of local service data, improving the performance of transmitting the local service data and reducing the load on network elements, such as a UPF.

Description

Communication method, terminal device, radio access device and core network device TECHNICAL FIELD

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

[0002] With the development of wireless communication technology, the connection density of terminal devices gradually increases, which will generate large-scale local service data. Therefore, how to improve the transmission performance of local service data becomes a problem to be solved.

[0003] SUMMARY

[0004] The present application provides a communication method, a terminal device, a radio access device and a core network device. The various aspects involved in the present application are introduced below.

[0005] In a first aspect, a communication method is provided, comprising: a first terminal device sending first data to a first radio access device, the first data being local service data or non-local service data.

[0006] In a second aspect, a communication method is provided, comprising: a first radio access device receiving first data sent by a first terminal device, the first data being local service data or non-local service data.

[0007] In a third aspect, a communication method is provided, comprising: a core network device sending third information to a first radio access device, the third information being used to determine whether the first data received by the first radio access device from a terminal device is local service data or non-local service data.

[0008] In a fourth aspect, a terminal device is provided, comprising: a transceiver unit configured to send first data to a first radio access device, the first data being local service data or non-local service data.

[0009] In a fifth aspect, a radio access device is provided, comprising: a transceiver unit configured to receive first data sent by a first terminal device, the first data being local service data or non-local service data.

[0010] In a sixth aspect, a core network device is provided, comprising: a transceiver unit configured to send third information to a first radio access device, the third information being used to determine whether the first data received by the first radio access device from a terminal device is local service data or non-local service data.

[0011] In a seventh aspect, a terminal device is provided, which includes a processor, a memory, and a transceiver. The memory is configured to store one or more computer programs. The processor is configured to invoke the computer programs in the memory to cause the terminal device to perform some or all of the steps in the method of the first aspect.

[0012] In an eighth aspect, a radio access device is provided, which includes a processor, a memory, and a transceiver. The memory is configured to store one or more computer programs. The processor is configured to invoke the computer programs in the memory to cause the radio access device to perform some or all of the steps in the method of the second aspect.

[0013] In a ninth aspect, a core network device is provided, which includes a processor, a memory, and a transceiver. The memory is configured to store one or more computer programs. The processor is configured to invoke the computer programs in the memory to cause the core network device to perform some or all of the steps in the method of the third aspect.

[0014] In a tenth aspect, a communication system is provided, which includes one or more of the terminal device, the radio access device, and the core network device described above. In some implementations, the communication system further includes other devices that interact with the terminal device, the radio access device, and the core network device.

[0015] In an eleventh aspect, a computer-readable storage medium is provided, which stores a computer program. The computer program causes a terminal device, a radio access device, or a core network device to perform some or all of the steps in the methods of the aspects described above.

[0016] In a twelfth aspect, a computer program product is provided, which includes a non-transitory computer-readable storage medium storing a computer program. The computer program is operable to cause a terminal device, a radio access device, or a core network device to perform some or all of the steps in the methods of the aspects described above. In some implementations, the computer program product can be a software installation package.

[0017] In a thirteenth aspect, a chip is provided, which includes a memory and a processor. The processor can invoke and run a computer program from the memory to implement some or all of the steps described in the methods of the aspects described above.

[0018] In the embodiments of the present application, the first terminal device can send local service data or non-local service data to the wireless access device. The base station can perform operations for the local service data and the non-local service data, for example, forwarding the local service data sent by the first terminal device to the second terminal device in a local routing manner through the wireless access device, realizing the forwarding of the local service data at the level of the wireless access device, without the need for forwarding at the level of network elements such as a user plane function (UPF), thereby improving the transmission delay of the local service data, improving the transmission performance of the local service data, and reducing the burden of the network elements such as the UPF. BRIEF DESCRIPTION OF DRAWINGS

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

[0020] FIG. 2 is a schematic diagram of a networking architecture to which embodiments of the present application can be applied.

[0021] FIG. 3 is a schematic diagram of a possible data forwarding manner of the present application.

[0022] FIG. 4 is a schematic diagram of a transmission path of local service data of an embodiment of the present application.

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

[0024] FIG. 6 is a schematic diagram in which first information is carried in an existing protocol layer.

[0025] FIG. 7 is a schematic diagram in which first information is carried in a newly added protocol layer.

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

[0027] FIG. 9 is a schematic diagram of an association relationship between QoS flows in the method shown in FIG. 8 in a protocol architecture.

[0028] FIG. 10 is a schematic diagram of an association relationship between PDU sessions in the method shown in FIG. 8 in a protocol architecture.

[0029] FIG. 11 is a schematic block diagram of a terminal device according to an embodiment of the present application.

[0030] FIG. 12 is a schematic block diagram of a wireless access device according to an embodiment of the present application.

[0031] FIG. 13 is a schematic block diagram of a core network device according to an embodiment of the present application.

[0032] FIG. 14 is a schematic block diagram of an apparatus for communication according to an embodiment of the present application. DETAILED DESCRIPTION

[0033] The technical solutions in the present application will be described below with reference to the drawings. In order to facilitate understanding, first, the communication terms and communication processes that may be involved in the embodiments of the present application will be introduced with reference to FIGS. 1 to 4.

[0034] Communication system

[0035] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as a 5th generation (5G) system or a new radio (NR) system, a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, etc. The technical solutions of the embodiments of the present application can also be applied to future communication systems, such as a 6th generation (6G) mobile communication system, a satellite communication system, etc.

[0036] As an example, FIG. 1 is a schematic diagram of an architecture of a wireless communication system to which the embodiments of the present application are applicable. The wireless communication system includes terminal devices, access network (AN) network elements, and core network (CN) network elements.

[0037] The terminal device can be referred to as a user equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station (MS), a mobile terminal (MT), a remote station, a remote terminal, a mobile device, a user terminal, a terminal device, a wireless communication device, a user agent, or a user apparatus. The terminal device can be, for example, a device that provides voice and / or data connectivity to a user, and can be used to connect a user to a network, such as a wireless connection function-enabled household appliance, a sensor, an electronic tag, and the like. The terminal device can also be a wireless terminal in a smart home, a wireless terminal in an IWSN, a wireless terminal in smart logistics and smart warehousing, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, and the like. Alternatively, the terminal device can be used to act as a base station. For example, the terminal device can act as a scheduling entity that provides sidelink signals between terminal devices in a vehicle-to-everything (V2X) or device-to-device (D2D) scenario, and the like. For example, a cellular phone and a car communicate with each other using sidelink signals; a cellular phone and a smart home device communicate without relaying the communication signals through a base station.

[0038] The access network element can be an access device for a terminal device to access the network architecture by a wireless manner, and is mainly responsible for wireless resource management, quality of service (QoS) management, data compression and encryption, and the like. In the embodiments of the present application, the access network element is also referred to as a radio access network (RAN) device or an access network (AN) device, for example, the access network device can be a base station. It should be understood that the AN or RAN in FIG. 1 is represented as (R)AN.

[0039] A base station can be broadly referred to as various names below, or can be replaced with the names below, for example: a Node B (NodeB), an evolved Node B (eNB), a next generation Node B (gNB), a relay station, an access point, a transmitting and receiving point (TRP), a transmitting point (TP), a master eNB (MeNB), a secondary eNB (SeNB), a multi-standard radio (MSR) node, a home base station, a network controller, an access node, a radio node, an access point (AP), a transmission node, a transceiver node, a base band unit (BBU), a remote radio unit (RRU), an active antenna unit (AAU), a remote radio head (RRH), a centralized unit (CU), a distributed unit (DU), a positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. The base station can also refer to a communication module, a modem, or a chip for being disposed in the aforementioned device or apparatus. The base station can also be a mobile switching center, and a device assuming a base station function in device-to-device (D2D), vehicle-to-everything (V2X), machine-to-machine (M2M) communication, a network side device in a 6G network, a device assuming a base station function in a future communication system, etc. The base station can support networks of the same or different access technologies. Embodiments of the present application do not limit the specific technology and specific device form adopted by the access network element.

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

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

[0042] The UPF network element can be used to forward and receive data of the terminal device. For example, the UPF network element can receive service data from the DN and transmit it to the terminal device through the access network element; the UPF network element can also receive user data from the terminal device through the access network element and forward it to the DN. Among them, the transmission resources allocated and scheduled by the UPF network element for the terminal device can be managed and controlled by the SMF network element. The bearer between the terminal device and the UPF network element includes, for example, the user plane (UP) connection between the UPF network element and the access network element, and the channel established between the access network element and the terminal device. Among them, the user plane connection is a quality of service (QoS) flow (QoS flow) that can establish a transmission data service between the UPF network element and the access network element.

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

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

[0045] The PCF network element is used to provide policies to the AMF network element and the SMF network element, for example, QoS policies, slice selection policies, and the like.

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

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

[0048] The NSSF is used for network slice selection, for example, it can support part or all of the following functions: selecting a set of network slice implementations to serve the terminal device; determining the allowed network slice selection assistance information (NSSAI), and determining the mapping to the single-network slice selection assistance information (S-NSSAI) of the subscription when needed; determining the configured NSSAI, and determining the mapping to the S-NSSAI of the subscription when needed; determining a set of AMFs that can be used to query the terminal device, or determining a list of candidate AMFs based on configuration.

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

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

[0051] The NEF is used for capability exposure, that is, based on the NEF, the capability of the network can be output to an external network. An external untrusted application can access internal data of the core network through the NEF to ensure the security of the network. The NEF can provide functions such as external application QoS capability exposure, event subscription, AF request distribution, and the like.

[0052] The NRF is used for registering, managing, and detecting the state of core network elements, thereby realizing automatic management of the core network elements. When a core network element is started, it must be registered with the NRF to provide services. The registration information may, for example, include the type, address, and service list of the core network element.

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

[0054] In a communication system such as a 5G system, the core network element is also referred to as a network function (NF).

[0055] Each network element in FIG. 1 can be a network element in a hardware device, a software function running on a dedicated hardware, or a virtualized function instantiated on a platform such as a cloud platform. It should be noted that in the network architecture shown in the above figure, only the network elements included in the entire network architecture are exemplarily illustrated. In the embodiments of the present application, the network elements included in the entire network architecture are not limited.

[0056] It can be understood that the network architecture shown in FIG. 1 does not constitute a limitation on the network architecture to which the embodiments of the present application can be applied. Specifically, the network architecture can include more or fewer network elements than those shown in the figure, or some network elements can be combined, and the like. The above-mentioned core network elements and access network elements can be referred to as network devices or network side devices.

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

[0058] In some deployments, the network device can refer to a CU or a DU; or, the network device includes a CU and a DU. Optionally, the gNB can include an AAU.

[0059] By way of example and without limitation, in some embodiments, a network device can have mobile characteristics, e.g., the network device can be a mobile device. In other implementations, a network device can also be a satellite, a balloon station. For example, a satellite can be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In other embodiments, a network device can also be disposed at a terrestrial, a water, etc. location.

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

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

[0062] Local service and non-local service

[0063] The IMT-2030+ Vision and Requirement White Paper mentions immersive experience, digital twin, intelligent interaction, etc. as potential application scenarios of 6G systems. At the same time, on the basis of traditional performance indicators, ultra-high rate, ultra-high transmission reliability, ultra-low latency, ultra-dense connection, ultra-low power consumption, etc. are proposed as extreme performance requirements, however, supporting these extreme performance requirements simultaneously in the entire network range will greatly increase the network burden and increase the operation cost of 6G networks, and thus is not feasible.

[0064] Considering that these specific application scenarios are usually deployed in a smaller range and have strong local data service attributes, it is an important direction to realize the 6G scenario requirements by deploying in a small range and providing localized extreme performance requirements for data service support. Therefore, concepts such as wide-area micro-area fusion and subnetworks (subnetworks / subnets) have been proposed for wireless access network networking. For example, data of terminal devices can be aggregated in a micro-area, and a header point (HP) can be introduced for each micro-area. Terminal devices in a micro-area can interact with terminal devices in other micro-areas or a wide-area network through the header point, thereby reducing the load and maintenance cost of the wide-area network and improving the utilization of spectrum resources.

[0065] As an example, a networking architecture as shown in FIG. 2, a macro network can include multiple subnetworks, the macro network can be provided by a macro base station (macro xNB), each subnetwork can include a header point and multiple terminal devices, and the terminal devices can interact with the macro base station or a core network through the header point. Among them, the header point shown in FIG. 2 can be a base station (xNB) or a terminal device.

[0066] It can be understood that the macro network described above can be replaced by a parent network, a parent mobile network, a wide-area network, etc., and its main functions may, for example, include providing external non-local connection support for a subnetwork, a main security anchor, bearing a billing function, and authorizing a batch of communication resources to a subnetwork. The subnetwork described above can be replaced by a micro network, a local area network, a micro-area network, etc., and its main functions may, for example, include connecting to a local wireless network of a macro network and having partial autonomy, being controlled by a header point, which can be implemented by a base station or a terminal device; managing a batch of authorized communication resources within the subnetwork; routing local data within the subnetwork to meet extremely high performance; routing non-local data to the macro network; group management and mobility of terminal devices within the subnetwork. The terminal device described above can be referred to as a micro-area terminal or a child terminal device (child UE), which supports both local services and non-local services. The header point described above can also be replaced by a cluster header point, a header, a node device, a wireless access device, etc., and the terminal devices within the subnetwork can interact with the macro base station or the core network through the corresponding header point.

[0067] Taking a micro-domain network as an example, the service types of micro-domain terminals can be divided into two types, one of which is a local service in a micro-domain, that is, a service that is generated, transmitted, and processed locally in the micro-domain; and the other is a non-local service, that is, a service that is generated in the micro-domain but processed outside the micro-domain, or a service that is generated outside the micro-domain but is directed to a node in the micro-domain. Such a service usually has a medium delay requirement of millisecond level or is a delay-insensitive service, and can be finally processed through a wide-area network.

[0068] Transmission of the local service in the micro-domain, including data transmission between micro-domain terminals and a micro-domain head node, and data transmission between micro-domain terminals, is implemented, for example, under the control and coordination of the micro-domain head node. Compared with conventional wide-area network transmission, the local service in the micro-domain is more conducive to achieving extreme performance requirements such as ultra-low delay and ultra-high reliability due to a shorter transmission path. In the wide-area micro-domain fusion networking architecture, the head node representing the entire micro-domain network is connected between a wide-area access network and a wide-area core network to perform signaling interaction.

[0069] In addition to supporting transmission of the local service in the micro-domain, it is also necessary to support transmission of the non-local service between terminal devices in the micro-domain and a wide-area network, to fully utilize cloud computing resources of the wide-area network, balance network loads of the micro-domain and the wide-area, and more effectively and flexibly process various services of terminal devices. In addition, the non-local service also includes transmission of services between micro-domains, for example, information transmission between terminal devices of one micro-domain and terminal devices of another micro-domain, or information transmission between head nodes of two micro-domains. For the non-local service of the micro-domain, the head node of the micro-domain can be used to forward the non-local service to the wide-area network based on a relay mode.

[0070] Transmission path of the local service

[0071] Currently, related technologies capable of supporting local processing of local services include, for example, a 5G virtual network (VN) group (5G VN group), a local IP access (LIPA) technology or a selected IP traffic offload (SIPTO) technology in LTE, a wireless access and backhaul (WAB) technology in release 19 (Rel-19) of 5G, and the like.

[0072] Taking a 5G virtual network group as an example, the coverage range of a 5G base station includes multiple virtual network groups (VN groups), namely virtual network group 1 to virtual network group N. Each virtual network group includes multiple terminal devices, which are used to implement 5G local area network type services. The 5G virtual network group has features such as a 5G virtual network group identifier, 5G virtual network group members, and 5G virtual network group data. The 5G virtual network group can support unicast, broadcast, groupcast and other services. Traffic forwarding within the 5G virtual network group can be achieved through the internal interface (5G VN internal) of the UPF, and the following detection and forwarding steps are performed.

[0073] First, the data received from the 5G virtual network group members will be forwarded to the internal interface of the UPF, that is, the target interface is configured as "5G VN internal", wherein the data sent by the virtual network group members can be received through the N6 or N19 interface, based on the PDU session (PDU session).

[0074] Secondly, based on the data detection rule (packet detect rule, PDR) configured on the internal interface of the UPF, the data is detected and forwarded to the corresponding 5G virtual network group member, wherein the data can be forwarded through the N6 or N19 interface, based on the PDU session.

[0075] When the terminal device accesses the 5G local area network type service, it can pass through the PDU session, which has, for example, an IP PDU session type or an Ethernet PDU session type. Among them, one PDU session only provides access to one 5G virtual network group. This has no effect on the terminal device, and the terminal device does not need to mark the data as different types such as 5G virtual network group data, and the traffic forwarding is handled by the UPF, for example, based on the target address of the data.

[0076] For a single 5G virtual network group, the SMF can configure the UPF to route traffic between PDU sessions in different traffic forwarding modes. For example, according to the different destination addresses, some message flows can be forwarded locally, some message flows can be forwarded from the N19 interface, and some message flows can be forwarded to the N6 interface.

[0077] The N6 interface is used for uplink (UL) and downlink (DL) traffic forwarding of 5G virtual network group communication to external DN or forwarding data from external DN. The N19 interface is used for uplink and downlink traffic forwarding of 5G virtual network group communication between UPFs of different PDU sessions of PDU session anchor (PSA). The N19 interface is based on a shared user plane (UP) channel connecting the UPFs of the PSA of a single 5G virtual network group. If the UPF is the UPF of the common PSA of different PDU sessions of a 5G virtual network group, the traffic is forwarded locally by a single UPF.

[0078] As shown in several data forwarding modes in FIG. 3, for non-local service data, for example, as shown in (b) of FIG. 3, the non-local service data is transmitted to the external DN through the base station, the UPF and other network elements in turn. For local service data, if it is not routed locally, it needs to be forwarded at the APP server level. Even if the terminal device 1 and the terminal device 2 are in the same area, the transmission of the local service data between the terminal device 1 and the terminal device 2 needs to pass through the following path: terminal device 1-base station 1-UPF 1-APP server-UPF 2-base station 2-terminal device 2. In this way, the transmission delay of the local service data is significantly increased, which is difficult to meet the extreme QoS requirement of the 6G network.

[0079] Related technologies capable of supporting local routing of local service data include, for example, 5G virtual network group, LTE LIPA / SIPTO, Rel-19 WAB, and the like. Such related technologies implement routing and forwarding of local service data at the UPF level. For example, as shown in (a) of FIG. 3, the transmission of local service data between the terminal device 1 and the terminal device 2 needs to pass through the following path: terminal device 1-base station 1-UPF-base station 2-terminal device 2; for example, as shown in (c) of FIG. 3, the transmission of local service data between the terminal device 1 and the terminal device 2 needs to pass through the following path: terminal device 1-base station 1-UPF 1-UPF 2-base station 2-terminal device 2.

[0080] However, the forwarding of local service data based on the UPF level in the related technologies has the following problems: first, considering the further improved data transmission rate and the connection density of terminal devices in the 6G network, if the large-scale local service data still needs to be forwarded through the UPF level, the burden of network elements such as UPF will be significantly increased; second, the transmission path routed through the UPF is still difficult to meet the more stringent transmission delay requirement of the 6G network, in order to shorten the delay, the core network elements such as UPF and APP server can be deployed locally at the base station, which increases the complexity of the base station, especially for the micro-domain network scenarios around the human body and vehicles.

[0081] Therefore, an embodiment of the present application proposes a transmission scheme of local service data, which aims to forward the local service data sent by a first terminal device to a second terminal device in a local routing manner through a wireless access device, so as to realize the forwarding of the local service data at the level of the wireless access device, without the need for forwarding at the level of network elements such as UPF, thereby improving the transmission delay of the local service data, improving the transmission performance of the local service data, and reducing the burden of network elements such as UPF. Here, the local routing refers to a data routing manner without passing through the core network.

[0082] As an example, FIG. 4 shows the transmission path of the local service data according to an embodiment of the present application, the local service data between the first terminal device and the second terminal device is directly forwarded through the first wireless access device, realizing the routing of the local service data at the level of the wireless access device, and the local deployment based on the core network elements such as UPF can be avoided.

[0083] The technical scheme of the embodiment of the present application can be applied to the forwarding process of local service data in any scenario, and is especially suitable for the forwarding process of local data in each micro network, sub-network, local area network and micro-domain network under the foregoing networking architecture. The wireless access device of the embodiment of the present application can also be referred to as a control device of a wireless network, for example, the wireless access device is a base station under a non-networking architecture or a head node under a networking architecture, wherein the head node can be a base station or a terminal device. The terminal device can access the core network in a wireless manner through the wireless access device.

[0084] In the embodiment of the present application, the first terminal device can send local service data or non-local service data to the wireless access device. The base station can perform operations for local service data and non-local service data, for example, the local service data sent by the first terminal device is forwarded to the second terminal device in a local routing manner through the wireless access device, which realizes the forwarding of the local service data at the level of the wireless access device, without the need for forwarding at the level of network elements such as UPF, thereby improving the transmission delay of the local service data, improving the transmission performance of the local service data, and reducing the burden of network elements such as UPF.

[0085] Fig. 5 is a flow chart of a communication method according to an embodiment of the present application. The method 100 shown in Fig. 5 can be performed by a first terminal device and a first radio access device. As shown in Fig. 5, the method 100 comprises some or all of the following steps.

[0086] In step 110, the first terminal device sends first data to the first radio access device.

[0087] Correspondingly, in step 120, the first radio access device receives the first data sent by the first terminal device.

[0088] The first data is local service data or non-local service data.

[0089] Optionally, in the case that the first data is local service data, the first radio access device forwards the local service data to a second terminal device by local routing. That is, the first radio access device is configured to forward the first data to the second terminal device by local routing.

[0090] Optionally, in the case that the first data is non-local service data, the first radio access device forwards the non-local service data to a core network device. That is, the first radio access device is further configured to forward the non-local service data to the core network.

[0091] The first terminal device can also be referred to as a source terminal device (SRC UE), and the second terminal device can also be referred to as a destination terminal device (DST UE).

[0092] In the embodiments of the present application, the data can also be replaced by data packets or traffic, etc. In addition, the forwarding in the embodiments of the present application can also be replaced by sending or transmitting, etc.

[0093] Optionally, the first radio access device can be located in the coverage of a second radio access device. The second radio access device can be a macro base station as shown in Fig. 3, and the first radio access device can be a head node in the coverage of the macro base station. The head node can be implemented by a base station or a terminal device.

[0094] For example, the embodiments of the present application can be applied to a subnet-based networking architecture, in which all child UEs under the header can form a group of local services, and the UEs can transmit local service data therebetween; all child UEs directly connected under the header can also form a group of local services, and the UEs can also transmit local service data therebetween. For another example, the embodiments of the present application can also not be applied to a subnet-based networking architecture, but be applied to a general base station, in which the network can also maintain corresponding group relationship and pairing relationship, etc.

[0095] The first data transmitted by the terminal device is user plane data. In the related art, the UPF is used for forwarding of the user plane data. In the embodiments of the present application, the first data is forwarded by the first wireless access device to the second terminal device in a local routing manner, and will not pass through the UPF, thereby improving the transmission delay of the local service data, improving the transmission performance of the local service data, and reducing the burden of the UPF and other network elements.

[0096] In the embodiments of the present application, the local service data refers to data that does not pass through the core network, i.e., service data that can be locally routed at the wireless access device level to achieve offloading, which is also referred to as local service. For example, for a networking architecture, the data source and the destination are in the same subnetwork, or the data source and the destination are in different subnetworks, but the different subnetworks are directly connected or the header nodes of different subnets are connected through an interface, and the data can be considered as local service data. For another example, regardless of the networking architecture, the data source and the destination are in the same network covered by a base station, or the data source and the destination are in different networks covered by different base stations, but the different base stations have an Xn interface connection, and the data can be considered as local service data. Correspondingly, service data that needs to be forwarded through the core network, such as the UPF, can be considered as non-local service data, which is also referred to as non-local service.

[0097] Based on the above description, for the local service data, in order to realize the forwarding of the local service data at the wireless access device level, the first wireless access device needs to identify whether the first data transmitted by the first terminal device is local service data or non-local service data, so as to locally route the local service data and route the non-local service data to the core network.

[0098] To this end, further, the embodiments of the present application also provide technical solutions for the wireless access device to identify the local service data and the non-local service data, for example, the indication manner of the service type of the first data can include one or more of the following: indication by the first information, the first information being sent by the first terminal device; determination based on the transmission resource of the first data; indication by the third information, the third information being sent by the core network device.

[0099] Hereinafter, how the first wireless access device identifies the local service data and the non-local service data will be described in detail in combination with FIG. 6 to FIG. 9.

[0100] Embodiment 1

[0101] In embodiment 1, the first terminal device sends the first information to the first wireless access device, for example, the first terminal device carries the indication information for indicating whether the first data is the local service data or the non-local service data while sending the first data. For example, the first information is carried in the first data and is used to indicate that the first data is the local service data. The first information can also be referred to as the local / non-local indication information.

[0102] For example, the first information can have 1 bit. When the bit is 1, it indicates that the first data is the local service data, and when the bit is 0, it indicates that the first data is the non-local service data; or, when the bit is 1, it indicates that the first data is the non-local service data, and when the bit is 0, it indicates that the first data is the local service data.

[0103] Alternatively, the first information is associated with the service information, and the first terminal device can generate the first information according to the characteristics of the service or APP, etc. For example, the first data is the broadcast service data, the first terminal device generates the corresponding first information according to the broadcast service, and after the first wireless access device receives the first data, it broadcasts the first data based on the first information in the first data.

[0104] Further, in some implementations, the first information is also used to indicate one or more of the following: the identification information of the first terminal device; the identification information of the second terminal device.

[0105] For example, the identification information of the first terminal device can be used to inform the second terminal device who sends the local service data to it when the first data is the local service data.

[0106] Optionally, the identification information of the second terminal device can be determined based on one or more of the following information: service information corresponding to the first data; and identification of one or more terminal devices indicated by the first radio access device. The one or more terminal devices refer to terminal devices that can be reached by the first radio access device through local routing, or terminal devices reachable by the first radio access device. That is, the identification information of the second terminal device can be for service information, or for a specific terminal device.

[0107] For example, the identification information of the second terminal device can be generated by an upper layer of the first terminal device according to service or APP characteristics, i.e., the first information is for a specific service or APP, rather than for a specific terminal device. After receiving the first data, the first radio access device determines that the first data is local service data based on the first information in the first data, and then forwards the first data to the second terminal device in the local network that supports the service. In this case, optionally, the first terminal device and the first radio access device need to know the association between service information and terminal devices, so as to forward the local service data to the second terminal device in the local network that supports the service according to the service information indicated by the first information and the association between the service information and the terminal devices.

[0108] For another example, the identification information of the second terminal device can be indicated by the first radio access device. The first radio access device can indicate the identification information of terminal devices that can be reached by the first radio access device through local routing to the first terminal device in advance, for example, by sending the identification information to the first terminal device or broadcasting the identification information. In this way, the first information in the first data sent by the first terminal device when sending the local service data can carry the identification of the second terminal device. Optionally, the information of terminal devices that can be reached by the first radio access device through local routing can be obtained by the first radio access device through terminal devices registered in the network provided by the first radio access device, and / or shared by radio access devices of adjacent networks. Here, the radio access devices of adjacent networks can be, for example, radio access devices having an Xn interface with the first radio access device, or radio access devices that are also located in the coverage of the second radio access device and are directly connected with the first radio access device.

[0109] In some implementations, the first information can be access layer (AS) information, or said to be carried in AS signaling. Generally, the terminal device PDU session endpoint is a UPF, and the wireless access device is responsible for transmitting user plane data to the UPF, and cannot interpret non-access layer (NAS) layer information, so the wireless access device cannot distinguish whether the service data sent by the terminal device is local service data or non-local service data. In the embodiment of the application, the first terminal device carries the first information in the AS layer while sending data, so that the first wireless access device can identify whether the destination of the first data is local or non-local through the first information in the AS layer, and then decide to route the local service data locally or forward the non-local service data to the UPF.

[0110] In some implementations, the first information is carried in the packet header of the first protocol layer.

[0111] The first protocol layer can be an existing protocol layer. For example, the first protocol layer can be a physical layer (PHY), a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a service data adaption protocol (SDAP) layer, and the like. As shown in FIG. 6, the first information is carried in the packet header of the SDAP layer as an example.

[0112] Here, if the existing protocol layer is multiplexed to carry the first information, the higher the layer of the protocol layer carrying the first information, the more precise the data granularity of the routing forwarding, but the first wireless access device needs to parse and process more layers of information to forward; on the contrary, the lower the layer of the protocol layer carrying the first information, the coarser the data granularity of the routing forwarding, but the processing complexity of the first wireless access device is lower, and the processing time is less.

[0113] Alternatively, the first protocol layer can also be a newly added protocol layer to reduce the impact on the original protocol layer and increase flexibility. The embodiment of the application does not make any limitation on the positional relationship between the newly added protocol layer and the existing protocol layer, such as the physical layer, the MAC layer, the RLC layer, the PDCP layer, and the SDAP layer. As shown in FIG. 7, a new protocol layer is added between the PDCP layer and the RLC layer, and the first information is carried in the packet header of the new protocol layer as an example.

[0114] In some implementations, the first data is initial transmission data, and the retransmission data of the first data does not carry the first information. That is, the first terminal device carries the first information in the first data when initially transmitting data, and for retransmission data, the first information is not carried in the data, thereby saving signaling overhead.

[0115] The first radio access device can determine whether the first data is initial transmission data or retransmission data according to whether a new data indicator (NDI) in the data is flipped. The NDI in initial transmission data is flipped, while the NDI in retransmission data is not flipped. If the corresponding NDI in the first data received by the first radio access device is not flipped, it can be considered as retransmission data, and in the case that the previous data is local service data, it can be considered that the retransmission data is also local service data, and is forwarded to the second terminal device through local routing.

[0116] Embodiment 2

[0117] In embodiment 2, the first radio access device can distinguish local service data and non-local service data based on transmission resources, thereby reducing the impact on the protocol. For example, in the case that the first data is local service data, the first data is transmitted through a first resource, and the first resource is a resource for transmitting local service data. For another example, in the case that the first data is non-local service data, the first data is transmitted through a second resource, and the second resource is a resource for transmitting non-local service data.

[0118] The first resource dedicated to local service data and the second resource dedicated to non-local service can be preconfigured, and the transmission resource of the first data includes one or more of the following, for example: a configured grant (CG) resource, a hybrid automatic repeat request (HARQ) process, a logical channel (LCH), and a data radio bearer (DRB). The first resource is only allowed to be used by local service data, and the second resource is only allowed to be used by non-local service.

[0119] The first terminal device needs to select a specific transmission resource to send the data when there is data to be transmitted according to the type of data, i.e., local service data or non-local service data, and the limitation of the corresponding transmission resource. For example, in the case where the first data to be sent by the first terminal device is local service data, the first terminal device will send the first data on the first resource. Correspondingly, the first radio access device distinguishes local service data and non-local service data according to the transmission resource used by the first terminal device to send the first data, and decides whether to perform local routing or non-local routing forwarding to the UPF. For example, the first radio access device receives the first data on the first resource, and can determine that the first data is local service data. For another example, the first radio access device receives the first data on the second resource, and can determine that the second data is non-local service data.

[0120] In some implementations, the transmission resource of the first data is associated with one or more of the following: local service data; and an identifier of the second terminal device. Optionally, in the case where the transmission resource of the first data is associated with the local service data, the first data further includes the identifier information of the second terminal device.

[0121] For example, the transmission resource of the first data is associated with the local service data. In this case, the first terminal device needs to carry the identifier information of the terminal device in the first data when sending the first data on the transmission resource of the first data. In this way, the first radio access device can determine whether the first data is local service data or non-local service data after receiving the first data on the transmission resource of the first data, and in the case where the first data is local service data, the first radio access device can determine which terminal device to forward the first data to in the manner of local routing according to the identifier information of the terminal device carried in the first information. In the case where the first information carries the identifier information of the second terminal device, the first radio access device forwards the first data to the second terminal device in the manner of local routing.

[0122] For another example, the transmission resource of the first data is associated with the identifier of the terminal device, i.e., the transmission resource of the first data is directly associated with a specific terminal device. In this way, the first radio access device can determine that the first data is local service data after receiving the first data on the transmission resource of the first data, and the first radio access device can determine which terminal device the first data transmitted on the transmission resource of the first data should be forwarded to in the manner of local routing based on the association between the transmission resource and the terminal device. In the case where the transmission resource of the first data is associated with the identifier of the second terminal device, the first radio access device forwards the first data to the second terminal device in the manner of local routing. The association can be agreed in a protocol or configured by the network.

[0123] The identity information of the second terminal device can be determined based on one or more of the following information: service information corresponding to the first data; and identity information of one or more terminal devices indicated by the first radio access device, wherein the one or more terminal devices are terminal devices that can be reached by the first radio access device through local routing. For details of obtaining the identity information of the second terminal device, refer to the description of the identity information of the second terminal device in Embodiment 1.

[0124] In some implementations, the method 100 can further include: the first radio access device sending second information to the first terminal device; or the first terminal device sending second information to the first radio access device; wherein the second information is used to adjust the association between the transmission resource of the first data and the local service data, and / or the association between the transmission resource of the first data and the identity of the second terminal device. The second information can be carried in AS signaling, for example.

[0125] That is, the first terminal device can request to change the association between the transmission resource of the first data and the local service data, or the first radio access device can also actively change the association, for example, change the local service data and the non-local service data, so that the local service data corresponding to the transmission resource of the first data changes, or change the identity information of the terminal device that transmits the local service data using the transmission resource of the first data.

[0126] Embodiment 3

[0127] In Embodiment 3, the first radio access device can distinguish between local services and non-local services based on information provided by the core network. The technical solution of Embodiment 3 does not bring any impact to the first terminal device, and the process involved is the interaction process between the first radio access device and the core network device.

[0128] For example, as shown in FIG. 8, the method 100 can further include part or all of the following steps.

[0129] In step 230, the core network device sends third information to the first radio access device.

[0130] Correspondingly, in step 240, the first radio access device receives the third information sent by the core network device.

[0131] The third information is used to determine whether the first data received by the first radio access device from the terminal device is local service data or non-local service data.

[0132] In step 250, the first radio access device forwards the first data according to the third information.

[0133] In a case where the first data is local service data, the first data received from the first terminal device is forwarded to the second terminal device in a local routing manner; or in a case where the first data is non-local service data, the first data received from the first terminal device is forwarded to the core network. In some implementations, the third information is used to indicate one or more of the following: an association relationship between QoS flows of the terminal device; an association relationship between PDU sessions of the terminal device. The association relationship can also be referred to as pairing information, group information, mapping information, etc. between QoS flows or between PDU sessions.

[0134] Each terminal device can have one or more PDU sessions, and each PDU session can include one or more QoS flows. Therefore, by providing, by the core network device such as a UPF, a SMF, or the like, the first wireless access device with an association relationship between PDU sessions or QoS flows of different terminal devices that transmit local service data, the first wireless access device can forward the local service data between different terminal devices at the granularity of PDU sessions or QoS flows according to the association relationship, for example, forward the first data sent by the first terminal device to the second terminal device without making any changes to the operations performed by the terminal devices.

[0135] For example, at the QoS flow level, different QoS flows of different terminal devices are indicated by two or more groups of (UE ID, QoS Flow ID) to be associated with each other and belong to the same local service. The QoS flow identifier (QoS Flow ID, QFI) is used to identify the QoS flow in the PDU session. Assuming that the third information sent by the core network device to the first wireless access device indicates that (UE ID 1, QoS Flow ID 2) is associated with (UE ID 2, QoS Flow ID 1), where UE ID 1 is the identifier of the first terminal device, and UE ID 2 is the identifier of the second terminal device.

[0136] Therefore, when the first wireless access device receives the first data sent by the first terminal device, if the first wireless access device stores the association relationship, the first data is considered to be local service data, and the first data in the QoS flow corresponding to QoS Flow ID 2 of the first terminal device is forwarded to the QoS flow corresponding to QoS Flow ID 1 of the second terminal device in a local routing manner based on the association relationship, without being forwarded to the UPF. If the first wireless access device does not store the association relationship, the first data is considered to be non-local service data, or the first data is forwarded to the UPF in a non-local routing manner.

[0137] For example, at the PDU session level, the association between different PDU sessions of different terminal devices is indicated by two or more groups of (UE ID, PDU session ID), and the PDU sessions belong to the same local service. The identifier of the PDU session (PDU Session ID) is used to identify the PDU session in the network. It is assumed that the core network device indicates in the third information sent to the first wireless access device that (UE ID 1, PDU session ID 1) is associated with (UE ID 2, PDU session ID 2), where UE ID 1 is the identifier of the first terminal device, and UE ID 2 is the identifier of the second terminal device.

[0138] In this way, when the first wireless access device receives the first data sent by the first terminal device, if the first wireless access device stores the association, the first data is considered as local service data, and the first wireless access device forwards the first data in the PDU session corresponding to the PDU session ID 1 of the first terminal device to the PDU session corresponding to the PDU session ID 2 of the second terminal device in a local routing manner, without forwarding it to the UPF. If the first wireless access device does not store the association, the first data is considered as non-local service data, or the first data is forwarded to the UPF in a non-local routing manner.

[0139] As an example, FIGS. 9 and 10 respectively show the implementation of the association relationship at the QoS flow level and the PDU session level indicated by the third information in the protocol layer architecture. In the example of the wireless access device being a gNB, gNB1 in FIGS. 9 and 10 represents the first wireless access device, gNB2 represents another wireless access device connected to the first wireless access device, and UE1 and UE2 respectively represent the first terminal device and the second terminal device.

[0140] As shown in FIG. 9, UE 1 sends first data to gNB1, and after the first data is processed by the relevant protocol layers of gNB1, the QoS flow information corresponding to the first data can be obtained. gNB1 stores the association between the QoS flows of different terminal devices, so gNB1 can forward the first data to the corresponding QoS flow of UE 2 according to the QoS flow corresponding to the first data and the association. FIG. 9 shows the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and SDAP layer of gNB1, and other protocol layers above SDAP. After the first data is processed by the SDAP layer or other protocol layers above the SDAP layer, the QoS flow information corresponding to the first data can be obtained.

[0141] As shown in FIG. 10, the UE 1 sends first data to the gNB 1, and the first data can obtain PDU session information corresponding to the first data after being processed by relevant protocol layers of the gNB 1. The gNB 1 stores an association relationship between PDU sessions of different terminal devices, and thus the gNB 1 can forward the first data to a corresponding PDU session of the UE 2 according to the PDU session corresponding to the first data and the association relationship. FIG. 10 shows relevant protocol layers of the gNB 1, including a physical layer, a MAC layer, an RLC layer, a PDCP layer, an SDAP layer, and an SDAP layer used for data transmission between the gNB 1 and the UE 1, and a general packet radio service (GPRS) tunneling protocol (GTP-U) layer, a user datagram protocol (UDP) / IP layer, an L2 layer, and an L1 layer used for data transmission between the gNB 1 and a core network, and the first data can obtain QoS flow information corresponding to the first data after being processed by the GTP-U layer.

[0142] It should be noted that the NAS layer shown in FIGS. 9 and 10 can refer to, for example, an IP, a Non-IP, an unstructured, an Ethernet, an address resolution protocol (ARP), and the like. In addition, in FIGS. 9 and 10, the UE 1 and the UE 2 can be located under coverage of the same base station, for example, the gNB 1, or can be located under coverage of two different base stations, for example, the gNB 1 and the gNB 2, where the gNB 1 and the gNB 2 are connected through an interface.

[0143] The method embodiments of the present application are described in detail above in combination with FIGS. 4 to 10, and the device embodiments of the present application are described in detail below in combination with FIGS. 11 to 14. It should be understood that the description of the method embodiments corresponds to the description of the device embodiments, and thus the parts not described in detail can be referred to the foregoing method embodiments.

[0144] FIG. 11 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 200 shown in FIG. 11 can include a transceiver unit 210. The transceiver unit 210 is configured to send first data to a first wireless access device, where the first data is local service data or non-local service data.

[0145] In some implementations, in a case where the first data is local service data, the first data is sent to a second terminal device by the first wireless access device in a local routing manner.

[0146] In some implementations, the first data is forwarded by the first radio access device to a core network in a case that the first data is non-local service data.

[0147] In some implementations, the indication manner of the service type of the first data comprises one or more of the following: indication by first information, the first information being sent by the first terminal device; determination based on transmission resource of the first data; determination by third information, the third information being sent by a core network device.

[0148] In some implementations, the first information is used to indicate that the first data is local service data or non-local service data.

[0149] In some implementations, the first information is carried in the first data.

[0150] In some implementations, the first information is further used to indicate one or more of the following: identification information of the first terminal device; identification information of the second terminal device.

[0151] In some implementations, the first information is access layer information.

[0152] In some implementations, the first information is carried in a packet header of a first protocol layer, the first protocol layer being an existing protocol layer or a newly added protocol layer.

[0153] In some implementations, the first protocol layer comprises one or more of the following: a physical layer, a MAC layer, an RLC layer, a PDCP layer, an SDAP layer.

[0154] In some implementations, the first data is initial transmission data, and retransmission data of the first data does not carry the first information.

[0155] In some implementations, in a case that the first data is local service data, transmission resource of the first data is a first resource; in a case that the first data is non-local service data, transmission resource of the first data is a second resource.

[0156] In some implementations, the transmission resource of the first data is in an association relationship with one or more of the following: the service type of the first data, the service type comprising local service data or non-local service data; identification of the second terminal device.

[0157] In some implementations, the transmission resource of the first data is associated with the service type of the first data, and the first data further comprises identification information of the first terminal device and / or identification information of the second terminal device.

[0158] In some embodiments, the transceiver is further configured to: receive, by the first terminal device, second information from the first radio access device; or transmit, by the first terminal device, second information to the first radio access device; wherein the second information is used to configure or adjust the association relationship.

[0159] In some embodiments, the second information is carried in access stratum signaling.

[0160] In some embodiments, the transmission resource of the first data comprises one or more of the following: configured grant resource, hybrid automatic repeat request process, logical channel, data radio bearer.

[0161] In some embodiments, the identity information of the second terminal device is determined based on one or more of the following: service information corresponding to the first data; identity of one or more terminal devices indicated by the first radio access device, the one or more terminal devices being terminal devices that the first radio access device can reach through the local routing.

[0162] In some embodiments, the third information is used to indicate one or more of the following: association relationship between QoS flows of a terminal device; association relationship between PDU sessions of a terminal device.

[0163] In some embodiments, the first data is user plane data.

[0164] In some embodiments, the first radio access device is located within the coverage of a second radio access device.

[0165] In some embodiments, the first radio access device is a base station or a head node.

[0166] In some embodiments, the head node is a base station or a terminal device.

[0167] It can be understood that the transceiver 210 may, for example, be a transceiver 530. In addition, the terminal device 200 may, for example, further include a processor 510 and a memory 520, as shown in FIG. 14.

[0168] FIG. 12 is a schematic diagram of a radio access device according to an embodiment of the present application. The radio access device 300 shown in FIG. 12 includes a transceiver 310. The transceiver 310 is configured to receive first data transmitted by a first terminal device, the first data being local service data or non-local service data.

[0169] In some embodiments, when the first data is local service data, the first data is transmitted by the first radio access device to the second terminal device through local routing.

[0170] In some embodiments, when the first data is non-local service data, the first data is forwarded by the first radio access device to a core network.

[0171] In some embodiments, the indication of the service type of the first data comprises one or more of the following: indication by first information, the first information being transmitted by the first terminal device; determination based on transmission resources of the first data; determination by third information, the third information being transmitted by a core network device.

[0172] In some embodiments, the first information is used to indicate that the first data is local service data or non-local service data.

[0173] In some embodiments, the first information is carried in the first data.

[0174] In some embodiments, the first information is further used to indicate one or more of the following: identification information of the first terminal device; identification information of the second terminal device.

[0175] In some embodiments, the first information is access layer information.

[0176] In some embodiments, the first information is carried in a packet header of a first protocol layer, the first protocol layer being an existing protocol layer or a newly added protocol layer.

[0177] In some embodiments, the first protocol layer comprises one or more of the following: a physical layer, a MAC layer, an RLC layer, a PDCP layer, an SDAP layer.

[0178] In some embodiments, the first data is initial transmission data, and retransmission data of the first data does not carry the first information.

[0179] In some embodiments, when the first data is local service data, the transmission resources of the first data are first resources; and when the first data is non-local service data, the transmission resources of the first data are second resources.

[0180] In some embodiments, the transmission resources of the first data are associated with one or more of the following: the service type of the first data, the service type comprising local service data or non-local service data; identification information of the second terminal device.

[0181] In some embodiments, the transmission resource of the first data is associated with a service type of the first data, and the first data further comprises identification information of the first terminal device and / or identification information of the second terminal device.

[0182] In some embodiments, the transceiver 310 is further configured to: receive second information sent by the first terminal device; or send second information to the first terminal device, wherein the second information is used to adjust the association relationship.

[0183] In some embodiments, the second information is carried in access layer signaling.

[0184] In some embodiments, the transmission resource of the first data comprises one or more of the following: configured grant resource, hybrid automatic repeat request process, logical channel, data radio bearer.

[0185] In some embodiments, the identification information of the second terminal device is determined based on one or more of the following: service information corresponding to the first data; and identification of one or more terminal devices indicated by the first radio access device, wherein the one or more terminal devices are terminal devices that can be reached by the first radio access device through the local routing.

[0186] In some embodiments, the transceiver 310 is further configured to: receive third information sent by a core network device, wherein the third information is used by the first radio access device to determine whether the first data is local service data or non-local service data.

[0187] In some embodiments, when the first data is the local service data, the first data is forwarded by the first radio access device to a second terminal device through local routing.

[0188] In some embodiments, when the first data is non-local service data, the first data is forwarded by the first radio access device to a core network.

[0189] In some embodiments, the third information is used to indicate one or more of the following: an association relationship between QoS flows of a terminal device; and an association relationship between PDU sessions of a terminal device.

[0190] In some embodiments, the first data is user plane data.

[0191] In some embodiments, the first radio access device is located within a coverage range of a second radio access device.

[0192] In some embodiments, the first radio access device is a base station or a head node.

[0193] In some embodiments, the head node is a base station or a terminal device.

[0194] It can be understood that the transceiver unit 310 can be, for example, the transceiver 530. In addition, the wireless access device 300 can optionally further include the processor 510 and the memory 520, as shown in FIG. 14.

[0195] FIG. 13 is a schematic diagram of a core network device according to an embodiment of the present application. The core network device 400 shown in FIG. 13 includes a transceiver unit 410. The transceiver unit 410 is configured to send third information to a first wireless access device, the third information being used to determine whether first data received by the first wireless access device from a terminal device is local service data or non-local service data.

[0196] In some embodiments, in a case where the first data is the local service data, the first data is forwarded by the first wireless access device to a second terminal device in a local routing manner.

[0197] In some embodiments, in a case where the first data is the non-local service data, the first data is forwarded by the first wireless access device to a core network.

[0198] In some embodiments, the third information is used to indicate one or more of the following: an association relationship between QoS flows of the terminal device; an association relationship between PDU sessions of the terminal device.

[0199] In some embodiments, the first data is user plane data.

[0200] In some embodiments, the first wireless access device is located within a coverage range of a second wireless access device.

[0201] In some embodiments, the first wireless access device is a base station or a head node.

[0202] In some embodiments, the head node is a base station or a terminal device.

[0203] It can be understood that the transceiver unit 410 can be, for example, the transceiver 530. In addition, the core network device 400 can optionally further include the processor 510 and the memory 520, as shown in FIG. 14.

[0204] FIG. 14 is a schematic structural diagram of an apparatus for communication according to an embodiment of the present application. The dashed line in FIG. 14 indicates that the unit or module is optional. The apparatus can be used to implement the methods described in the above method embodiments. The apparatus can be, for example, a chip, a terminal device, a wireless access device, or a core network device.

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

[0206] The apparatus 500 can also include one or more memories 520. The memory 520 stores a program that can be executed by the processor 510, so that the processor 510 performs the method described in the foregoing method embodiments. The memory 520 can be independent of the processor 510 or integrated in the processor 510.

[0207] The apparatus 500 can also include a transceiver 530. The processor 510 can communicate with other devices or chips through the transceiver 530. For example, the processor 510 can perform data transceiving with other devices or chips through the transceiver 530.

[0208] The embodiments of the present application also provide a communication system. The system includes one or more of the terminal device, the wireless access device and the core network device described above. In some implementations, the system further includes other devices that interact with the terminal device, the wireless access device or the core network device.

[0209] The embodiments of the present application also provide a computer readable storage medium for storing a program. The computer readable storage medium can be applied to the terminal device, the wireless access device or the core network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the terminal device, the wireless access device or the core network device in the various embodiments of the present application. Optionally, the readable storage medium is a non-volatile readable storage medium.

[0210] The embodiment of the present application further provides a computer program product. The computer program product comprises a program. The computer program product can be applied to the terminal device, the radio access device or the core network device provided by the embodiment of the present application, and the program causes the computer to execute the method performed by the terminal device, the radio access device or the core network device in the various embodiments of the present application.

[0211] The embodiment of the present application further provides a computer program. The computer program can be applied to the terminal device, the radio access device or the core network device provided by the embodiment of the present application, and the computer program causes the computer to execute the method performed by the terminal device, the radio access device or the core network device in the various embodiments of the present application.

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

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

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

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

[0216] In the embodiments of the present application, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables or other information that can be used to indicate related information in devices such as terminal devices, radio access devices or core network devices, and the present application does not limit the specific implementation manner. For example, predefinition can mean definition in a protocol.

[0217] The term "and / or" in the embodiments of the present application is only used to describe the association relationship of the associated objects, and can represent three relationships, for example, A and / or B can represent three cases of A alone, A and B together, and B alone. In addition, the character " / " in this paper generally represents an "or" relationship between the front and rear associated objects.

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

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

[0220] In several embodiments provided by the present application, it should be understood that the disclosed system, device and method can be implemented by other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and there can be another division way in actual implementation, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0221] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. According to actual needs, part or all of the units can be selected to achieve the purpose of the embodiments of the present application.

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

[0223] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media sets. The available media can be magnetic media such as floppy disk, hard disk, magnetic tape, etc., or optical media such as digital video disc (DVD), or semiconductor media such as solid state disk (SSD), etc.

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

Claims

1. A communication method, characterized in that, include: The first terminal device sends first data to the first wireless access device, wherein the first data is local service data or non-local service data.

2. The communication method according to claim 1, characterized in that, If the first data is local service data, the first data is sent from the first wireless access device to the second terminal device via local routing.

3. The communication method according to claim 1 or 2, characterized in that, If the first data is non-local service data, the first data is sent to the core network by the first wireless access device.

4. The communication method according to any one of claims 1 to 3, characterized in that, The indication method for the service type of the first data includes one or more of the following: The first information indicates that the first information was sent by the first terminal device; The transmission resources are determined based on the first data; It is determined through third information that the third information was sent by the core network equipment.

5. The communication method according to claim 4, characterized in that, The first information is used to indicate whether the first data is local business data or non-local business data.

6. The communication method according to claim 5, characterized in that, The first information is carried in the first data.

7. The communication method according to claim 5 or 6, characterized in that, The first information is also used to indicate one or more of the following: The identification information of the first terminal device; The identification information of the second terminal device.

8. The communication method according to claim 6 or 7, characterized in that, The first piece of information is access layer information.

9. The communication method according to claim 8, characterized in that, The first information is carried in the header of the first protocol layer, which may be an existing protocol layer or a newly added protocol layer.

10. The communication method according to claim 9, characterized in that, The first protocol layer includes one or more of the following: physical layer, medium access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, and service data application protocol (SDAP) layer.

11. The communication method according to any one of claims 5 to 10, characterized in that, The first data is the initial transmission data, and the retransmission data of the first data does not carry the first information.

12. The communication method according to claim 4, characterized in that, When the first data is local business data, the transmission resources of the first data are the first resources; when the first data is non-local business data, the transmission resources of the first data are the second resources.

13. The communication method according to claim 12, characterized in that, The transmission resources for the first data are associated with one or more of the following: The business type of the first data, wherein the business type includes local business data or non-local business data; The identifier of the second terminal device.

14. The communication method according to claim 13, characterized in that, The transmission resources of the first data are associated with the service type of the first data, and the first data also includes the identification information of the first terminal device and / or the identification information of the second terminal device.

15. The communication method according to claim 13 or 14, characterized in that, The method further includes: The first terminal device receives the second information from the first wireless access device; or, The first terminal device sends the second information to the first wireless access device; The second information is used to configure or adjust the association relationship.

16. The communication method according to claim 15, characterized in that, The second information is carried in the access layer signaling.

17. The communication method according to any one of claims 12 to 16, characterized in that, The transmission resources for the first data include one or more of the following: configuration authorization resources, hybrid automatic repeat request process, logical channel, and data radio bearer.

18. The communication method according to claim 7 or 13, characterized in that, The identification information of the second terminal device is determined based on one or more of the following: The business information corresponding to the first data; The first wireless access device indicates the identifier of one or more terminal devices, wherein the one or more terminal devices are terminal devices that the first wireless access device can reach through the local routing.

19. The communication method according to claim 18, characterized in that, The third information is used to indicate one or more of the following: the association between QoS flows of the terminal devices; the association between Protocol Data Unit (PDU) sessions of the terminal devices.

20. The communication method according to any one of claims 1 to 19, characterized in that, The first data is user plane data.

21. The communication method according to any one of claims 1 to 20, characterized in that, The first wireless access device is located within the coverage area of ​​the second wireless access device.

22. The communication method according to any one of claims 1 to 21, characterized in that, The first wireless access device is a base station or a head node.

23. The communication method according to claim 22, characterized in that, The head node is a base station or a terminal device.

24. A communication method, characterized in that, include: The first wireless access device receives first data sent by the first terminal device, wherein the first data is local service data or non-local service data.

25. The communication method according to claim 24, characterized in that, If the first data is local service data, the first data is sent from the first wireless access device to the second terminal device via local routing.

26. The communication method according to claim 24 or 25, characterized in that, If the first data is non-local service data, the first data is sent to the core network by the first wireless access device.

27. The communication method according to any one of claims 24 to 26, characterized in that, The indication method for the service type of the first data includes one or more of the following: The first information indicates that the first information was sent by the first terminal device; The transmission resources are determined based on the first data; It is determined through third information that the third information was sent by the core network equipment.

28. The communication method according to claim 27, characterized in that, The first information is used to indicate whether the first data is local business data or non-local business data.

29. The communication method according to claim 28, characterized in that, The first information is carried in the first data.

30. The communication method according to claim 28 or 29, characterized in that, The first information is also used to indicate one or more of the following: The identification information of the first terminal device; The identification information of the second terminal device.

31. The communication method according to any one of claims 28 to 30, characterized in that, The first piece of information is access layer information.

32. The communication method according to claim 31, characterized in that, The first information is carried in the header of the first protocol layer, which may be an existing protocol layer or a newly added protocol layer.

33. The communication method according to claim 32, characterized in that, The first protocol layer includes one or more of the following: physical layer, medium access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, and service data application protocol (SDAP) layer.

34. The communication method according to any one of claims 28 to 33, characterized in that, The first data is the initial transmission data, and the retransmission data of the first data does not carry the first information.

35. The communication method according to claim 27, characterized in that, When the first data is local business data, the transmission resources of the first data are the first resources; when the first data is non-local business data, the transmission resources of the first data are the second resources.

36. The communication method according to claim 35, characterized in that, The transmission resources for the first data are associated with one or more of the following: The business type of the first data, wherein the business type includes local business data or non-local business data; The identifier of the second terminal device.

37. The communication method according to claim 36, characterized in that, The transmission resources of the first data are associated with the service type of the first data, and the first data also includes the identification information of the first terminal device and / or the identification information of the second terminal device.

38. The communication method according to claim 36 or 37, characterized in that, The method further includes: The first wireless access device receives the second information sent by the first terminal device; or... The first wireless access device sends the second information to the first terminal device; The second information is used to adjust the association relationship.

39. The communication method according to claim 38, characterized in that, The second information is carried in the access layer signaling.

40. The communication method according to any one of claims 35 to 39, characterized in that, The transmission resources for the first data include one or more of the following: configuration authorization resources, hybrid automatic repeat request process, logical channel, and data radio bearer.

41. The communication method according to claim 30 or 36, characterized in that, The identification information of the second terminal device is determined based on one or more of the following: The business information corresponding to the first data; The first wireless access device indicates the identifier of one or more terminal devices, wherein the one or more terminal devices are terminal devices that the first wireless access device can reach through the local routing.

42. The communication method according to claim 27, characterized in that, The method further includes: The first wireless access device receives third information sent by the core network device, the third information being used by the first wireless access device to determine whether the first data is local service data or non-local service data.

43. The communication method according to claim 42, characterized in that, The third information is used to indicate one or more of the following: The correlation between QoS flows of terminal devices; The association between Protocol Data Unit (PDU) sessions of terminal devices.

44. The communication method according to any one of claims 24 to 43, characterized in that, The first data is user plane data.

45. The communication method according to any one of claims 24 to 44, characterized in that, The first wireless access device is located within the coverage area of ​​the second wireless access device.

46. ​​The communication method according to any one of claims 24 to 45, characterized in that, The first wireless access device is a base station or a head node.

47. The communication method according to claim 46, characterized in that, The head node is a base station or a terminal device.

48. A communication method, characterized in that, include: The core network device sends third information to the first wireless access device. The third information is used to determine whether the first data is local service data or non-local service data after the first wireless access device receives the first data from the terminal device.

49. The communication method according to claim 48, characterized in that, If the first data is the local service data, the first data is sent from the first wireless access device to the second terminal device via local routing.

50. The communication method according to claim 48 or 49, characterized in that, In the case that the first data is non-local service data, the first data is sent to the core network by the first wireless access device.

51. The communication method according to any one of claims 48 to 50, characterized in that, The third information is used to indicate one or more of the following: The correlation between QoS flows of terminal devices; The association between Protocol Data Unit (PDU) sessions of terminal devices.

52. The communication method according to any one of claims 48 to 51, characterized in that, The first data is user plane data.

53. The communication method according to any one of claims 48 to 52, characterized in that, The first wireless access device is located within the coverage area of ​​the second wireless access device.

54. The communication method according to any one of claims 48 to 53, characterized in that, The first wireless access device is a base station or a head node.

55. The communication method according to claim 54, characterized in that, The head node is a base station or a terminal device.

56. A terminal device, characterized in that, The terminal device is a first terminal device, comprising: The transceiver unit is used to send first data to the first wireless access device, wherein the first data is local service data or non-local service data.

57. The terminal device according to claim 56, characterized in that, If the first data is local service data, the first data is sent from the first wireless access device to the second terminal device via local routing.

58. The terminal device according to claim 56 or 57, characterized in that, If the first data is non-local service data, the first data is sent to the core network by the first wireless access device.

59. The terminal device according to any one of claims 56 to 58, characterized in that, The indication method for the service type of the first data includes one or more of the following: The first information indicates that the first information was sent by the first terminal device; The transmission resources are determined based on the first data; It is determined through third information that the third information was sent by the core network equipment.

60. The terminal device according to claim 59, characterized in that, The first information is used to indicate whether the first data is local business data or non-local business data.

61. The terminal device according to claim 60, characterized in that, The first information is carried in the first data.

62. The terminal device according to claim 60 or 61, characterized in that, The first information is also used to indicate one or more of the following: The identification information of the first terminal device; The identification information of the second terminal device.

63. The terminal device according to claim 61 or 62, characterized in that, The first piece of information is access layer information.

64. The terminal device according to claim 63, characterized in that, The first information is carried in the header of the first protocol layer, which may be an existing protocol layer or a newly added protocol layer.

65. The terminal device according to claim 64, characterized in that, The first protocol layer includes one or more of the following: physical layer, medium access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, and service data application protocol (SDAP) layer.

66. The terminal device according to any one of claims 60 to 65, characterized in that, The first data is the initial transmission data, and the retransmission data of the first data does not carry the first information.

67. The terminal device according to claim 59, characterized in that, When the first data is local business data, the transmission resources of the first data are the first resources; when the first data is non-local business data, the transmission resources of the first data are the second resources.

68. The terminal device according to claim 67, characterized in that, The transmission resources for the first data are associated with one or more of the following: The business type of the first data, wherein the business type includes local business data or non-local business data; The identifier of the second terminal device.

69. The terminal device according to claim 68, characterized in that, The transmission resources of the first data are associated with the service type of the first data, and the first data also includes the identification information of the first terminal device and / or the identification information of the second terminal device.

70. The terminal device according to claim 68 or 69, characterized in that, The transceiver unit is also used for: The first terminal device receives the second information from the first wireless access device; or, The first terminal device sends the second information to the first wireless access device; The second information is used to configure or adjust the association relationship.

71. The terminal device according to claim 70, characterized in that, The second information is carried in the access layer signaling.

72. The terminal device according to any one of claims 67 to 71, characterized in that, The transmission resources for the first data include one or more of the following: configuration authorization resources, hybrid automatic repeat request process, logical channel, and data radio bearer.

73. The terminal device according to claim 62 or 68, characterized in that, The identification information of the second terminal device is determined based on one or more of the following: The business information corresponding to the first data; The first wireless access device indicates the identifier of one or more terminal devices, wherein the one or more terminal devices are terminal devices that the first wireless access device can reach through the local routing.

74. The terminal device according to claim 73, characterized in that, The third information is used to indicate one or more of the following: the association between QoS flows of the terminal devices; the association between Protocol Data Unit (PDU) sessions of the terminal devices.

75. The terminal device according to any one of claims 56 to 74, characterized in that, The first data is user plane data.

76. The terminal device according to any one of claims 56 to 75, characterized in that, The first wireless access device is located within the coverage area of ​​the second wireless access device.

77. The terminal device according to any one of claims 56 to 76, characterized in that, The first wireless access device is a base station or a head node.

78. The terminal device according to claim 77, characterized in that, The head node is a base station or a terminal device.

79. A wireless access device, characterized in that, include: The transceiver unit is used to receive first data sent by the first terminal device, wherein the first data is local business data or non-local business data.

80. The wireless access device according to claim 79, characterized in that, If the first data is local service data, the first data is sent from the first wireless access device to the second terminal device via local routing.

81. The wireless access device according to claim 79 or 80, characterized in that, If the first data is non-local service data, the first data is sent to the core network by the first wireless access device.

82. The wireless access device according to any one of claims 79 to 81, characterized in that, The indication method for the service type of the first data includes one or more of the following: The first information indicates that the first information was sent by the first terminal device; The transmission resources are determined based on the first data; It is determined through third information that the third information was sent by the core network equipment.

83. The wireless access device according to claim 82, characterized in that, The first information is used to indicate whether the first data is local business data or non-local business data.

84. The wireless access device according to claim 83, characterized in that, The first information is carried in the first data.

85. The wireless access device according to claim 83 or 84, characterized in that, The first information is also used to indicate one or more of the following: The identification information of the first terminal device; The identification information of the second terminal device.

86. The wireless access device according to any one of claims 83 to 85, characterized in that, The first piece of information is access layer information.

87. The wireless access device according to claim 86, characterized in that, The first information is carried in the header of the first protocol layer, which may be an existing protocol layer or a newly added protocol layer.

88. The wireless access device according to claim 87, characterized in that, The first protocol layer includes one or more of the following: physical layer, medium access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, and service data application protocol (SDAP) layer.

89. The wireless access device according to any one of claims 83 to 88, characterized in that, The first data is the initial transmission data, and the retransmission data of the first data does not carry the first information.

90. The wireless access device according to claim 89, characterized in that, When the first data is local business data, the transmission resources of the first data are the first resources; when the first data is non-local business data, the transmission resources of the first data are the second resources.

91. The wireless access device according to claim 90, characterized in that, The transmission resources for the first data are associated with one or more of the following: The business type of the first data, wherein the business type includes local business data or non-local business data; The identifier of the second terminal device.

92. The wireless access device according to claim 91, characterized in that, The transmission resources of the first data are associated with the service type of the first data, and the first data also includes the identification information of the first terminal device and / or the identification information of the second terminal device.

93. The wireless access device according to claim 91 or 92, characterized in that, The transceiver unit is also used for: Receive the second information sent by the first terminal device; or... Send the second information to the first terminal device; The second information is used to adjust the association relationship.

94. The wireless access device according to claim 93, characterized in that, The second information is carried in the access layer signaling.

95. The wireless access device according to any one of claims 90 to 94, characterized in that, The transmission resources for the first data include one or more of the following: configuration authorization resources, hybrid automatic repeat request process, logical channel, and data radio bearer.

96. The wireless access device according to claim 85 or 91, characterized in that, The identification information of the second terminal device is determined based on one or more of the following: The business information corresponding to the first data; The first wireless access device indicates the identifier of one or more terminal devices, wherein the one or more terminal devices are terminal devices that the first wireless access device can reach through the local routing.

97. The wireless access device according to claim 96, characterized in that, The transceiver unit is also used for: The first wireless access device receives third information sent by the core network device, the third information being used to determine whether the first data is local service data or non-local service data.

98. The wireless access device according to claim 97, characterized in that, The third information is used to indicate one or more of the following: The correlation between QoS flows of terminal devices; The association between Protocol Data Unit (PDU) sessions of terminal devices.

99. The wireless access device according to any one of claims 79 to 98, characterized in that, The first data is user plane data.

100. The wireless access device according to any one of claims 79 to 99, characterized in that, The first wireless access device is located within the coverage area of ​​the second wireless access device.

101. The wireless access device according to any one of claims 79 to 100, characterized in that, The first wireless access device is a base station or a head node.

102. The wireless access device according to claim 101, characterized in that, The head node is a base station or a terminal device.

103. A core network device, characterized in that, include: The transceiver unit is configured to send third information to the first wireless access device, wherein the third information is used to determine whether the first data is local service data or non-local service data after the first wireless access device receives the first data from the terminal device.

104. The core network equipment according to claim 103, characterized in that, If the first data is the local service data, the first data is sent from the first wireless access device to the second terminal device via local routing.

105. The core network equipment according to claim 103 or 104, characterized in that, In the case that the first data is non-local service data, the first data is sent to the core network by the first wireless access device.

106. The core network equipment according to any one of claims 103 to 105, characterized in that, The third information is used to indicate one or more of the following: The correlation between QoS flows of terminal devices; The association between Protocol Data Unit (PDU) sessions of terminal devices.

107. The core network equipment according to any one of claims 103 to 106, characterized in that, The first data is user plane data.

108. The core network equipment according to any one of claims 103 to 107, characterized in that, The first wireless access device is located within the coverage area of ​​the second wireless access device.

109. The core network equipment according to any one of claims 103 to 108, characterized in that, The first wireless access device is a base station or a head node.

110. The core network equipment according to claim 109, characterized in that, The head node is a base station or a terminal device.

111. A terminal device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or send signals so that the terminal device performs the method according to any one of claims 1 to 23.

112. A wireless access device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the wireless access device performs the method according to any one of claims 24 to 47.

113. A core network device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the core network device performs the method according to any one of claims 48 to 55.

114. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the apparatus to perform the method according to any one of claims 1 to 23, or the method according to any one of claims 24 to 47, or the method according to any one of claims 48 to 55.

115. A chip, characterized in that, Includes a processor for calling a program from memory to cause the chip to perform the method according to any one of claims 1 to 23, or the method according to any one of claims 24 to 47, or the method according to any one of claims 48 to 55.

116. A non-volatile computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method according to any one of claims 1 to 23, or the method according to any one of claims 24 to 47, or the method according to any one of claims 48 to 55.

117. A computer program product, characterized in that, Includes a program that causes a computer to perform the method according to any one of claims 1 to 23, or the method according to any one of claims 24 to 47, or the method according to any one of claims 48 to 55.

118. A computer program, characterized in that, The computer program causes the computer to perform the method according to any one of claims 1 to 23, or the method according to any one of claims 24 to 47, or the method according to any one of claims 48 to 55.

Images