A communication method and apparatus

Abstract

The application relates to the communication technical field, and discloses a communication method and device. The method comprises the following steps: an access network device receives first indication information, the first indication information indicates that M sessions have an association relationship, M is an integer greater than 1; and then, the M sessions are processed according to the first indication information. In this way, when the access network device processes the M sessions, the association relationship between the M sessions is considered, so that the synchronization requirement between different sessions can be met.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and in particular to a communication method and device. BACKGROUND

[0002] Virtual reality (VR) technology is a new man-machine interaction method created with the help of computers and the latest sensor technology. VR technology integrates computer graphics technology, computer simulation technology, sensor technology, display technology and other scientific technologies, and mainly includes simulated environment, perception, natural skills and sensing devices. Simulated environment is a real-time dynamic three-dimensional stereoscopic image generated by a computer; perception means that ideal VR should have all the perceptions of a person, in addition to visual perception generated by computer graphics technology, there are auditory, tactile, force perception, motion and other perceptions, and even smell and taste, also known as multi-perception; natural skills means that the head rotation, eyes, gestures or other human body behavior actions are processed by a computer to adapt to the data of the participant's actions, and the computer responds to the user's input in real time and feeds back to the user's five senses; sensing devices means three-dimensional interactive devices.

[0003] For VR services, due to the limitation of VR head mounted device (HMD) rendering capability, the large bandwidth requirement of VR (50Mbps-1Gbps or more), and the short latency requirement of motion to photon latency of about 20ms, VR services exist in the scene of local secondary rendering. In the scene of local secondary rendering, the VR head mounted device can first send head rotation, eye, gesture and other behavior action data to the VR server, the VR server generates a simulated environment according to the data, and pre- renders the simulated environment, and then the VR server sends the pre-rendered data to the local device for secondary rendering, and then the local device sends the secondary rendered data to the VR head mounted device, and the head mounted device presents a three-dimensional stereoscopic image, and even includes auditory, tactile, force perception and motion perception.

[0004] However, further research is still needed for related implementations of scenarios involving edge computing, such as the above-mentioned local secondary rendering scenario. SUMMARY

[0005] The present application provides a communication method and device, which facilitates meeting the synchronization requirements between different sessions.

[0006] In a first aspect, an embodiment of the present application provides a communication method, which can be applied to a first access network device or a chip in the first access network device. Taking the case that the method is applied to the first access network device, in the method, the first access network device can receive first indication information, the first indication information indicating that M sessions have an association relationship, M being an integer greater than 1; and perform processing on the M sessions according to the first indication information.

[0007] By using the above method, when performing processing on the M sessions, the first access network device can consider the association relationship between the M sessions, thereby facilitating to meet the synchronization requirement between different sessions and effectively ensuring the quality of experience of users on services.

[0008] In a possible design, the processing on the M sessions includes: admitting or rejecting an establishment request of at least two sessions of the M sessions; or admitting or rejecting a modification request of at least two sessions of the M sessions.

[0009] By using the above method, the first access network device can determine whether to admit or reject the establishment request or the modification request of a session according to the association relationship between sessions, thereby effectively avoiding the problem that the first access network device admits or rejects the establishment request or the modification request of part of the sessions, and the service cannot be normally implemented.

[0010] In a possible design, the M sessions include a first session between a terminal device and an application server, a second session between the application server and a local device, and a third session between the local device and the terminal device; and the terminal device establishes a radio resource control (RRC) connection with the first access network device.

[0011] In a possible design, the method further includes: receiving second indication information and / or third indication information; the second indication information indicates that the local device performs edge computing on data in the received second session or third session; and the third indication information indicates a time length required by the local device for performing local edge computing.

[0012] In a possible design, the processing on the M sessions includes: determining that the local device performs edge computing on data in the received second session; scheduling the data in the second session at a first time, and scheduling the data in the third session at a second time after the first time; and the time interval between the first time and the second time is obtained according to the time length required by the local device for performing edge computing.

[0013] In a possible design, the M sessions are processed, including: determining that the local device performs edge computing on data in the received third session; scheduling the data in the third session at a first time, and scheduling the data in the second session at a second time after the first time; where a time interval between the first time and the second time is obtained according to a time length required for the local device to perform edge computing.

[0014] By using the method, the first access network device can schedule the data in the second session and the third session according to the time length required for edge computing, so that the service data in different sessions in the synchronous session set can be cooperatively transmitted according to a certain order and time relationship; for example, the data in the third session is scheduled at the second time after the first time, which can avoid the local device from not completing edge computing due to too early scheduling of the data in the third session, or can avoid affecting data transmission efficiency due to too late scheduling of the data in the third session.

[0015] In a possible design, the local device includes an auxiliary terminal device, or the local device includes an access network device.

[0016] In a possible design, the method further includes: sending fourth indication information to the local device, where the fourth indication information indicates that a data radio bearer (DRB) corresponding to the second session has an association relationship with a DRB corresponding to the third session.

[0017] In a possible design, the method further includes: sending the second indication information and / or the third indication information to the local device, where the second indication information indicates that the local device performs edge computing on data in the received second session or third session, and the third indication information indicates a time length required for the local device to perform local edge computing.

[0018] In a possible design, the local device includes a wireless backhaul device.

[0019] By using the method, when the local device includes a wireless backhaul device, the first access network device can send the fourth indication information, the second indication information, and / or the third indication information to the local device, so that the local device can process the second session and the third session based on the fourth indication information, the second indication information, and / or the third indication information.

[0020] In a possible design, the method further includes: determining that the local device performs edge computing on the received data in the second session; sending, to the local device, first configuration information, where the first configuration information includes a first DRX cycle in which the local device receives data in the second session, the first DRX cycle is the same as a transmission cycle of the data in the second session, and a start offset of the first DRX cycle is aligned with a start offset of the data in the second session; and sending, to the terminal device, second configuration information, where the second configuration information includes a second DRX cycle in which the terminal device receives data in the first session, the second DRX cycle is the same as the first DRX cycle, and a time interval between a start offset of the second DRX cycle and a start offset of the first DRX cycle is obtained according to a time length required for the edge computing performed by the local device.

[0021] In a possible design, the method further includes: determining that the local device performs edge computing on the received data in the third session; sending, to the local device, first configuration information, where the first configuration information includes a first DRX cycle in which the local device receives data in the third session, the first DRX cycle is the same as a transmission cycle of the data in the third session, and a start offset of the first DRX cycle is aligned with a start offset of the data in the third session; and sending, to the terminal device, second configuration information, where the second configuration information includes a second DRX cycle in which the terminal device receives data in the first session, the second DRX cycle is the same as the first DRX cycle, and a time interval between a start offset of the second DRX cycle and a start offset of the first DRX cycle is obtained according to a round-trip time; where the round-trip time is a time interval between a sending time of first data sent by the terminal device through the third session and a receiving time of second data received by the terminal device through the first session, and the second data is obtained according to the first data.

[0022] In a possible design, the method further includes: sending, to the terminal device, fifth indication information, where the fifth indication information indicates the round-trip time; where the round-trip time is a time interval between a sending time of first data sent by the terminal device through the third session and a receiving time of second data received by the terminal device through the first session, and the second data is obtained according to the first data; or the round-trip time is a time interval between a sending time of third data sent by the terminal device through the first session and a receiving time of fourth data received by the terminal device through the third session, and the fourth data is obtained according to the third data.

[0023] By sending the fifth indication information to the terminal device, the terminal device can perform power saving and other related optimization according to the round-trip time.

[0024] In a possible design, the receiving the first indication information includes: receiving the first indication information from the core network device or a second access network device; the second access network device is a source access network device of the terminal device, and the first access network device is a target access network device of the terminal device.

[0025] In a possible design, the first indication information includes M pieces of association information corresponding to the M sessions respectively, and / or, identification information of the local device; the M pieces of association information are the same.

[0026] In a possible design, the M sessions include a first session, and the association information corresponding to the first session includes type information of the first session and / or an association identifier of the first session; the type information of the first session is used to indicate that the type of the first session is separate rendering or segmented calculation.

[0027] In a possible design, the method further includes: receiving sixth indication information, the sixth indication information indicating that the M sessions are no longer associated; and releasing resources of the second session and resources of the third session according to the sixth indication information.

[0028] By using the method, it can be switched from edge computing to non-edge computing, so that the terminal device can freely select a corresponding mode under different working modes (such as with or without a connected power supply, with or without an externally hung strong computing power device, and the like), while guaranteeing service experience and user experience.

[0029] In a second aspect, an embodiment of the present application provides a communication method, which can be applied to a first core network device or a chip in the first core network device. For example, the method is applied to the first core network device, in which the first core network device can acquire first indication information, the first indication information indicating that M sessions have an association relationship, M being an integer greater than 1; and the first core network device can send the first indication information to an access network device.

[0030] In a possible design, the M sessions include a first session between a terminal device and an application server, a second session between the application server and a local device, and a third session between the local device and the terminal device; the terminal device has an RRC connection with the access network device.

[0031] In a possible design, the method further includes: sending second indication information and / or third indication information to the access network device; the second indication information indicates that the local device performs edge computing on data received in the second session or the third session, and the third indication information indicates a time length required by the local device for local edge computing.

[0032] In a possible design, the obtaining the first indication information includes: obtaining the first indication information from the terminal device; or obtaining the first indication information from the second core network device.

[0033] In a possible design, the obtaining the first indication information from the terminal device includes: receiving a first request message from the terminal device, where the first request message is used to request establishment or modification of the M sessions or a first session in the M sessions, and the request message includes the first indication information.

[0034] In a possible design, the method further includes: sending sixth indication information to the access network device, where the sixth indication information indicates that the M sessions are no longer associated.

[0035] In a possible design, the method further includes: receiving a second request message from the terminal device, where the second request message is used to request modification of the first session in the M sessions, the second request message includes seventh indication information, the seventh indication information indicates that the first session is no longer associated with other sessions in the M sessions, and the sixth indication information is determined according to the second request message.

[0036] In a third aspect, an embodiment of the present application provides a communication method, which can be applied to a local device or a chip in the local device, and the local device can include a wireless backhaul device. Taking the case where the method is applied to the local device as an example, in the method, the local device receives fourth indication information from an access network device, where the fourth indication information indicates that a DRB corresponding to a second session has an association relationship with a DRB corresponding to a third session; and the local device processes the second session and the third session according to the second indication information.

[0037] In a possible design, the second session is a session between an application server and the local device, and the third session is a session between the local device and a terminal device.

[0038] In a possible design, the method further includes: receiving second indication information and / or third indication information from the access network device, where the second indication information indicates that the local device performs edge computing on data received in the second session or the third session, and the third indication information indicates a time length required by the local device for local edge computing.

[0039] In a possible design, the processing the second session and the third session includes: determining that the local device performs edge computing on data received in the second session; scheduling the data in the second session at a first time and scheduling data in the third session at a second time after the first time; and the time interval between the first time and the second time is obtained according to the time length required by the local device for edge computing.

[0040] In a possible design, the processing of the second session and the third session includes: determining that the local device performs edge computing on data in the received third session; and scheduling the data in the third session at a first time and scheduling the data in the second session at a second time after the first time, where a time interval between the first time and the second time is obtained according to a time length required for the local device to perform edge computing.

[0041] In a possible design, the method further includes: receiving first configuration information from the access network device, where the first configuration information is used to configure a first DRX cycle of the local device for receiving data in the second session, the first DRX cycle is the same as a transmission cycle of the data in the second session, and a start offset of the first DRX cycle is aligned with a start offset of the data in the second session; and receiving second configuration information from the access network device and sending the second configuration information to the terminal device, where the second configuration information includes a second DRX cycle of the terminal device for receiving data in the third session, the second DRX cycle is the same as the first DRX cycle, and a time interval between a start offset of the second DRX cycle and a start offset of the first DRX cycle is obtained according to a time length required for the local device to perform edge computing.

[0042] In a possible design, the method further includes: receiving first configuration information from the access network device, where the first configuration information is used to configure a first DRX cycle of the local device for receiving data in the third session, the first DRX cycle is the same as a transmission cycle of the data in the third session, and a start offset of the first DRX cycle is aligned with a start offset of the data in the third session; and receiving second configuration information from the access network device and sending the second configuration information to the terminal device, where the second configuration information includes a second DRX cycle of the terminal device for receiving data in the first session, the second DRX cycle is the same as the first DRX cycle, and a time interval between a start offset of the second DRX cycle and a start offset of the first DRX cycle is obtained according to a round trip time, where the round trip time is a time interval between a sending time of first data sent by the terminal device through the third session and a receiving time of second data received by the terminal device through the first session, and the second data is obtained according to the first data.

[0043] In a fourth aspect, an embodiment of the present application provides a communication method, which can be applied to a terminal device or a chip in the terminal device. In the case of the method being applied to the terminal device, in the method, the terminal device determines that M sessions have an association relationship, and sends a first request message, where the first request message is used to request to establish or modify the M sessions or a first session in the M sessions, and the request message includes first indication information, and the first indication information indicates that the M sessions have the association relationship.

[0044] In a possible design, the M sessions include a first session between the terminal device and the application server, a second session between the application server and the local device, and a third session between the local device and the terminal device; and the terminal device has established an RRC connection with the access network device.

[0045] In a possible design, the method further includes: sending a second request message, where the second request message is used to request modification of the first session, and the second request message includes seventh indication information, where the seventh indication information indicates that the first session is no longer associated with other sessions in the M sessions.

[0046] It should be noted that the method described in the second aspect, the third aspect, and the fourth aspect corresponds to the method described in the first aspect, and the beneficial effects of the related technical features in the method described in the second aspect, the third aspect, and the fourth aspect can be referred to the description of the first aspect, and will not be repeated here.

[0047] In the fifth aspect, an embodiment of the present application provides a communication system, which can include a first access network device and a core network device; where the first access network device can be configured to perform the method in any possible design or implementation manner of the first aspect, and the core network device can be configured to perform the method in any possible design or implementation manner of the second aspect.

[0048] In a possible design, the communication system can further include a local device, and the local device can be configured to perform the method in any possible design or implementation manner of the third aspect.

[0049] In a possible design, the communication system can further include a terminal device, and the terminal device can be configured to perform the method in any possible design or implementation manner of the fourth aspect.

[0050] In the sixth aspect, the present application provides a communication apparatus, which can be an access network device (such as the first access network device) or a chip arranged in the access network device. The communication apparatus has the function of implementing the first aspect, for example, the communication apparatus includes a module or unit or means corresponding to the operation of the first aspect, which can be implemented by software or hardware, or the hardware can execute the corresponding software.

[0051] In a possible design, the communication apparatus includes a processing unit and a communication unit, where the communication unit can be configured to transceive signals to implement communication between the communication apparatus and other apparatuses, for example, the communication unit is configured to receive configuration information from a terminal device; and the processing unit can be configured to perform some internal operations of the communication apparatus. The functions performed by the processing unit and the communication unit can correspond to the operations described in the first aspect.

[0052] In an example, the communication apparatus includes a processor. The processor can be configured to couple with a memory. The memory can store necessary computer programs or instructions for implementing the functions of the above first aspect. The processor can execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, the communication apparatus can implement the method in any possible design or implementation manner of the above first aspect.

[0053] In an example, the communication apparatus includes a processor and a memory. The memory can store necessary computer programs or instructions for implementing the functions of the above first aspect. The processor can execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, the communication apparatus can implement the method in any possible design or implementation manner of the above first aspect.

[0054] In an example, the communication apparatus includes a processor and an interface circuit. The processor can be configured to communicate with other apparatuses via the interface circuit, and execute the method in any possible design or implementation manner of the above first aspect.

[0055] In a seventh aspect, a communication apparatus is provided. The communication apparatus can be a core network device (e.g., a first core network device) or a chip arranged in a core network device. The communication apparatus can implement the functions of the above second aspect. For example, the communication apparatus includes a module or unit or means for performing the operations of the above second aspect. The functions of the module or unit or means can be implemented by software or by hardware, and also can be implemented by executing corresponding software by hardware.

[0056] In an example, the communication apparatus includes a processing unit and a communication unit. The communication unit can be configured to transmit and receive signals, so as to implement the communication between the communication apparatus and other apparatuses. For example, the communication unit can be configured to transmit system information to a terminal device. The processing unit can be configured to perform some internal operations of the communication apparatus. The functions performed by the processing unit and the communication unit can correspond to the operations of the above second aspect.

[0057] In an example, the communication apparatus includes a processor. The processor can be configured to couple with a memory. The memory can store necessary computer programs or instructions for implementing the functions of the above second aspect. The processor can execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, the communication apparatus can implement the method in any possible design or implementation manner of the above second aspect.

[0058] In a possible design, the communication apparatus includes a processor and a memory. The memory can store computer programs or instructions necessary for implementing the functions of the second aspect. The processor can execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, the communication apparatus can implement the method in any possible design or implementation manner of the second aspect.

[0059] In a possible design, the communication apparatus includes a processor and an interface circuit. The processor is configured to communicate with other apparatuses through the interface circuit, and implement the method in any possible design or implementation manner of the second aspect.

[0060] It can be understood that, in the sixth aspect or the seventh aspect, the processor can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, or the like. When implemented by software, the processor can be a general-purpose processor, which implements the functions by reading software codes stored in a memory. In addition, the processor can be one or more, and the memory can be one or more. The memory can be integrated with the processor, or the memory and the processor can be separately arranged. In a specific implementation process, the memory and the processor can be integrated on the same chip, or can be separately arranged on different chips. The type of the memory and the arrangement manner of the memory and the processor are not limited in the embodiments of the present application.

[0061] In an eighth aspect, the present application provides a computer readable storage medium, which stores computer readable instructions. When a computer reads and executes the computer readable instructions, the computer can execute the method in any possible design of the first aspect to the fourth aspect.

[0062] In a ninth aspect, the present application provides a computer program product. When a computer reads and executes the computer program product, the computer can execute the method in any possible design of the first aspect to the fourth aspect.

[0063] In a tenth aspect, the present application provides a chip. The chip includes a processor, which is coupled with a memory and configured to read and execute software programs stored in the memory, so as to implement the method in any possible design of the first aspect to the fourth aspect.

[0064] These and other aspects of the present application will become more apparent from the following description of the embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0065] Figure 1 A network architecture suitable for the embodiments of the present application is shown in the following figure;

[0066] Figure 2a An example diagram of a protocol layer structure between a terminal device and a network device is provided for an embodiment of the present application.

[0067] Figure 2b An example diagram of a CU-DU separation architecture is provided for an embodiment of the present application.

[0068] Figure 2c An example diagram of another CU-DU separation architecture is provided for an embodiment of the present application.

[0069] Figure 2d An example diagram of an air interface protocol stack distribution is provided for an embodiment of the present application.

[0070] Figure 3a An example diagram of session 1, session 2 and session 3 in scenario 1 is provided for an embodiment of the present application.

[0071] Figure 3b An example diagram of session 1, session 2 and session 3 in scenario 2 is provided for an embodiment of the present application.

[0072] Figure 3c An example diagram of a PDU session establishment process is provided for an embodiment of the present application.

[0073] Figure 3d An example diagram of four sessions is provided for an embodiment of the present application.

[0074] Figure 4a An example diagram of session 1, session 2 and session 3 in a certain scenario is provided for an embodiment of the present application.

[0075] Figure 4b An example diagram of session 1, session 2 and session 3 in a certain scenario is provided for an embodiment of the present application.

[0076] Figure 4c An example diagram of session 1, session 2 and session 3 in a certain scenario is provided for an embodiment of the present application.

[0077] Figure 5 An example diagram of a process corresponding to a communication method is provided for an embodiment of the present application.

[0078] Figure 6 An example diagram of a process corresponding to a communication method is provided for an embodiment of the present application.

[0079] Figure 7 An example diagram of a process corresponding to a communication method is provided for an embodiment of the present application.

[0080] Figure 8 An example diagram of a process corresponding to a communication method is provided for an embodiment of the present application.

[0081] Figure 9This is a flowchart illustrating the communication method provided in Embodiment 4 of this application.

[0082] Figure 10 This is a flowchart illustrating the communication method provided in Embodiment 5 of this application.

[0083] Figure 11 This is a flowchart illustrating the communication method provided in Embodiment Six of this application;

[0084] Figure 12 The following are possible exemplary block diagrams of the apparatus involved in the embodiments of this application;

[0085] Figure 13 This is a schematic diagram of the structure of an access network device provided in an embodiment of this application;

[0086] Figure 14 This is a schematic diagram of the structure of a core network device provided in an embodiment of this application. Detailed Implementation

[0087] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0088] Figure 1 This is a schematic diagram of a network architecture applicable to an embodiment of this application. For example... Figure 1 As shown, a terminal device can access a wireless network to obtain services from an external network (e.g., a data network (DN)) or to communicate with other devices, such as other terminal devices. This wireless network includes a radio access network ((R)AN) and a core network (CN). The (R)AN (hereinafter referred to as RAN) is used to connect the terminal device to the wireless network, while the CN is used to manage the terminal device and provide a gateway for communication with the DN.

[0089] The following sections respectively address... Figure 1 The terminal equipment, RAN, CN, and DN involved are described in detail.

[0090] I. Terminal Equipment

[0091] A terminal device includes a device that provides voice and / or data connectivity to a user, e.g., a handheld phone, a device that connects to a wireless modem, etc. The terminal device can include a device that communicates with a core network via a radio access network (RAN), exchanging voice and / or data with the RAN. The terminal device can include a user equipment (UE), a wireless terminal device, a mobile terminal device, a device-to-device (D2D) terminal device, a vehicle to everything (V2X) terminal device, a machine-to-machine / Machine-Type Communications (M2M / MTC) terminal device, an internet of things (IoT) terminal device, a subscriber unit, a subscriber station, a mobile station, a remote station, an access point (AP), a remote terminal, an access terminal, a user terminal, a user agent, or a user equipment, etc. For example, it can include a mobile telephone (also known as a "cellular" telephone), a computer with a mobile terminal device, a portable, pocket, hand-held, computer-included, or car-mounted mobile device, etc. For example, it can include a personal communication service (PCS) phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), etc. It can also include a restricted device, e.g., a device with lower power consumption or limited storage capacity or limited computing capability, etc. For example, it can include a bar code, a radio frequency identification (RFID), a sensor, a global positioning system (GPS), a laser scanner, etc. information sensing device.

[0092] By way of example and not limitation, in embodiments of the present application, the terminal device can also be a VR device, an augmented reality (AR) device, a cloud gaming device, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in remote surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc.

[0093] The VR device includes a VR glass, a VR head, a VR box, etc. A user can experience VR application services such as a VR video and a VR game through the VR device, and obtain immersive scene experience. The wireless terminal in the smart city can include a monitoring camera, which can trigger further actions such as reporting to the police station and uploading the recently captured video when capturing a specific object or event.

[0094] In the embodiments of the present application, the device for implementing the function of the terminal device can be a terminal device, or a device capable of supporting the terminal device to implement the function, such as a chip system or a combination device or component capable of implementing the function of the terminal device, which can be installed in the terminal device. In the embodiments of the present application, the chip system can be composed of a chip, or can include a chip and other discrete devices. In the technical solutions provided in the embodiments of the present application, the device for implementing the function of the terminal is taken as an example of the terminal device to describe the technical solutions provided in the embodiments of the present application.

[0095] II. RAN

[0096] The RAN can include one or more RAN devices, and the interface between the RAN device and the terminal device can be a Uu interface (or an air interface). Of course, in future communications, the names of these interfaces can remain unchanged, or can be replaced by other names, which are not limited in the present application.

[0097] The RAN device is a node or device for accessing the terminal device to the wireless network, and the RAN device can also be referred to as a radio access network device or an access network device. The RAN device includes, but is not limited to, a new generation node B (gNB) in a 5G communication system, an evolved node B (eNB), a next generation evolved node B (ng-eNB), a wireless backhaul device, a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home evolved node B (HeNB) or a home node B (HNB), a baseband unit (BBU), a transmitting and receiving point (TRP), a transmitting point (TP), a mobile switching center, etc.

[0098] In an embodiment of the present application, the device for implementing the function of the access network device can be the access network device, or can be a device capable of supporting the access network device to implement the function, such as a chip system or a combined device or component that can implement the function of the access network device, and the device can be installed in the access network device. In the technical solution provided in the embodiment of the present application, the device for implementing the function of the access network device is taken as an example of the access network device to describe the technical solution provided in the embodiment of the present application.

[0099] (1) Protocol layer structure

[0100] The communication between the RAN device and the terminal device follows a certain protocol layer structure. For example, the control plane protocol layer structure can include a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a media access control (MAC) layer, and a physical layer; and the user plane protocol layer structure can include a PDCP layer, an RLC layer, a MAC layer, and a physical layer. In a possible implementation, the PDCP layer can further include a service data adaptation protocol (SDAP) layer.

[0101] Taking the data transmission between the access network device and the terminal device as an example, the data transmission needs to pass through the user plane protocol layer, such as the SDAP layer, the PDCP layer, the RLC layer, the MAC layer, and the physical layer, which can also be collectively referred to as the access layer. Illustratively, the access network device and the terminal device transmit data by establishing at least one data radio bearer (DRB), and each DRB can correspond to a set of function entities, such as including a PDCP layer entity, at least one RLC layer entity corresponding to the PDCP layer entity, at least one MAC layer entity corresponding to the at least one RLC layer entity, and at least one physical layer entity corresponding to the at least one MAC layer entity. It should be noted that the access network device and the terminal device can also transmit signaling by establishing at least one signaling radio bearer (SRB), and the DRB and the SRB can be collectively referred to as a radio bearer (RB).

[0102] Taking the downlink data transmission as an example, Figure 2a a schematic diagram of the transmission of the downlink data between layers, Figure 2aThe downward arrow indicates data transmission, and the upward arrow indicates data reception. After the SDAP layer entity obtains data from the upper layer, the data can be mapped to the PDCP layer entity of the corresponding DRB according to the quality of service flow identifier (QoS flow indicator, QFI) of the data, the PDCP layer entity can transmit the data to at least one RLC layer entity corresponding to the PDCP layer entity, and then the data is transmitted to the corresponding MAC layer entity by the at least one RLC layer entity, and then a transport block is generated by the MAC layer entity, and then the data is wirelessly transmitted by the corresponding physical layer entity. The data is encapsulated in each layer. The data received by a layer from the upper layer of the layer is regarded as a service data unit (SDU) of the layer, and after layer encapsulation, it becomes a protocol data unit (PDU) and is transmitted to the next layer. For example, the data received by the PDCP layer entity from the upper layer is called a PDCP SDU, and the data transmitted by the PDCP layer entity to the lower layer is called a PDCP PDU; the data received by the RLC layer entity from the upper layer is called an RLC SDU, and the data transmitted by the RLC layer entity to the lower layer is called an RLC PDU. Among them, the data can be transmitted between different layers through corresponding channels, such as the logical channel (LCH) between the RLC layer entity and the MAC layer entity, and the transport channel between the MAC layer entity and the physical layer entity.

[0103] Exemplarily, according to Figure 2a It can also be seen that the terminal device further has an application layer and a non-access layer; wherein the application layer can be used to provide services to the application program installed in the terminal device, for example, the downlink data received by the terminal device can be transmitted to the application layer by the physical layer in turn, and then provided to the application program by the application layer; for example, the application layer can obtain the data generated by the application program, and transmit the data to the physical layer in turn and send it to other communication devices. The non-access layer can be used to forward user data, such as forwarding the uplink data received from the application layer to the SDAP layer or forwarding the downlink data received from the SDAP layer to the application layer.

[0104] (2) CU and DU

[0105] In embodiments of the present application, the RAN device can include one or more centralized units (CU) and one or more distributed units (DU), and the plurality of DUs can be centrally controlled by one CU. As an example, the interface between the CU and the DU can be referred to as the F1 interface, where the control panel (CP) interface can be F1-C and the user panel (UP) interface can be F1-U. The CU and the DU can be divided according to the protocol layer of the wireless network, for example Figure 2b As shown, the functions of the PDCP layer and the protocol layer above the PDCP layer are arranged in the CU, and the functions of the protocol layer below the PDCP layer (such as the RLC layer and the MAC layer) are arranged in the DU.

[0106] It can be understood that the above-mentioned processing functions of the CU and the DU according to the protocol layer division are only an example, and can also be divided in other ways, such as the functions of the protocol layer above the RLC layer are arranged in the CU, and the functions of the protocol layer below the RLC layer are arranged in the DU, or the CU or the DU can be divided into more protocol layer functions, or the CU or the DU can also be divided into partial processing functions of the protocol layer. In one design, part of the functions of the RLC layer and the functions of the protocol layer above the RLC layer are arranged in the CU, and the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer are arranged in the DU. In another design, the functions of the CU or the DU can also be divided according to the service type or other system requirements, for example, according to the delay, the functions that need to meet the delay requirement of the processing time are arranged in the DU, and the functions that do not need to meet the delay requirement are arranged in the CU. In another design, the CU can also have one or more functions of the core network. For example, the CU can be arranged on the network side for centralized management; the DU can have multiple radio frequency functions, or the radio frequency function can be remotely arranged. Embodiments of the present application do not limit this.

[0107] For example, the functions of the CU can be implemented by one entity, or can also be implemented by different entities. For example, as shown in FIG. 2, the CU can include a radio resource control (RRC) layer, a service data adaptation protocol (SDAP) layer, and a PDCP layer, and the RRC layer, the SDAP layer, and the PDCP layer can be implemented by different entities. Figure 2cAs shown, the functions of the CU can be further split, i.e., the control plane and the user plane are separated and implemented by different entities, respectively, a control plane CU entity (i.e., a CU-CP entity) and a user plane CU entity (i.e., a CU-UP entity), which can be coupled with the DU to jointly complete the functions of the RAN device. The interface between the CU-CP entity and the CU-UP entity can be an E1 interface, the interface between the CU-CP entity and the DU can be an F1-C interface, and the interface between the CU-UP entity and the DU can be an F1-U interface. One DU and one CU-UP can be connected to one CU-CP. Under the control of the same CU-CP, one DU can be connected to multiple CU-UPs, and one CU-UP can be connected to multiple DUs.

[0108] Based on Figure 2c , Figure 2d is a schematic diagram of an air interface protocol stack. As shown, for the user plane and the control plane, the air interface protocol stack can be RLC, MAC, and PHY at the DU, and PDCP and above protocol layers at the CU. Figure 2d

[0109] It should be noted that: in the architecture shown in the above Figure 2b to Figure 2d , the signaling generated by the CU can be sent to the terminal device through the DU, or the signaling generated by the terminal device can be sent to the CU through the DU. The DU can not analyze the signaling but directly encapsulate and transmit it to the terminal device or the CU through the protocol layer. In the following embodiments, if the transmission of such signaling between the DU and the terminal device is involved, the transmission or reception of the signaling by the DU includes this scenario. For example, the RRC or PDCP layer signaling will eventually be processed as physical layer data and sent to the terminal device, or be converted from the received physical layer data. In this architecture, the RRC or PDCP layer signaling can also be considered as being sent by the DU, or by the DU and the radio frequency device.

[0110] (3) Wireless backhaul device

[0111] The above Figure 1 ​In the illustrated architecture, the access network device can include a host node and one or more wireless backhaul devices (not shown). The terminal device accesses the host node through one or more wireless backhaul devices. In the 5G communication system, the wireless backhaul device can be referred to as an integrated access and backhaul (IAB) node; in the long term evolution (LTE) communication system, the wireless backhaul device can be referred to as a relay node (RN). Of course, in other communication systems, the wireless backhaul device can also have different names, which are not limited here.

[0112] The uplink data of the terminal device can be transmitted by one or more IAB nodes to the host node through a wireless backhaul link, and the downlink data of the terminal device can be transmitted by one or more IAB nodes to the terminal device through a wireless backhaul link. Among them, the host node can be referred to as an IAB donor or a donor gNodeB (DgNB) or a base station.

[0113] For example, if the terminal device and the base station include one IAB node, it can be understood as a one-level IAB node; if the terminal device and the base station include multiple IAB nodes, it can be understood as a multi-level IAB node (or a multi-hop IAB node). For a multi-hop IAB node, the last hop node of a certain IAB node can refer to the node that receives the data packet last in the wireless backhaul link containing the node before the node; the next hop node of a certain IAB node can refer to the node that receives the data packet first in the wireless backhaul link containing the node after the node.

[0114] III. CN

[0115] One or more CN devices can be included in the CN. For example, in the 5G communication system, the CN can include an access and mobility management function (AMF) network element, a session management function (SMF) network element, a user plane function (UPF) network element, a policy control function (PCF) network element, a unified data management (UDM) network element, and an application function (AF) network element.

[0116] The AMF network element is a control plane network element provided by the operator network, responsible for access control and mobility management of terminal devices accessing the operator network, for example, including functions such as mobile state management, allocation of user temporary identity, authentication and authorization of users, etc.

[0117] The SMF network element is a control plane network element provided by the operator network, responsible for managing PDU sessions of terminal devices. A PDU session is a channel for transmitting PDUs, and terminal devices need to transmit PDUs with DN through the PDU session. The PDU session is responsible for establishment, maintenance and deletion, etc. by the SMF network element. The SMF network element includes session management (such as session establishment, modification and release, including maintenance of tunnels between UPF and RAN), selection and control of UPF network elements, selection of service and session continuity (SSC) mode, roaming and other session-related functions.

[0118] The UPF network element is a gateway provided by the operator, which is a gateway for communication between the operator network and the DN. The UPF network element includes functions related to the user plane, such as data packet routing and transmission, packet detection, quality of service (QoS) processing, lawful interception, uplink packet detection, and downlink data packet storage.

[0119] The PCF network element is a control plane function provided by the operator, which is used to provide policies for PDU sessions to the SMF network element. The policy can include charging-related policies, QoS-related policies, and authorization-related policies, etc.

[0120] The UDM network element is a control plane network element provided by the operator, responsible for storing information such as subscriber permanent identifier (SUPI) and subscription data of subscribed users in the operator network.

[0121] The AF network element is a functional network element that provides various service services, and can interact with the core network through other network elements, and can interact with the policy management framework for policy management.

[0122] In addition, although not shown, other possible network elements in the CN can also be included, such as a network exposure function (NEF) and a unified data repository (UDR) network element.

[0123] In the embodiments of this application, the device for implementing the function of the core network device can be a core network device, or a device capable of supporting the core network device to implement the function, such as a chip system or a combination device or component that can implement the function of the core network device, which can be installed in the core network device. In the technical solutions provided in the embodiments of this application, the device for implementing the function of the core network device is taken as an example to describe the technical solutions provided in the embodiments of this application.

[0124] In addition, in the embodiments of this application, the access network device, the wireless backhaul device, the core network device and the like can be collectively referred to as a network device for ease of description.

[0125] IV. DN

[0126] The DN can also be referred to as a packet data network (PDN), which is a network located outside the operator network. The operator network can access multiple DNs, and various application servers (such as VR servers) corresponding to various services can be deployed in the DN to provide various possible services for terminal devices. Among them, the application server can be provided with an application layer that is equivalent to the application layer of the terminal device.

[0127] Figure 1 Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface sequence numbers. The meanings of these interface sequence numbers can be referred to the meanings defined in the related standard protocols, which are not limited herein.

[0128] It can be understood that, Figure 1 The 5G communication system is taken as an example for illustration, and the solutions in the embodiments of this application can also be applicable to other possible communication systems, such as the LTE communication system or the 6th generation (6G) communication system in the future. The above-mentioned network elements or functions can be network elements in a hardware device, or software functions running on a dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform). Optionally, the above-mentioned network elements or functions can be implemented by one device, or can be implemented by multiple devices together, or can be a functional module in a device, and the embodiments of this application do not make a specific limitation.

[0129] The above-mentioned Figure 1 The network architecture illustrated can support various possible service scenarios, and two possible scenarios are described below.

[0130] (1) Scenario 1

[0131] The above-mentioned Figure 1The terminal device shown in the figure is a VR headset. In the local secondary rendering scene, the VR headset can be connected to the VR server through the access network device, and the posture information of the VR headset and eyeball, etc. is sent to the VR server. The VR server generates a VR scene according to the posture information, and pre-renders a VR viewport in the VR scene to generate VR media data and optional VR rendering metadata. Further, the VR server can send the VR media data and optional VR rendering metadata to the local device for local secondary rendering through the mobile network. According to the latest posture information of the VR headset and eyeball received from the VR headset or according to the VR rendering metadata, the local device performs secondary rendering on the received VR media data to generate new VR media data, and then sends the secondary rendered new VR media data to the HMD for display. For detailed VR processing process, please refer to the 3rd generation partnership project (3GPP) technical report (TR) 26.928 version 16.0.0.

[0132] In the 5G communication system, in order to complete the above rendering process, three sessions can be established, i.e. session 1 between the VR headset and the VR server, session 2 between the VR server and the local device, and session 3 between the local device and the VR headset. See Figure 3a The arrow can represent the data transmission direction. The VR headset sends the posture information of the VR headset and eyeball to the VR server through session 1. The VR server sends the VR media data and optional VR rendering metadata to the local device for local secondary rendering through session 2. The local device sends the secondary rendered new VR media data to the VR headset through session 3, and optionally, the VR headset can send the latest posture information of the VR headset and eyeball to the local device through session 3.

[0133] As can be seen from the above description, for VR services, there is a synchronization requirement for session 1, session 2 and session 3, such as the need to establish three sessions at the same time, so as to ensure effective transmission of data.

[0134] (2) Scene 2

[0135] The above Figure 1The terminal device shown in the figure is a monitoring camera in a smart city. The monitoring camera can need to perform image recognition in order to trigger further actions such as reporting to the police, uploading the latest captured video, etc. when a certain object or event is captured. However, image recognition requires very complex calculations (such as image recognition methods using artificial intelligence), and roadside monitoring cameras usually do not have such computing power or only have very simple computing power. At this time, part or all of the image recognition related calculations need to be offloaded to the base station and / or cloud server for calculation. However, frequently uploading images to the base station and / or cloud server requires a lot of mobile network bandwidth. Therefore, one possible approach is that the monitoring camera, the local device and the cloud server perform part of the image recognition calculation in turn, and finally the cloud server gives the final recognition result and returns the result to the monitoring camera.

[0136] Similarly, in a 5G communication system, in order to complete the above image recognition process, three sessions can be established, i.e. session 3 between the monitoring camera and the local device, session 2 between the local device and the cloud server, and session 1 between the cloud server and the monitoring camera; see Figure 3b , wherein the arrows can represent the data transmission direction. The monitoring camera sends image data and / or calculation context information to the local device through session 3, which is the image or the image data processed by the monitoring camera; the local device sends image data and / or calculation context information to the cloud server through session 2, which is the image data further processed by the local device; and the cloud server sends the image recognition result to the monitoring camera through session 1.

[0137] As can be seen from the above description, for image recognition services, there is also a synchronization requirement for session 1, session 2 and session 3, such as the need to establish three sessions at the same time, so as to ensure effective data transmission.

[0138] Taking the sessions involved in the above two scenarios as PDU sessions for example, Figure 3c The current PDU session establishment process in the 3GPP protocol is shown in the figure Figure 3c , which can include:

[0139] S301, the SMF network element sends a PDU session resource setup request message to the access network device through the AMF network element, and the PDU session resource setup request message includes the identifier of one or more PDU sessions to be established for the terminal device, such as PDU session 1, PDU session 2 and PDU session 3.

[0140] S302, the access network device receives the PDU session resource establishment request message, and performs admission control on the PDU session according to the PDU session resource establishment request message.

[0141] Exemplarily, the access network device can admit the establishment request of part or all of the PDU sessions in the PDU session resource establishment request message, or can also reject the establishment request of part or all of the PDU sessions in the PDU session resource establishment request message. For example, the access network device admits the establishment request of PDU session 1 and PDU session 2, and rejects the establishment request of PDU session 3.

[0142] S303, the access network device sends a PDU session resource establishment response message to an SMF network element through an AMF network element.

[0143] Here, the PDU session resource establishment response message can include a PDU session establishment failure list (PDU Session Failed to Setup List), and the PDU session establishment failure list includes the identity of the rejected PDU session, such as the identity of PDU session 3.

[0144] According to the above S301 to S303, it can be seen that in the PDU session establishment process, the access network device can reject the establishment request of part or all of the PDU sessions of the terminal device. However, for the two scenarios described above, such as for VR services, if the access network device rejects the establishment request of a certain session in session 1, session 2 and session 3, the VR service cannot be normally implemented.

[0145] Based on this, in the embodiments of the present application, a synchronous session set is introduced, and multiple sessions belonging to the same synchronous session set have an association relationship, so that the access network device can process multiple sessions based on the association relationship between the multiple sessions to meet the synchronization requirements between different sessions.

[0146] The related technical features involved in the embodiments of the present application will be explained first. It should be noted that these explanations are to make the embodiments of the present application easier to understand, and should not be regarded as limiting the scope of protection required by the present application.

[0147] I. Session

[0148] The session involved in the embodiments of the present application can be used to provide a connectivity service between the first device and the second device, or in other words, can be used to implement data transmission between the first device and the second device. For example, the first device and the second device can be a terminal device and an application server respectively, or the first device and the second device can also be different terminal devices (for example, terminal device 1 and terminal device 2), or the first device and the second device can also be a terminal device and a network device respectively, or the first device and the second device can also be other possible devices, and the specific implementation is not limited.

[0149] In one example, the session can refer to a PDU session, or can also refer to an Internet protocol (IP) connectivity access network (IP-CAN) session or a traffic detection function (TDF) session, or other possible sessions, and the specific implementation is not limited. The IP-CAN session is an association between a terminal device and an IP network, which can be identified by an IP address of the terminal device and available identification information of the terminal device.

[0150] It should be noted that: (1) in the above scenario 1 or scenario 2, the embodiments of the present application are described by taking an example of establishing three different sessions (i.e., session 1, session 2 and session 3) for the same service, but in practice, it can also be understood that: one session is established for the same service, and the session includes three parts, such as the session includes the part between the terminal device and the application server, the part between the application server and the local device, and the part between the local device and the terminal device; or two sessions are established for the same service, such as the above session 1 is understood as one session, and the above session 2 and session 3 are combined into one session including two parts (i.e., the part between the application server and the local device, and the part between the local device and the terminal device). In the following description of the embodiments of the present application, the session will continue to be taken as an example, and in the specific implementation, other possible expressions can be replaced.

[0151] (2) In the above-mentioned scenario 1 and scenario 2, three different sessions are established for the same service, that is, local edge computing based on one local device, but the scheme provided in the embodiments of the present application can also be applicable to a scenario in which multiple local devices perform local edge computing, for example, one possible scenario is that each local device performs a part of edge computing, local device N sends the calculation result and optional metadata to local device N+1, and the last local device participating in the partial edge computing sends the calculation result and optional metadata to the terminal device or the cloud server. The local device can be a terminal device, a base station, an IAB node, a relay node, a CU, a DU, a CU-CP or a CU-UP, and the like, which is a network device outside the core network.

[0152] That is, the scheme provided in the embodiments of the present application can be applicable to a scenario in which more sessions are established for the same service, such as four sessions or five sessions, and the specific number is not limited. For example, referring to FIG. 4, a schematic diagram of four sessions is shown; the four sessions can be session 1 between the terminal device and the application server, session 2 between the application server and the local device 1, session 3 between the local device 1 and the local device 2, and session 4 between the local device 2 and the terminal device. In one possible case, assuming that the terminal device in FIG. 4 is a VR headset and the application server is a VR server, one possible data transmission process is that the VR headset sends the posture information of the VR headset and the eyeball to the VR server through session 1. The VR server sends the VR media data to the local device 1 through session 2, the local device 1 performs secondary rendering on part of the VR media data. The local device 1 sends the new VR media data obtained by secondary rendering to the local device 2 through session 3, the local device 2 performs tertiary rendering on the new VR media data obtained by secondary rendering to obtain the new VR media data after tertiary rendering. The local device 2 sends the new VR media data after tertiary rendering to the VR headset through session 3. In this example, the VR server, the local device 1, the local device 2 and the VR headset perform serial processing on the VR media data, but in actual application, there can also be parallel processing, for example, the local device 1 and the local device 2 each perform a part of secondary rendering on the VR media data from the VR server, and then combine and give to the VR headset for display, which is not limited herein. Figure 3d Figure 3c That is, the scheme provided in the embodiments of the present application can be applicable to a scenario in which more sessions are established for the same service, such as four sessions or five sessions, and the specific number is not limited. For example, referring to FIG. 4, a schematic diagram of four sessions is shown; the four sessions can be session 1 between the terminal device and the application server, session 2 between the application server and the local device 1, session 3 between the local device 1 and the local device 2, and session 4 between the local device 2 and the terminal device. In one possible case, assuming that the terminal device in FIG. 4 is a VR headset and the application server is a VR server, one possible data transmission process is that the VR headset sends the posture information of the VR headset and the eyeball to the VR server through session 1. The VR server sends the VR media data to the local device 1 through session 2, the local device 1 performs secondary rendering on part of the VR media data. The local device 1 sends the new VR media data obtained by secondary rendering to the local device 2 through session 3, the local device 2 performs tertiary rendering on the new VR media data obtained by secondary rendering to obtain the new VR media data after tertiary rendering. The local device 2 sends the new VR media data after tertiary rendering to the VR headset through session 3. In this example, the VR server, the local device 1, the local device 2 and the VR headset perform serial processing on the VR media data, but in actual application, there can also be parallel processing, for example, the local device 1 and the local device 2 each perform a part of secondary rendering on the VR media data from the VR server, and then combine and give to the VR headset for display, which is not limited herein.

[0153] In the following description of the embodiments of the present application, the establishment of three different sessions for the same service will continue to be taken as an example, and the implementation of the establishment of more sessions for the same service can be adaptively referred to the implementation.

[0154] II. Local device

[0155] ​The local device involved in the embodiments of the present application can have an application layer function or can process application layer data. For example, for a VR service, the local device can be used to implement image rendering of the VR service; for example, for an image recognition service, the local device can be used to implement segmented calculation (for example, partial calculation of a neural network in an artificial intelligence (AI) based image recognition algorithm).

[0156] Exemplarily, considering that an edge application server (EAS) has an application layer function, in one example, the local device can include an assistant terminal device (A-UE) and the EAS deployed together, where the assistant terminal device can be a mobile phone or a customer premise equipment (CPE). For example, the EAS can be a software application in the assistant terminal device. In this case, see Figure 4a , the session 1, the session 2 and the session 3 described in the above scenario 1 and scenario 2 are illustrated.

[0157] In another example, the local device can include an access network device and the EAS deployed together, where the EAS can be directly connected to the access network device. In this case, see Figure 4b , the session 1, the session 2 and the session 3 described in the above scenario 1 and scenario 2 are illustrated. It should be noted that, for the example, in other possible scenarios, the EAS can also be connected to the access network device through a local user plane function (L-UPF), in which case, the local device can include the access network device, the L-UPF and the EAS deployed together, or the local device can also be an access network device containing the L-UPF and the EAS function.

[0158] In another example, the local device can include a wireless backhaul device (such as an IAB node) and the EAS deployed together, where the IAB node can be directly connected to the EAS; or the local device can also be an IAB node containing the EAS software application. In this case, see Figure 4c , the session 1, the session 2 and the session 3 described in the above scenario 1 and scenario 2 are illustrated.

[0159] It should be noted that: the above only describes several possible examples of local devices, and it can be understood that the method in the embodiment of the application can be applied to the scene of deployment or integration of EAS and network devices such as gNB, eNB, ng-eNB, gNB-CU, eNB-CU, gNB-CU-UP, eNB-CU-UP, IAB node, and auxiliary terminal device. In order to facilitate description, the network device, EAS and possible related network entities deployed together or integrated in the embodiment of the application are regarded as one network entity, which is collectively referred to as a local device. In addition, the embodiment of the application can be applied to the scene where more than one EAS is deployed in different network devices for the same service; the embodiment of the application does not limit the connection mode of EAS and network device, such as EAS can be directly connected with access network device, or EAS can be connected with access network device through L-UPF, or they are integrated into one physical device.

[0160] Based on the above related technical features, the communication method provided by the embodiment of the application will be described in detail below.

[0161] It should be noted that, in the following, scenarios 1 and 2 will be mainly taken as examples, but the communication method provided by the embodiment of the application can also be applied to other possible scenarios, such as the method provided by the embodiment of the application can also be applied to cloud gaming, mixed reality (MR) and other possible scenarios that may exist downlink local rendering or downlink edge computing, and can also be applied to other scenarios that exist uplink edge computing except scenario 2, without limitation.

[0162] Figure 5 The flowchart corresponding to the communication method provided by the embodiment of the application is shown in Figure 5 The method comprises S501, S502 and S503, and the execution order of S501, S502 and S503 is not limited by the embodiment of the application.

[0163] S501, the first core network device acquires first indication information, and the first indication information indicates that M sessions have an association relationship, and M is an integer greater than 1.

[0164] Here, the first core network device can be an SMF network element or an AMF network element. The first indication information indicates that the M sessions have an association relationship, which can also be described as the first indication information indicating that the M sessions belong to the same synchronization session set, and the synchronization session set can also be called a synchronization session group (group) or other possible names, without limitation; the multiple sessions in the synchronization session set have an association relationship.

[0165] In one example, M=3, the M sessions can include a first session between the terminal device and the application server (such as session 1 in the scenario 1 or scenario 2 described above), a second session between the application server and the local device (such as session 2 in the scenario 1 or scenario 2 described above), and a third session between the local device and the terminal device (such as session 3 in the scenario 1 or scenario 2 described above). Wherein, the terminal device establishes an RRC connection with the first access network device.

[0166] Exemplarily, there can be multiple ways for the first core network device to obtain the first indication information, and two possible implementation manners are described herein.

[0167] In one possible implementation manner, the first core network device can obtain the first indication information from the terminal device. For example, the terminal device can send a first request message to the first core network device, the first request message being used to request establishment or modification of the M sessions or the first session in the M sessions, and the first request message including the first indication information. In one example, the first request message can be a PDU session establishment request message or a PDU session modification request message.

[0168] In another possible implementation manner, the first core network device can obtain the first indication information from a second core network device, wherein the second core network device can be a UDM network element or a PCF network element. For example, the terminal device can send a PDU session establishment request message or a PDU session modification request message to the first core network device, and after receiving the PDU session establishment request message or the PDU session modification request message, the first core network device can obtain the first indication information from the second core network device (such as a UDM network element or a PCF network element).

[0169] Further, the first core network device can further acquire second indication information and / or third indication information. The second indication information indicates that the local device performs edge computing on the received data of the second session (such as the above scenario 1), or the second indication information indicates that the local device performs edge computing on the received data of the third session (such as the above scenario 2); and the third indication information indicates a time length required by the local device for local edge computing. If the first core network device acquires the second indication information and the third indication information, when the second indication information indicates that the local device performs edge computing on the received data of the second session, the time length required by the local device for local edge computing indicated by the third indication information refers to a time length required by the local device for edge computing on the received data of the second session; and when the second indication information indicates that the local device performs edge computing on the received data of the third session, the time length required by the local device for local edge computing indicated by the third indication information refers to a time length required by the local device for edge computing on the received data of the third session.

[0170] Exemplarily, the first core network device can acquire the second indication information and / or the third indication information in multiple ways, which can be referred to the way of acquiring the first indication information by the first core network device.

[0171] It can be understood that the above first indication information, second indication information and third indication information can be provided by the terminal device to the first core network device through the first request message, or can also be acquired by the first core network device from the second core network device after receiving the first request message sent by the terminal device. That is, the first indication information, the second indication information and the third indication information can be provided by the terminal device or the second core network device, such as all of the three information provided by the terminal device or the second core network device, or each part provided.

[0172] S502, the first core network device sends the first indication information to the first access network device; correspondingly, the first access network device can receive the first indication information.

[0173] Exemplarily, the first core network device can further send the second indication information and / or the third indication information to the first access network device. In an example, the first core network device can send the first indication information, the second indication information and the third indication information to the first access network device through the same message; or can also send the first indication information, the second indication information and the third indication information to the first access network device through different messages respectively.

[0174] It should be noted that in other possible embodiments, S502 can also be replaced by S502', the second access network device sends the first indication information to the first access network device. Here, the second access network device can be a source network device of the terminal device, and the first access network device can be a target network device of the terminal device. When the terminal device is handed over by the second access network device or resumes to the first access network device from the RRC inactive state (RRC_INACTIVE state), the second access network device can send the first indication information to the first access network device. Optionally, the second access network device can also send the second indication information and / or the third indication information to the first access network device. In this case, S501 can no longer be performed.

[0175] S503, the first access network device processes the M sessions according to the first indication information.

[0176] Here, the first access network device processing the M sessions can include: (1) the first access network device performing admission control on the M sessions according to the first indication information; and / or (2) the first access network device scheduling data in the M PDU sessions according to the first indication information, the second indication information, and the third indication information.

[0177] (1) The first access network device performing admission control on the M sessions according to the first indication information can mean that the first access network device simultaneously admits establishment requests of at least two sessions of the M sessions or simultaneously rejects establishment requests of at least two sessions of the M sessions according to the first indication information; or simultaneously admits modification requests of at least two sessions of the M sessions or simultaneously rejects modification requests of at least two sessions of the M sessions. The M sessions belong to one synchronous session set, and the at least two sessions can be all the sessions in the synchronous session set that need to be controlled by the first access network device.

[0178] For example, in the case shown in the above Figure 4a or Figure 4c The first access network device can simultaneously admit establishment requests of the session 1, the session 2, and the session 3 or simultaneously reject establishment requests of the session 1, the session 2, and the session 3 according to the first indication information; or simultaneously admit modification requests of the session 1, the session 2, and the session 3 or simultaneously reject modification requests of the session 1, the session 2, and the session 3. In the above Figure 4bIn the scenario shown, the first access network device can accept or reject the establishment request of session 1 and session 3 at the same time according to the first indication information, or accept or reject the modification request of session 1 and session 3 at the same time; where session 2 does not involve air interface transmission, and is assumed to not require admission control by the first access network device. In this way, since the first access network device can determine whether to accept or reject the establishment request or modification request of a session according to the association relationship between sessions, the problem that the first access network device accepts or rejects the establishment request or modification request of part of the sessions, resulting in the inability of the service to be normally implemented, can be effectively avoided.

[0179] (2) The first access network device can perform scheduling processing on the data in the M PDU sessions according to the first indication information, the second indication information and the third indication information, which can mean that if the first access network device determines that the local device performs edge computing on the received data in the second session, the data in the second session can be scheduled at a first time (i.e., the first access network device allocates wireless resources between the first access network device and the local device at the first time to transmit the data in the second session), and the data in the third session can be scheduled at a second time after the first time (i.e., the local device allocates wireless resources between the local device and the terminal device at the second time to transmit the data in the third session); where the time interval between the first time and the second time is obtained according to the time length required for the local device to perform edge computing. Alternatively, if the first access network device determines that the local device performs edge computing on the received data in the third session, the data in the third session can be scheduled at the first time, and the data in the second session can be scheduled at the second time after the first time; where the time interval between the first time and the second time is obtained according to the time length required for the local device to perform edge computing. In one example, the time interval between the first time and the second time can be equal to the time length required for the local device to perform edge computing. In this way, since the first access network device can schedule the data in the second session and the third session according to the time length required for edge computing, the business data in different sessions within the synchronous session set can be cooperatively transmitted according to a certain order and time relationship; for example, scheduling the data in the third session at the second time after the first time can avoid scheduling the data in the third session too early and causing the local device to possibly not complete edge computing, or can avoid scheduling the data in the third session too late and affecting data transmission efficiency.

[0180] By using the above method, in the embodiments of the present application, when the first access network device processes the M sessions, the association relationship between the M sessions can be considered, thereby facilitating to meet the synchronization requirements between different sessions and effectively ensuring the quality of experience (QoE) of users on the service.

[0181] The above Figure 5 The described method can be applied to Figure 4a to Figure 4c In any of the scenarios described above, there are some differences in the implementation process due to the differences in the local device in different scenarios. The communication method provided by the embodiments of the present application will be described below in conjunction with Figure 4a to Figure 4c the scenarios described above.

[0182] It should be noted that the access network device described in embodiments 1 to 6 can be a base station, CU or CU-CP, etc. The device has the function of RRC connection control.

[0183] Embodiment I

[0184] In embodiment one, the scenario described in Figure 4a will be taken as an example to describe a possible implementation. Figure 4a In the embodiment, the local device can include an auxiliary terminal device and an EAS, in order to clearly show the difference between each embodiment, the local device is directly referred to as an auxiliary terminal device in this embodiment.

[0185] Figure 6 The flowchart corresponding to the communication method provided by the first embodiment of the present application is shown in Figure 6 , which includes S600 to S610, and the execution order of S600 to S610 is not limited by the embodiments of the present application.

[0186] S600, the access network device and / or the first core network device obtains the capability information of the auxiliary terminal device, and the capability information of the auxiliary terminal device is used to indicate whether the auxiliary terminal device supports edge computing.

[0187] In one example, the auxiliary terminal device can send the capability information to the access network device and / or the first core network device. For example, the auxiliary terminal device reports the capability information to the access network device and / or the first core network device after completing the RRC connection establishment with the access network device, or during the registration process, or after completing the registration.

[0188] In another example, the first core network device can also obtain the capability information of the auxiliary terminal device from the UDM network element during the registration process of the auxiliary terminal device or after completing the registration.

[0189] S601, the terminal device sends a first request message to the first core network device; correspondingly, the first core network device can receive the first request message. In this embodiment, the first request message is taken as an example of PDU session establishment request message.

[0190] Here, the PDU session establishment request message can be used to request to establish M PDU sessions, such as the PDU session establishment request message can include information of M PDU sessions (such as session 1, session 2 and session 3) and first indication information, the first indication information indicates that session 1, session 2 and session 3 have an association relationship; wherein the information of the PDU session can include at least one of the PDU session identifier (ID), the type information of the PDU session and the requested SSC mode.

[0191] Optionally, the PDU session establishment request message can also include second indication information and third indication information, wherein the second indication information indicates that the auxiliary terminal device is used for edge computing on the received data of session 2 or session 3; the third indication information indicates the time length required by the auxiliary terminal device for local edge computing. In one example, the non-access layer of the terminal device can first obtain the second indication information and / or the third indication information through the application layer (possibly via the operating system), and then send to the first core network device through the PDU session establishment request message.

[0192] I. Explanation and description of the first indication information.

[0193] Exemplarily, the implementation mode of the first indication information indicating that session 1, session 2 and session 3 have an association relationship can be various, and several possible implementation modes are described below.

[0194] Implementation mode 1: the first indication information includes M association information corresponding to M PDU sessions respectively. Wherein, the association information corresponding to the PDU session can include the type information of the PDU session and / or the association identifier (association ID) of the PDU session, and the PDU sessions with the same type information and / or the same association identifier have an association relationship. Wherein, the type information of the PDU session can be used to indicate that the type of the PDU session is split rendering (for scenario 1) or segment computing (for scenario 2); split rendering can also be described as local rendering, similarly, segment computing can also have other descriptions, such as split inference, which is not limited in detail. For example, the types of session 1, session 2 and session 3 are all split rendering, which indicates that session 1, session 2 and session 3 have an association relationship.

[0195] Exemplarily, there can be multiple ways for the PDU session establishment request message to carry the first indication information. For example, in the information of each of the M PDU sessions, a current information element (IE) can be reused, such as adding "separate rendering or segment calculation" as a new enumeration value in the type information of each PDU session. For another example, in the information of each of the M PDU sessions, a new IE can be added, which is used to carry the association identifier of the PDU session.

[0196] In implementation 2, the first indication information includes the identification information of the auxiliary terminal device. In the scenario shown in 4a, the identification information of the auxiliary terminal device can include the IP address and / or MAC address of the auxiliary terminal device, or can also include other possible information such as the SUPI of the auxiliary terminal device, which is not limited in particular. As long as the information can uniquely identify the auxiliary terminal device for the first core network device, it can be understood as the identification information of the auxiliary terminal device. Exemplarily, the identification information of the auxiliary terminal device can be carried in a newly added IE independent of the information of the PDU session, such as carrying the identification information of the auxiliary terminal device by adding an independent IE "Local Device ID" in the PDU session establishment request message; or, an IE can be added in the information of each of the M PDU sessions, which is used to carry the identification information of the auxiliary terminal device.

[0197] In implementation 3, the first indication information includes M association information respectively corresponding to the M PDU sessions and the identification information of the auxiliary terminal device, and the specific implementation can refer to the above implementation 1 and implementation 2.

[0198] II. Explanation and description of the second indication information and the third indication information.

[0199] Exemplarily, the second indication information can indicate in multiple ways the indication manner of the auxiliary terminal device for performing edge computing on the received data of session 2 or session 3. For example, the second indication information can include a type of mobile edge computing, which indicates whether the auxiliary terminal device performs edge computing on uplink service data of the terminal device or downlink service data of the terminal device (wherein local rendering and segment computing both belong to edge computing, which is relevant “computing” of application layer data by a local device at the edge of the network, but in the present application, the edge “computing” can not be limited to only application layer data, but also applies to other protocol layer data). If the type is downlink, it means that the auxiliary terminal device performs edge computing on downlink service data of the terminal device, i.e., the auxiliary terminal device is used for performing edge computing on the received data of session 2; if the type is uplink, it means that the auxiliary terminal device performs edge computing on uplink service data of the terminal device, i.e., the auxiliary terminal device is used for performing edge computing on the received data of session 3. It can be understood that the type of mobile edge computing can also be replaced by other possible descriptions, such as rendering service direction, and the specific implementation is not limited.

[0200] Exemplarily, the PDU session establishment request message can carry the second indication information and / or the third indication information in multiple ways. In one example, the second indication information can be carried in an added information element independent of the PDU session, such as by adding an independent information element “MEC type” in the PDU session establishment request message to carry the second indication information; the third indication information can be carried in an added information element independent of the PDU session, such as by adding an independent information element “Local Process Time” in the PDU session establishment request message to carry the third indication information. In another example, two information elements can also be added in the information of each of the M PDU sessions to carry the second indication information and the third indication information, respectively.

[0201] Based on the above description, as a specific example, if the PDU session establishment request message includes: information of three PDU sessions, the Local Device ID is an IPv4 address 10.10.10.1, the MEC type is “downlink”, and the Local Process Time is 5 ms, it means that the auxiliary terminal device with the IPv4 address 10.10.10.1 performs edge computing on downlink service data of the terminal device, and the required time length of edge computing is 5 ms.

[0202] It should be noted that: (1) In other possible examples, the PDU session establishment request message can also be used to request to establish one PDU session (such as session 1, session 2 and session 3) of M PDU sessions, such as session 1. Among them, the PDU session establishment request message can include the information of session 1 and the first indication information, and the first indication information indicates that the requested is a session related to edge computing, such as the first indication information can include the identification information of the auxiliary terminal device, to implicitly indicate that session 1 is a session related to edge computing, and other implementations can refer to the above description. In this case, the first core network device can subsequently determine and trigger other session establishment, such as after the first core network device receives the PDU session establishment request message, it is determined that the PDU session establishment request message carries the first indication information, then the establishment of session 1, session 2 and session 3 can be triggered according to the first indication information (that is, S602 is executed).

[0203] (2) The above is described by taking the first indication information, the second indication information and the third indication information as PDU session level information as an example, in other possible examples, the first indication information, the second indication information and the third indication information can also be QoS flow level information, that is, the configuration information of one or more QoS flows contained in the PDU session includes these information, in this case, the QoS flows in the three PDU sessions that contain these information have synchronization requirements. Exemplarily, it can also be agreed by the value of 5G quality of service identifier (5G QoS identifier, 5QI) which 5QI corresponding to the QoS flow belongs to the same synchronization session set, such as all QoS flows whose 5QI of the QoS rule corresponding to the QoS flow takes value in the range of 64-71 belong to the same synchronization session set.

[0204] In addition, the first core network device receives the PDU session establishment request message, can judge whether it meets the preset condition, if it meets, S602 can be executed, otherwise, S602 will not be executed.

[0205] For example, after receiving the PDU session establishment request message, the first core network device can determine whether the auxiliary terminal device supports edge computing. If the auxiliary terminal device supports edge computing, S602 can be performed, otherwise, S602 can not be performed. For another example, after receiving the PDU session establishment request message, the AMF network element can perform SMF network element selection, and then hand over the PDU session establishment request message to the selected SMF network element for processing. The SMF network element can further obtain the subscription information of the terminal device from the UDM network element to determine whether the terminal device is allowed to perform the PDU session (i.e., M PDU sessions). If so, S602 is performed. After receiving the PDU session establishment request message, the processing procedure of the core network side can refer to 3GPP technical standard (technical specification, TS) 23.502 version 16.4.0. The embodiments of the present application do not limit the processing procedure of the core network.

[0206] S602, the first core network device sends a PDU session resource establishment request message to the access network device; correspondingly, the access network device receives the PDU session resource establishment request message.

[0207] Here, the PDU session resource establishment request message can include first indication information. The description of the first indication information can be referred to the above. It can be understood that the way in which the PDU session resource establishment request message carries the first indication information can be the same as or different from the way in which the PDU session establishment request message carries the first indication information, and the specific implementation is not limited.

[0208] The possible ways of carrying the first indication information in the PDU session resource setup request message are described below. Here, taking the first indication information including the association identifiers of M PDU sessions as an example, for example, the PDU session resource setup request message includes the PDU session resource setup request items (PDU Session Resource Setup Request Item) corresponding to the PDU sessions (such as session 1, session 2, or session 3). The PDU session resource setup request item corresponding to the PDU session can include the identifier of the PDU session (PDU Session ID), the PDU session non-access layer PDU (PDU Session NAS-PDU), single network slice selection assistance information (S-NSSAI), and PDU session resource setup request transfer (PDU Session Resource Setup Request Transfer). In the embodiment of the application, the PDU session resource setup request item corresponding to the PDU session can also include the association identifier. That is, a new information element (referred to as information element 1) can be added in the PDU session resource setup request item corresponding to the PDU session, and the information element is used to carry the association identifier.

[0209] Table 1 below is an example of carrying the first indication information in the PDU session resource setup request message.

[0210] Table 1: Example of carrying the first indication information in the PDU session resource setup request message

[0211] >PDU Session Resource Setup Request Item >>PDU Session ID >>PDU Session NAS-PDU >>S-NSSAI >>PDU Session Resource Setup Request Transfer >>Associated ID (cell 1) ]]> ​

[0212] Exemplarily, the PDU session resource setup request message can also include the second indication information and / or the third indication information, and the description of the second indication information and / or the third indication information can be referred to the above. It can be understood that the way of carrying the second indication information and / or the third indication information in the PDU session resource setup request message can be the same as or different from the way of carrying the second indication information and / or the third indication information in the PDU session establishment request message, which is not limited specifically.

[0213] The following describes possible ways in which the PDU session resource establishment request message carries the second indication information and the third indication information. For example, the PDU session resource establishment request message includes a PDU session resource establishment request item corresponding to a PDU session (such as session 1, session 2, or session 3). In an embodiment of the present application, the PDU session resource establishment request item corresponding to the PDU session can also include the second indication information and the third indication information. That is, two information elements (referred to as information element 2 and information element 3) can be added to the PDU session resource establishment request item corresponding to the PDU session, the information element 2 is used to carry the second indication information, and the information element 3 is used to carry the third indication information.

[0214] Table 2 below is an example of the PDU session resource establishment request message carrying the second indication information and the third indication information.

[0215] Table 2: Example of PDU session resource establishment request message carrying second indication information and third indication information

[0216] >PDU Session Resource Setup Request Item >>PDU Session ID >>PDU Session NAS-PDU >>S-NSSAI >>PDU Session Resource Setup Request Transfer >>MEC type (cell 2) >>Local Process Time (cell 3) ]]> ​

[0217] It should be noted that, taking session 1 as an example, if session 1 and other sessions belong to a synchronous session set, the session resource establishment request item corresponding to session 1 can add the above information element 1, information element 2, and information element 3; if session 1 does not belong to a synchronous session set with any other session, the session resource establishment request item corresponding to session 1 can no longer add the above information element 1, information element 2, and information element 3.

[0218] S603, the access network device performs admission control on the M PDU sessions according to the first indication information, and sends a PDU session resource establishment response message to the first core network device.

[0219] Here, the access network device can perform admission control on session 1, session 2, and session 3 by simultaneously admitting or simultaneously rejecting according to the first indication information; and the access network device can send a PDU session resource establishment response message to the first core network device according to the admission result, which can include information about whether each PDU session is admitted by the access network device.

[0220] In an embodiment of the present application, the access network device can determine whether to admit the M PDU sessions based on multiple factors. As an implementation manner, the access network device can determine whether to admit the M PDU sessions based on the current serving cell of the terminal device, the load condition of the access network device, and the like. Further, the access network device can also determine whether to admit the M PDU sessions based on the capability and coverage condition of the terminal device, and the like, and consider whether the QoS requirements of the M PDU sessions can be met by configuring more serving cells or adding a secondary base station, and the like. In this case, the access network device performing the admission control process can trigger the terminal device to be configured with a secondary carrier and / or a secondary base station. The process in which the access network device configures the terminal device with the secondary carrier and / or the secondary base station can refer to an existing scheme, and will not be described herein.

[0221] In one example, the access network device can determine whether the secondary terminal device supports edge computing. If the secondary terminal device supports edge computing, the access network device can perform admission control on the M PDU sessions based on the above factors to simultaneously admit or simultaneously reject the M PDU sessions. If the secondary terminal device does not support edge computing, the access network device can reject the establishment request or the modification request of the M PDU sessions, or can admit the establishment request or the modification request of session 1 and reject the establishment request or the modification request of session 2 and session 3, that is, fall back to a service support mode without edge computing. The specific implementation is not limited.

[0222] S604, the access network device sends an RRC reconfiguration message 1 to the secondary terminal device.

[0223] Here, the RRC reconfiguration message 1 can carry configuration information of one or more DRBs and configuration information of one or more SLRBs (sidelink radio bearers). The one or more DRBs are mapped from session 2, and the one or more SLRBs are mapped from session 3. The specific mapping manner is an internal implementation of the access network device, for example, the mapping of the QoS flow to the DRB or the SLRB can be performed based on the QoS requirements of the QoS flow in the session. The specific implementation is not limited.

[0224] S605, the secondary terminal device sends an RRC reconfiguration sidelink message to the terminal device.

[0225] Here, the RRC reconfiguration sidelink message can carry configuration information of one or more SLRBs, which is used to establish a radio bearer for D2D communication between the terminal device and the secondary terminal device.

[0226] S606, the terminal device sends an RRC reconfiguration sidelink complete message to the secondary terminal device.

[0227] S607, the secondary terminal device sends an RRC reconfiguration complete message 1 to the access network device.

[0228] S608, the access network device sends an RRC reconfiguration message 2 to the terminal device.

[0229] Here, the RRC reconfiguration message 2 can carry configuration information of one or more DRBs mapped by session 1.

[0230] Further, after sending the RRC reconfiguration message 2 to the terminal device, the access network device can also send a PDU session establishment accept message to the terminal device, which is a NAS message generated by the first core network device.

[0231] S609, the terminal device sends an RRC reconfiguration complete message 2 to the access network device.

[0232] S610, the access network device schedules data in the M PDU sessions according to the first indication information, the second indication information and the third indication information.

[0233] Here, taking scenarios 1 and 2 as examples, the specific implementation of the access network device scheduling data in the M PDU sessions is described.

[0234] (1) For scenario 1

[0235] According to the first indication information, the second indication information and the third indication information, the access network device can determine that one or more DRBs mapped by session 2 have an association relationship with one or more SLRBs mapped by session 3, and can determine that the secondary terminal device will perform edge computing on the downlink service data of the terminal device, and the time length required for edge computing. Based on this information, when the access network device schedules the downlink data of the DRB to be sent at time N (i.e. the first time), it schedules the data of the SLRB (data from the secondary terminal device to the terminal device) to be sent at time N+k (i.e. the second time after the first time), to ensure that the downlink data after edge computing is sent to the terminal device in time. Wherein, k is the time length required for the secondary terminal device to perform edge computing on the downlink service data of the terminal device.

[0236] (2) For scenario 2

[0237] According to the first indication information, the second indication information and the third indication information, the access network device can determine that the one or more DRBs mapped by the session 2 are associated with the one or more SLRBs mapped by the session 3, and can determine that the auxiliary terminal device will perform edge computing on the uplink service data of the terminal device and the time length required by the edge computing. Based on the information, when the access network device schedules the data of the SLRB (the data from the terminal device to the auxiliary terminal device) to be sent at time N, the access network device schedules the uplink data of the DRB to be sent at time N+k, so as to ensure that the uplink data after the edge computing is sent to the application server in time. Wherein, k is the time length required by the auxiliary terminal device to perform edge computing on the uplink service data of the terminal device.

[0238] In the embodiments of the present application, the time length required by the auxiliary terminal device to perform edge computing can be a relatively conservative time length, so as to ensure that the auxiliary terminal device can complete the edge computing within the time length.

[0239] In addition, in one example, if the traffic pattern of the terminal device is regular, such as data burst arriving according to a period, the access network device can also configure a corresponding DRX period for the terminal device and the auxiliary terminal device, which will be described below by taking scene 1 and scene 2 as examples.

[0240] (1) For scene 1

[0241] If the downlink traffic pattern of the session 2 is regular, that is, the data in the session 2 is transmitted according to a transmission period, the access network device can send first configuration information to the auxiliary terminal device, the first configuration information being used to configure the first DRX of the auxiliary terminal device receiving the data in the session 2. The first DRX period is the same as the period of the data burst (that is, the transmission period of the data in the session 2), and the starting offset of the first DRX is also aligned with the starting offset of the data burst. Since the time length required by the auxiliary terminal device to perform edge computing is k, the access network device or the auxiliary terminal device can send second configuration information to the terminal device, the second configuration information being used to configure the second DRX of the terminal device receiving the data in the session 3 (that is, D2D communication), the second DRX period being the same as the first DRX period, but the starting offset being the first DRX starting offset plus k. In this way, the terminal device can not only avoid continuously listening to the data sent from the auxiliary terminal device to save power, but also can send the data to the terminal device in time after the auxiliary terminal device completes the local secondary rendering, so as to ensure the strict time delay requirement of the VR service.

[0242] (2) For scene 2

[0243] If the uplink traffic pattern of session 3 is regular, i.e., the data in session 3 is transmitted according to a transmission period, the access network device can send first configuration information to the auxiliary terminal device, the first configuration information being used to configure the auxiliary terminal device to receive the data in session 3 according to a first DRX period. The first DRX period is the same as the period of the data burst, i.e., the transmission period of the data in session 3, and the start offset of the first DRX period is also aligned with the start offset of the data burst. If the round-trip delay is t, the access network device or the auxiliary terminal device can send second configuration information to the terminal device, the second configuration information being used to configure the terminal device to receive the data in session 1 according to a second DRX period, the second DRX period being the same as the first DRX period but having a start offset that is the start offset of the first DRX period plus t. Here, the round-trip delay can be the time interval between the transmission time of the first data sent by the terminal device through session 3 and the reception time of the second data received by the terminal device through session 1, the second data being obtained based on the first data. For example, the first data can be an image captured by a surveillance camera or image data and / or computing context information that is preliminarily processed by the surveillance camera, and the second data can be image recognition results obtained based on the first data.

[0244] In yet another example, the access network device can send fifth indication information to the terminal device, the fifth indication information indicating the round-trip delay, and then the terminal device can perform power saving and other related optimizations based on the round-trip delay. This scheme can be applicable to the case where the traffic pattern of the terminal device is irregular, or can also be applicable to the case where the traffic pattern of the terminal device is regular, without limitation. In scenario 2, the round-trip delay can be the time interval between the transmission time of the first data sent by the terminal device through session 3 and the reception time of the second data received by the terminal device through session 1, the second data being obtained based on the first data. For example, after sending the first data, the terminal device can enter a sleep state, and after the duration of the sleep state reaches a threshold (the threshold being obtained based on the round-trip delay, e.g., the threshold can be equal to or slightly less than the round-trip delay), the terminal device can wake up from the sleep state to receive the second data. In scenario 1, the round-trip delay is the time interval between the transmission time of the third data sent by the terminal device through session 1 and the reception time of the fourth data received by the terminal device through session 3, the fourth data being obtained based on the third data. For example, the third data can be helmet movement or eye pose information captured by a VR headset, and the fourth data can be VR media data after secondary rendering.

[0245] It should be noted that the processes described in S601 to S610 above are only one possible example of a process, and in actual implementation, adaptive adjustment can be made on the basis of the processes described above. For example, the access network device can perform admission control on the M PDU sessions according to the first indication information; and no longer schedule data in the M PDU sessions according to the first indication information, the second indication information and the third indication information, in which case the access network device can schedule data in the M PDU sessions according to the prior art. For another example, the network device can schedule data in the M PDU sessions according to the first indication information, the second indication information and the third indication information, and no longer perform admission control on the M PDU sessions according to the first indication information, in which case the network device can perform admission control on the M PDU sessions according to the prior art.

[0246] According to the content in the above embodiment one, when edge computing is performed by the auxiliary terminal device, the access network device can perform admission control on the simultaneous admission or simultaneous rejection of session 1, session 2 and session 3, so as to avoid that admission of part of the sessions causes the service to be unable to be normally implemented; and the access network device can also control the data in different sessions (such as session 2 and session 3) in the synchronous session set to be cooperatively transmitted according to a certain order and time relationship, so as to meet the delay requirement of the service.

[0247] Embodiment II

[0248] In embodiment two, a possible implementation will be described taking the case shown in FIG. 8 as an example. Figure 4a

[0249] In the embodiments of the present application, it is considered that the terminal device can need to switch between edge computing and non-edge computing. For example, taking a terminal device of a VR headset as an example, when the VR headset does not have an externally-attached strong computing capability device, secondary rendering needs to be performed by the auxiliary terminal device, in which case the VR headset can select edge computing, i.e., the M sessions have an association relationship; and when the VR headset has an externally-attached strong computing capability device, secondary rendering no longer needs to be performed by the auxiliary terminal device, in which case the VR headset can select non-edge computing, i.e., the M sessions no longer have an association relationship. In other possible examples, the VR headset can also switch between edge computing and non-edge computing according to other possible reasons (such as whether a power source is connected).

[0250] In the above embodiment one, the related implementation in which the M sessions have an association relationship is described, and in embodiment two, a possible implementation in which the M sessions having an association relationship is switched to the M sessions no longer having an association relationship will be described. It should be noted that embodiment two can be implemented in combination with embodiment one, or can also be implemented separately.

[0251] ​Figure 7 A flowchart diagram corresponding to the communication method provided for Embodiment Two of the present application is shown in Figure 7 The method includes S701 to S708, and the execution sequence of S701 to S708 is not limited in the embodiments of the present application.

[0252] S701, the terminal device sends a second request message to the first core network device; correspondingly, the first core network device can receive the second request message.

[0253] Here, the second request message can be a PDU session modification request message, which can be used to modify session 1, for example, the message can carry information of session 1. In an example, the PDU session resource modification request message can also carry seventh indication information, which indicates that session 1 is no longer associated with other sessions (i.e. session 2, session 3) in the M sessions.

[0254] It should be noted that in other possible examples, the association between session 1 and other sessions (i.e. session 2, session 3) in the M sessions can also be indicated implicitly, for example, if the PDU session resource modification request message does not carry the first indication information (optionally, also does not carry the second indication information and the third indication information), it can be understood as implicitly indicating that session 1 is no longer associated with other sessions (i.e. session 2, session 3) in the M sessions.

[0255] After receiving the message, the first core network device can learn from the seventh indication information that the message is to initiate a switch from edge computing to no edge computing, and then execute S702. The processing process on the core network side after the first core network device receives the message can refer to 3GPP TS 23.502 version 16.4.0, which is not limited in detail.

[0256] S702, the first core network device sends a PDU session resource release command message to the access network device; correspondingly, the access network device can receive the PDU session resource release command message.

[0257] Here, the PDU session resource release command message can be used to release session 2 and session 3, for example, the PDU session resource release command message can include information of session 2 and session 3. In an example, the PDU session resource release command message can include sixth indication information, which indicates that the M sessions are no longer associated. It should be noted that in other possible examples, the association between the M sessions can also be indicated implicitly, which is not limited in detail.

[0258] S703, the access network device releases session 2 and session 3 according to the PDU session resource release command message, and sends a PDU session resource release response message to the first core network device.

[0259] S704, the access network device sends an RRC reconfiguration message to the auxiliary terminal device.

[0260] Here, the RRC reconfiguration message can carry indication information that the DRB and SLRB corresponding to session 2 and session 3 are released. Further, the access network device can also send a PDU session modification accept message to the terminal device after sending the RRC reconfiguration message to the auxiliary terminal device, which is a NAS message generated by the SMF network element.

[0261] S705, the auxiliary terminal device sends an RRC reconfiguration sidelink message to the terminal device.

[0262] Here, the RRC reconfiguration sidelink message can carry indication information that the SLRB corresponding to session 3 is released, and then the terminal device can release one or more SLRB related configurations and resources corresponding to session 3.

[0263] S706, the terminal device sends an RRC reconfiguration sidelink complete message to the auxiliary terminal device.

[0264] S707, the auxiliary terminal device sends an RRC reconfiguration complete message to the access network device.

[0265] S708, the access network device cancels scheduling data in the M PDU sessions according to the first indication information, the second indication information and the third indication information.

[0266] In this way, after S708, the service of the terminal device will be switched from edge computing to no edge computing. If edge computing is needed again later, the terminal device can trigger a PDU session modification or PDU session establishment process, such as the process shown in Embodiment 1 above, to switch to edge computing.

[0267] In the embodiments of the present application, the terminal device triggers the switching from edge computing to no edge computing, and in actual applications, the local device can also trigger it, such as the local device sending an edge computing release request to the terminal device or the access network device or the core network device when the computing resource is insufficient or the storage resource is insufficient or the transmission resource is insufficient or the edge computing has been completed.

[0268] Using the above method, terminal devices can switch from edge computing to edgeless computing, or from edgeless computing to edge computing, thereby ensuring that terminal devices can freely choose the appropriate mode under different working conditions (such as whether or not they are connected to a power source, or whether or not they have external devices with strong computing capabilities), while ensuring both business experience and user experience.

[0269] Embodiment III

[0270] In Example 3, the following will be used Figure 4b Taking the scenario shown as an example, we will describe one possible implementation. Figure 4b The local device may include access network devices and EAS. To clearly illustrate the differences between the various embodiments, in this embodiment, the local device is directly referred to as the access network device.

[0271] Figure 8 This is a flowchart illustrating the communication method provided in Embodiment 3 of this application, as shown below. Figure 8 As shown, the method includes S800 to S806, and the execution order of S800 to S806 is not limited in this embodiment.

[0272] S800: The first core network device obtains the capability information of the access network device. The capability information of the access network device is used to indicate whether the access network device supports edge computing.

[0273] In one example, the access network device can report capability information to the first core network device. For instance, the access network device can report capability information when the N2 interface is established.

[0274] S801, the terminal device sends a first request message to the first core network device; correspondingly, the first core network device can receive the first request message. In this embodiment, the first request message is a PDU session establishment request message as an example.

[0275] Here, the PDU session establishment request message may include first indication information, and may also include second indication information and / or third indication information.

[0276] S802, the first core network device sends a PDU session resource establishment request message to the access network device; correspondingly, the access network device receives the PDU session resource establishment request message.

[0277] Here, the PDU session resource establishment request message may include first indication information, and may also include second indication information and / or third indication information.

[0278] The implementations of S801 and S802 described above can be found in S601 and S602 in Embodiment 1.

[0279] S803, the access network device performs admission control on the M PDU sessions according to the first indication information, and sends a PDU session resource establishment response message to the first core network device.

[0280] Here, the access network device can perform simultaneous admission or simultaneous rejection admission control on session 1 and session 3 according to the first indication information. Here, it is assumed that the access network device does not need to perform admission control on session 2 because session 2 does not involve wireless resource usage, and wireless resource is usually a resource bottleneck in a mobile network.

[0281] S804, the access network device sends an RRC reconfiguration message to the terminal device.

[0282] S805, the terminal device sends an RRC reconfiguration complete message to the access network device.

[0283] The related implementation of S804 and S805 above can refer to S608 and S609 in Embodiment I.

[0284] S806, the access network device schedules data in the M PDU sessions according to the first indication information, the second indication information, and the third indication information.

[0285] Here, taking scenario 1 and scenario 2 as examples, the specific implementation of the access network device scheduling data in the M PDU sessions is described.

[0286] (1) For scenario 1

[0287] The access network device can determine the association relationship between session 2 and session 3, and can determine that the downlink data of session 2 will be edge computed, and the time length required for edge computing according to the first indication information, the second indication information, and the third indication information. Based on this information, when the access network device receives the downlink data of session 2 at time N, it can schedule the downlink data (data from the access network device to the terminal device) of the DRB mapped by session 3 to be sent at time N+k to ensure that the downlink data after edge computing is sent to the terminal device in time. Wherein, k is the time length required by the access network device for edge computing of the downlink data of the terminal device.

[0288] (2) For scenario 2

[0289] The access network device can determine the association between session 2 and session 3 according to the first indication information, the second indication information, and the third indication information, and can determine that edge computing will be performed on the uplink service data of session 3 and the time length required by the edge computing. Based on this information, when the access network device receives the uplink data of session 3 at time N, the access network device can schedule the data of session 2 (data from the access network device to the application server) to be sent at time N+k, so as to ensure that the data after edge computing is sent to the application server in time. Wherein, k is the time length required by the access network device to perform edge computing on the uplink service data of the terminal device.

[0290] In addition, in one example, the access network device can send fifth indication information to the terminal device, and the fifth indication information indicates the round-trip delay; for details, see the description in Embodiment 1.

[0291] In yet another example, if the service pattern of the terminal device is regular, such as data bursts arriving at a period, the access network device can also configure a corresponding DRX period for the terminal device, which will be described below with respect to scenarios 1 and 2.

[0292] (1) For scenario 1

[0293] If the downlink service pattern of session 2 is regular, that is, the data in session 2 is transmitted according to a transmission period, the access network device can send configuration information to the terminal device, and the configuration information is used to configure the DRX period of the terminal device for receiving data in session 3. The DRX period is the same as the transmission period of the data in session 2, but the starting offset is the starting offset of the data in session 2 plus k. In this way, the terminal device can avoid continuously listening to the data sent from the access network device and consuming power, and the data can be sent to the terminal device in time after the access network device completes the local secondary rendering, thereby ensuring the strict delay requirement of the VR service.

[0294] (2) For scenario 2

[0295] If the downlink service pattern of session 3 is regular, that is, the data in session 3 is transmitted according to a transmission period, the access network device can send configuration information to the terminal device, and the configuration information is used to configure the DRX period of the terminal device for receiving data in session 1. The DRX period is the same as the transmission period of the data in session 3, but the starting offset is the starting offset of the data in session 3 plus the round-trip delay (t). The round-trip delay here can be the time interval between the sending time of the first data sent by the terminal device through session 3 and the receiving time of the second data received by the terminal device through session 1, and the second data is obtained according to the first data.

[0296] According to the content in Embodiment Three, when edge computing is performed through the access network device, the access network device can perform admission control on session 1 and session 3 to simultaneously admit or simultaneously reject, so as to avoid that a part of the sessions are admitted and the service cannot be normally implemented; and the access network device can also control the data in different sessions (such as session 2 and session 3) in the synchronous session set to be cooperatively transmitted in a certain order and time relationship, so as to meet the delay requirement of the service.

[0297] Embodiment IV

[0298] In Embodiment Four, a possible implementation will be described by taking the scenario shown in FIG. 4 as an example. Figure 4b

[0299] In Embodiment Three, the related implementation that the M sessions have the association relationship is described, and in Embodiment Four, a possible implementation that the M sessions have the association relationship is switched to the M sessions no longer having the association relationship will be described. It should be noted that Embodiment Four can be implemented in combination with Embodiment Three, or can also be implemented separately.

[0300] Figure 9 The flowchart corresponding to the communication method provided in Embodiment Four of the present application is shown in FIG. 5, which includes S901 to S906, and the execution sequence of S901 to S906 is not limited in the embodiments of the present application. Figure 9

[0301] S901, the terminal device sends a second request message to the first core network device; correspondingly, the first core network device can receive the second request message.

[0302] S902, the first core network device sends a PDU session resource release command message to the access network device; correspondingly, the first access network device can receive the PDU session resource release command message.

[0303] S903, the access network device sends a PDU session resource release response message to the first core network device.

[0304] S904, the access network device sends an RRC reconfiguration message to the terminal device.

[0305] Here, the RRC reconfiguration message can carry indication information that the DRB corresponding to session 3 is released. Further, after sending the message to the terminal device, the access network device can also send a PDU session modification acceptance message to the terminal device, which is an NAS message generated by the SMF network element.

[0306] S905, the terminal device sends an RRC reconfiguration complete message to the access network device.

[0307] ​​S906, the access network device cancels scheduling data in the M PDU sessions according to the first indication information, the second indication information, and the third indication information.

[0308] In this way, after S906, the service of the terminal device will be switched from edge computing to no edge computing. If edge computing is needed again subsequently, the terminal device can trigger a PDU session modification or PDU session establishment process, such as the process shown in Embodiment Three described above, to switch to edge computing.

[0309] By using the above method, the terminal device can be switched from edge computing to no edge computing, or from no edge computing to edge computing, so as to ensure that the terminal device can freely select the corresponding mode under different working modes (such as with or without a connected power supply, with or without an externally connected strong computing power device, etc.), while ensuring service experience and user experience.

[0310] Embodiment V

[0311] In Embodiment Five, the case shown in Figure 4c will be taken as an example to describe a possible implementation. Figure 4c The local device can include an IAB node and an EAS. In order to clearly show the difference between the embodiments, in this embodiment, the local device is directly referred to as an IAB node.

[0312] Figure 10 The flowchart corresponding to the communication method provided in Embodiment Five of the present application is shown in Figure 10 , which includes S1000 to S1010. The present application does not limit the execution order of S1000 to S1010.

[0313] S1000, the access network device and / or the first core network device obtains the capability information of the IAB node, and the capability information of the IAB node is used to indicate whether the IAB node supports edge computing.

[0314] In one example, the IAB node can send the capability information to the access network device and / or the first core network device. For example, the IAB node reports the capability information to the access network device and / or the first core network device after completing the RRC connection establishment with the access network device, or during the registration process, or after completing the registration.

[0315] In another example, the first core network device can also obtain the capability information of the IAB node from the UDM network element during the registration process of the IAB node or after completing the registration.

[0316] S1001, the terminal device sends a first request message to the first core network device; correspondingly, the first core network device can receive the first request message. In this embodiment, the first request message is taken as an example of a PDU session establishment request message.

[0317] Here, the PDU session establishment request message can include the first indication information, and can also include the second indication information and / or the third indication information.

[0318] S1002, the first core network device sends a PDU session resource establishment request message to the access network device; correspondingly, the access network device receives the PDU session resource establishment request message.

[0319] Here, the PDU session resource establishment request message can include the first indication information, and can also include the second indication information and / or the third indication information.

[0320] S1003, the access network device performs admission control on the M PDU sessions according to the first indication information, and sends a PDU session resource establishment response message to the first core network device.

[0321] The related implementation of S1001 to S1003 above can refer to S601 to S603 in Embodiment I.

[0322] S1004, the access network device sends a context modification request (UE context modification request) message of the terminal device to the IAB node.

[0323] Here, the context modification request message can include configuration information of the DRB mapped from session 1, so that the IAB node performs configuration related to these DRBs, such as configuration related to the RLC protocol layer between the IAB node and the terminal device.

[0324] S1005, the IAB node sends a context modification response (UE context modification response) message of the terminal device to the access network device.

[0325] S1006, the access network device sends an RRC reconfiguration message 1 to the IAB node.

[0326] Here, the RRC reconfiguration message can include configuration information of the DRB mapped by the session 2 and the session 3 and fourth indication information indicating that the DRB corresponding to the session 2 has an association relationship with the DRB corresponding to the session 3. For example, the fourth indication information can include association information between one or more pairs of DRBs (one DRB mapped by the session 2 and one DRB mapped by the session 3 constitute a pair of DRBs). Optionally, the RRC reconfiguration message can further include the second indication information and / or the third indication information.

[0327] S1007, the IAB node sends an RRC reconfiguration complete message 1 to the access network device.

[0328] As an alternative, the access network device can also send the access network device configuration information of the DRB mapped by the session 2 and the configuration information of the DRB mapped by the session 3 to the IAB node respectively, that is, the configuration process of S1006 and S1007 is split into two configuration processes, and the specific implementation is not limited.

[0329] S1008, the access network device sends an RRC reconfiguration message 2 to the terminal device.

[0330] Here, the RRC reconfiguration message can include configuration information related to the DRB mapped by the session 1 and the session 3.

[0331] S1009, the terminal device sends an RRC reconfiguration complete message 2 to the access network device.

[0332] S1010, the IAB node schedules data in the M PDU sessions according to the first indication information, the second indication information and the third indication information.

[0333] Here, taking the scenario 1 and the scenario 2 as examples, the specific implementation of the IAB node scheduling data in the M PDU sessions is described.

[0334] (1) For scenario 1

[0335] The IAB node can determine, according to the first indication information, the second indication information and the third indication information, that one or more DRBs mapped by the session 2 have an association relationship with one or more DRBs mapped by the session 3, and can determine that the IAB node will perform edge computing on the downlink service data of the terminal device and the time length required for edge computing. Based on this information, if the IAB node receives data of the DRB mapped by the session 2 at time N, the data (IAB node to terminal device data) of the DRB mapped by the session 3 is scheduled to be sent at time N+k, so as to ensure that the downlink data after edge computing is sent to the terminal device in time. Wherein, k is the time length required for the IAB node to perform edge computing on the downlink service data of the terminal device.

[0336] (2) For scenario 2

[0337] According to the first indication information, the second indication information and the third indication information, the IAB node can determine that the one or more DRBs mapped by session 2 are associated with the one or more DRBs mapped by session 3, and can determine that the IAB node will perform edge computing on the uplink service data of the terminal device and the time length required for edge computing. Based on this information, if the IAB node receives the data of the DRB mapped by session 3 at time N, the data of the DRB mapped by session 2 (the data from the IAB node to the application server) is scheduled to be sent at time N+k, so as to ensure that the uplink data after edge computing is sent to the application server in time. Wherein, k is the time length required for the IAB node to perform edge computing on the uplink service data of the terminal device.

[0338] In the embodiment of the application, the time length required for the IAB node to perform edge computing can be a relatively conservative time length, so as to ensure that the IAB node can complete edge computing within the time length.

[0339] In addition, in one example, if the traffic pattern of the terminal device is regular, such as data bursts arriving periodically, the access network device can also configure the corresponding DRX cycle for the terminal device and the IAB node, which will be described below with respect to scenarios 1 and 2 respectively.

[0340] (1) For scenario 1

[0341] If the downlink traffic pattern of session 2 is regular, that is, the data in session 2 is transmitted according to the transmission period, the access network device can send first configuration information to the IAB node, the first configuration information being used to configure the first DRX of the IAB node receiving the data in session 2. The first DRX cycle is the same as the cycle of the data burst (i.e. the transmission period of the data in session 2), and the start offset of the first DRX is also aligned with the start offset of the data burst. Since the time length required for the IAB node to perform edge computing is k, the access network device can send second configuration information to the terminal device through the IAB node, the second configuration information being used to configure the second DRX of the terminal device receiving the data in session 3, the second DRX cycle being the same as the first DRX cycle, but the start offset being the first DRX start offset plus k. In this way, the terminal device can not only avoid continuously listening to the data sent from the IAB node to save power, but also can send the data to the terminal device in time after the IAB node completes the local secondary rendering, thereby ensuring the strict time delay requirement of the VR service.

[0342] (2) For scenario 2

[0343] If the uplink traffic pattern of the session 3 is regular, i.e., the data in the session 3 is transmitted according to a transmission period, the access network device can send first configuration information to the IAB node, the first configuration information being used for configuring the IAB node to receive the data in the session 3 according to a first DRX period. The first DRX period is the same as the period of the data burst, i.e., the transmission period of the data in the session 3, and the start offset of the first DRX period is also aligned with the start offset of the data burst. If the round-trip delay is t, the access network device can send second configuration information to the terminal device through the IAB node, the second configuration information being used for configuring the terminal device to receive the data in the session 1 according to a second DRX period, the second DRX period being the same as the first DRX period but having a start offset of the first DRX period start offset plus t. The round-trip delay here can be the time interval between the transmission time of the terminal device sending the first data through the session 3 and the reception time of the terminal device receiving the second data through the session 1, the second data being obtained according to the first data.

[0344] In yet another example, the access network device can send fifth indication information to the terminal device, the fifth indication information indicating the round-trip delay; and then the terminal device can perform power saving and other related optimization according to the round-trip delay. For example, the fifth indication information can be carried in the RRC reconfiguration message 2 in S1008 described above.

[0345] It should be noted that: (1) the processes described in S1001 to S1010 above are only one possible example of the processes, and in specific implementation, adaptive adjustment can be made on the basis of the processes described above. For example, the access network device can perform admission control on the M PDU sessions according to the first indication information; and the IAB node does not schedule the data in the M PDU sessions according to the first indication information, the second indication information and the third indication information, in which case the IAB node can schedule the data in the M PDU sessions by referring to the prior art. For another example, the IAB node can schedule the data in the M PDU sessions according to the first indication information, the second indication information and the third indication information, and the access network device no longer performs admission control on the M PDU sessions according to the first indication information, in which case the access network device can perform admission control on the M PDU sessions by referring to the prior art.

[0346] (2) The method provided by the embodiments of the present application can be applied to the scenario of a one-level IAB node, and also to the scenario of multiple-level IAB nodes. For the scenario of multiple-level IAB nodes, the IAB node described in the embodiments of the present application can be any one-level IAB node. The multiple-level IAB node can be adaptively extended by referring to the description of the embodiments of the present application, and details are not described again.

[0347] According to the content in the above embodiment five, when edge computing is performed through the IAB node, the access network device can perform admission control of simultaneously admitting or simultaneously rejecting the session 1, the session 2 and the session 3, so as to avoid that a part of the sessions are admitted and the service cannot be normally implemented; and the IAB node can control the data in different sessions (such as the session 2 and the session 3) in the synchronization session set to be cooperatively transmitted in a certain order and time relationship, so as to meet the delay requirement of the service.

[0348] Embodiment VI

[0349] In the embodiment six, a possible implementation will be described taking the scenario shown in FIG. 6 as an example. Figure 4c

[0350] In the above embodiment five, the related implementation that the M sessions have the association relationship is described, and in the embodiment four, a possible implementation that the M sessions have the association relationship is switched to the M sessions no longer have the association relationship will be described. It should be noted that the embodiment six can be implemented in combination with the embodiment five, or can be implemented separately.

[0351] Figure 11 The flowchart corresponding to the communication method provided in the embodiment six of the present application is shown in FIG. 6, which includes S1101 to S1108, and the execution sequence of S1101 to S1108 is not limited in the embodiments of the present application. Figure 11

[0352] S1101, the terminal device sends a second request message to the first core network device; correspondingly, the first core network device can receive the second request message.

[0353] S1102, the first core network device sends a PDU session resource release command message to the access network device; correspondingly, the first access network device can receive the PDU session resource release command message.

[0354] S1103, the access network device sends a PDU session resource release response message to the first core network device.

[0355] S1104, the access network device sends an RRC reconfiguration message 1 to the IAB node.

[0356] Here, the RRC reconfiguration message can carry indication information that the DRBs corresponding to the session 2 and the session 3 are released.

[0357] S1105, the IAB node releases the DRBs corresponding to the session 2 and the session 3, and sends an RRC reconfiguration completion message 1 to the access network device.

[0358] S1106, the access network device sends an RRC reconfiguration message 2 to the terminal device. ​​

[0359] Here, the RRC reconfiguration message can carry indication information that the DRB corresponding to session 3 is released, and then the terminal device can release the configuration and resources related to one or more DRBs corresponding to session 3.

[0360] S1107, the terminal device sends an RRC reconfiguration completion message 2 to the access network device.

[0361] S1108, the IAB node cancels scheduling data in the M PDU sessions according to the first indication information, the second indication information and the third indication information.

[0362] After S1108, the terminal device's service will be switched from edge computing to no edge computing. If edge computing is needed again later, the terminal device can trigger a PDU session modification or PDU session establishment process, such as the process shown in Embodiment Five above, to switch to edge computing.

[0363] By using the above method, the terminal device can be switched from edge computing to no edge computing, or from no edge computing to edge computing, so as to ensure that the terminal device can freely select the corresponding mode under different working modes (such as with or without a connected power supply, with or without an externally attached strong computing power device, etc.), while ensuring service experience and user experience.

[0364] For the above, it should be noted that:

[0365] (1) The communication method provided by the embodiments of the present application can also be applied to a switching scenario, such as switching of a terminal device from a cell of a first access network device to a cell of a second access network device. The first access network device can be a source access network device, and the second access network device can be a target access network device. The source access network device and the target access network device can be access network devices under the same AMF network element, or can also be access network devices under different AMF network elements.

[0366] In the scenario shown in FIG. 1, the terminal device and the auxiliary terminal device access the same access network device, and the terminal device and the auxiliary terminal device can also access different access network devices in actual implementation. For example, the terminal device accesses the access network device 1, and the auxiliary terminal device accesses the access network device 2. In this case, the interaction between the access network device 1 and the access network device 2 can also be involved, and the implementation can be adaptively referred to the description of the terminal device and the auxiliary terminal device accessing the same access network device. Similarly, in the scenario shown in FIG. 2, one access network device is also taken as an example for description, and in actual implementation, the terminal device can access the access network device 1, and the local device includes the access network device 2. In the scenario shown in FIG. 3, one access network device is also taken as an example for description, and in actual implementation, the terminal device can access the access network device 1, and the IAB node can access the access network device 2.

[0367] (2) In the scenario shown in FIG. 1, the terminal device and the auxiliary terminal device access the same access network device, and the terminal device and the auxiliary terminal device can also access different access network devices in actual implementation. For example, the terminal device accesses the access network device 1, and the auxiliary terminal device accesses the access network device 2. In this case, the interaction between the access network device 1 and the access network device 2 can also be involved, and the implementation can be adaptively referred to the description of the terminal device and the auxiliary terminal device accessing the same access network device. Similarly, in the scenario shown in FIG. 2, one access network device is also taken as an example for description, and in actual implementation, the terminal device can access the access network device 1, and the local device includes the access network device 2. In the scenario shown in FIG. 3, one access network device is also taken as an example for description, and in actual implementation, the terminal device can access the access network device 1, and the IAB node can access the access network device 2. Figure 4a (2) In the scenario shown in FIG. 1, the terminal device and the auxiliary terminal device access the same access network device, and the terminal device and the auxiliary terminal device can also access different access network devices in actual implementation. For example, the terminal device accesses the access network device 1, and the auxiliary terminal device accesses the access network device 2. In this case, the interaction between the access network device 1 and the access network device 2 can also be involved, and the implementation can be adaptively referred to the description of the terminal device and the auxiliary terminal device accessing the same access network device. Similarly, in the scenario shown in FIG. 2, one access network device is also taken as an example for description, and in actual implementation, the terminal device can access the access network device 1, and the local device includes the access network device 2. In the scenario shown in FIG. 3, one access network device is also taken as an example for description, and in actual implementation, the terminal device can access the access network device 1, and the IAB node can access the access network device 2. Figure 4b (2) In the scenario shown in FIG. 1, the terminal device and the auxiliary terminal device access the same access network device, and the terminal device and the auxiliary terminal device can also access different access network devices in actual implementation. For example, the terminal device accesses the access network device 1, and the auxiliary terminal device accesses the access network device 2. In this case, the interaction between the access network device 1 and the access network device 2 can also be involved, and the implementation can be adaptively referred to the description of the terminal device and the auxiliary terminal device accessing the same access network device. Similarly, in the scenario shown in FIG. 2, one access network device is also taken as an example for description, and in actual implementation, the terminal device can access the access network device 1, and the local device includes the access network device 2. In the scenario shown in FIG. 3, one access network device is also taken as an example for description, and in actual implementation, the terminal device can access the access network device 1, and the IAB node can access the access network device 2. Figure 4c (2) In the scenario shown in FIG. 1, the terminal device and the auxiliary terminal device access the same access network device, and the terminal device and the auxiliary terminal device can also access different access network devices in actual implementation. For example, the terminal device accesses the access network device 1, and the auxiliary terminal device accesses the access network device 2. In this case, the interaction between the access network device 1 and the access network device 2 can also be involved, and the implementation can be adaptively referred to the description of the terminal device and the auxiliary terminal device accessing the same access network device. Similarly, in the scenario shown in FIG. 2, one access network device is also taken as an example for description, and in actual implementation, the terminal device can access the access network device 1, and the local device includes the access network device 2. In the scenario shown in FIG. 3, one access network device is also taken as an example for description, and in actual implementation, the terminal device can access the access network device 1, and the IAB node can access the access network device 2. (2) In the scenario shown in FIG. 1, the terminal device and the auxiliary terminal device access the same access network device, and the terminal device and the auxiliary terminal device can also access different access network devices in actual implementation. For example, the terminal device accesses the access network device 1, and the auxiliary terminal device accesses the access network device 2. In this case, the interaction between the access network device 1 and the access network device 2 can also be involved, and the implementation can be adaptively referred to the description of the terminal device and the auxiliary terminal device accessing the same access network device. Similarly, in the scenario shown in FIG. 2, one access network device is also taken as an example for description, and in actual implementation, the terminal device can access the access network device 1, and the local device includes the access network device 2. In the scenario shown in FIG. 3, one access network device is also taken as an example for description, and in actual implementation, the terminal device can access the access network device 1, and the IAB node can access the access network device 2.

[0368] (3) The operation numbers of the various flowcharts described in the above embodiments are only examples of the execution flow, and do not constitute a limitation on the execution order of the operations. There is no strict execution order between the operations that have no time sequence dependency relationship among the embodiments of the present application. In addition, not all the operations shown in the various flowcharts are necessary operations, and part of the operations can be added or deleted based on the various flowcharts as needed.

[0369] (4) The above focuses on describing the differences between different embodiments in Embodiments 1-6. Except for the differences, Embodiments 1-6 can be mutually referred to.

[0370] (5) The above embodiments 1-6 use some messages in the 5G communication system, but in the specific implementation, different messages or message names can be used, and the embodiments of the present application do not limit this.

[0371] The above mainly introduces the scheme provided by the embodiments of the present application from the perspective of device interaction. It can be understood that, in order to realize the above functions, the network device, the core network device or the terminal device can include the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed in the present application, the embodiments of the present application can be realized in the form of hardware or a combination of hardware and computer software. Whether a certain function is realized in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0372] The embodiments of the present application can divide the functional units of the network device, the core network device or the terminal device according to the above method examples, for example, each functional unit can be divided according to each function, or two or more functions can be integrated in one unit. The integrated unit can be realized in the form of hardware or software functional unit.

[0373] In the case of using integrated units, Figure 12 A possible exemplary block diagram of the device involved in the embodiments of the present application is shown. As shown in the figure, Figure 12 The device 1200 can include a processing unit 1202 and a communication unit 1203. The processing unit 1202 is used to control and manage the actions of the device 1200. The communication unit 1203 is used to support the communication of the device 1200 with other devices. Optionally, the communication unit 1203, also known as the transceiver unit, can include a receiving unit and / or a sending unit, which are used to perform receiving and sending operations, respectively. The device 1200 can also include a storage unit 1201 for storing the program code and / or data of the device 1200.

[0374] The apparatus 1200 can be the access network device in the above embodiments, or can also be a chip arranged in the access network device. The processing unit 1202 can support the apparatus 1200 to perform the actions of the access network device in the above method examples. Alternatively, the processing unit 1202 mainly performs the internal actions of the access network device in the method examples, and the communication unit 1203 can support the communication between the apparatus 1200 and other devices.

[0375] Specifically, in one embodiment, the communication unit 1203 is configured to receive first indication information, the first indication information indicating that M sessions have an association relationship, M being an integer greater than 1; and the processing unit 1202 is configured to process the M sessions according to the first indication information.

[0376] In a possible design, the processing unit 1202 is specifically configured to accept or reject an establishment request of at least two of the M sessions, or accept or reject a modification request of at least two of the M sessions.

[0377] In a possible design, the M sessions include a first session between a terminal device and an application server, a second session between the application server and a local device, and a third session between the local device and the terminal device; and the terminal device establishes a radio resource control (RRC) connection with the first access network device.

[0378] In a possible design, the communication unit 1203 is further configured to receive second indication information and / or third indication information; the second indication information indicates that the local device performs edge computing on data in the received second session or third session, and the third indication information indicates a time length required by the local device for performing local edge computing.

[0379] In a possible design, the processing unit 1202 is specifically configured to determine that the local device performs edge computing on data in the received second session, and schedule the data in the second session at a first time and schedule the data in the third session at a second time after the first time; and a time interval between the first time and the second time is obtained according to the time length required by the local device for performing edge computing.

[0380] In a possible design, the processing unit 1202 is specifically configured to determine that the local device performs edge computing on data in the received third session, and schedule the data in the third session at a first time and schedule the data in the second session at a second time after the first time; and a time interval between the first time and the second time is obtained according to the time length required by the local device for performing edge computing.

[0381] In a possible design, the local device includes an auxiliary terminal device, or the local device includes an access network device.

[0382] In a possible design, the communication unit 1203 is further configured to send, to the local device, fourth indication information, where the fourth indication information indicates that the DRB corresponding to the second session has an association relationship with the DRB corresponding to the third session.

[0383] In a possible design, the communication unit 1203 is further configured to send, to the local device, second indication information and / or third indication information, where the second indication information indicates that the local device performs edge computing on the data received in the second session or the third session, and the third indication information indicates a time length required by the local device for local edge computing.

[0384] In a possible design, the local device includes a wireless backhaul device.

[0385] In a possible design, the communication unit 1203 is further configured to send, to the terminal device, fifth indication information, where the fifth indication information indicates a round-trip time delay; and the round-trip time delay is a time interval between a sending time of the terminal device sending first data through the third session and a receiving time of the terminal device receiving second data through the first session, the second data being obtained according to the first data, or the round-trip time delay is a time interval between a sending time of the terminal device sending third data through the first session and a receiving time of the terminal device receiving fourth data through the third session, the fourth data being obtained according to the third data.

[0386] In a possible design, the communication unit 1203 is specifically configured to receive, from a core network device or a second access network device, the first indication information, where the second access network device is a source access network device of the terminal device, and the first access network device is a target access network device of the terminal device.

[0387] In a possible design, the first indication information includes M pieces of association information corresponding to M sessions respectively, and / or identification information of the local device; and the M pieces of association information are the same.

[0388] In a possible design, the M sessions include the first session, and the association information corresponding to the first session includes type information of the first session and / or an association identifier of the first session; and the type information of the first session is used to indicate that the type of the first session is separate rendering or segmented computing.

[0389] In a possible design, the communication unit 1203 is further configured to receive sixth indication information, where the sixth indication information indicates that the M sessions are no longer associated; and release, according to the sixth indication information, a resource of the second session and a resource of the third session.

[0390] The apparatus 1200 can be a core network device in the above embodiments, or can also be a chip arranged in a core network device. The processing unit 1202 can support the apparatus 1200 to perform the actions of the core network device in each method example. Alternatively, the processing unit 1202 mainly performs the internal actions of the core network device in the method example, and the communication unit 1203 can support the communication between the apparatus 1200 and other devices.

[0391] Specifically, in one embodiment, the communication unit 1203 is configured to: obtain first indication information, the first indication information indicating that M sessions have an association relationship, M being an integer greater than 1; and send the first indication information to the access network device.

[0392] In a possible design, the M sessions include a first session between a terminal device and an application server, a second session between the application server and a local device, and a third session between the local device and the terminal device; and the terminal device has established an RRC connection with the access network device.

[0393] In a possible design, the communication unit 1203 is further configured to: send second indication information and / or third indication information to the access network device; the second indication information indicating that the local device performs edge computing on data received in the second session or the third session, and the third indication information indicating a time length required by the local device for local edge computing.

[0394] In a possible design, the communication unit 1203 is specifically configured to: obtain the first indication information from the terminal device; or obtain the first indication information from a second core network device.

[0395] In a possible design, the communication unit 1203 is specifically configured to: receive a first request message from the terminal device, the first request message being used to request to establish or modify the M sessions or a first session in the M sessions, and the request message including the first indication information.

[0396] In a possible design, the communication unit 1203 is further configured to: send sixth indication information to the access network device, the sixth indication information indicating that the M sessions are no longer associated.

[0397] In a possible design, the communication unit 1203 is further configured to: receive a second request message from the terminal device, the second request message being used to request to modify the first session in the M sessions, and the second request message including seventh indication information, the seventh indication information indicating that the first session is no longer associated with other sessions in the M sessions; and determine the sixth indication information according to the second request message.

[0398] It should be understood that the division of units in the above apparatus is only a logical function division, and in actual implementation, all or part of the units can be integrated into one physical entity, or can be physically separated. The units in the apparatus can all be implemented in the form of software invoked by a processing element; or all be implemented in the form of hardware; or part of the units are implemented in the form of software invoked by a processing element, and part of the units are implemented in the form of hardware. For example, each unit can be a separately established processing element, or can be integrated into a chip of the apparatus, in addition, the unit can also be stored in the form of a program in a memory, and the function of the unit is invoked and executed by a processing element of the apparatus. In addition, all or part of the units can be integrated together, or can be independently implemented. The processing element mentioned herein can be a processor, which can be an integrated circuit with a signal processing capability. In the implementation process, each operation of the above method or each unit can be implemented by an integrated logic circuit of hardware in the processing element, or in the form of software invoked by the processing element.

[0399] In one example, the units in any of the above apparatuses can be one or more integrated circuits configured to implement the above method, for example, one or more application specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For another example, when the units in the apparatus can be implemented in the form of a program invoked by a processing element, the processing element can be a processor, such as a general purpose central processing unit (CPU), or other processor capable of invoking programs. For another example, the units can be integrated together to implement a system-on-a-chip (SOC).

[0400] The above receiving unit is an interface circuit of the apparatus for receiving signals from other apparatuses. For example, when the apparatus is implemented in the form of a chip, the receiving unit is an interface circuit of the chip for receiving signals from other chips or apparatuses. The above transmitting unit is an interface circuit of the apparatus for transmitting signals to other apparatuses. For example, when the apparatus is implemented in the form of a chip, the transmitting unit is an interface circuit of the chip for transmitting signals to other chips or apparatuses.

[0401] Reference is made to Figure 13 A structure schematic diagram of an access network device provided by the embodiment of the present application is shown in FIG. 1. The access network device (or base station) can be applied to a system as shown in FIG. 2.Figure 1 In the system architecture shown, the functions of the access network device in the above method embodiments are performed. The access network device 130 can include one or more DUs 1301 and one or more CUs 1302. The DU 1301 can include at least one antenna 13011, at least one radio frequency unit 13012, at least one processor 13013, and at least one memory 13014. The DU 1301 is mainly used for the transceiving of radio frequency signals and the conversion between radio frequency signals and baseband signals, and part of the baseband processing. The CU 1302 can include at least one processor 13022 and at least one memory 13021.

[0402] The CU 1302 is mainly used for baseband processing, controlling the access network device, etc. The DU 1301 and the CU 1302 can be physically arranged together or physically separated, i.e., a distributed base station. The CU 1302 is the control center of the access network device, also known as a processing unit, and is mainly used to complete the baseband processing function. For example, the CU 1302 can be used to control the access network device to perform the operation processes of the access network device in the above method embodiments.

[0403] In addition, the access network device 130 can include one or more radio frequency units, one or more DUs, and one or more CUs. Among them, the DU can include at least one processor 13013 and at least one memory 13014, the radio frequency unit can include at least one antenna 13011 and at least one radio frequency unit 13012, and the CU can include at least one processor 13022 and at least one memory 13021.

[0404] In one example, the CU 1302 can be composed of one or more single boards, and multiple single boards can jointly support a single access indicated wireless access network (such as a 5G network), or can separately support wireless access networks of different access systems (such as an LTE network, a 5G network, or other networks). The memory 13021 and the processor 13022 can serve one or more single boards. That is, the memory and the processor can be separately arranged on each single board. Multiple single boards can also share the same memory and processor. In addition, necessary circuits can also be arranged on each single board. The DU 1301 can be composed of one or more single boards, and multiple single boards can jointly support a single access indicated wireless access network (such as a 5G network), or can separately support wireless access networks of different access systems (such as an LTE network, a 5G network, or other networks). The memory 13014 and the processor 13013 can serve one or more single boards. That is, the memory and the processor can be separately arranged on each single board. Multiple single boards can also share the same memory and processor. In addition, necessary circuits can also be arranged on each single board.

[0405] Figure 13 The access network device shown can implement Figure 5 to Figure 11 The method embodiment shown involves various processes of the access network device. Figure 13 The operation and / or function of each module in the access network device shown is respectively to implement the corresponding flow in the above method embodiment. For details, please refer to the description in the above method embodiment, and the detailed description is appropriately omitted here to avoid repetition.

[0406] Reference Figure 14 A structural schematic diagram of a core network device is provided for the embodiments of the present application. It can be the SMF network element or the AMF network element in the above embodiments, used to implement the operation of the SMF network element or the AMF network element in the above embodiments.

[0407] As Figure 14 The core network device 1400 can include a processor 1401, a memory 1402, and an interface circuit 1403. The processor 1401 can be used to process communication protocols and communication data, and control the communication device. The memory 1402 can be used to store programs and data, and the processor 1401 can execute the method performed by the AMF network element or the SMF network element in the embodiments of the present application based on the programs. The interface circuit 1403 can be used for the core network device 1400 to communicate with other devices, which can be wired or wireless communication, and the interface circuit can be, for example, a service-oriented communication interface.

[0408] The above memory 1402 can also be external to the core network device 1400, at this time the core network device 1400 can include the interface circuit 1403 and the processor 1401. The above interface circuit 1403 can also be external to the core network device 1400, at this time the core network device 1400 can include the memory 1402 and the processor 1401. When the interface circuit 1403 and the memory 1402 are both external to the core network device 1400, the communication device 1400 can include the processor 1401.

[0409] Figure 14 The core network device shown can implement Figure 5 to Figure 11 The method embodiment shown involves various processes of the core network device. Figure 14 The operation and / or function of each module in the core network device shown is respectively to implement the corresponding flow in the above method embodiment. For details, please refer to the description in the above method embodiment, and the detailed description is appropriately omitted here to avoid repetition.

[0410] The terms "system" and "network" in the embodiments of the present application can be used interchangeably. "At least one" means one or more, and "multiple" means two or more. "And / or" describes the association relationship of associated objects, which means that there can be three relationships, for example, A and / or B can represent the cases of A alone, A and B together, and B alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects before and after it. "At least one of the following" or similar expressions means any combination of these items, including any combination of single item or multiple items. For example, "at least one of A, B, and C" includes A, B, C, AB, AC, BC, or ABC. In addition, unless otherwise specified, the ordinal numbers "first", "second", etc. mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the order, time sequence, priority, or importance of the multiple objects.

[0411] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0412] The present application is described with reference to flowcharts and / or block diagrams according to the methods, devices (systems), and computer program products of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus produce a device that implements the functions specified in the flowcharts and / or block diagrams. Figure I The functions specified in one or more flows and / or blocks. Figure I The functions specified in one or more flows and / or blocks.

[0413] These computer program instructions can also be stored in a computer-readable memory that can direct the computer or other programmable data processing apparatus to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including instruction devices that implement the functions specified in the flowcharts and / or block diagrams. Figure I The functions specified in one or more flows and / or blocks. Figure I The functions specified in one or more flows and / or blocks.

[0414] These computer program instructions can also be loaded into a computer or other programmable data processing devices, so that a series of operational steps are performed on the computer or other programmable data processing devices to generate computer-implemented processes, thus the instructions executed on the computer or other programmable data processing devices provide processes for implementing the functions specified in the flowchart Figure I flow or multiple flows and / or blocks Figure I flow or multiple flows and / or blocks

[0415] Obviously, those skilled in the art can make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims

1. A communication method characterized by comprising: The method is applied to a first access network device or a chip in the first access network device, and the method comprises: receiving first indication information, the first indication information indicating that M sessions have an association relationship, M being an integer greater than 1; processing the M sessions according to the first indication information; wherein the M sessions comprise a first session between a terminal device and an application server, a second session between the application server and a local device, and a third session between the local device and the terminal device; the terminal device and the first access network device establish a radio resource control (RRC) connection.

2. The method of claim 1, wherein, The processing of the M sessions comprises: admitting or rejecting establishment requests of at least two of the M sessions; or admitting or rejecting modification requests of at least two of the M sessions.

3. The method of claim 1, wherein, The method further comprises: receiving second indication information and / or third indication information; wherein the second indication information indicates that the local device performs edge computing on data received in the second session or the third session, and the third indication information indicates a time length required by the local device for local edge computing.

4. The method of claim 3, wherein, The processing of the M sessions comprises: determining that the local device performs edge computing on data received in the second session; scheduling data in the second session at a first time and scheduling data in the third session at a second time after the first time; wherein a time interval between the first time and the second time is obtained according to the time length required by the local device for edge computing.

5. The method of claim 3, wherein, The processing of the M sessions comprises: determining that the local device performs edge computing on data received in the third session; scheduling data in the third session at a first time and scheduling data in the second session at a second time after the first time; wherein a time interval between the first time and the second time is obtained according to the time length required by the local device for edge computing.

6. The method of claim 5, wherein, The local device comprises an auxiliary terminal device, or the local device comprises the access network device.

7. The method of claim 3, wherein, The method further comprises: sending fourth indication information to the local device, the fourth indication information indicating that a data radio bearer (DRB) corresponding to the second session and a DRB corresponding to the third session have an association relationship.

8. The method of claim 7, wherein, The method further comprises: sending second indication information and / or third indication information to the local device, wherein the second indication information indicates that the local device performs edge computing on data received in the second session or the third session, and the third indication information indicates a time length required by the local device for local edge computing.

9. The method of claim 8, wherein, The local device comprises a wireless backhaul device.

10. The method according to any one of claims 1 to 9, characterized in that, The method further comprises: sending fifth indication information to the terminal device, the fifth indication information indicating a round-trip time (RTT). The round-trip delay is a time interval between a sending time of sending first data by the terminal device through the third session and a receiving time of receiving second data by the terminal device through the first session, the second data being obtained according to the first data. The round-trip delay is a time interval between a sending time of sending third data by the terminal device through the first session and a receiving time of receiving fourth data by the terminal device through the third session, the fourth data being obtained according to the third data.

11. The method according to any one of claims 1 to 9, characterized in that, The receiving first indication information comprises: The first indication information is received from a core network device or a second access network device. The second access network device is a source access network device of the terminal device, and the first access network device is a target access network device of the terminal device.

12. The method according to any one of claims 1 to 9, characterized in that, The first indication information comprises M pieces of association information corresponding to the M sessions respectively, and / or identification information of the local device; wherein the M pieces of association information are the same.

13. The method of claim 12, wherein, The M sessions comprise a first session, and the association information corresponding to the first session comprises type information of the first session and / or an association identifier of the first session. The type information of the first session is used to indicate that the type of the first session is separate rendering or segmented calculation.

14. The method according to any one of claims 1 to 9, characterized in that, The method further comprises: The sixth indication information is received, and the sixth indication information indicates that the M sessions are no longer associated. According to the sixth indication information, resources of the second session and resources of the third session are released.

15. A method of communication, comprising: The method is applied to a first core network device or a chip in the first core network device, and the method comprises: Obtaining first indication information, the first indication information indicating that M sessions have an association relationship, M being an integer greater than 1; The first indication information is sent to an access network device. The M sessions comprise a first session between a terminal device and an application server, a second session between the application server and a local device, and a third session between the local device and the terminal device; and the terminal device establishes an RRC connection with the access network device.

16. The method of claim 15, wherein, The method further comprises: Second indication information and / or third indication information are sent to the access network device; wherein the second indication information indicates that the local device performs edge calculation on data received in the second session or the third session, and the third indication information indicates a time length required for the local device to perform local edge calculation.

17. The method of claim 15, wherein, Obtaining first indication information comprises: The first indication information is obtained from the terminal device; or The first indication information is obtained from a second core network device.

18. The method of claim 17, wherein, Obtaining the first indication information from the terminal device comprises: A first request message is received from the terminal device, the first request message being used to request to establish or request to modify the M sessions or a first session in the M sessions, and the request message comprises the first indication information.

19. The method according to any one of claims 15 to 18, characterized in that, The method further comprises: The sixth indication information is sent to the access network device, the sixth indication information indicating that the M sessions are no longer associated.

20. The method of claim 19, wherein, The method further comprises: receiving a second request message from the terminal device, the second request message requesting to modify a first session of the M sessions, the second request message comprising seventh indication information, the seventh indication information indicating that the first session is no longer associated with other sessions of the M sessions; determining the sixth indication information according to the second request message.

21. A communications device, characterized by A module for performing the method of any of claims 1-14.

22. A communications device, characterized by A module for performing the method of any of claims 15-20.

23. A communications device, characterized by A processor and a memory coupled to the processor, the processor configured to implement a method recited in any of claims 1-14.

24. A communications device, characterized by A processor and a memory coupled to the processor, the processor configured to implement a method recited in any of claims 15-20.

25. A communications device, characterized by A processor and an interface circuit, the interface circuit for receiving a signal from another communication device outside the communication device and transmitting the signal to the processor or sending a signal from the processor to the another communication device outside the communication device, the processor configured to implement a method recited in any of claims 1-14 through logic circuitry or executable code instructions.

26. A communications device, characterized by A processor and an interface circuit, the interface circuit for receiving a signal from another communication device outside the communication device and transmitting the signal to the processor or sending a signal from the processor to the another communication device outside the communication device, the processor configured to implement a method recited in any of claims 15-20 through logic circuitry or executable code instructions.

27. A computer readable storage medium, characterized in that, The storage medium has stored therein a computer program or instructions, which, when executed by a communication device, implement a method recited in any of claims 1-14 or a method recited in any of claims 15-20.

28. A communication system, characterized by A communication device recited in any of claims 21, 23, 25 and a communication device recited in any of claims 22, 24, 26.

29. A computer program product, characterised in that, When a computer reads and executes the program or instructions in the computer program product, a method recited in any of claims 1-20 is caused to be performed.

Images