WO2022001753A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2022001753A1
WO2022001753A1 PCT/CN2021/101563 CN2021101563W WO2022001753A1 WO 2022001753 A1 WO2022001753 A1 WO 2022001753A1 CN 2021101563 W CN2021101563 W CN 2021101563W WO 2022001753 A1 WO2022001753 A1 WO 2022001753A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
indication information
data
sessions
network device
Prior art date
Application number
PCT/CN2021/101563
Other languages
English (en)
French (fr)
Inventor
曾清海
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2022001753A1 publication Critical patent/WO2022001753A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a communication method and device.
  • VR technology is a new means of human-computer interaction 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, mainly including simulated environment, perception, natural skills and sensing equipment.
  • the simulated environment is a real-time dynamic three-dimensional realistic image generated by a computer; perception means that an ideal VR should have the perception that all people have. , motion and other perceptions, even including smell and taste, also known as multisensory; natural skills refer to people's head turning, eyes, gestures, or other human behaviors, which are processed by the computer to adapt to the movements of the participants
  • Sensing devices refer to three-dimensional interactive devices.
  • VR services have local secondary rendering scenarios.
  • the VR helmet can first send behavioral data such as head rotation, eyes, gestures, etc. to the VR server.
  • the VR server generates a simulation environment based on these data, and pre-renders the simulation environment, and then the VR server will The pre-rendered data is sent to the local device for re-rendering, and then the local device sends the re-rendered data to the VR headset, and the headset presents a three-dimensional realistic image, including hearing, touch, force and motion. wait for perception.
  • the present application provides a communication method and device, which are convenient to meet the synchronization requirements between different sessions.
  • an embodiment of the present application provides a communication method, and the method can be applied to a first access network device or a chip in the first access network device.
  • the first access network device may receive first indication information, where the first indication information indicates that M sessions have an association relationship, where M is an integer greater than 1; and process the M sessions according to the first indication information .
  • the first access network device when processing the M sessions, the first access network device can consider the association relationship among the M sessions, thereby facilitating synchronization requirements between different sessions and effectively ensuring the user experience quality of services.
  • processing the M sessions includes: accepting establishment requests of at least two sessions among the M sessions or rejecting establishment requests of at least two sessions among the M sessions; or, accepting establishment requests of at least two sessions among the M sessions; Modify requests for at least two sessions or reject modification requests for at least two sessions among the M sessions.
  • the first access network device can decide whether to accept or reject the session establishment request or modification request according to the association relationship between the sessions, thereby effectively preventing the first access network device from accepting or rejecting the establishment of some sessions The problem that the business cannot be realized normally due to the request or modification of the request.
  • 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 session; wherein, the terminal device and the first access network device establish a radio resource control RRC connection.
  • the method further includes: receiving second indication information and/or third indication information; wherein the second indication information indicates that the local device is not responsible for the received second session or third session.
  • the data is subjected to edge computing, and the third indication information indicates the duration required for the local device to perform local edge computing.
  • processing the M sessions includes: determining that the local device performs edge computing on the received data in the second session; scheduling the data in the second session at the first time, and at the first time The second time after the time schedules the data in the third session; wherein, the time interval between the first time and the second time is obtained according to the time duration required by the local device to perform edge computing.
  • processing the M sessions includes: determining that the local device performs edge computing on the data in the third session received; scheduling the data in the third session at the first time, and at the first time The second time after the time schedules the data in the second session; wherein, the time interval between the first time and the second time is obtained according to the time duration required by the local device to perform edge computing.
  • the first access network device can schedule the data in the second session and the third session according to the time required for edge computing, it is possible to synchronize the service data of different sessions in the session set in a certain order and time. Relational cooperative transmission; for example, scheduling the data in the third session at a second time after the first time can avoid scheduling the data in the third session prematurely, which may cause the local device to have not completed edge computing, or avoid scheduling too late
  • the data in the third session affects the data transmission efficiency.
  • the local equipment includes auxiliary terminal equipment, or the local equipment includes access network equipment.
  • the method further includes: sending fourth indication information to the local device, where the fourth indication information indicates that the data radio bearer DRB corresponding to the second session has an association relationship with the DRB corresponding to the third session.
  • the method further includes: sending second indication information and/or third indication information to the local device, where the second indication information indicates that the local device is not involved in the received second session or third session
  • the data is used for edge computing, and the third indication information indicates the time required for the local device to perform local edge computing.
  • the local device includes a wireless backhaul device.
  • the first access network device can send the fourth indication information and the second indication information and/or the third indication information to the local device, so that the local device can The fourth indication information and the second indication information and/or the third indication information are used to process the second session and the third session.
  • the method further includes: determining that the local device performs edge computing on the received data in the second session; sending first configuration information to the local device, where the first configuration information includes the local device receiving the first configuration information.
  • the first DRX cycle of the data in the two sessions, the first DRX cycle is the same as the transmission cycle of the data in the second session, and the starting offset of the first DRX cycle is aligned with the starting offset of the data in the second session;
  • the terminal device sends second configuration information, where the second configuration information includes a second DRX cycle during which the terminal device receives data in the third session, the second DRX cycle is the same as the first DRX cycle, and the start offset of the second DRX cycle is the same as the first DRX cycle.
  • the time interval between the start offsets of the DRX cycle is obtained according to the time required for the local device to perform edge computing.
  • the method further includes: determining that the local device performs edge computing on data in the received third session; sending first configuration information to the local device, where the first configuration information includes the local device receiving the third session
  • the first DRX cycle of the data in the first DRX cycle is the same as the transmission cycle of the data in the third session, and the starting offset of the first DRX cycle is aligned with the starting offset of the data in the third session;
  • the terminal equipment Send second configuration information, where the second configuration information includes a second DRX cycle for the terminal device to receive data in the first session, the second DRX cycle is the same as the first DRX cycle, and the start offset of the second DRX cycle is the same as the first DRX cycle
  • the time interval between the starting offsets of is obtained according to the round-trip delay; wherein, the round-trip delay is the time between the time when the terminal device sends the first data through the third session and the time when the terminal device receives the second data through the first session.
  • the time interval between the receiving times is obtained
  • the method further includes: sending fifth indication information to the terminal device, where the fifth indication information indicates a round-trip delay; wherein the round-trip delay is the time when the terminal device sends the first data through the third session.
  • the terminal device can perform related optimizations such as power saving according to the round-trip delay.
  • the receiving the first indication information includes: receiving the first indication information from the core network device or the second access network device; wherein the second access network device is the source access of the terminal device network device, the first access network device is the target access network device of the terminal device.
  • the first indication information includes M pieces of association information respectively corresponding to the M sessions, and/or identification information of the local device, wherein the M pieces of association information are the same.
  • the M sessions include a first session, and the associated information corresponding to the first session includes type information of the first session and/or an associated identifier of the first session; wherein the type information of the first session is used for Indicates that the type of the first session is split rendering or segmented computing.
  • the method further includes: receiving sixth indication information, where the sixth indication information indicates that the M sessions are no longer associated; and according to the sixth indication information, releasing the resources of the second session and the resources of the third session .
  • edge computing it is possible to switch from edge computing to edge computing, so as to ensure that the terminal device can freely choose the corresponding mode under different working modes (such as whether to connect the power supply, whether there is a plug-in device with strong computing power, etc.) Business experience and user experience.
  • 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.
  • the first core network device may acquire first indication information, where the first indication information indicates that M sessions are associated, where M is an integer greater than 1; and, send the first indication information to the access network device.
  • 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; Wherein, the terminal device establishes an RRC connection with the access network device.
  • the method further includes: sending second indication information and/or third indication information to the access network device; wherein the second indication information indicates that the local device is not responsible for the received second session or The data in the third session is subjected to edge computing, and the third indication information indicates the duration required for the local device to perform local edge computing.
  • acquiring the first indication information includes: acquiring the first indication information from a terminal device; or acquiring the first indication information from a second core network device.
  • acquiring 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 the establishment or modification of M sessions or a first one of the M sessions session, the request message includes first indication information.
  • 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.
  • the method further includes: receiving a second request message from the terminal device, where the second request message is used to request to modify the first session among the M sessions, and 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; the sixth indication information is determined according to the second request message.
  • an embodiment of the present application provides a communication method, and the method may be applied to a local device or a chip in the local device, and the local device may include a wireless backhaul device.
  • the local device receives fourth indication information from the access network device, and 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. ; and, according to the second indication information, process the second session and the third session.
  • the second session is a session between the application server and the local device
  • the third session is a session between the local device and the terminal device.
  • the method further includes: receiving second indication information and/or third indication information from the access network device, wherein the second indication information indicates that the local device is not responsible for the received second session Or the data in the third session performs edge computing, and the third indication information indicates the duration required for the local device to perform local edge computing.
  • processing the second session and the third session includes: determining that the local device performs edge computing on the data received in the second session; scheduling the data in the second session at the first time, and scheduling the data in the third session at a second time after the first time; wherein, the time interval between the first time and the second time is obtained according to the time duration required by the local device to perform edge computing.
  • processing the second session and the third session includes: determining that the local device performs edge computing on the data received in the third session; scheduling the data in the third session at the first time, and scheduling the data in the second session at a second time after the first time; wherein, the time interval between the first time and the second time is obtained according to the time duration required for the local device to perform edge computing.
  • 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 for the local device to receive data in the second session, the first DRX cycle The same as the transmission period of the data in the second session, the starting offset of the first DRX period is aligned with the starting offset of the data in the second session; and receiving the second configuration information from the access network device, and sending the The terminal device sends second configuration information, where the second configuration information includes a second DRX cycle during which the terminal device receives data in the third session, the second DRX cycle is the same as the first DRX cycle, and the start offset of the second DRX cycle is the same as the first DRX cycle.
  • the time interval between the start offsets of the DRX cycle is obtained according to the time required for the local device to perform edge computing.
  • 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 for the local device to receive data in the third session, the first The DRX cycle is the same as the transmission cycle of the data in the third session, and the start offset of the first DRX cycle is aligned with the start offset of the data in the third session; and, receiving the second configuration information from the access network device , send second configuration information to the terminal device, the second configuration information includes the second DRX cycle for the terminal device to receive data in the first session, the second DRX cycle is the same as the first DRX cycle, and the start offset of the second DRX cycle is the same as the first DRX cycle.
  • the time interval between the start offsets of the first DRX cycle is obtained according to the round-trip delay; wherein, the round-trip delay is the time between the time when the terminal device sends the first data through the third session and the time when the terminal device sends the first data through the first session.
  • the time interval between the receiving times of receiving the second data, the second data is obtained according to the first data.
  • an embodiment of the present application provides a communication method, which can be applied to a terminal device or a chip in a terminal device. Taking the method applied to a terminal device as an example, in this method, the terminal device determines that M sessions have association relationship, and send a first request message, the first request message is used to request the establishment or modification of M sessions or the first session in the M sessions, the request message includes first indication information, and the first indication information indicates M Sessions are associated.
  • 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; Wherein, the terminal device establishes an RRC connection with the access network device.
  • the method further includes: sending a second request message, where the second request message is used to request to modify the first session, the second request message includes seventh indication information, and the seventh indication information indicates that the first session is related to The other sessions of the M sessions are no longer associated.
  • an embodiment of the present application provides a communication system, where the communication system may include a first access network device and a core network device; wherein the first access network device may be used to perform any possible possibility of the first aspect
  • the core network device may be used to execute the method in any possible design or implementation of the second aspect.
  • the communication system may further include a local device, and the local device may be used to execute the method in any possible design or implementation manner of the third aspect.
  • the communication system may further include a terminal device, and the terminal device may be used to execute the method in any possible design or implementation manner of the fourth aspect.
  • the present application provides a communication device, where the communication device may be an access network device (such as a first access network device) or a chip provided inside the access network device.
  • the communication device has the function of implementing the first aspect.
  • the communication device includes modules or units or means (means) corresponding to the operations involved in performing the first aspect, and the modules, units or means may be implemented by software. , or implemented by hardware, or by executing corresponding software by hardware.
  • the communication device includes a processing unit and a communication unit, wherein the communication unit can be used to send and receive signals to implement communication between the communication device and other devices, for example, the communication unit is used to receive data from Configuration information of the terminal device; the processing unit can be used to perform some internal operations of the communication device.
  • the functions performed by the processing unit and the communication unit may correspond to the operations involved in the first aspect above.
  • the communication device includes a processor, which may be operative to couple with the memory.
  • the memory may store necessary computer programs or instructions to implement the functions involved in the first aspect above.
  • the processor may execute computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication apparatus to implement the method in any possible design or implementation manner of the first aspect.
  • the communication device includes a processor and a memory, which can store necessary computer programs or instructions to implement the functions involved in the first aspect above.
  • the processor may execute computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication apparatus to implement the method in any possible design or implementation manner of the first aspect.
  • the communication device includes a processor and an interface circuit, wherein the processor is configured to communicate with other devices through the interface circuit, and execute the method in any possible design or implementation of the first aspect above .
  • the present application provides a communication device, where the communication device may be a core network device (such as a first core network device) or a chip provided inside the core network device.
  • the communication device has the functions involved in the second aspect.
  • the communication device includes modules or units or means corresponding to the operations involved in the second aspect.
  • the functions, units or means may be implemented by software, or It can be realized by hardware, and it can also be realized by executing corresponding software by hardware.
  • the communication device includes a processing unit and a communication unit, wherein the communication unit can be used to send and receive signals to realize communication between the communication device and other devices, for example, the communication unit is used to send a message to the terminal
  • the device sends system information; the processing unit may be used to perform some internal operations of the communication device.
  • the functions performed by the processing unit and the communication unit may correspond to the operations involved in the second aspect above.
  • the communication device includes a processor, which may be operative to couple with the memory.
  • the memory may store necessary computer programs or instructions to implement the functions involved in the second aspect above.
  • the processor can execute computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication apparatus to implement the method in any possible design or implementation manner of the second aspect.
  • the communication device includes a processor and a memory
  • the memory can store necessary computer programs or instructions for implementing the functions involved in the second aspect above.
  • the processor can execute computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication apparatus to implement the method in any possible design or implementation manner of the second aspect.
  • the communication device includes a processor and an interface circuit, wherein the processor is configured to communicate with other devices through the interface circuit, and execute the method in any possible design or implementation of the second aspect above .
  • the processor may be implemented by hardware or by software.
  • the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor may be a logic circuit or an integrated circuit.
  • the processor may be a general-purpose processor, which is implemented by reading software codes stored in a memory.
  • the above processors may be one or more, and the memory may be one or more.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor. In a specific implementation process, the memory and the processor may be integrated on the same chip, or may be separately provided on different chips.
  • the embodiment of the present application does not limit the type of the memory and the manner of setting the memory and the processor.
  • the present application provides a computer-readable storage medium, where computer-readable instructions are stored in the computer storage medium, and when the computer reads and executes the computer-readable instructions, the computer is made to execute the above-mentioned first aspect to The method in any possible design of the fourth aspect.
  • the present application provides a computer program product that, when the computer reads and executes the computer program product, causes the computer to execute the method in any possible design of the first to fourth aspects.
  • the present application provides a chip including a processor, which is coupled to a memory and configured to read and execute a software program stored in the memory, so as to implement the above-mentioned first to fourth aspects any possible design method of the aspect.
  • FIG. 1 is a schematic diagram of a network architecture to which an embodiment of the present application is applicable;
  • FIG. 2a is a schematic diagram of a protocol layer structure between a terminal device and a network device provided by an embodiment of the present application;
  • FIG. 2b is a schematic diagram of a CU-DU separation architecture provided by an embodiment of the present application.
  • FIG. 2c is a schematic diagram of another CU-DU separation architecture provided by an embodiment of the present application.
  • FIG. 2d is a schematic diagram of the distribution of an air interface protocol stack provided by an embodiment of the present application.
  • 3a is a schematic diagram of session 1, session 2, and session 3 in scenario 1 provided by an embodiment of the present application;
  • 3b is a schematic diagram of session 1, session 2, and session 3 in scenario 2 provided by an embodiment of the present application;
  • FIG. 3c is a schematic flowchart of a PDU session establishment process provided by an embodiment of the present application.
  • FIG. 3d is a schematic diagram of four sessions provided by an embodiment of the present application.
  • 4a is a schematic diagram of session 1, session 2, and session 3 in a situation provided by an embodiment of the present application;
  • 4b is a schematic diagram of session 1, session 2, and session 3 in a situation provided by an embodiment of the present application;
  • 4c is a schematic diagram of session 1, session 2, and session 3 in a situation provided by an embodiment of the present application;
  • FIG. 5 is a schematic flowchart corresponding to the communication method provided by the embodiment of the present application.
  • FIG. 6 is a schematic flowchart corresponding to the communication method provided in Embodiment 1 of the present application.
  • FIG. 7 is a schematic flowchart corresponding to the communication method provided in Embodiment 2 of the present application.
  • FIG. 8 is a schematic flowchart corresponding to the communication method provided in Embodiment 3 of the present application.
  • FIG. 9 is a schematic flowchart corresponding to the communication method provided in Embodiment 4 of the present application.
  • FIG. 10 is a schematic flowchart corresponding to the communication method provided in Embodiment 5 of the present application.
  • FIG. 11 is a schematic flowchart corresponding to the communication method provided by Embodiment 6 of the present application.
  • FIG. 12 is a possible exemplary block diagram of the apparatus involved in the embodiment of the application.
  • FIG. 13 is a schematic structural diagram of an access network device according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a core network device according to an embodiment of the present application.
  • FIG. 1 is a schematic diagram of a network architecture to which an embodiment of the present application is applied.
  • a terminal device can access a wireless network to obtain services from an external network (such as a data network (DN)) through the wireless network, or communicate with other devices through the wireless network, such as with other terminals device communication.
  • the wireless network includes a (radio access network, (R)AN) and a core network (core network, CN), wherein the (R)AN (hereinafter described as RAN) is used to access terminal devices
  • the CN is used to manage the terminal equipment and provide the gateway to communicate with the DN.
  • the terminal equipment, RAN, CN, and DN involved in FIG. 1 are respectively described in detail below.
  • Terminal devices include devices that provide voice and/or data connectivity to users, and may include, for example, handheld devices with wireless connectivity, or processing devices connected to a wireless modem.
  • the terminal equipment may communicate with the core network via the radio access network, exchanging voice and/or data with the RAN.
  • the terminal equipment may include user equipment (UE), wireless terminal equipment, mobile terminal equipment, device-to-device (D2D) terminal equipment, vehicle to everything (V2X) terminal equipment , Machine-to-machine/machine-type communications (M2M/MTC) terminal equipment, Internet of things (IoT) terminal equipment, subscriber units, subscriber stations, mobile stations, remote stations , access point (AP), remote terminal, access terminal, user terminal, user agent, or user equipment, etc.
  • UE user equipment
  • D2D device-to-device
  • V2X vehicle to everything
  • M2M/MTC Machine-to-machine/machine-type communications
  • IoT Internet of things
  • these may include mobile telephones (or "cellular" telephones), computers with mobile terminal equipment, portable, pocket-sized, hand-held, computer-embedded mobile devices, and the like.
  • mobile telephones or "cellular" telephones
  • PCS personal communication service
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • constrained devices such as devices with lower power consumption, or devices with limited storage capacity, or devices with limited computing power, etc.
  • it includes information sensing devices such as barcodes, radio frequency identification (RFID), sensors, global positioning system (GPS), and laser scanners.
  • RFID radio frequency identification
  • GPS global positioning system
  • the terminal device may also be a VR device, an augmented reality (AR) device, a cloud game device, a wireless terminal in industrial control, or a wireless terminal in unmanned driving.
  • a VR device an augmented reality (AR) device
  • AR augmented reality
  • cloud game device a wireless terminal in industrial control
  • wireless terminal in unmanned driving wireless terminals in remote surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • VR equipment includes VR Glass, VR head thief, VR Box, etc.
  • VR application services such as VR video and VR games, and obtain immersive scene experience.
  • Wireless terminals in smart cities can include surveillance cameras that can trigger further actions when they capture specific objects or events, such as alerting police stations, uploading recently captured video, etc.
  • the device for realizing the function of the terminal device may be the terminal device, or it may be a device capable of supporting the terminal device to realize the function, such as a chip system or a combined device or component capable of realizing the function of the terminal device.
  • a chip system may be composed of chips, or may include chips and other discrete devices.
  • the RAN may include one or more RAN devices, and the interface between the RAN device and the terminal device may be a Uu interface (or called an air interface).
  • the names of these interfaces may remain unchanged, or may be replaced with other names, which are not limited in this application.
  • a RAN device is a node or device that accesses a terminal device to a wireless network, and the RAN device may also be referred to as a radio access network device or an access network device.
  • RAN equipment includes, but is not limited to, a new generation base station (generation node B, gNB), an evolved node B (evolved node B, eNB), and a next generation eNB (next generation eNB, ng-eNB) in the 5G communication system.
  • radio network controller radio network controller
  • node B node B
  • BSC base station controller
  • base transceiver station base transceiver station
  • BTS Home base station
  • baseBand unit baseband unit
  • TRP transmitting and receiving point
  • TRP transmitting point
  • TP Mobile switching center
  • the device for implementing the function of the access network device may be the access network device, or may be a device capable of supporting the access network device to realize the function, such as a chip system or a device capable of realizing the function of the access network device
  • the combination device and component of the device can be installed in the access network equipment.
  • the technical solutions provided by the embodiments of the present application are described by taking the device for implementing the functions of the access network equipment as the access network equipment as an example.
  • the control plane protocol layer structure may include a radio resource control (RRC) layer, a packet data convergence protocol (packet data convergence protocol, PDCP) layer. , radio link control (radio link control, RLC) layer, media access control (media access control, MAC) layer and physical layer; user plane protocol layer structure may include PDCP layer, RLC layer, MAC layer and physical layer, in a possible implementation, the PDCP layer may further include a service data adaptation protocol (SDAP) layer.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC media access control
  • SDAP service data adaptation protocol
  • the data transmission needs to go through the user plane protocol layer, such as the SDAP layer, PDCP layer, RLC layer, MAC layer, and physical layer, among which SDAP layer, PDCP layer,
  • the RLC layer, the MAC layer, and the physical layer may also be collectively referred to as the access layer.
  • data is transmitted between the access network device and the terminal device by establishing at least one data radio bearer (DRB), and each DRB may correspond to a set of functional entities, such as including a PDCP layer entity, the 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.
  • DRB and SRB can be collectively referred to as radio bearer (RB) .
  • FIG. 2a is a schematic diagram of downlink data transmission between layers.
  • the downward arrow in FIG. 2a indicates data transmission, and the upward arrow indicates data reception.
  • the SDAP layer entity obtains the data from the upper layer, it can map the data to the PDCP layer entity of the corresponding DRB according to the QoS flow indicator (QFI) of the data, and the PDCP layer entity can transmit the data to at least one corresponding to the PDCP layer entity.
  • QFI QoS flow indicator
  • One RLC layer entity is further transmitted by at least one RLC layer entity to the corresponding MAC layer entity, and then the MAC layer entity generates a transport block, and then performs wireless transmission through the corresponding physical layer entity.
  • the data is encapsulated correspondingly in each layer.
  • the data received by a certain layer from the upper layer of the layer is regarded as the service data unit (SDU) of the layer, and becomes the protocol data unit (protocol data unit) after layer encapsulation. unit, PDU), and then passed to the next layer.
  • SDU service data unit
  • PDU protocol data unit
  • the data received by the PDCP layer entity from the upper layer is called PDCP SDU
  • the data sent by the PDCP layer entity to the lower layer is called PDCP PDU
  • the data received by the RLC layer entity from the upper layer is called RLC SDU
  • the data sent by the RLC layer entity to the lower layer Called RLC PDU can be transmitted between different layers through corresponding channels.
  • data can be transmitted between the RLC layer entity and the MAC layer entity through a logical channel (LCH), and the MAC layer entity and the physical layer entity can be transmitted through the A transport channel to transmit data.
  • LCH logical channel
  • the terminal device also has an application layer and a non-access layer; wherein, the application layer can be used to provide services to applications installed in the terminal device, for example, the terminal device receives Downlink data can be sequentially transmitted from the physical layer to the application layer, and then provided by the application layer to the application program; for another example, the application layer can obtain the data generated by the application program, transmit the data to the physical layer in turn, and send it to other communication devices.
  • the non-access layer can be used for forwarding user data, for example, 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.
  • the RAN device may include one or more centralized units (centralized units, CUs) and one or more distributed units (distributed units, DUs), and multiple DUs may be centrally controlled by one CU.
  • the interface between the CU and the DU may be referred to as an F1 interface, wherein the control panel (CP) interface may be F1-C, and the user panel (UP) interface may be F1-U.
  • CP control panel
  • UP user panel
  • the CU and DU can be divided according to the protocol layer of the wireless network: for example, as shown in Figure 2b, the functions of the PDCP layer and the above protocol layers are set in the CU, and the functions of the protocol layers below the PDCP layer (such as the RLC layer and the MAC layer, etc.) are set in the DU.
  • the above division of the processing functions of CU and DU according to the protocol layer is only an example, and can also be divided in other ways, for example, the functions of the protocol layer above the RLC layer are set in the CU, and the RLC layer and the following protocol layers.
  • the function of the CU is set in the DU.
  • the CU or DU can be divided into functions with more protocol layers.
  • the CU or DU can also be divided into partial processing functions with protocol layers. In one design, some functions of the RLC layer and functions of the protocol layers above the RLC layer are placed in the CU, and the remaining functions of the RLC layer and the functions of the protocol layers below the RLC layer are placed in the DU.
  • the functions of the CU or DU can also be divided according to the service type or other system requirements, for example, by the delay, the functions whose processing time needs to meet the delay requirements are set in the DU, and do not need to meet the delay.
  • the required functionality is set in the CU.
  • the CU may also have one or more functions of the core network.
  • the CU can be set on the network side to facilitate centralized management; the DU can have multiple radio functions, or the radio functions can be set remotely. This embodiment of the present application does not limit this.
  • the functions of the CU may be implemented by one entity, or may also be implemented by different entities.
  • the functions of the CU can be further divided, that is, the control plane and the user plane can be separated and implemented by different entities, namely the control plane CU entity (ie the CU-CP entity) and the user plane CU entity. (ie the CU-UP entity), the CU-CP entity and the CU-UP entity 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 may be the E1 interface
  • the interface between the CU-CP entity and the DU may be the F1-C interface
  • the interface between the CU-UP entity and the DU may be the F1-U interface interface.
  • one DU and one CU-UP can be connected to one CU-CP.
  • one DU can be connected to multiple CU-UPs
  • one CU-UP can be connected to multiple DUs.
  • FIG. 2d is a schematic diagram of the distribution of an air interface protocol stack.
  • the air interface protocol stack may be RLC, MAC, and PHY in the DU, and PDCP and above protocol layers in the CU.
  • the signaling generated by the CU may be sent to the terminal device through the DU, or the signaling generated by the terminal device may be sent to the CU through the DU.
  • the DU may not parse the signaling, but directly encapsulate it through the protocol layer and transparently transmit it to the terminal device or CU.
  • the sending or receiving of the signaling by the DU includes this scenario.
  • the signaling of the RRC or PDCP layer will eventually be processed as the data of the physical layer and sent to the terminal device, or converted from the received data of the physical layer.
  • the signaling of the RRC or PDCP layer can also be considered to be sent by the DU, or sent by the DU and the radio frequency device.
  • the access network device may include a host node and one or more wireless backhaul devices (not shown yet).
  • the terminal device accesses the host node through one or more wireless backhaul devices.
  • 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 medium Relay node (RN).
  • IAB integrated access and backhaul
  • LTE long term evolution
  • RN medium Relay node
  • the wireless backhaul device may also have different names, which are not limited here.
  • Uplink data of the terminal device may be transmitted by one or more IAB nodes to the host node through a wireless backhaul link, and downlink data of the terminal device may be transmitted by one or more IAB nodes to the terminal device through a wireless backhaul link.
  • the donor node may be referred to as an IAB donor (IAB donor) or a donor base station (donor gNodeB, DgNB) or a base station.
  • the previous hop node of a certain IAB node may refer to the last node in the wireless backhaul link including the node that received the data packet before the node; a certain IAB node
  • the next hop node may refer to the node in the wireless backhaul link including the node that first receives the data packet after the node.
  • CN may include one or more CN devices. Taking 5G communication system as an example, CN may include access and mobility management function (AMF) network elements, session management function (SMF) ) network element, user plane function (UPF) network element, policy control function (PCF) network element, unified data management (unified data management, UDM) network element, application function (application function, AF) ) network element, etc.
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • PCF policy control function
  • UDM unified data management
  • UDM application function
  • AF application function
  • the AMF network element is the control plane network element provided by the operator's network. It is responsible for the access control and mobility management of the terminal equipment accessing the operator's network, such as the management of mobility status, the allocation of user temporary identities, and the authentication and authorization of users. .
  • the SMF network element is the control plane network element provided by the operator's network and is responsible for managing the PDU sessions of the terminal equipment.
  • a PDU session is a channel for transmitting PDUs. Terminal devices need to communicate PDUs with the DN through the PDU session.
  • the PDU session is established, maintained and deleted by the SMF network element.
  • SMF network elements include session management (such as session establishment, modification and release, including tunnel maintenance between UPF and RAN), selection and control of UPF network elements, service and session continuity (SSC) mode selection, Session related functions such as roaming.
  • the UPF network element is the gateway provided by the operator, and is the gateway for the communication between the operator's network and the DN.
  • UPF network elements include user plane-related functions such as packet routing and transmission, packet detection, quality of service (QoS) processing, legal interception, upstream packet detection, and downstream packet storage.
  • QoS quality of service
  • the PCF network element is a control plane function provided by the operator, and is used to provide the SMF network element with the policy of the PDU session.
  • the policies may include charging-related policies, QoS-related policies, authorization-related policies, and the like.
  • the UDM network element is a control plane network element provided by an operator, and is responsible for storing information such as subscriber permanent identifier (SUPI) and subscription data of subscribers in the operator's network.
  • SUPI subscriber permanent identifier
  • the AF network element is a functional network element that provides various business services, can interact with the core network through other network elements, and can interact with the policy management framework for policy management.
  • network exposure function NEF
  • UDR network element unified data repository
  • the device for implementing the function of the core network device may be the core network device, or may be a device capable of supporting the core network device to realize the function, such as a chip system or a combined device that can realize the function of the core network device, component, the device can be installed in the core network equipment.
  • the technical solutions provided by the embodiments of the present application are described by taking the device for implementing the functions of the core network equipment as the core network equipment as an example.
  • access network devices for convenience of description, access network devices, wireless backhaul devices, core network devices, and the like may be collectively referred to as network devices.
  • a DN can also be called a packet data network (PDN), which is a network outside the operator's network.
  • PDN packet data network
  • the operator's network can access multiple DNs, and application servers corresponding to various services can be deployed in the DNs (such as VR server), providing a variety of possible services for terminal devices.
  • the application server may be provided with an application layer equivalent to the application layer of the terminal device.
  • Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers.
  • interface serial numbers please refer to the meanings defined in the relevant standard protocols, which are not limited here.
  • a 5G communication system is used as an example for illustration in FIG. 1
  • the solutions in the embodiments of the present application may also be applied to other possible communication systems, such as an LTE communication system or a future sixth generation (the 6th generation) generation, 6G) communication system.
  • the above network elements or functions may be either network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (eg, a cloud platform).
  • the foregoing network element or function may be implemented by one device, or may be implemented jointly by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.
  • the network architecture shown in FIG. 1 can support multiple possible service scenarios, and two possible scenarios are described below.
  • the VR helmet in the local secondary rendering scene, can be connected to the VR server through the access network device, and the posture information of the VR helmet and eyeballs can be sent to the VR server.
  • the VR server generates a VR scene (VR scene) based on the pose information, pre-renders the VR viewport in the VR scene (pre-rendering), generates VR media data, and optionally VR rendering metadata (rendering). metadata); further, the VR server may send the VR media data and optional VR rendering metadata to the local device through the mobile network for local secondary rendering.
  • the local device performs secondary rendering of the VR viewport on the received VR media data, generates new VR media data, and then renders the secondary rendering
  • the new VR media data is then sent to the HMD for display.
  • 3GPP 3rd generation partnership project
  • TR technical report
  • three sessions can be established, namely: session 1 between the VR headset and the VR server, session 2 between the VR server and the local device, and session 2 between the local device and the VR headset Session 3; see Figure 3a, where arrows may represent the direction of data transmission.
  • the VR headset sends the VR headset and eyeball pose information to the VR server through session 1.
  • the VR server sends VR media data and optional VR rendering metadata to the local device for local secondary rendering through session 2.
  • the local device sends the new VR media data after secondary rendering to the VR headset through session 3, and optionally, the VR headset can send the latest VR headset and eyeball pose information to the local device through session 3.
  • the surveillance camera may need to perform image recognition in order to trigger further actions when a specific object or event is captured, such as alarming the police station, uploading recent shots video, etc.
  • image recognition requires very complex computing (such as image recognition methods using artificial intelligence), and roadside surveillance cameras usually do not have this computing power or only have very simple computing power.
  • part or all of the calculation related to image recognition needs to be offloaded to the base station and/or cloud server for calculation.
  • frequently uploading images to the base station and/or cloud server consumes a lot of mobile network bandwidth. Therefore, a possible approach is that the surveillance 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 surveillance camera.
  • three sessions can be established, namely: session 3 between the surveillance camera and the local device, session 2 between the local device and the cloud server, and session 2 between the cloud server and the cloud server.
  • Session 1 between surveillance cameras see Figure 3b, where arrows can represent the direction of data transmission.
  • the surveillance camera sends the image or image data and/or computing context information preliminarily processed by the surveillance camera to the local device through session 3; the local device sends the image data and/or computing context information further processed by the local device to the cloud server through session 2 ; and then the cloud server sends the image recognition result to the surveillance camera through session 1.
  • FIG. 3c is a schematic diagram of a PDU session establishment process in the current 3GPP protocol. Referring to FIG. 3c, the process may include:
  • the SMF network element sends a PDU session resource setup request (PDU session resource setup request) message to the access network device through the AMF network element, where the PDU session resource setup request message includes the identifiers 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.
  • PDU session resource setup request includes the identifiers 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.
  • 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.
  • the access network device may accept some or all of the PDU session establishment requests in the PDU Session Resource Establishment Request message, or may reject some or all of the PDU session establishment requests in the PDU Session Resource Establishment Request message.
  • the access network device accepts the establishment request of PDU session 1 and PDU session 2, and rejects the establishment request of PDU session 3.
  • the access network device sends a PDU session resource establishment response message to the SMF network element through the AMF network element.
  • the PDU session resource establishment response message may include a PDU session establishment failure list (PDU Session Failed to Setup List), and the PDU session establishment failure list includes the identification of the rejected PDU session, such as the identification of the PDU session 3.
  • PDU Session Failed to Setup List PDU Session Failed to Setup List
  • the access network device may reject the establishment request of part or all of the PDU session of the terminal device.
  • the access network device rejects the establishment request of a session among session 1, session 2 and session 3, the VR service will not work normally. accomplish.
  • a synchronous session set (set) will be introduced in this embodiment of the present application, and multiple sessions belonging to the same synchronous session set have an association relationship, so that the access network device can Each session is processed to meet the synchronization requirements between different sessions.
  • the session involved in the embodiments of this application may be used to provide a connectivity service between the first device and the second device, or may be used to implement data transmission between the first device and the second device.
  • the first device and the second device may be a terminal device and an application server respectively, or the first device and the second device may be different terminal devices (for example, terminal device 1 and terminal device 2), or, the first device and the second device may be different terminal devices respectively.
  • the first device and the second device may also be a terminal device and a network device, respectively, or, the first device and the second device may also be other possible devices, which are not specifically limited.
  • a session may refer to a PDU session, or may also refer to an Internet protocol (Internet protocol, IP) connection access network (IP-connectivity access network, IP-CAN) session or a traffic detection function (traffic detection function, TDF) session and other possible sessions, which are not specifically limited.
  • IP Internet protocol
  • IP-connectivity access network IP-CAN
  • TDF traffic detection function
  • the embodiment of the present application is described by taking the establishment of three different sessions (that is, session 1, session 2, and session 3) for implementing the same service as an example, but in practice, it can also be understood as: establishing a session for the same service, and the session includes three parts.
  • 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 local device.
  • the statement of conversation will continue to be used as an example, and in specific practice, it may be replaced by other possible statements.
  • each local device performs a part of edge computing, and the local device N sends the calculation result and optional metadata to the local device N+1, and the last participating part of the edge computing
  • the computing local device sends the computing result and optional metadata to the terminal device or cloud server.
  • the local device may be a terminal device, a base station, an IAB node, a relay node, a CU, DU, CU-CP or CU-UP and other network devices outside the core network.
  • FIG. 3d it is a schematic diagram of four sessions; wherein, the four sessions can be respectively: session 1 between the terminal device and the application server, session 2 between the application server and the local device 1, and the local device Session 3 between local device 1 and local device 2, and session 4 between local device 2 and terminal device.
  • the terminal device in Figure 3c is a VR headset and the application server is a VR server
  • a possible data transmission process is: the VR headset sends the VR headset and eyeball pose information to VR server.
  • the VR server sends the VR media data to the local device 1 through the session 2, and the local device 1 re-renders part of the VR media data.
  • the local device 1 sends the new VR media data obtained by the second rendering to the local device 2 through the session 3, and the local device 2 renders the new VR media data obtained by the second rendering three times to obtain the new VR media data after the third rendering.
  • the local device 2 sends the new VR media data rendered three times to the VR headset through session 3.
  • the VR server, local device 1, local device 2 and VR headset perform serial processing on VR media data, but in practical applications, there may also be parallel processing, such as local device 1 and local device 2 on the VR server Part of the incoming VR media data is re-rendered, and then combined and handed over to the VR headset for display, which is not limited here.
  • the local device involved in the embodiments of the present application may have an application layer function, or may process application layer data.
  • local devices can be used to implement image rendering for VR services; for example, for image recognition services, local devices can be used to implement segmented computing (such as images based on artificial intelligence (AI). Part of the computation of the neural network in the recognition algorithm).
  • AI artificial intelligence
  • the local device may include an auxiliary terminal device (assistant UE, A-UE) and EAS deployed together
  • the auxiliary terminal device may be a mobile phone or a customer premise equipment (customer premise equipment, CPE).
  • the EAS may be a software application in an auxiliary terminal device.
  • FIG. 4a the session 1, session 2 and session 3 described in the above scenario 1 and scenario 2 are illustrated.
  • the local device may include an access network device and an EAS deployed together, wherein the EAS may be directly connected to the access network device.
  • the EAS may also be connected to the access network device through the local user plane function (local-UPF, L-UPF).
  • the local device may include deployment The access network equipment, L-UPF and EAS together, or the local equipment may also be the access network equipment including the L-UPF and EAS functions.
  • the local device may include a wireless backhaul device (such as an IAB node) and an EAS deployed together, where the IAB node may be directly connected to the EAS; alternatively, the local device may be an IAB containing an EAS software application node.
  • a wireless backhaul device such as an IAB node
  • the local device may be an IAB containing an EAS software application node.
  • the above only describes several possible examples of the local device. It is understood that the methods in the embodiments of this application can be applied to EAS and gNB, eNB, ng-eNB, gNB-CU, and eNB-CU , gNB-CU-UP, eNB-CU-UP, IAB nodes and other network devices or auxiliary terminal devices are deployed or integrated together.
  • the embodiments of this application will deploy together or integrate network devices,
  • the EAS and possibly related network entities are regarded as one network entity, collectively referred to as the local device.
  • the embodiments of the present application may be applicable to scenarios in which more than one EAS is deployed on different network devices for the same service; the embodiments of the present application do not limit the connection method between the EAS and the network device, for example, the EAS may directly connect to the access network
  • the equipment is connected, or the EAS can also be connected with the access network equipment through the L-UPF, or they are integrated into a physical equipment.
  • Scenario 1 and Scenario 2 will be mainly used as examples in the following, but the communication method provided by the embodiment of the present application may also be applicable to other possible scenarios.
  • the method provided by the embodiment of the present application may also be applicable to Cloud games, mixed reality (MR) and other scenarios that may have downlink local rendering or downlink edge computing are also applicable to other scenarios with uplink edge computing except scenario 2, which are not specifically limited.
  • MR mixed reality
  • FIG. 5 is a schematic flowchart corresponding to the communication method provided by the embodiment of the present application. As shown in FIG. 5 , the method includes S501 , S502 and S503 , and the embodiment of the present application does not limit the execution order of S501 , S502 and S503 .
  • the first core network device acquires first indication information, where the first indication information indicates that M sessions are associated, and M is an integer greater than 1.
  • the first core network device may 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 indicates that the M sessions belong to the same synchronization session set, and the synchronization session set may also be called a synchronization session group (group) or other possible names, There is no specific limitation; multiple sessions in the synchronization session set are associated.
  • the M sessions may include the first session between the terminal device and the application server (such as the session 1 in the above scenario 1 or scenario 2), and the second session between the application server and the local device (eg session 2 in the above scenario 1 or scenario 2), a third session between the local device and the terminal device (eg session 3 in the aforementioned scenario 1 or scenario 2).
  • an RRC connection is established between the terminal device and the first access network device.
  • the first core network device may acquire the first indication information from the terminal device.
  • the terminal device may send a first request message to the first core network device, where the first request message is used to request to establish or modify the M sessions or the first session in the M sessions, and the first request message includes the first indication information.
  • the first request message may be a PDU session establishment request (PDU session establishment request) message or a PDU session modification request (PDU session modification request) message.
  • the first core network device may acquire the first indication information from the second core network device, where the second core network device may be a UDM network element or a PCF network element.
  • the terminal device can send a PDU session establishment request message or a PDU session modification request message to the first core network device.
  • the first core network device can A device (such as a UDM network element or a PCF network element) acquires the first indication information.
  • the first core network device may also acquire the second indication information and/or the third indication information.
  • the second indication information instructs the local device to perform edge computing on the received data of the second session (such as the above scenario 1), or the second indication information instructs the local device to perform edge computing on the received data of the third session (such as the above-mentioned scenario 1) Scenario 2);
  • the third indication information indicates the duration required for the local device to perform local edge computing.
  • the third indication information indicates The time required for the local device to perform local edge computing refers to the time required for the local device to perform edge computing on the received data of the second session; when the second indication information instructs the local device to perform edge computing on the received data of the third session.
  • the time required for the local device to perform local edge computing indicated by the third indication information refers to the time required for the local device to perform edge computing on the received data of the third session.
  • the first core network device may acquire the second indication information and/or the third indication information in various manners, for example, the manner in which the first core network device acquires the first indication information may be referred to.
  • first indication information, second indication information and third indication information may be provided by the terminal device to the first core network device through the first request message, or may also be received by the first core network device. After the first request message sent by the terminal device, it is obtained from the second core network device. That is to say, the first indication information, the second indication information and the third indication information may be provided by the terminal device or the second core network device, for example, the terminal device or the second core network device may provide all the three pieces of information, or provide each part.
  • the first core network device sends the first indication information to the first access network device; correspondingly, the first access network device may receive the first indication information.
  • the first core network device may also send the second indication information and/or the third indication information to the first access network device.
  • the first core network device may 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, it may also send the first access network device through different messages respectively.
  • the network device sends the first indication information, the second indication information, and the third indication information.
  • the above S502 may also be replaced with: S502', the second access network device sends the first indication information to the first access network device.
  • the second access network device may be the source network device of the terminal device, and the first access network device may be the target network device of the terminal device.
  • RRC RRC_INACTIVE state
  • the second access network device may send the above-mentioned first indication information to the first access network device.
  • the second access network device may also send the second indication information and/or the third indication information to the first access network device. In this case, the above S501 may not be executed.
  • the first access network device processes the M sessions according to the first indication information.
  • the processing of the M sessions by the first access network device may include: (1) The first access network device performs admission control on the M sessions according to the first indication information. And/or, (2) the first 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.
  • the first access network device performs admission control on M sessions according to the first indication information, which may refer to: the first access network device simultaneously admits at least two of the M sessions according to the first indication information
  • the M sessions belong to a synchronous session set, and the at least two sessions may be all sessions in the synchronous session set that require the first access network device to perform admission control.
  • the first access network device may accept the establishment requests of session 1, session 2 and session 3 at the same time or reject session 1, session 2 and session 3 at the same time according to the first indication information.
  • the establishment request of session 3 or, simultaneously accept the modification request of session 1, session 2 and session 3 or reject the modification request of session 1, session 2 and session 3 at the same time.
  • FIG. 4a or FIG. 4c the first access network device may accept the establishment requests of session 1, session 2 and session 3 at the same time or reject session 1, session 2 and session 3 at the same time according to the first indication information.
  • the first access network device may accept the establishment requests of session 1 and session 3 at the same time or reject the establishment requests of session 1 and session 3 at the same time according to the first indication information; or, accept the session at the same time
  • the modification request of session 1 and session 3 or the modification request of session 1 and session 3 is rejected at the same time; wherein, since session 2 does not involve air interface transmission, it is assumed that admission control by the first access network device is not required.
  • the first access network device can decide whether to accept or reject the session establishment request or modification request according to the association relationship between the sessions, it can effectively prevent the first access network device from accepting or rejecting part of the session establishment request. Or modify the request, which leads to the problem that the business cannot be realized normally.
  • the first access network device performs 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 may refer to: if the first access network device determines the local The device performs edge computing on the received data in the second session, and can schedule the data in the second session at the first time (that is, assigning the wireless resource transmission between the first access network device and the local device at the first time) data of the second session), and scheduling the data of the third session at a second time after the first time (that is, allocating radio resources between the local device and the terminal device at the second time to transmit the data of the third session); wherein , the time interval between the first time and the second time is obtained according to the time required for the local device to perform edge computing.
  • the data in the third session may be scheduled at the first time, and the second time after the first time Schedule data in the second session; wherein, the time interval between the first time and the second time is obtained according to the time duration required by the local device to perform edge computing.
  • the time interval between the first time and the second time may be equal to the length of time required for the local device to perform edge computing.
  • scheduling the data in the third session at a second time after the first time can avoid scheduling the data in the third session prematurely, which may cause the local device to have not completed edge computing, or avoid scheduling the third session too late.
  • the data in the session affects the efficiency of data transmission.
  • the first access network device when processing the M sessions, may consider the association relationship between the M sessions, so as to facilitate meeting the synchronization requirements between different sessions and effectively ensure that the user Quality of experience (QoE) for the business.
  • QoE Quality of experience
  • FIG. 5 The method described in FIG. 5 above can be applied to any of the situations shown in FIG. 4a to FIG. 4c. Since the local devices in different situations are different, there are some differences in the implementation process.
  • the communication method provided by the embodiment of the present application will be described below with reference to the situations shown in FIG. 4a to FIG. 4c respectively.
  • the access network device described in the first embodiment to the sixth embodiment may be a device having an RRC connection control function, such as a base station, a CU or a CU-CP.
  • Embodiment 1 a possible implementation will be described by taking the situation shown in FIG. 4a as an example.
  • the local device in FIG. 4a may include an auxiliary terminal device and an EAS.
  • the local device is directly referred to as an auxiliary terminal device.
  • FIG. 6 is a schematic flowchart corresponding to the communication method provided in Embodiment 1 of the present application. As shown in FIG. 6 , the method includes S600 to S610, and the embodiment of the present application does not limit the execution order of S600 to S610.
  • the access network device and/or the first core network device acquire capability information of the auxiliary terminal device, where the capability information of the auxiliary terminal device is used to indicate whether the auxiliary terminal device supports edge computing.
  • the auxiliary terminal device may send capability information to the access network device and/or the first core network device.
  • the auxiliary terminal device reports 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 the registration is completed.
  • the first core network device may also acquire capability information of the auxiliary terminal device from the UDM network element.
  • the terminal device sends a first request message to a first core network device; correspondingly, the first core network device may receive the first request message.
  • the first request message is an example of a PDU session establishment request message.
  • the PDU session establishment request message may be used to request the establishment of M PDU sessions.
  • the PDU session establishment request message may include information of M PDU sessions (such as session 1, session 2, and session 3) and first indication information.
  • An indication information indicates that session 1, session 2 and session 3 have an associated relationship; wherein, the information of the PDU session may include the PDU session identifier (ID), the type of PDU session (type) information and the requested SSC mode (requested SSC mode) in at least one of.
  • ID PDU session identifier
  • type type
  • requested SSC mode requested SSC mode
  • the PDU session establishment request message may further include second indication information and third indication information, wherein the second indication information indicates that the auxiliary terminal device is used to perform edge computing on the received data of session 2 or session 3;
  • the third indication information indicates the duration required for the auxiliary terminal device to perform local edge computing.
  • the non-access layer of the terminal device may first obtain the second indication information and/or the third indication information through the application layer (possibly via the operating system), and then send the PDU session establishment request message to the first core network device .
  • the first indication information indicates that the session 1, the session 2, and the session 3 are associated with various implementations, and several possible implementations are described below.
  • the first indication information includes M pieces of association information respectively corresponding to the M PDU sessions.
  • the association information corresponding to the PDU session may include type information of the PDU session and/or an association ID (association ID) of the PDU session, and PDU sessions with the same type information and/or the same association ID have an association relationship.
  • the type information of the PDU session can be used to indicate that the type of the PDU session is split rendering (for scene 1) or segmented calculation (for scene 2); split rendering (split rendering) can also be described as local rendering, similarly , the segmentation calculation may also have other descriptions, such as split inference, which is not specifically limited. For example, if the types of session 1, session 2, and session 3 are all rendered separately, it means that session 1, session 2, and session 3 are related.
  • the PDU session establishment request message carries the first indication information.
  • the existing information element information element, IE
  • the existing information element can be reused, for example, "separate rendering or segmentation calculation" is added to the type information of each PDU session as a new enumeration value.
  • an information element may be added to the information of each PDU session of the M PDU sessions, and the information element is used to carry the associated identifier of the PDU session.
  • the first indication information includes the identification information of the auxiliary terminal device.
  • the identification information of the auxiliary terminal device may include the IP address and/or the MAC address of the auxiliary terminal device, or may also include other possible information, such as the SUPI of the auxiliary terminal device, is not specifically limited, but any information that enables the first core network device to uniquely identify the auxiliary terminal device can be understood as the identification information of the auxiliary terminal device.
  • the identification information of the auxiliary terminal equipment may be carried in a new information element independent of the information of the PDU session, such as by adding an independent information element "Local Device ID" in the PDU session establishment request message to carry the auxiliary terminal equipment.
  • an information element may be added to the information of each PDU session in the M PDU sessions, which is used to carry the identification information of the auxiliary terminal device.
  • the first indication information includes M pieces of association information respectively corresponding to the M PDU sessions and identification information of the auxiliary terminal device. For specific implementation, refer to implementation mode 1 and implementation mode 2 above.
  • the second indication information indicates that there may be various indication manners for the auxiliary terminal device to perform edge computing on the received data of session 2 or session 3 .
  • the second indication information may include the type of mobile edge computing, and the type of mobile edge computing indicates whether the auxiliary terminal device performs edge computing on the uplink service data of the terminal device or performs edge computing on the downlink service data of the terminal device.
  • Calculation (wherein, local rendering and segmentation calculation belong to edge computing, both are at the edge of the network, that is, the local device performs related "calculation" on the application layer data, but in the present invention, it may not be limited to only the application layer data. edge "computing" for other protocol layer data).
  • the type is downlink, it means that the auxiliary terminal device is performing edge computing on the downlink service data of the terminal device, that is, the auxiliary terminal device is used to perform edge computing on the received data of session 2; if the type is uplink ( uplink), it means that the auxiliary terminal equipment performs edge computing on the uplink service data of the terminal equipment, that is, the auxiliary terminal equipment is used to perform edge computing on the data of the received session 3. It is understandable that the type of mobile edge computing can also be replaced with other possible descriptions, such as rendering business direction, etc., which is not specifically limited.
  • the PDU session establishment request message carries the second indication information and/or the third indication information.
  • the second indication information may be carried in a new information element independent of the information of the PDU session, for example, 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 may be carried in a newly added information element independent of the information of the PDU session, for example, the third indication information is carried by adding an independent information element "Local Process Time" in the PDU session establishment request message.
  • two information elements may be added to the information of each PDU session in the M PDU sessions, which are respectively used to carry the second indication information and the third indication information.
  • the PDU session establishment request message includes: information about three PDU sessions, the Local Device ID is the IPv4 address 10.10.10.1, the MEC type is "downlink", and the Local Process Time is 5ms, it means : Edge computing is performed on the downlink service data of the terminal device by the auxiliary terminal device whose IPv4 address is 10.10.10.1, and the time required for the edge computing is 5ms.
  • the PDU session establishment request message can also be used to request the establishment of one PDU session among M PDU sessions (such as session 1, session 2 and session 3), such as session 1 .
  • the PDU session establishment request message may include session 1 information and first indication information, where the first indication information indicates that the request is for a session involving edge computing.
  • the first indication information may include the identification information of the auxiliary terminal device to implicitly Indicates that session 1 is a session involving edge computing, and other implementations may refer to the above.
  • the first core network device can subsequently determine and trigger the establishment of other sessions. For example, after the first core network device receives the PDU session establishment request message and determines that the PDU session establishment request message carries the first indication information, it can Trigger establishment of session 1, session 2 and session 3 according to the first indication information (ie, perform S602).
  • 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 included in the PDU session includes this information.
  • the QoS flows containing this information in the three PDU sessions are synchronized. need.
  • the value of the 5G quality of service identifier 5G QoS identifier, 5QI
  • the first core network device may determine whether the preset condition is met, and if so, S602 may be executed, otherwise, S602 will not be executed.
  • the first core network device may determine whether the auxiliary terminal device supports edge computing, and if the auxiliary terminal device supports edge computing, S602 may be performed, otherwise, S602 may not be performed.
  • the AMF network element can perform SMF network element selection, and then send the PDU session establishment request message to the selected SMF network element for processing, and the SMF network element can further obtain the terminal from the UDM network element.
  • the subscription information of the device is used to determine whether the terminal device is allowed to execute these PDU sessions (ie, M PDU sessions). If yes, execute S602.
  • the processing process on the core network side can refer to 3GPP technical standard (technical specification, TS) 23.502 version 16.4.0, and the embodiment of this application does not limit the processing process of the core network.
  • 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.
  • the PDU session resource establishment request message may include first indication information, and the description about the first indication information may refer to the above. It can be understood that the manner in which the PDU session resource establishment request message carries the first indication information may be the same as or different from the manner in which the PDU session establishment request message carries the first indication information, which is not specifically limited.
  • the PDU session resource establishment request message includes the PDU session resource establishment request item corresponding to the PDU session (such as session 1, session 2 or session 3) (PDU Session Resource Setup Request Item).
  • the PDU session resource establishment request item corresponding to the PDU session may include the PDU session identifier (PDU Session ID), the PDU session non-access stratum PDU (PDU Session NAS-PDU), and the single network slice selection assistance information (single network slice selection assistance).
  • the PDU session resource establishment request item corresponding to the PDU session may further include an association identifier. That is to say, an information element (referred to as information element 1) may be added to the PDU session resource establishment request item corresponding to the PDU session, and the information element is used to carry the association identifier.
  • information element 1 an information element (referred to as information element 1) may be added to the PDU session resource establishment request item corresponding to the PDU session, and the information element is used to carry the association identifier.
  • the following Table 1 is an example of the first indication information carried in the PDU session resource establishment request message.
  • Table 1 Example of carrying the first indication information in the PDU session resource establishment request message
  • the PDU session resource establishment request message may further include second indication information and/or third indication information.
  • second indication information and/or the third indication information please refer to the above. It can be understood that the manner in which the PDU session resource establishment request message carries the second indication information and/or the third indication information may be the same as or different from the manner in which the PDU session establishment request message carries the second indication information and/or the third indication information. The same, no specific limitation is imposed.
  • 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).
  • the PDU session resource establishment request item corresponding to the PDU session may also be It includes second indication information and third indication information. That is to say, two new information elements (called 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
  • the information element 3 is used to carry the information. third indication information.
  • the following Table 2 is an example of carrying the second indication information and the third indication information in the PDU session resource establishment request message.
  • Table 2 Example of carrying the second indication information and the third indication information in the PDU session resource establishment request message
  • session 1 if session 1 and other sessions belong to a synchronous session set, the above-mentioned information element 1, information element 2, and information element 3 can be added to the session resource establishment request item corresponding to session 1; If session 1 does not belong to a synchronous session set with any other session, the above-mentioned information element 1, information element 2, and information element 3 may not be added to the session resource establishment request item corresponding to session 1.
  • 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.
  • the access network device may adopt simultaneous admission or simultaneous rejection admission control for session 1, session 2 and session 3 according to the first indication information; and, the access network device may send the admission result to the first core network device according to the admission result PDU session establishment response (PDU session establishment response) message, which may contain information on whether each PDU session is accepted by the access network device.
  • PDU session establishment response PDU session establishment response
  • the access network device may perform admission control on the M PDU sessions based on various basis.
  • the access network device can determine whether to accept M PDU sessions according to information such as the current serving cell of the terminal device, the load situation of the access network device, etc. Consider whether the QoS requirements of M PDU sessions can be met by configuring more serving cells or adding secondary base stations, etc., and then determine whether M PDU sessions can be accommodated.
  • the access network equipment may trigger the configuration of the secondary carrier and/or the secondary base station to the terminal equipment by performing the admission control process. There are plans, which will not be repeated here.
  • the access network device can determine whether the auxiliary terminal device supports edge computing, and if the auxiliary terminal device supports edge computing, it can adopt the admission control of simultaneous admission or simultaneous rejection of M PDU sessions based on the above basis, and if the auxiliary terminal device supports edge computing If the device does not support edge computing, it can reject the establishment request or modification request of M PDU sessions, or it can accept the establishment request or modification request of session 1, and reject the establishment request or modification request of session 2 and session 3, that is, fallback
  • edge computing there is no specific limitation.
  • the access network device sends an RRC reconfiguration (RRC reconfiguration) message 1 to the auxiliary terminal device.
  • RRC reconfiguration RRC reconfiguration
  • the RRC reconfiguration message 1 may carry configuration information of one or more DRBs and configuration information of one or more SLRBs (sidelink radio bearers, side link radio bearers).
  • one or more DRBs are obtained by mapping session 2
  • one or more SLRBs are obtained by mapping session 3.
  • How to do the mapping specifically belongs to the internal implementation of the access network device.
  • the QoS flow can be mapped to the DRB or SLRB according to the QoS requirements of each QoS flow in the session, which is not specifically limited.
  • the auxiliary terminal device sends an RRC reconfiguration sidelink (RRC reconfiguration sidelink) message to the terminal device.
  • RRC reconfiguration sidelink RRC reconfiguration sidelink
  • the RRC reconfiguration side link message may carry configuration information of one or more SLRBs, which are used to establish a radio bearer for D2D communication between the terminal device and the auxiliary terminal device.
  • the terminal device sends an RRC reconfiguration sidelink complete (RRC reconfiguration sidelink complete) message to the auxiliary terminal device.
  • RRC reconfiguration sidelink complete RRC reconfiguration sidelink complete
  • the auxiliary terminal device sends an RRC reconfiguration complete (RRC reconfiguration complete) message 1 to the access network device.
  • the access network device sends an RRC reconfiguration message 2 to the terminal device.
  • the RRC reconfiguration message 2 may carry the configuration information of one or more DRBs, and the one or more DRBs are obtained by mapping the session 1 .
  • the access network device may also send a PDU session establishment accept (PDU session establishment accept) message to the terminal device, where the message is a NAS message generated by the first core network device.
  • PDU session establishment accept PDU session establishment accept
  • the terminal device sends an RRC reconfiguration complete message 2 to the access network device.
  • 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.
  • scenario 1 and scenario 2 are taken as examples to describe the specific implementation of the access network device scheduling data in M PDU sessions.
  • the access network device can determine that one or more DRBs mapped by session 2 are associated with one or more SLRBs mapped by session 3, and can determine The auxiliary terminal device will perform edge computing on the downlink service data of the terminal device, and the time required for the edge computing. Based on this information, when scheduling the downlink data of the DRB to be sent at time N (ie the first time), the access network device schedules the data of the SLRB (data from the auxiliary terminal device to the terminal device) at time N+k (That is, the second time after the first time) is sent to ensure that the downlink data after edge computing is sent to the terminal device in time. Wherein, k is the time duration required by the auxiliary terminal device to perform edge computing on the downlink service data of the terminal device.
  • the access network device can determine that one or more DRBs mapped by session 2 are associated with one or more SLRBs mapped by session 3, and can determine The auxiliary terminal equipment will perform edge computing on the uplink service data of the terminal equipment, and the time required for the edge computing. Based on this information, when the access network device schedules the data of the SLRB (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 to ensure that the edge is sent in time. The calculated uplink data is sent to the application server. Wherein, k is the duration required for the auxiliary terminal device to perform edge computing on the uplink service data of the terminal device.
  • the duration required for the auxiliary terminal device to perform edge computing may be a relatively conservative duration, so as to ensure that the auxiliary terminal device can complete the edge computing within the duration.
  • the access network device may also configure corresponding DRX cycles for the terminal device and the auxiliary terminal device. Take Scenario 1 and Scenario 2 as examples for description.
  • the access network device can send the first configuration information to the auxiliary terminal device, and the first configuration information is used to configure the auxiliary terminal device to receive the session. 2 in the first DRX of the data.
  • the first DRX cycle is the same as the data burst cycle (ie, the data transmission cycle in session 2), and the start offset (offset) of the first DRX is also aligned with the data burst start offset.
  • the access network device or the auxiliary terminal device can send the second configuration information to the terminal device, and the second configuration information is used to configure the terminal device to receive the data in session 3 (ie D2D Communication) of the second DRX, the second DRX cycle is the same as the first DRX cycle, but the start offset is the first DRX start offset plus k.
  • the terminal device can not only avoid power consumption due to continuous monitoring of data sent from the auxiliary terminal device, 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 delay requirements of the VR service. .
  • the access network device can send the first configuration information to the auxiliary terminal device, and the first configuration information is used to configure the auxiliary terminal device to receive the session.
  • the first DRX cycle is the same as the data burst cycle (ie, the data transmission cycle in session 3), and the start offset (offset) of the first DRX cycle is also aligned with the data burst start offset.
  • the access network device or the auxiliary terminal device can send the second configuration information to the terminal device.
  • the second configuration information is used to configure the second DRX cycle for the terminal device to receive data in session 1.
  • the second DRX cycle The same as the first DRX cycle, but the starting offset is the starting offset of the first DRX cycle plus t.
  • the round-trip delay here may be the time interval between the time when the terminal device sends the first data through session 3 and the time when the terminal device receives the second data through session 1.
  • the second data is obtained according to the first data,
  • the first data may be an image collected by a surveillance camera or image data and/or computing context information preliminarily processed by the surveillance camera
  • the second data may be an image recognition result obtained according to the first data.
  • the access network device may send fifth indication information to the terminal device, where the fifth indication information indicates the round-trip delay; further, the terminal device may perform related optimizations such as power saving according to the round-trip delay.
  • This solution can be applied to a situation where the service pattern of the terminal device is irregular, or can also be applied to a situation where the service pattern of the terminal device is regular, which is not specifically limited.
  • the round-trip delay may be the time interval between the time when the terminal device sends the first data through session 3 and the time when the terminal device receives the second data through session 1. The second data is obtained according to the first data.
  • the terminal device can enter the sleep state, and after the sleep duration reaches the threshold (the threshold is obtained according to the round-trip delay, for example, the threshold can be equal to or slightly smaller than the round-trip delay), The sleep state can be woken up to receive the second data.
  • the round-trip delay is the time interval between the time when the terminal device sends the third data through session 1 and the time when the terminal device receives the fourth data through session 3, and the fourth data is obtained according to the third data
  • the third data may be the helmet movement or eyeball posture information collected by the VR helmet, and the fourth data may be the VR media data after secondary rendering.
  • the access network device may perform admission control on the M PDU sessions according to the first indication information; instead of scheduling the data in the M PDU sessions according to the first indication information, the second indication information and the third indication information, In this case, the access network device may schedule data in the M PDU sessions with reference to the prior art.
  • the network device may 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 this case, the network device may perform admission control on the M PDU sessions with reference to the prior art.
  • the access network device when edge computing is performed through the auxiliary terminal device, the access network device can simultaneously accept or reject the session 1, session 2 and session 3. As a result, the service cannot be implemented normally; and, the access network device can also control the coordinated transmission of data in different sessions (such as session 2 and session 3) of the synchronous session set according to a certain order and time relationship, so as to meet the service delay requirement.
  • the terminal device may need to switch between edge computing and edge computing, for example, taking the terminal device as a VR helmet as an example, when the VR helmet has no external device with strong computing capability, the auxiliary terminal needs to be The device performs secondary rendering.
  • the VR headset can choose to have edge computing, that is, M sessions have an associated relationship; and when the VR headset has external devices with strong computing capabilities, it is no longer necessary to use auxiliary terminal equipment to perform secondary rendering.
  • the VR headset can choose no edge computing, that is, the M sessions are no longer related.
  • the VR headset can also switch between edge computing and edge computing based on other possible reasons (such as whether to connect to a power supply).
  • FIG. 7 is a schematic flowchart corresponding to the communication method provided in Embodiment 2 of the present application. As shown in FIG. 7 , the method includes S701 to S708, and the embodiment of the present application does not limit the execution order of S701 to S708.
  • the terminal device sends a second request message to the first core network device; correspondingly, the first core network device may receive the second request message.
  • the second request message may be a PDU session modification request message, and the PDU session modification request message may be used to modify session 1, for example, the message may carry session 1 information.
  • the PDU session resource modification request message may further carry seventh indication information, where the seventh indication information indicates that session 1 is no longer associated with other sessions (ie, session 2 and session 3) in the M sessions.
  • session 1 is no longer associated with other sessions (ie, session 2 and session 3) in the M sessions in an implicit manner, for example, a 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 an implicit indication of session 1 and other sessions in the M sessions (ie session 2, session 3 ) is no longer associated.
  • the first core network device may learn, according to the seventh indication information, that the message is to initiate a handover from edge computing to no edge computing, and may then execute S702.
  • the processing procedure on the core network side after the first core network device receives the message may refer to 3GPP TS 23.502 version 16.4.0, which is not specifically limited.
  • the first core network device sends a PDU session resource release command message to the access network device; correspondingly, the access network device may receive the PDU session resource release command message.
  • the PDU session resource release command message may be used to release session 2 and session 3, for example, the PDU session resource release command message may include information about session 2 and session 3.
  • the PDU session resource release command message may include sixth indication information, where the sixth indication information indicates that the M sessions are no longer associated. It should be noted that, in other possible examples, it is also possible to indicate that the M sessions are no longer associated in an implicit manner, which is not specifically limited.
  • the access network device releases the session 2 and the 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.
  • the access network device sends an RRC reconfiguration message to the auxiliary terminal device.
  • the RRC reconfiguration message may carry indication information that the DRBs and SLRBs corresponding to the session 2 and the session 3 are released. Further, after sending the RRC reconfiguration message to the auxiliary terminal device, the access network device may also send a PDU session modification accept (PDU session modification accept) message to the terminal device, where the message is a NAS message generated by the SMF network element.
  • PDU session modification accept PDU session modification accept
  • the auxiliary terminal device sends an RRC reconfiguration side link message to the terminal device.
  • the RRC reconfiguration side link message may carry the indication information that the SLRB corresponding to the session 3 is released, and then the terminal device may release the configuration and resources related to one or more SLRBs corresponding to the session 3.
  • the terminal device sends an RRC reconfiguration side link completion message to the auxiliary terminal device.
  • the auxiliary terminal device sends an RRC reconfiguration complete message to the access network device.
  • the access network device cancels the scheduling of data in the M PDU sessions according to the first indication information, the second indication information and the third indication information.
  • the terminal device may trigger a PDU session modification or PDU session establishment process, such as the process shown in Embodiment 1 above, to switch to edge computing.
  • the terminal device triggers the switch from edge computing to edgeless computing. In practical applications, it can also be triggered by a local device.
  • the local device is insufficient in computing resources, storage resources, or transmission resources, or has completed In the case of edge computing, etc., an edge computing release request is sent to the terminal device, access network device, or core network device.
  • the terminal device can switch from edge computing to edge computing, or from edge computing to edge computing, so as to ensure that the terminal device can work in different working modes (such as whether there is a power connection, whether there is a plug-in strong computing
  • the corresponding mode can be freely selected under the conditions of the device with the capability of the device, etc., and the service experience and user experience can be guaranteed at the same time.
  • the local device in FIG. 4b may include an access network device and an EAS.
  • the local device is directly referred to as an access network device.
  • FIG. 8 is a schematic flowchart corresponding to the communication method provided in Embodiment 3 of the present application. As shown in FIG. 8 , the method includes S800 to S806, and the embodiment of the present application does not limit the execution order of S800 to S806.
  • the first core network device acquires capability information of the access network device, where the capability information of the access network device is used to indicate whether the access network device supports edge computing.
  • the access network device may report capability information to the first core network device.
  • the access network device may report capability information when the N2 interface is established.
  • a terminal device sends a first request message to a first core network device; correspondingly, the first core network device may receive the first request message.
  • the first request message is an example of a PDU session establishment request message.
  • the PDU session establishment request message may include first indication information, and may further include second indication information and/or third indication information.
  • 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.
  • the PDU session resource establishment request message may include first indication information, and may further include second indication information and/or third indication information.
  • 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.
  • the access network device may adopt admission control of simultaneous admission or simultaneous rejection for session 1 and session 3.
  • the access network equipment does not need to perform admission control on session 2, because session 2 does not involve the use of radio resources, which are usually resource bottlenecks in mobile networks.
  • the access network device sends an RRC reconfiguration message to the terminal device.
  • the terminal device sends an RRC reconfiguration complete message to the access network device.
  • 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.
  • scenario 1 and scenario 2 are taken as examples to describe the specific implementation of the access network device scheduling data in M PDU sessions.
  • the access network device can determine that session 2 and session 3 are associated, and can determine that edge computing and edge computing will be performed on the downlink service data of session 2 required time. 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 of the DRB mapped by session 3 (data from the access network device to the terminal device) 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 required for the access network device to perform edge computing on the downlink service data of the terminal device.
  • the access network device can determine that session 2 and session 3 are associated, and can determine that edge computing and edge computing will be performed on the uplink service data of session 3 required time. Based on this information, when the access network device receives the uplink data of session 3 at time N, it can schedule the data of session 2 (data from the access network device to the application server) to be sent at time N+k to ensure that the edge computing The latter data is sent to the application server. Wherein, k is the time required for the access network device to perform edge computing on the uplink service data of the terminal device.
  • the access network device may send fifth indication information to the terminal device, where the fifth indication information indicates the round-trip delay; for details, refer to the description in the first embodiment.
  • the access network device may also configure a corresponding DRX cycle for the terminal device.
  • the following uses scenario 1 and scenario 2 as examples to perform instruction.
  • the access network device can send configuration information to the terminal device, and the configuration information is used to configure the DRX cycle for the terminal device to receive the data in session 3 , the DRX cycle is the same as the data transmission cycle in session 2, but the starting offset is the starting offset of the data in session 2 plus k.
  • the terminal device can avoid power consumption due to continuous monitoring of data sent from the access network device, and can also send the data to the terminal device in time after the access network device completes the local secondary rendering, so as to ensure the strict timing of the VR service. extension request.
  • the access network device can send configuration information to the terminal device, and the configuration information is used to configure the DRX cycle for the terminal device to receive the data in session 1 , the DRX cycle is the same as the transmission cycle 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 may be the time interval between the time when the terminal device sends the first data through session 3 and the time when the terminal device receives the second data through session 1, and the second data is obtained according to the first data.
  • the access network device when edge computing is performed through the access network device, the access network device can perform admission control of simultaneous admission or simultaneous rejection of session 1 and session 3, so as to avoid admitting part of the session and causing traffic It cannot be implemented normally; and, the access network device can also control the coordinated transmission of data in different sessions (such as session 2 and session 3) of the synchronous session set according to a certain order and time relationship, so as to meet the service delay requirement.
  • Embodiment 4 a possible implementation will be described by taking the situation shown in FIG. 4b as an example.
  • FIG. 9 is a schematic flowchart corresponding to the communication method provided in Embodiment 4 of the present application. As shown in FIG. 9 , the method includes S901 to S906 , and the embodiment of the present application does not limit the execution order of S901 to S906 .
  • the terminal device sends a second request message to the first core network device; correspondingly, the first core network device may receive the second request message.
  • the first core network device sends a PDU session resource release command message to the access network device; correspondingly, the first access network device may receive the PDU session resource release command message.
  • the access network device sends a PDU session resource release response message to the first core network device.
  • the access network device sends an RRC reconfiguration message to the terminal device.
  • the RRC reconfiguration message may 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 may also send a PDU session modification accept message to the terminal device, where the message is a NAS message generated by the SMF network element.
  • the terminal device sends an RRC reconfiguration complete message to the access network device.
  • the access network device cancels the scheduling of data in the M PDU sessions according to the first indication information, the second indication information and the third indication information.
  • the terminal device may trigger a PDU session modification or PDU session establishment process, such as the process shown in the third embodiment above, to switch to edge computing.
  • the terminal device can switch from edge computing to edge computing, or from edge computing to edge computing, so as to ensure that the terminal device can work in different working modes (such as whether there is a power connection, whether there is a plug-in strong computing
  • the corresponding mode can be freely selected under the conditions of the device with the capability of the device, etc., and the service experience and user experience can be guaranteed at the same time.
  • the local device in FIG. 4c may include an IAB node and an EAS.
  • the local device is directly referred to as an IAB node.
  • FIG. 10 is a schematic flowchart corresponding to the communication method provided by Embodiment 5 of the present application. As shown in FIG. 10 , the method includes S1000 to S1010 , and the embodiment of the present application does not limit the execution order of S1000 to S1010 .
  • the access network device and/or the first core network device acquire capability information of the IAB node, where the capability information of the IAB node is used to indicate whether the IAB node supports edge computing.
  • the IAB node may send capability information to the access network device and/or the first core network device. For example, the IAB node reports 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 the registration is completed.
  • the first core network device may also acquire capability information of the IAB node from the UDM network element.
  • a terminal device sends a first request message to a first core network device; correspondingly, the first core network device may receive the first request message.
  • the first request message is an example of a PDU session establishment request message.
  • the PDU session establishment request message may include first indication information, and may further include second indication information and/or third indication information.
  • 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.
  • the PDU session resource establishment request message may include first indication information, and may further include second indication information and/or third indication information.
  • 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.
  • the access network device sends a context modification request (UE context modification request) message of the terminal device to the IAB node.
  • UE context modification request UE context modification request
  • the context modification request message may include DRB configuration information mapped by session 1, so that the IAB node can perform DRB-related configuration, such as the RLC protocol layer between the IAB node and the terminal device.
  • the IAB node sends a context modification response (UE context modification response) message of the terminal device to the access network device.
  • UE context modification response UE context modification response
  • the access network device sends an RRC reconfiguration message 1 to the IAB node.
  • the RRC reconfiguration message may include configuration information of DRBs mapped from session 2 and session 3 and fourth indication information, where the fourth indication information indicates that the DRB corresponding to session 2 is associated with the DRB corresponding to session 3 .
  • the fourth indication information may include association information between one or more pairs of DRBs (one DRB obtained by mapping session 2 and one DRB obtained by mapping session 3 constitute a pair of DRBs).
  • the RRC reconfiguration message may further include second indication information and/or third indication information.
  • the IAB node sends an RRC reconfiguration complete message 1 to the access network device.
  • the access network device may also send the DRB configuration information mapped by session 2 and the DRB configuration information mapped by session 3 to the IAB node, that is, the configuration process of S1006 and S1007 is split into two configurations process, the specific implementation is not limited.
  • the access network device sends an RRC reconfiguration message 2 to the terminal device.
  • the RRC reconfiguration message may include DRB-related configuration information obtained by mapping session 1 and session 3.
  • the terminal device sends an RRC reconfiguration complete message 2 to the access network device.
  • 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.
  • the IAB node can determine that one or more DRBs mapped by session 2 are associated with one or more DRBs mapped by session 3, and can determine the IAB node Edge computing will be performed on the downlink service data of the terminal device and the time required for the edge computing. Based on this information, if the IAB node receives the DRB data mapped by session 2 at time N, the DRB data mapped by session 3 (data from the IAB node to the terminal device) is scheduled to be sent at time N+k to ensure timely delivery. The downlink data after edge computing is sent to the terminal device. Wherein, k is the time required for the IAB node to perform edge computing on the downlink service data of the terminal device.
  • the IAB node can determine that one or more DRBs mapped by session 2 are associated with one or more DRBs mapped by session 3, and can determine the IAB node Edge computing will be performed on the uplink service data of the terminal device and the time required for the edge computing. Based on this information, if the IAB node receives the DRB data mapped by session 3 at time N, it schedules the DRB data mapped by session 2 (data from the IAB node to the application server) to be sent at time N+k to ensure timely delivery. Send the upstream data after edge computing to the application server. Wherein, k is the time required for the IAB node to perform edge computing on the uplink service data of the terminal device.
  • the time required for the IAB node to perform the edge computing may be a relatively conservative time, so as to ensure that the IAB node can complete the edge computing within the time.
  • the access network device can also configure the corresponding DRX cycle for the terminal device and the IAB node.
  • Scenario 1 and Scenario 2 are used as examples for description.
  • the access network device can send the first configuration information to the IAB node, and the first configuration information is used to configure the IAB node to receive the data in the session 2.
  • the first DRX of the data is the same as the data burst cycle (ie, the data transmission cycle in session 2), and the start offset of the first DRX is also aligned with the data burst start offset.
  • the access network device can send the second configuration information to the terminal device through the IAB node, and the second configuration information is used to configure the terminal device to receive the second DRX of the data in session 3,
  • the second DRX cycle is the same as the first DRX cycle, but the start offset is the first DRX start offset plus k.
  • the terminal device can avoid power consumption by continuously monitoring the data sent from the IAB node, and can also send the data to the terminal device in time after the IAB node completes the local secondary rendering, so as to ensure the strict delay requirements of the VR service.
  • the access network device can send the first configuration information to the IAB node, and the first configuration information is used to configure the IAB node to receive the data in session 3.
  • the first DRX cycle of data is the same as the data burst cycle (ie, the data transmission cycle in session 3), and the start offset of the first DRX cycle is also aligned with the data burst start offset. If the round-trip delay is t, the access network device can send the second configuration information to the terminal device through the IAB node. The second configuration information is used to configure the second DRX cycle for the terminal device to receive data in session 1.
  • the second DRX cycle The same as the first DRX cycle, but the starting offset is the starting offset of the first DRX cycle plus t.
  • the round-trip delay here may be the time interval between the time when the terminal device sends the first data through session 3 and the time when the terminal device receives the second data through session 1, and the second data is obtained according to the first data.
  • the access network device may send fifth indication information to the terminal device, where the fifth indication information indicates the round-trip delay; further, the terminal device may perform related optimizations such as power saving according to the round-trip delay.
  • the fifth indication information may be carried in the RRC reconfiguration message 2 in the foregoing S1008.
  • the process described in the above S1001 to S1010 is only an example of a possible process, and in specific implementation, adaptive adjustment can be made on the basis of the above-described process.
  • the access network device may perform admission control on M PDU sessions according to the first indication information; but the IAB node does not schedule data in the M PDU sessions according to the first indication information, the second indication information and the third indication information , in this case, the IAB node can schedule the data in the M PDU sessions with reference to the prior art.
  • the IAB node may schedule 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 the M PDU sessions according to the first indication information.
  • Admission control in this case, the access network device may perform admission control on M PDU sessions with reference to the prior art.
  • the methods provided in the embodiments of the present application may be applicable to both a scenario of a one-level IAB node and a scenario of a multi-level IAB node.
  • the IAB nodes described in the embodiments of this application may be any level of IAB nodes.
  • the multi-level IAB node can be adaptively expanded with reference to the description of the embodiments of the present application, and details are not repeated here.
  • the access network device when edge computing is performed through the IAB node, the access network device can simultaneously accept or reject session 1, session 2 and session 3.
  • the service cannot be implemented normally; and, the IAB node can control the coordinated transmission of data in different sessions (such as session 2 and session 3) of the synchronous session set according to a certain order and time relationship, so as to meet the service delay requirement.
  • Embodiment 6 a possible implementation will be described by taking the situation shown in FIG. 4c as an example.
  • FIG. 11 is a schematic flowchart corresponding to the communication method provided by Embodiment 6 of the present application. As shown in FIG. 11 , the method includes S1101 to S1108 , and the embodiment of the present application does not limit the execution order of S1101 to S1108 .
  • the terminal device sends a second request message to the first core network device; correspondingly, the first core network device may receive the second request message.
  • the first core network device sends a PDU session resource release command message to the access network device; correspondingly, the first access network device may receive the PDU session resource release command message.
  • the access network device sends a PDU session resource release response message to the first core network device.
  • the access network device sends an RRC reconfiguration message 1 to the IAB node.
  • the RRC reconfiguration message may carry the indication information that the DRBs corresponding to the session 2 and the session 3 are released.
  • the IAB node releases the DRBs corresponding to the session 2 and the session 3, and sends an RRC reconfiguration complete message 1 to the access network device.
  • the access network device sends an RRC reconfiguration message 2 to the terminal device.
  • the RRC reconfiguration message may carry the indication information that the DRB corresponding to the session 3 is released, and then the terminal device may release the configuration and resources related to one or more DRBs corresponding to the session 3 .
  • the terminal device sends an RRC reconfiguration complete message 2 to the access network device.
  • the IAB node cancels the scheduling of data in the M PDU sessions according to the first indication information, the second indication information and the third indication information.
  • the service of the terminal device will be switched from edge computing to edgeless computing. If edge computing is required subsequently, the terminal device may trigger a PDU session modification or PDU session establishment process, such as the process shown in the fifth embodiment above, to switch to edge computing.
  • the terminal device can switch from edge computing to edge computing, or from edge computing to edge computing, so as to ensure that the terminal device can work in different working modes (such as whether there is a power connection, whether there is a plug-in strong computing
  • the corresponding mode can be freely selected under the conditions of the device with the capability of the device, etc., and the service experience and user experience can be guaranteed at the same time.
  • the communication method provided in this embodiment of the present application may also be applicable to a handover scenario, for example, a terminal device is handed over from a cell of a first access network device to a cell of a second access network device, and the first access network device may be The source access network device and the second access network device may be the target access network device, and the source access network device and the target access network device may be access network devices under the same AMF network element, or may be different AMFs Access network equipment under the NE.
  • the source access network device may receive the first indication information from the core network device or the terminal device, and optionally may also receive the second indication information and the third indication information, and may receive the first indication information and the second indication information according to the received first indication information and the second indication information.
  • the information and the third indication information perform corresponding operations.
  • the access network device in the above-mentioned first embodiment, the third embodiment, and the fifth embodiment can be understood as the source network device of the terminal device.
  • the source access network device may send the first indication information to the target access network device, and optionally may also send second indication information and third indication information, such as the first indication information, the second indication
  • second indication information and third indication information such as the first indication information, the second indication
  • the information and the third indication information can be carried in the handover command; and then the target access network device can perform corresponding operations according to the received first indication information, second indication information and third indication information.
  • the target access network device may adopt admission control of simultaneous admission or simultaneous rejection for M PDU sessions according to the first indication information.
  • the target access network device may also receive the first indication information from the core network device, and optionally may also receive the second indication information and the third indication information, which is not specifically limited.
  • the terminal equipment and the auxiliary terminal equipment access the same access network equipment as an example for description.
  • the terminal equipment and the auxiliary terminal equipment can also access different access network equipment.
  • the terminal equipment is connected to access network equipment 1, and the auxiliary terminal equipment is connected to access network equipment 2.
  • the interaction between access network equipment 1 and access network equipment 2 may also be involved.
  • the specific implementation can be adapted to Refer to the description of terminal equipment and auxiliary terminal equipment accessing the same access network equipment.
  • an access network device is also used as an example for description.
  • the terminal device can access the access network device 1, and the local device includes the access network device 2;
  • an access network device is also used as an example for description.
  • the terminal device can access the access network device 1, and the IAB node can access the access network device 2.
  • Embodiments 1 to 6 (4) The above focuses on describing the differences between the different embodiments in Embodiments 1 to 6. Except for other contents of the differences, the embodiments 1 to 6 can be referred to each other.
  • the network device, core network device or terminal device may include corresponding hardware structures and/or software modules for performing each function.
  • the embodiments of the present application can be implemented in hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • the network device, core network device, or terminal device may be divided into functional units according to the foregoing method examples.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one in the unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • FIG. 12 shows a possible exemplary block diagram of the apparatus involved in the embodiment of the present application.
  • the apparatus 1200 may 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 between the apparatus 1200 and other devices.
  • the communication unit 1203 is also referred to as a transceiving unit, and may include a receiving unit and/or a sending unit, which are respectively configured to perform receiving and sending operations.
  • the apparatus 1200 may further include a storage unit 1201 for storing program codes and/or data of the apparatus 1200 .
  • the apparatus 1200 may be the access network device in the foregoing embodiment, or may also be a chip provided in the access network device.
  • the processing unit 1202 may support the apparatus 1200 to perform the actions of the access network device in each method example above. Alternatively, the processing unit 1202 mainly performs the internal actions of the access network device in the method example, and the communication unit 1203 may support the communication between the apparatus 1200 and other devices.
  • the communication unit 1203 is configured to: receive first indication information, where the first indication information indicates that M sessions have an association relationship, where M is an integer greater than 1; the processing unit 1202 is configured to: according to the first indication information to process M sessions.
  • the processing unit 1202 is specifically configured to: accept establishment requests of at least two sessions among the M sessions or reject establishment requests of at least two sessions among the M sessions; or, accept at least two session establishment requests among the M sessions modification requests of the M sessions or reject modification requests of at least two sessions of the M sessions.
  • 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 session; wherein, the terminal device and the first access network device establish a radio resource control RRC connection.
  • the communication unit 1203 is further configured to: receive the second indication information and/or the third indication information; wherein the second indication information indicates that the local device is not aware of the received second session or the third session The data in the device performs edge computing, and the third indication information indicates the time required for the local device to perform local edge computing.
  • the processing unit 1202 is specifically configured to: determine that the local device performs edge computing on the received data in the second session; schedule the data in the second session at the first time, and after the first time The second time schedules the data in the third session; wherein, the time interval between the first time and the second time is obtained according to the time duration required for the local device to perform edge computing.
  • the processing unit 1202 is specifically configured to: determine that the local device performs edge computing on the received data in the third session; schedule the data in the third session at the first time, and after the first time The second time schedules the data in the second session; wherein, the time interval between the first time and the second time is obtained according to the time required for the local device to perform edge computing.
  • the local equipment includes auxiliary terminal equipment, or the local equipment includes access network equipment.
  • the communication unit 1203 is further configured to send fourth indication information to the local device, 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.
  • the communication unit 1203 is further configured to: send the second indication information and/or the third indication information to the local device, where the second indication information indicates that the local device is not aware of the received second session or third indication information.
  • the data in the session is subjected to edge computing, and the third indication information indicates the duration required for the local device to perform local edge computing.
  • the local device includes a wireless backhaul device.
  • the communication unit 1203 is further configured to: send fifth indication information to the terminal device, where the fifth indication information indicates the round-trip delay; wherein, the round-trip delay is the time when the terminal device sends the first The time interval between the time when the data is sent and the time when the terminal device receives the second data through the first session, and the second data is obtained according to the first data; or, the round-trip delay is the time when the terminal device sends the second data through the first session. The time interval between the time when the third data is sent and the time when the terminal device receives the fourth data through the third session, where the fourth data is obtained according to the third data.
  • the communication unit 1203 is specifically configured to: receive the first indication information from the core network device or the second access network device; wherein the second access network device is the source access network device of the terminal device, The first access network device is a target access network device of the terminal device.
  • the first indication information includes M pieces of association information respectively corresponding to the M sessions, and/or identification information of the local device, wherein the M pieces of association information are the same.
  • the M sessions include a first session, and the associated information corresponding to the first session includes type information of the first session and/or an associated identifier of the first session; wherein the type information of the first session is used for Indicates that the type of the first session is split rendering or segmented computing.
  • 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 the resources of the second session and the third session according to the sixth indication information Resources.
  • the apparatus 1200 may be the core network device in the foregoing embodiment, or may also be a chip provided in the core network device.
  • the processing unit 1202 may support the apparatus 1200 to perform the actions of the core network device in each method example above.
  • the processing unit 1202 mainly performs the internal actions of the core network device in the method example, and the communication unit 1203 may support the communication between the apparatus 1200 and other devices.
  • the communication unit 1203 is configured to: obtain first indication information, where the first indication information indicates that M sessions are associated, and M is an integer greater than 1; and, send the first indication to the access network device Instructions.
  • 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; Wherein, the terminal device establishes an RRC connection with the access network device.
  • the communication unit 1203 is further configured to: send the second indication information and/or the third indication information to the access network device; wherein the second indication information indicates that the local device responds to the received second indication information
  • the data in the session or the third session is used for edge computing, and the third indication information indicates the time required for the local device to perform local edge computing.
  • the communication unit 1203 is specifically configured to: acquire the first indication information from the terminal device; or acquire the first indication information from the second core network device.
  • the communication unit 1203 is specifically configured to: receive a first request message from the terminal device, where the first request message is used to request to establish or modify the M sessions or the first session among the M sessions, the The request message includes first indication information.
  • the communication unit 1203 is further configured to: send sixth indication information to the access network device, where the sixth indication information indicates that the M sessions are no longer associated.
  • the communication unit 1203 is further configured to: receive a second request message from the terminal device, where the second request message is used to request modification of the first session among the M sessions, and the second request message includes a seventh indication information, the seventh indication information indicates that the first session is no longer associated with other sessions in the M sessions; the sixth indication information is determined according to the second request message.
  • each unit in the above apparatus can be realized in the form of software calling through the processing element; also can all be realized in the form of hardware; some units can also be realized in the form of software calling through the processing element, and some units can be realized in the form of hardware.
  • each unit can be a separately established processing element, or can be integrated in a certain chip of the device to be implemented, and can also be stored in the memory in the form of a program, which can be called by a certain processing element of the device and execute the unit's processing.
  • each operation of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in the processor element or implemented in the form of software being invoked by the processing element.
  • a unit in any of the above apparatuses may be one or more integrated circuits configured to implement the above methods, eg, one or more application specific integrated circuits (ASICs), or, one or more Multiple microprocessors (digital singnal processors, DSPs), or, one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.
  • ASICs application specific integrated circuits
  • DSPs digital singnal processors
  • FPGAs field programmable gate arrays
  • a unit in the apparatus can be implemented in the form of a processing element scheduler
  • the processing element can be a processor, such as a general-purpose central processing unit (CPU), or other processors that can invoke programs.
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip
  • the above unit for receiving is an interface circuit of the device for receiving signals from other devices.
  • the receiving unit is an interface circuit used by the chip to receive signals from other chips or devices.
  • the above unit for sending is an interface circuit of the device for sending signals to other devices.
  • the sending unit is an interface circuit used by the chip to send signals to other chips or devices.
  • Access network equipment 130 may include one or more DUs 1301 and one or more CUs 1302.
  • the DU 1301 may 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 part is mainly used for the transmission and reception of radio frequency signals, the conversion of radio frequency signals and baseband signals, and part of baseband processing.
  • the CU 1302 may include at least one processor 13022 and at least one memory 13021 .
  • the CU 1302 part is mainly used to perform baseband processing, control access network equipment, and the like.
  • the DU 1301 and the CU 1302 may be physically set together, or may be physically separated, that is, a distributed base station.
  • the CU 1302 is the control center of the access network equipment, which can also be called a processing unit, and is mainly used to complete the baseband processing function.
  • the CU 1302 may be used to control the access network device to perform the operation process of the access network device in the foregoing method embodiments.
  • the access network device 130 may include one or more radio frequency units, one or more DUs, and one or more CUs.
  • the DU may include at least one processor 13013 and at least one memory 13014
  • the radio unit may include at least one antenna 13011 and at least one radio frequency unit 13012
  • the CU may include at least one processor 13022 and at least one memory 13021 .
  • the CU1302 may be composed of one or more boards, and the multiple boards may jointly support a wireless access network (such as a 5G network) with a single access indication, or may respectively support wireless access systems of different access standards.
  • Access network such as LTE network, 5G network or other network.
  • the memory 13021 and the processor 13022 may serve one or more single boards. That is to say, the memory and processor can be provided separately on each single board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits may also be provided on each single board.
  • the DU1301 can be composed of one or more single boards.
  • Multiple single boards can jointly support a wireless access network (such as a 5G network) with a single access indication, or can support a wireless access network with different access standards (such as a 5G network). LTE network, 5G network or other network).
  • the memory 13014 and processor 13013 may serve one or more single boards. That is to say, the memory and processor can be provided separately on each single board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits may also be provided on each single board.
  • the access network device shown in FIG. 13 can implement each process involving the access network device in the method embodiments shown in FIGS. 5 to 11 .
  • the operations and/or functions of each module in the access network device shown in FIG. 13 are respectively to implement the corresponding processes in the foregoing method embodiments.
  • FIG. 14 it is a schematic structural diagram of a core network device according to an embodiment of the present application. It may be the SMF network element or the AMF network element in the above embodiment, and is used to implement the operations of the SMF network element or the AMF network element in the above embodiment.
  • the core network device 1400 may include a processor 1401 , a memory 1402 and an interface circuit 1403 .
  • the processor 1401 can be used to process the communication protocol and communication data, and control the communication device.
  • the memory 1402 may be used to store programs and data, and the processor 1401 may execute the method performed by the AMF network element or the SMF network element in the embodiments of the present application based on the program.
  • the interface circuit 1403 can be used for the core network device 1400 to communicate with other devices, and the communication can be wired communication or wireless communication.
  • the interface circuit can be a service-oriented communication interface.
  • the above memory 1402 may also be externally connected to the core network device 1400 .
  • the core network device 1400 may include an interface circuit 1403 and a processor 1401 .
  • the above interface circuit 1403 may also be externally connected to the core network device 1400 .
  • the core network device 1400 may include a memory 1402 and a processor 1401 .
  • the communication device 1400 may include a processor 1401 .
  • the core network device shown in FIG. 14 can implement each process involving the core network device in the method embodiments shown in FIGS. 5 to 11 .
  • the operations and/or functions of each module in the core network device shown in FIG. 14 are respectively to implement the corresponding processes in the foregoing method embodiments.
  • system and “network” in the embodiments of the present application may be used interchangeably.
  • At least one means one or more, and “plurality” means two or more.
  • And/or which describes the association relationship of the associated objects, means that there can be three kinds of relationships, for example, A and/or B, which can mean: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects are an “or” relationship.
  • At least one item(s) below” or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • At least one of A, B and C includes A, B, C, AB, AC, BC or ABC.
  • ordinal numbers such as “first” and “second” mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the order, sequence, priority or importance of multiple objects degree.
  • the embodiments of the present application may be provided as a method, a system, or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions
  • the apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请涉及通信技术领域，公开了一种通信方法及装置。其中方法包括：接入网设备接收第一指示信息，第一指示信息指示M个会话具有关联关系，M为大于1的整数；进而根据第一指示信息，对M个会话进行处理。采用该种方式，接入网设备在对M个会话进行处理时，考虑了M个会话之间的关联关系，从而便于满足不同会话之间的同步需求。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2020年06月29日提交中国专利局、申请号为202010609711.4、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
虚拟现实(virtual reality，VR)技术是借助计算机及最新传感器技术创造的一种崭新的人机交互手段。VR技术综合了计算机图形技术、计算机仿真技术、传感器技术、显示技术等多种科学技术，主要包括模拟环境、感知、自然技能和传感设备等方面。模拟环境是由计算机生成的、实时动态的三维立体逼真图像；感知是指理想的VR应该具有一切人所具有的感知，除计算机图形技术所生成的视觉感知外，还有听觉、触觉、力觉、运动等感知，甚至还包括嗅觉和味觉等，也称为多感知；自然技能是指人的头部转动，眼睛、手势、或其他人体行为动作，由计算机来处理与参与者的动作相适应的数据，并对用户的输入实时响应，并分别反馈到用户的五官；传感设备是指三维交互设备。
针对于VR业务，由于VR头盔(head mounted device，HMD)渲染能力限制、VR带宽需求大(50Mbps～1Gbps以上)，以及动作到显示延迟(motion to photon latency)约20ms的短时延要求，因此，VR业务存在本地二次渲染的场景。在本地二次渲染场景中，VR头盔可以先将头部转动、眼睛、手势等行为动作数据发送给VR服务器，VR服务器根据这些数据生成模拟环境，并对模拟环境进行预渲染，然后VR服务器将预渲染后的数据发送给本地设备进行二次渲染，进而本地设备再将二次渲染后的数据发送给VR头盔，由头盔呈现三维立体的逼真图像，甚至还包括听觉、触觉、力觉和运动等感知。
然而，针对于涉及边缘计算的场景(比如上述本地二次渲染场景)的相关实现，仍需进一步的研究。
发明内容
本申请提供了一种通信方法及装置，便于满足不同会话之间的同步需求。
第一方面，本申请实施例提供一种通信方法，该方法可以应用于第一接入网设备或者第一接入网设备中的芯片，以该方法应用于第一接入网设备为例，在该方法中，第一接入网设备可以接收第一指示信息，第一指示信息指示M个会话具有关联关系，M为大于1的整数；并根据第一指示信息，对M个会话进行处理。
采用上述方法，第一接入网设备在对M个会话进行处理时，可以考虑M个会话之间的关联关系，从而便于满足不同会话之间的同步需求，有效保证用户对业务的体验质量。
在一种可能的设计中，对M个会话进行处理，包括：接纳M个会话中至少两个会话的建立请求或者拒绝M个会话中至少两个会话的建立请求；或者，接纳M个会话中至少 两个会话的修改请求或者拒绝M个会话中至少两个会话的修改请求。
采用上述方法，第一接入网设备可以根据会话之间的关联关系，来决定是否接纳或拒绝会话的建立请求或修改请求，从而能够有效避免第一接入网设备接纳或拒绝部分会话的建立请求或修改请求，而导致业务无法正常实现的问题。
在一种可能的设计中，M个会话包括终端设备与应用服务器之间的第一会话、所述应用服务器与本地设备之间的第二会话、所述本地设备与终端设备之间的第三会话；其中，终端设备与第一接入网设备建立有无线资源控制RRC连接。
在一种可能的设计中，该方法还包括：接收第二指示信息和/或第三指示信息；其中，第二指示信息指示所述本地设备对接收到的第二会话或第三会话中的数据进行边缘计算，第三指示信息指示所述本地设备进行本地边缘计算所需的时长。
在一种可能的设计中，对M个会话进行处理，包括：确定本地设备对接收到的第二会话中的数据进行边缘计算；在第一时间调度第二会话中的数据，以及在第一时间之后的第二时间调度第三会话中的数据；其中，第一时间和第二时间之间的时间间隔是根据本地设备进行边缘计算所需的时长得到的。
在一种可能的设计中，对M个会话进行处理，包括：确定本地设备对接收到的第三会话中的数据进行边缘计算；在第一时间调度第三会话中的数据，以及在第一时间之后的第二时间调度第二会话中的数据；其中，第一时间和第二时间之间的时间间隔是根据本地设备进行边缘计算所需的时长得到的。
采用上述方法，由于第一接入网设备可以根据边缘计算所需的时长来调度第二会话和第三会话中的数据，从而能够实现同步会话集内不同会话的业务数据按照一定的顺序和时间关系协同传输；比如，在第一时间之后的第二时间调度第三会话中的数据，能够避免过早调度第三会话中的数据而导致本地设备可能尚未完成边缘计算，或者能够避免过晚调度第三会话中的数据而导致影响数据传输效率。
在一种可能的设计中，本地设备包括辅助终端设备，或者，本地设备包括接入网设备。
在一种可能的设计中，该方法还包括：向本地设备发送第四指示信息，第四指示信息指示第二会话对应的数据无线承载DRB与第三会话对应的DRB具有关联关系。
在一种可能的设计中，该方法还包括：向本地设备发送第二指示信息和/或第三指示信息，其中，第二指示信息指示本地设备对接收到的第二会话或第三会话中的数据进行边缘计算，第三指示信息指示本地设备进行本地边缘计算所需的时长。
在一种可能的设计中，本地设备包括无线回传设备。
采用上述方法，当本地设备包括无线回传设备时，第一接入网设备可以向本地设备发送上述第四指示信息以及第二指示信息和/或第三指示信息，从而使得本地设备可以基于第四指示信息以及第二指示信息和/或第三指示信息，对第二会话和第三会话进行处理。
在一种可能的设计中，该方法还包括：确定本地设备对接收到的所述第二会话中的数据进行边缘计算；向本地设备发送第一配置信息，第一配置信息包括本地设备接收第二会话中数据的第一DRX周期，第一DRX周期与第二会话中数据的传输周期相同，第一DRX周期的起始偏置与第二会话中数据的起始偏置对齐；以及，向终端设备发送第二配置信息，第二配置信息包括终端设备接收第三会话中数据的第二DRX周期，第二DRX周期与第一DRX周期相同，第二DRX周期的起始偏置与第一DRX周期的起始偏置之间的时间间隔是根据本地设备进行边缘计算所需的时长得到的。
在一种可能的设计中，该方法还包括：确定本地设备对接收到的第三会话中的数据进行边缘计算；向本地设备发送第一配置信息，第一配置信息包括本地设备接收第三会话中数据的第一DRX周期，第一DRX周期与第三会话中数据的传输周期相同，第一DRX周期的起始偏置与第三会话中数据的起始偏置对齐；以及，向终端设备发送第二配置信息，第二配置信息包括终端设备接收第一会话中数据的第二DRX周期，第二DRX周期与第一DRX周期相同，第二DRX周期的起始偏置与第一DRX周期的起始偏置之间的时间间隔是根据往返时延得到的；其中，所述往返时延为终端设备通过第三会话发送第一数据的发送时间与终端设备通过第一会话接收第二数据的接收时间之间的时间间隔，第二数据是根据第一数据得到的。
在一种可能的设计中，该方法还包括：向终端设备发送第五指示信息，第五指示信息指示往返时延；其中，所述往返时延为终端设备通过第三会话发送第一数据的发送时间与终端设备通过第一会话接收第二数据的接收时间之间的时间间隔，第二数据是根据第一数据得到的；或者，所述往返时延为终端设备通过第一会话发送第三数据的发送时间与终端设备通过第三会话接收第四数据的接收时间之间的时间间隔，第四数据是根据第三数据得到的。
采用上述方法，通过向终端设备发送第五指示信息，使得终端设备可以根据往返时延进行省电等相关优化。
在一种可能的设计中，所述接收第一指示信息，包括：从核心网设备或者第二接入网设备接收第一指示信息；其中，第二接入网设备为终端设备的源接入网设备，第一接入网设备为终端设备的目标接入网设备。
在一种可能的设计中，第一指示信息包括M个会话分别对应的M个关联信息，和/或，本地设备的标识信息；其中，M个关联信息相同。
在一种可能的设计中，M个会话包括第一会话，第一会话对应的关联信息包括第一会话的类型信息和/或第一会话的关联标识；其中，第一会话的类型信息用于指示第一会话的类型为分离渲染或分段计算。
在一种可能的设计中，该方法还包括：接收第六指示信息，第六指示信息指示M个会话不再关联；以及根据第六指示信息，释放第二会话的资源和第三会话的资源。
采用上述方法，可以从有边缘计算切换到无边缘计算，从而能够保证终端设备可以在不同工作方式(比如有无连接电源、有无外挂强计算能力设备等)下自由地选择相应模式，同时保证业务体验和用户体验。
第二方面，本申请实施例提供一种通信方法，该方法可以应用于第一核心网设备或者第一核心网设备中的芯片，以该方法应用于第一核心网设备为例，在该方法中，第一核心网设备可以获取第一指示信息，第一指示信息指示M个会话具有关联关系，M为大于1的整数；以及，向接入网设备发送第一指示信息。
在一种可能的设计中，M个会话包括终端设备与应用服务器之间的第一会话、所述应用服务器与本地设备之间的第二会话、本地设备与终端设备之间的第三会话；其中，终端设备与所述接入网设备建立有RRC连接。
在一种可能的设计中，该方法还包括：向所述接入网设备发送第二指示信息和/或第三指示信息；其中，第二指示信息指示本地设备对接收到的第二会话或第三会话中的数据进行边缘计算，第三指示信息指示本地设备进行本地边缘计算所需的时长。
在一种可能的设计中，获取第一指示信息，包括：从终端设备获取第一指示信息；或者，从第二核心网设备获取第一指示信息。
在一种可能的设计中，从终端设备获取第一指示信息，包括：接收来自终端设备的第一请求消息，第一请求消息用于请求建立或修改M个会话或者M个会话中的第一会话，所述请求消息包括第一指示信息。
在一种可能的设计中，该方法还包括：向所述接入网设备发送第六指示信息，第六指示信息指示M个会话不再关联。
在一种可能的设计中，该方法还包括：接收来自终端设备的第二请求消息，第二请求消息用于请求修改M个会话中的第一会话，第二请求消息包括第七指示信息，第七指示信息指示第一会话与M个会话中的其它会话不再关联；根据第二请求消息，确定第六指示信息。
第三方面，本申请实施例提供一种通信方法，该方法可以应用于本地设备或者本地设备中的芯片，本地设备可以包括无线回传设备。以该方法应用于本地设备为例，在该方法中，本地设备接收来自接入网设备的第四指示信息，第四指示信息指示第二会话对应的DRB与第三会话对应的DRB具有关联关系；以及，根据第二指示信息，对第二会话和第三会话进行处理。
在一种可能的设计中，第二会话为应用服务器与本地设备之间的会话，第三会话为本地设备与终端设备之间的会话。
在一种可能的设计中，该方法还包括：接收来自所述接入网设备的第二指示信息和/或第三指示信息，其中，第二指示信息指示本地设备对接收到的第二会话或第三会话中的数据进行边缘计算，第三指示信息指示本地设备进行本地边缘计算所需的时长。
在一种可能的设计中，对第二会话和第三会话进行处理，包括：确定本地设备对接收到的第二会话中的数据进行边缘计算；在第一时间调度第二会话中的数据，以及在第一时间之后的第二时间调度第三会话中的数据；其中，第一时间和第二时间之间的时间间隔是根据本地设备进行边缘计算所需的时长得到的。
在一种可能的设计中，对第二会话和第三会话进行处理，包括：确定本地设备对接收到的第三会话中的数据进行边缘计算；在第一时间调度第三会话中的数据，以及在第一时间之后的第二时间调度第二会话中的数据；其中，第一时间和第二时间之间的时间间隔是根据本地设备进行边缘计算所需的时长得到的。
在一种可能的设计中，该方法还包括：接收来自接入网设备的第一配置信息，第一配置信息用于配置本地设备接收第二会话中数据的第一DRX周期，第一DRX周期与第二会话中数据的传输周期相同，第一DRX周期的起始偏置与第二会话中数据的起始偏置对齐；以及，接收来自所述接入网设备的第二配置信息，向终端设备发送第二配置信息，第二配置信息包括终端设备接收第三会话中数据的第二DRX周期，第二DRX周期与第一DRX周期相同，第二DRX周期的起始偏置与第一DRX周期的起始偏置之间的时间间隔是根据本地设备进行边缘计算所需的时长得到的。
在一种可能的设计中，该方法还包括：接收来自所述接入网设备的第一配置信息，第一配置信息用于配置本地设备接收第三会话中数据的第一DRX周期，第一DRX周期与第三会话中数据的传输周期相同，第一DRX周期的起始偏置与第三会话中数据的起始偏置对齐；以及，接收来自所述接入网设备的第二配置信息，向终端设备发送第二配置信息， 第二配置信息包括终端设备接收第一会话中数据的第二DRX周期，第二DRX周期与第一DRX周期相同，第二DRX周期的起始偏置与第一DRX周期的起始偏置之间的时间间隔是根据往返时延得到的；其中，所述往返时延为终端设备通过第三会话发送第一数据的发送时间与终端设备通过第一会话接收第二数据的接收时间之间的时间间隔，第二数据是根据第一数据得到的。
第四方面，本申请实施例提供一种通信方法，该方法可以应用于终端设备或者终端设备中的芯片，以该方法应用于终端设备为例，在该方法中，终端设备确定M个会话具有关联关系，并发送第一请求消息，第一请求消息用于请求建立或修改M个会话或者M个会话中的第一会话，所述请求消息包括第一指示信息，第一指示信息指示M个会话具有关联关系。
在一种可能的设计中，M个会话包括终端设备与应用服务器之间的第一会话、所述应用服务器与本地设备之间的第二会话、本地设备与终端设备之间的第三会话；其中，终端设备与所述接入网设备建立有RRC连接。
在一种可能的设计中，该方法还包括：发送第二请求消息，第二请求消息用于请求修改第一会话，第二请求消息包括第七指示信息，第七指示信息指示第一会话与M个会话中的其它会话不再关联。
需要说明的是，上述第二方面、第三方面和第四方面所描述的方法与第一方面所描述的方法相对应，第二方面、第三方面和第四方面所描述的方法中相关技术特征的有益效果可以参见第一方面的描述，具体不再赘述。
第五方面，本申请实施例提供了一种通信系统，该通信系统可以包括第一接入网设备和核心网设备；其中，所述第一接入网设备可以用于执行第一方面任意可能的设计或实现方式中的方法，核心网设备可以用于执行第二方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，该通信系统还可以包括本地设备，本地设备可以用于执行上述第三方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，该通信系统还可以包括终端设备，终端设备可以用于执行上述第四方面任意可能的设计或实现方式中的方法。
第六方面，本申请提供一种通信装置，所述通信装置可以为接入网设备(比如第一接入网设备)或者设置在接入网设备内部的芯片。所述通信装置具备实现上述第一方面的功能，比如，所述通信装置包括执行上述第一方面涉及操作所对应的模块或单元或手段(means)，所述模块或单元或手段可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述通信装置包括处理单元、通信单元，其中，通信单元可以用于收发信号，以实现该通信装置和其它装置之间的通信，比如，通信单元用于接收来自终端设备的配置信息；处理单元可以用于执行该通信装置的一些内部操作。处理单元、通信单元执行的功能可以和上述第一方面涉及的操作相对应。
在一种可能的设计中，所述通信装置包括处理器，处理器可以用于与存储器耦合。所述存储器可以保存实现上述第一方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第一方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器和存储器，存储器可以保存实现上述 第一方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第一方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器和接口电路，其中，处理器用于通过所述接口电路与其它装置通信，并执行上述第一方面任意可能的设计或实现方式中的方法。
第七方面，本申请提供一种通信装置，所述通信装置可以为核心网设备(比如第一核心网设备)或者设置在核心网设备内部的芯片。所述通信装置具备实现上述第二方面涉及的功能，比如，所述通信装置包括执行上述第二方面涉及操作所对应的模块或单元或手段，所述功能或单元或手段可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述通信装置包括处理单元、通信单元，其中，通信单元可以用于收发信号，以实现该通信装置和其它装置之间的通信，比如，通信单元用于向终端设备发送系统信息；处理单元可以用于执行该通信装置的一些内部操作。处理单元、通信单元执行的功能可以和上述第二方面涉及的操作相对应。
在一种可能的设计中，所述通信装置包括处理器，处理器可以用于与存储器耦合。所述存储器可以保存实现上述第二方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第二方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器和存储器，存储器可以保存实现上述第二方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第二方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器和接口电路，其中，处理器用于通过所述接口电路与其它装置通信，并执行上述第二方面任意可能的设计或实现方式中的方法。
可以理解地，上述第六方面或第七方面中，处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。此外，以上处理器可以为一个或多个，存储器可以为一个或多个。存储器可以与处理器集成在一起，或者存储器与处理器分离设置。在具体实现过程中，存储器可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
第八方面，本申请提供一种计算机可读存储介质，所述计算机存储介质中存储有计算机可读指令，当计算机读取并执行所述计算机可读指令时，使得计算机执行上述第一方面至第四方面的任一种可能的设计中的方法。
第九方面，本申请提供一种计算机程序产品，当计算机读取并执行所述计算机程序产品时，使得计算机执行上述第一方面至第四方面的任一种可能的设计中的方法。
第十方面，本申请提供一种芯片，所述芯片包括处理器，所述处理器与存储器耦合，用于读取并执行所述存储器中存储的软件程序，以实现上述第一方面至第四方面的任一种可能的设计中的方法。
本申请的这些方面或其它方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为本申请实施例适用的一种网络架构示意图；
图2a为本申请实施例提供的终端设备与网络设备之间的协议层结构示例图；
图2b为本申请实施例提供的一种CU-DU分离架构的示意图；
图2c为本申请实施例提供的又一种CU-DU分离架构的示意图；
图2d为本申请实施例提供的一种空口协议栈分布示意图；
图3a为本申请实施例提供的场景1中的会话1、会话2和会话3示意图；
图3b为本申请实施例提供的场景2中的会话1、会话2和会话3示意图；
图3c为本申请实施例提供的PDU会话建立流程示意图；
图3d为本申请实施例提供的四个会话示意图；
图4a为本申请实施例提供的一种情形中会话1、会话2和会话3示意图；
图4b为本申请实施例提供的一种情形中会话1、会话2和会话3示意图；
图4c为本申请实施例提供的一种情形中会话1、会话2和会话3示意图；
图5为本申请实施例提供的通信方法所对应的流程示意图；
图6为本申请实施例一提供的通信方法所对应的流程示意图；
图7为本申请实施例二提供的通信方法所对应的流程示意图；
图8为本申请实施例三提供的通信方法所对应的流程示意图；
图9为本申请实施例四提供的通信方法所对应的流程示意图；
图10为本申请实施例五提供的通信方法所对应的流程示意图；
图11为本申请实施例六提供的通信方法所对应的流程示意图；
图12为本申请实施例中所涉及的装置的可能的示例性框图；
图13为本申请实施例提供的一种接入网设备的结构示意图；
图14为本申请实施例提供的一种核心网设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
图1为本申请实施例适用的一种网络架构示意图。如图1所示，终端设备可接入到无线网络，以通过无线网络获取外网(例如数据网络(data network，DN))的服务，或者通过无线网络与其它设备通信，如可以与其它终端设备通信。该无线网络包括(无线)接入网(radio access network，(R)AN)和核心网(core network，CN)，其中，(R)AN(后文描述为RAN)用于将终端设备接入到无线网络，CN用于对终端设备进行管理并提供与DN通信的网关。
下面分别对图1中所涉及的终端设备、RAN、CN、DN进行详细说明。
一、终端设备
终端设备包括向用户提供语音和/或数据连通性的设备，例如可以包括具有无线连接功能的手持式设备、或连接到无线调制解调器的处理设备。该终端设备可以经无线接入网与核心网进行通信，与RAN交换语音和/或数据。该终端设备可以包括用户设备(user  equipment，UE)、无线终端设备、移动终端设备、设备到设备通信(device-to-device，D2D)终端设备、车到一切(vehicle to everything，V2X)终端设备、机器到机器/机器类通信(machine-to-machine/machine-type communications，M2M/MTC)终端设备、物联网(internet of things，IoT)终端设备、订户单元、订户站，移动站、远程站、接入点(access point，AP)、远程终端、接入终端、用户终端、用户代理、或用户装备等。例如，可以包括移动电话(或称为“蜂窝”电话)，具有移动终端设备的计算机，便携式、袖珍式、手持式、计算机内置的移动装置等。例如，个人通信业务(personal communication service，PCS)电话、无绳电话、会话发起协议(session initiation protocol，SIP)话机、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、等设备。还包括受限设备，例如功耗较低的设备，或存储能力有限的设备，或计算能力有限的设备等。例如包括条码、射频识别(radio frequency identification，RFID)、传感器、全球定位系统(global positioning system，GPS)、激光扫描器等信息传感设备。
作为示例而非限定，在本申请实施例中，该终端设备还可以是VR设备、增强现实(augmented reality，AR)设备、云游戏设备、工业控制中的无线终端、无人驾驶中的无线终端、远程手术中的无线终端、智能电网中的无线终端、运输安全中的无线终端、智慧城市中的无线终端、智慧家庭中的无线终端等。
其中，VR设备包括VR眼镜(VR Glass)、VR头盗、VR盒子(VR Box)等，用户通过VR设备可以体验诸如VR视频、VR游戏等VR应用服务，获得浸入式的场景体验。智慧城市中的无线终端可以包括监控摄像头，监控摄像头可以在捕捉到特定物体或事件时触发进一步动作，比如向警察局报警、上传最近拍摄的视频等。
本申请实施例中，用于实现终端设备的功能的装置可以是终端设备，也可以是能够支持终端设备实现该功能的装置，例如芯片系统或可实现终端设备功能的组合器件、部件，该装置可以被安装在终端设备中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。本申请实施例提供的技术方案中，以用于实现终端的功能的装置是终端设备为例，描述本申请实施例提供的技术方案。
二、RAN
RAN中可以包括一个或多个RAN设备，RAN设备与终端设备之间的接口可以为Uu接口(或称为空口)。当然，在未来通信中，这些接口的名称可以不变，或者也可以用其它名称代替，本申请对此不限定。
RAN设备即为将终端设备接入到无线网络的节点或设备，RAN设备又可以称为无线接入网设备或接入网设备。RAN设备例如包括但不限于：5G通信系统中的新一代基站(generation node B，gNB)、演进型节点B(evolved node B，eNB)、下一代演进型节点B(next generation eNB，ng-eNB)、无线回传设备、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站((home evolved nodeB，HeNB)或(home node B，HNB))、基带单元(baseBand unit，BBU)、传输接收点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。
本申请实施例中，用于实现接入网设备的功能的装置可以是接入网设备，也可以是能够支持接入网设备实现该功能的装置，例如芯片系统或可实现接入网设备功能的组合器件、部件，该装置可以被安装在接入网设备中。在本申请实施例提供的技术方案中，以用于实 现接入网设备的功能的装置是接入网设备为例，描述本申请实施例提供的技术方案。
(1)协议层结构
RAN设备和终端设备之间的通信遵循一定的协议层结构，例如控制面协议层结构可以包括无线资源控制(radio resource control，RRC)层、分组数据汇聚层协议(packet data convergence protocol，PDCP)层、无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理层；用户面协议层结构可以包括PDCP层、RLC层、MAC层和物理层，在一种可能的实现中，PDCP层之上还可以包括业务数据适配(service data adaptation protocol，SDAP)层。
以接入网设备和终端设备之间的数据传输为例，数据传输需要经过用户面协议层，比如经过SDAP层、PDCP层、RLC层、MAC层、物理层，其中，SDAP层、PDCP层、RLC层、MAC层、物理层也可以统称为接入层。示例性地，接入网设备和终端设备之间通过建立至少一个数据无线承载(data radio bearer，DRB)来传输数据，每个DRB可以对应一组功能实体集合，比如包括一个PDCP层实体，该PDCP层实体对应的至少一个RLC层实体，至少一个RLC层实体对应的至少一个MAC层实体，至少一个MAC层实体对应的至少一个物理层实体。需要说明的是，接入网设备和终端设备之间还可以通过建立至少一个信令无线承载(signalling radio bearer，SRB)来传输信令，DRB和SRB可以统称为无线承载(radio bearer，RB)。
以下行数据传输为例，图2a为下行数据在各层间传输的示意图，图2a中向下的箭头表示数据发送，向上的箭头表示数据接收。SDAP层实体自上层取得数据后，可以根据数据的服务质量流标识(QoS flow indicator，QFI)将数据映射到相应DRB的PDCP层实体，PDCP层实体可以将数据传送到该PDCP层实体对应的至少一个RLC层实体，进而由至少一个RLC层实体传输到对应的MAC层实体，再由MAC层实体生成传输块，然后通过对应的物理层实体进行无线传输。数据在各个层中进行相对应的封装，某一层从该层的上层收到的数据视为该层的服务数据单元(service data unit，SDU)，经过层封装后成为协议数据单元(protocol data unit，PDU)，再传递给下一个层。例如PDCP层实体从上层接收到的数据称为PDCP SDU，PDCP层实体发送到下层的数据称为PDCP PDU；RLC层实体从上层接收到的数据称为RLC SDU，RLC层实体发送到下层的数据称为RLC PDU。其中，不同层之间可以通过相应的通道来传输数据，比如RLC层实体与MAC层实体之间可以通过逻辑信道(logical channel，LCH)来传输数据，MAC层实体与物理层实体之间可以通过传输通道(transport channel)来传输数据。
示例性地，根据图2a还可以看出，终端设备还具有应用层和非接入层；其中，应用层可以用于向终端设备中所安装的应用程序提供服务，比如，终端设备接收到的下行数据可以由物理层依次传输到应用层，进而由应用层提供给应用程序；又比如，应用层可以获取应用程序产生的数据，并将数据依次传输到物理层，发送给其它通信装置。非接入层可以用于转发用户数据，比如将从应用层接收到的上行数据转发给SDAP层或者将从SDAP层接收到的下行数据转发给应用层。
(2)CU和DU
本申请实施例中，RAN设备可以包括一个或多个集中单元(centralized unit，CU)和一个或多个分布单元(distributed unit，DU)，多个DU可以由一个CU集中控制。作为示例，CU和DU之间的接口可以称为F1接口，其中，控制面(control panel，CP)接口可 以为F1-C，用户面(user panel，UP)接口可以为F1-U。CU和DU可以根据无线网络的协议层划分：比如图2b所示，PDCP层及以上协议层的功能设置在CU，PDCP层以下协议层(例如RLC层和MAC层等)的功能设置在DU。
可以理解的，上述对CU和DU的处理功能按照协议层的划分仅仅是一种举例，也可以按照其他的方式进行划分，比如RLC层以上协议层的功能设置在CU，RLC层及以下协议层的功能设置在DU，又比如可以将CU或者DU划分为具有更多协议层的功能，又比如CU或DU还可以划分为具有协议层的部分处理功能。在一种设计中，将RLC层的部分功能和RLC层以上的协议层的功能设置在CU，将RLC层的剩余功能和RLC层以下的协议层的功能设置在DU。在另一种设计中，还可以按照业务类型或者其他系统需求对CU或者DU的功能进行划分，例如按时延划分，将处理时间需要满足时延要求的功能设置在DU，不需要满足该时延要求的功能设置在CU。在另一种设计中，CU也可以具有核心网的一个或多个功能。示例性地，CU可以设置在网络侧方便集中管理；DU可以具有多个射频功能，也可以将射频功能拉远设置。本申请实施例对此并不进行限定。
示例性地，CU的功能可以由一个实体来实现，或者也可以由不同的实体来实现。例如，如图2c所示，可以对CU的功能进行进一步切分，即将控制面和用户面分离并通过不同实体来实现，分别为控制面CU实体(即CU-CP实体)和用户面CU实体(即CU-UP实体)，CU-CP实体和CU-UP实体可以与DU相耦合，共同完成RAN设备的功能。CU-CP实体与CU-UP实体之间的接口可以为E1接口，CU-CP实体与DU之间的接口可以为F1-C接口，CU-UP实体与DU之间的接口可以为F1-U接口。其中，一个DU和一个CU-UP可以连接到一个CU-CP。在同一个CU-CP控制下，一个DU可以连接到多个CU-UP，一个CU-UP可以连接到多个DU。
基于图2c，图2d为一种空口协议栈分布示意图。如图2d所示，针对用户面和控制面来说，空口协议栈都可以是RLC、MAC、PHY在DU，PDCP及以上协议层在CU。
需要说明的是：在上述图2b至图2d所示意的架构中，CU产生的信令可以通过DU发送给终端设备，或者终端设备产生的信令可以通过DU发送给CU。DU可以不对该信令进行解析而直接通过协议层封装后透传给终端设备或CU。以下实施例中如果涉及这种信令在DU和终端设备之间的传输，此时，DU对信令的发送或接收包括这种场景。例如，RRC或PDCP层的信令最终会处理为物理层的数据发送给终端设备，或者，由接收到的物理层的数据转变而来。在这种架构下，该RRC或PDCP层的信令，即也可以认为是由DU发送的，或者，由DU和射频装置发送的。
(3)无线回传设备
上述图1所示意的架构中，接入网设备可以包括宿主节点和一个或多个无线回传设备(暂未示意出)。终端设备通过一个或多个无线回传设备接入到宿主节点。在5G通信系统中，无线回传设备可以称为接入回程一体化(integrated access and backhaul，IAB)节点；在长期演进(long term evolution，LTE)通信系统中，无线回传设备可以称为中继节点(relay node，RN)。当然，在其他通信系统中，无线回传设备还可以有不同的名称，在此不作限制。
终端设备的上行数据可以由一个或多个IAB节点通过无线回传链路传输到宿主节点，以及终端设备的下行数据可以由一个或多个IAB节点通过无线回传链路传输到终端设备。其中，宿主节点可以称为IAB宿主(IAB donor)或者宿主基站(donor gNodeB，DgNB) 或者基站。
示例性地，若终端设备与基站之间包括一个IAB节点，则可以理解为是一级IAB节点；若终端设备与基站之间包括多个IAB节点，则可以理解为是多级IAB节点(或者多跳IAB节点)。针对于多跳IAB节点，其中某一IAB节点的上一跳节点可以是指在包含该节点的无线回传链路中的、在该节点之前最后一个接收到数据包的节点；某一IAB节点的下一跳节点可以是指在包含该节点的无线回传链路中的、在该节点之后第一个接收到数据包的节点。
三、CN
CN中可以包括一个或多个CN设备，以5G通信系统为例，CN中可以包括接入和移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、用户面功能(user plane function，UPF)网元、策略控制功能(policy control function，PCF)网元、统一数据管理(unified data management，UDM)网元、应用功能(application function，AF)网元等。
AMF网元是由运营商网络提供的控制面网元，负责终端设备接入运营商网络的接入控制和移动性管理，例如包括移动状态管理，分配用户临时身份标识，认证和授权用户等功能。
SMF网元是由运营商网络提供的控制面网元，负责管理终端设备的PDU会话。PDU会话是一个用于传输PDU的通道，终端设备需要通过PDU会话与DN互相传送PDU。PDU会话由SMF网元负责建立、维护和删除等。SMF网元包括会话管理(如会话建立、修改和释放，包含UPF和RAN之间的隧道维护)、UPF网元的选择和控制、业务和会话连续性(service and session continuity，SSC)模式选择、漫游等会话相关的功能。
UPF网元是由运营商提供的网关，是运营商网络与DN通信的网关。UPF网元包括数据包路由和传输、包检测、服务质量(quality of service，QoS)处理、合法监听、上行包检测、下行数据包存储等用户面相关的功能。
PCF网元是由运营商提供的控制面功能，用于向SMF网元提供PDU会话的策略。策略可以包括计费相关策略、QoS相关策略和授权相关策略等。
UDM网元是由运营商提供的控制面网元，负责存储运营商网络中签约用户的用户永久标识符(subscriber permanent identifier，SUPI)、签约数据等信息。
AF网元是提供各种业务服务的功能网元，能够通过其它网元与核心网交互，以及能够和策略管理框架交互进行策略管理。
此外，尽管未示出，CN中还可以包括其它可能的网元，比如网络开放功能(network exposure function，NEF)、网元统一数据仓储(unified data repository，UDR)网元。
本申请实施例中，用于实现核心网设备的功能的装置可以是核心网设备，也可以是能够支持核心网设备实现该功能的装置，例如芯片系统或可实现核心网设备功能的组合器件、部件，该装置可以被安装在核心网设备中。在本申请实施例提供的技术方案中，以用于实现核心网设备的功能的装置是核心网设备为例，描述本申请实施例提供的技术方案。
此外，本申请实施例中，为便于描述，可以将接入网设备、无线回传设备、核心网设备等统称为网络设备。
四、DN
DN也可以称为分组数据网络(packet data network，PDN)，是位于运营商网络之外的 网络，运营商网络可以接入多个DN，DN中可部署有多种业务对应的应用服务器(比如VR服务器)，为终端设备提供多种可能的服务。其中，应用服务器中可以设置有与终端设备的应用层相对等的应用层。
图1中Npcf、Nudm、Naf、Namf、Nsmf、N1、N2、N3、N4，以及N6为接口序列号。这些接口序列号的含义可参见相关标准协议中定义的含义，在此不做限制。
可以理解的是，图1中是以5G通信系统为例进行示意的，本申请实施例中的方案还可以适用于其它可能的通信系统中，比如LTE通信系统或者未来的第六代(the 6th generation，6G)通信系统中。上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
上述图1所示意的网络架构中可以支持多种可能的业务场景，下面描述两种可能的场景。
(1)场景1
以上述图1中所示意的终端设备为VR头盔为例，在本地二次渲染场景中，VR头盔可以通过接入网设备连接到VR服务器，并将VR头盔和眼球的姿势信息等发送到VR服务器。VR服务器根据这些姿势信息生成VR场景(VR scene)，并对VR场景中的VR视窗(VR viewport)进行预渲染(pre-rendering)，生成VR媒体数据，以及可选的VR渲染元数据(rendering metadata)；进一步地，VR服务器可以通过移动网络将VR媒体数据和可选的VR渲染元数据发送给本地设备进行本地二次渲染。根据从VR头盔接收到的最新VR头盔和眼球的姿势信息或根据VR渲染元数据，本地设备对接收到的VR媒体数据进行VR视窗二次渲染，生成新的VR媒体数据，然后将二次渲染后的新VR媒体数据发送给HMD进行显示。VR详细处理过程请参考第三代合作伙伴计划(3rd generation partnership project，3GPP)技术报告(technical report，TR)26.928版本16.0.0。
在5G通信系统中，为了完成上述渲染过程，可以建立三个会话，即：VR头盔与VR服务器之间的会话1、VR服务器与本地设备之间的会话2，以及本地设备与VR头盔之间的会话3；参见图3a所示，其中，箭头可以代表数据传输方向。VR头盔通过会话1将VR头盔和眼球的姿势信息发送到VR服务器。VR服务器通过会话2将VR媒体数据和可选的VR渲染元数据发送给进行本地二次渲染的本地设备。本地设备通过会话3将二次渲染后的新VR媒体数据发送给VR头盔，以及可选地，VR头盔可以通过会话3将最新VR头盔和眼球的姿势信息发送给本地设备。
根据上述描述可以看出，针对于VR业务来说，会话1、会话2和会话3存在同步需求，比如三个会话需要同时建立，从而才能保证数据的有效传输。
(2)场景2
以上述图1中所示意的终端设备为智慧城市中的监控摄像头为例，监控摄像头可能需要进行图像识别，以便在捕捉到特定物体或事件时触发进一步动作，比如向警察局报警、上传最近拍摄的视频等。但是，图像识别需要非常复杂的计算(比如采用人工智能的图像识别方法)，路边监控摄像头通常不具备这种计算能力或只具备很简单的计算能力。这时，需要将图像识别相关的部分或全部计算卸载到基站和/或云服务器去进行计算。但是，频繁 地将图像上传给基站和/云服务器需要消耗很大的移动网络带宽。因此，一种可能的做法是监控摄像头、本地设备和云服务器依次分别进行一部分图像识别计算，最后由云服务器给出最终识别结果，将结果返还给监控摄像头。
类似地，在5G通信系统中，为了完成上述图像识别过程，可以建立三个会话，即：监控摄像头与本地设备之间的会话3、本地设备与云服务器之间的会话2，以及云服务器与监控摄像头之间的会话1；参见图3b所示，其中，箭头可以代表数据传输方向。监控摄像头通过会话3将图像或经过监控摄像头初步处理的图像数据和/或计算上下文信息发送到本地设备；本地设备通过会话2将本地设备进一步处理的图像数据和/或计算上下文信息发送给云服务器；进而云服务器通过会话1将图像识别结果发送给监控摄像头。
根据上述描述可以看出，针对于图像识别业务来说，会话1、会话2和会话3也存在同步需求，比如三个会话需要同时建立，从而才能保证数据的有效传输。
以上述两种场景中所涉及的会话为PDU会话为例，图3c为当前3GPP协议中PDU会话建立流程示意图，参见图3c所示，该流程可以包括：
S301，SMF网元通过AMF网元向接入网设备发送PDU会话资源建立请求(PDU session resource setup request)消息，PDU会话资源建立请求消息包括为终端设备待建立的一个或多个PDU会话的标识，比如PDU会话1、PDU会话2和PDU会话3。
S302，接入网设备接收PDU会话资源建立请求消息，根据PDU会话资源建立请求消息对PDU会话进行接纳控制。
示例性地，接入网设备可以接纳PDU会话资源建立请求消息中部分或全部PDU会话的建立请求，或者，也可以拒绝PDU会话资源建立请求消息中部分或全部PDU会话的建立请求。比如，接入网设备接纳PDU会话1、PDU会话2的建立请求，拒绝PDU会话3的建立请求。
S303，接入网设备通过AMF网元向SMF网元发送PDU会话资源建立响应消息。
此处，PDU会话资源建立响应消息中可以包括PDU会话建立失败列表(PDU Session Failed to Setup List)，PDU会话建立失败列表包括被拒绝的PDU会话的标识，比如PDU会话3的标识。
根据上述S301至S303可以看出，在PDU会话建立过程中，接入网设备可以拒绝终端设备的部分或全部PDU会话的建立请求。然而，针对于上述所描述的两种场景，比如针对VR业务来说，若接入网设备拒绝了会话1、会话2和会话3中的某个会话的建立请求，则会导致VR业务无法正常实现。
基于此，本申请实施例中将引入同步会话集(set)，属于同一同步会话集的多个会话具有关联关系，从而使得接入网设备可以基于多个会话之间的关联关系，来对多个会话进行处理，以满足不同会话之间的同步需求。
下面先对本申请实施例涉及的相关技术特征进行解释说明。需要说明的是，这些解释是为了让本申请实施例更容易被理解，而不应该视为对本申请所要求的保护范围的限定。
一、会话
本申请实施例中所涉及的会话，可以用于提供第一设备和第二设备之间的连接性服务，或者说，可以用于实现第一设备和第二设备之间的数据传输。比如，第一设备和第二设备 可以分别为终端设备和应用服务器，或者，第一设备和第二设备也可以分别为不同的终端设备(比如终端设备1和终端设备2)，又或者，第一设备和第二设备也可以分别为终端设备和网络设备，又或者，第一设备和第二设备也可以分别为其它可能的设备，具体不做限定。
在一个示例中，会话可以是指PDU会话，或者也可以是指网络协议(Internet protocol，IP)连接接入网(IP-connectivity access network，IP-CAN)会话或业务检测功能(traffic detection function，TDF)会话等其它可能的会话，具体不做限定。其中，IP-CAN会话是一种终端设备与IP网络之间的关联，该关联可以通过终端设备的IP地址及可用的终端设备的标识信息来标识。
需要说明的是：(1)在上述场景1或场景2中，本申请实施例是以为实现同一个业务建立三个不同的会话(即会话1、会话2和会话3)为例进行描述的，但在实践中，也可以理解为：为同一个业务建立一个会话，该会话包含三部分，比如该会话包括终端设备与应用服务器之间的部分、应用服务器与本地设备之间的部分、以及本地设备与终端设备之间的部分；或者，为同一个业务建立两个会话，比如将上述会话1理解为一个会话，而将上述会话2和会话3合并成一个包含两部分的会话(即应用服务器与本地设备之间的部分、本地设备与终端设备之间的部分)。本申请实施例的下文描述中，将继续以会话这一说法为例，具体实践中，可以替换为其它可能的说法。
(2)上述场景1和场景2中，为同一个业务建立了三个不同的会话，即基于一个本地设备进行本地边缘计算，但本申请实施例提供的方案也可以适用于多个本地设备进行本地边缘计算的场景，比如一种可能的场景是：每个本地设备分别进行一部分边缘计算，本地设备N将计算结果和可选的元数据发送给本地设备N+1，由最后一个参与部分边缘计算的本地设备将计算结果和可选的元数据发送给终端设备或云服务器。其中，本地设备可以为终端设备、基站、IAB节点、中继节点、CU、DU、CU-CP或CU-UP等核心网之外的网络设备。
也就是说，本申请实施例提供的方案可以适用于为同一个业务建立更多个会话的场景，比如四个会话或者五个会话，具体个数可以不做限定。举个例子，参见图3d所示，为四个会话示意图；其中，四个会话可以分别为：终端设备与应用服务器之间的会话1、应用服务器与本地设备1之间的会话2、本地设备1与本地设备2之间的会话3，以及本地设备2与终端设备之间的会话4。在一种可能的情形中，假设图3c中的终端设备为VR头盔，应用服务器为VR服务器，则一种可能的数据传输过程为：VR头盔通过会话1将VR头盔和眼球的姿势信息发送到VR服务器。VR服务器通过会话2将VR媒体数据发送给进行本地设备1，本地设备1对部分VR媒体数据进行二次渲染。本地设备1通过会话3将二次渲染得到的新VR媒体数据发送给本地设备2，本地设备2对二次渲染得到的新VR媒体数据进行三次渲染，得到三次渲染后的新VR媒体数据。本地设备2通过会话3将三次渲染后的新VR媒体数据发送给VR头盔。在该例子中，VR服务器、本地设备1、本地设备2和VR头盔对VR媒体数据进行串行处理，但在实际应用中，也可能有并行处理，比如本地设备1和本地设备2对VR服务器来的VR媒体数据各进行一部分二次渲染，然后合并交给VR头盔显示，在此不做限制。
本申请实施例的下文描述中，将继续以为同一个业务建立三个不同的会话为例，而为同一个业务建立更多个会话的实现，可以适应性参照实施。
二、本地设备
本申请实施例中所涉及的本地设备，可以具有应用层功能，或者可以对应用层数据进行处理。比如，针对于VR业务，本地设备可以用于实现VR业务的图像渲染；又比如，针对于图像识别业务，本地设备可以用于实现分段计算(比如基于人工智能(artificial intelligence，AI)的图像识别算法中的神经网络的部分计算)。
示例性地，考虑到边缘应用服务器(edge application server，EAS)具有应用层功能，因此，在一个示例中，本地设备可以包括部署在一起的辅助终端设备(assistant UE，A-UE)和EAS，其中，辅助终端设备可以为手机或者客户前置设备(customer premise equipment，CPE)。比如，EAS可以是辅助终端设备中的一个软件应用程序。此种情形下，参见图4a，示意出了上述场景1、场景2中所描述的会话1、会话2和会话3。
在又一个示例中，本地设备可以包括部署在一起的接入网设备和EAS，其中，EAS可以直接与接入网设备相连。此种情形下，参见图4b，示意出了上述场景1、场景2中所描述的会话1、会话2和会话3。需要说明的是，针对于示例，在其它可能的场景中，EAS也可以通过本地用户面功能(local-UPF，L-UPF)与接入网设备相连，此种情形下，本地设备可以包括部署在一起的接入网设备、L-UPF和EAS，或者本地设备也可以是包含L-UPF和EAS功能的接入网设备。
在又一个示例中，本地设备可以包括部署在一起的无线回传设备(比如IAB节点)和EAS，其中，IAB节点可以直接与EAS相连；或者，本地设备也可以是包含EAS软件应用程序的IAB节点。此种情形下，参见图4c，示意出了上述场景1、场景2中所描述的会话1、会话2和会话3。
需要说明的是：上述仅是描述了本地设备的几种可能的示例，可以理解地，本申请实施例中的方法可以适用于EAS与gNB、eNB、ng-eNB、gNB-CU、eNB-CU、gNB-CU-UP、eNB-CU-UP、IAB节点等网络设备或辅助终端设备同部署或一体化的场景，为了便于描述，本申请实施例中将部署在一起或一体化的网络设备、EAS和可能的相关网络实体视为一个网络实体，统称为本地设备。此外，本申请实施例可以适用于对同一个业务，存在多于一个EAS部署在不同的网络设备的场景；本申请实施例不限定EAS与网络设备的连接方式，比如EAS可以直接与接入网设备相连，或者EAS也可以通过L-UPF与接入网设备相连，或者它们一体化成一个物理设备。
基于上述相关技术特征，下面对本申请实施例提供的通信方法进行详细介绍。
需要说明的是，下文中将主要以场景1和场景2为例，但本申请实施例提供的通信方法也可以适用于其它多种可能的场景，比如本申请实施例提供的方法同样可以适用于云游戏、混合现实(mixed reality，MR)等可能存在下行本地渲染或下行边缘计算的场景，也同样可以适用于除场景2以外的其它存在上行边缘计算的场景，具体不做限定。
图5为本申请实施例提供的通信方法所对应的流程示意图，如图5所示，该方法包括S501、S502和S503，本申请实施例对S501、S502和S503的执行顺序不作限制。
S501，第一核心网设备获取第一指示信息，第一指示信息指示M个会话具有关联关系，M为大于1的整数。
此处，第一核心网设备可以为SMF网元或AMF网元。第一指示信息指示M个会话具有关联关系，也可以描述为，第一指示信息指示M个会话属于同一同步会话集，同步会 话集也可以称为同步会话组(group)或者其它可能的名称，具体不做限定；同步会话集中的多个会话具有关联关系。
在一个示例中，M＝3，M个会话可以包括终端设备与应用服务器之间的第一会话(比如上述场景1或场景2中的会话1)、应用服务器与本地设备之间的第二会话(比如上述场景1或场景2中的会话2)、本地设备与终端设备之间的第三会话(比如上述场景1或场景2中的会话3)。其中，终端设备与第一接入网设备建立有RRC连接。
示例性地，第一核心网设备获取第一指示信息的方式可以有多种，此处描述两种可能的实现方式。
在一种可能的实现方式中，第一核心网设备可以从终端设备获取第一指示信息。比如，终端设备可以向第一核心网设备发送第一请求消息，第一请求消息用于请求建立或修改M个会话或者M个会话中的第一会话，第一请求消息包括第一指示信息。在一个示例中，第一请求消息可以为PDU会话建立请求(PDU session establishment request)消息或者PDU会话修改请求(PDU session modification request)消息。
在又一种可能的实现方式中，第一核心网设备可以从第二核心网设备获取第一指示信息，其中，第二核心网设备可以为UDM网元或PCF网元。比如，终端设备可以向第一核心网设备发送PDU会话建立请求消息或者PDU会话修改请求消息，第一核心网设备接收到PDU会话建立请求消息或者PDU会话修改请求消息后，可以从第二核心网设备(比如UDM网元或PCF网元)获取第一指示信息。
此外，第一核心网设备还可以获取第二指示信息和/或第三指示信息。第二指示信息指示本地设备对接收到的第二会话的数据进行边缘计算(比如上述场景1)，或者，第二指示信息指示本地设备对接收到的第三会话的数据进行边缘计算(比如上述场景2)；第三指示信息指示本地设备进行本地边缘计算所需的时长。其中，若第一核心网设备获取到了第二指示信息和第三指示信息，则当第二指示信息指示本地设备对接收到的第二会话的数据进行边缘计算时，第三指示信息所指示的本地设备进行本地边缘计算所需的时长是指，本地设备对接收到的第二会话的数据进行边缘计算所需的时长；当第二指示信息指示本地设备对接收到的第三会话的数据进行边缘计算时，第三指示信息所指示的本地设备进行本地边缘计算所需的时长是指，本地设备对接收到的第三会话的数据进行边缘计算所需的时长。
示例性地，第一核心网设备获取第二指示信息和/或第三指示信息的方式可以有多种，比如可以参照第一核心网设备获取第一指示信息的方式。
可以理解地，上述第一指示信息、第二指示信息和第三指示信息可以是由终端设备通过第一请求消息提供给第一核心网设备，又或者，也可以是第一核心网设备接收到终端设备发送的第一请求消息后，从第二核心网设备获取。也就是说，第一指示信息、第二指示信息和第三指示信息可以由终端设备或第二核心网设备提供，比如由终端设备或第二核心网设备全部提供这三个信息，或各提供一部分。
S502，第一核心网设备向第一接入网设备发送第一指示信息；相应地，第一接入网设备可以接收第一指示信息。
示例性地，第一核心网设备还可以向第一接入网设备发送第二指示信息和/或第三指示信息。在一个示例中，第一核心网设备可以通过同一消息向第一接入网设备发送第一指示信息、第二指示信息、第三指示信息；或者，也可以分别通过不同消息向第一接入网设备发送第一指示信息、第二指示信息、第三指示信息。
需要说明的是，在其它可能的实施例中，上述S502也可以替换为：S502’，第二接入网设备向第一接入网设备发送第一指示信息。此处，第二接入网设备可以为终端设备的源网络设备，第一接入网设备可以为终端设备的目标网络设备，当终端设备由第二接入网设备切换或由RRC去激活态(RRC_INACTIVE态)恢复至第一接入网设备时，第二接入网设备可以向第一接入网设备发送上述第一指示信息。可选地，第二接入网设备还可以向第一接入网设备发送上述第二指示信息和/或第三指示信息。此种情形下，也可以不再执行上述S501。
S503，第一接入网设备根据第一指示信息，对M个会话进行处理。
此处，第一接入网设备对M个会话进行处理，可以包括：(1)第一接入网设备根据第一指示信息，对M个会话进行接纳控制。和/或，(2)第一接入网设备根据第一指示信息、第二指示信息和第三指示信息对M个PDU会话中的数据进行调度。
其中，(1)第一接入网设备根据第一指示信息，对M个会话进行接纳控制，可以是指：第一接入网设备根据第一指示信息，同时接纳M个会话中至少两个会话的建立请求或者同时拒绝M个会话中至少两个会话的建立请求；或者，同时接纳M个会话中至少两个会话的修改请求或者同时拒绝M个会话中至少两个会话的修改请求。所述M个会话属于一个同步会话集，所述至少两个会话可以是该同步会话集中所有需要第一接入网设备进行接纳控制的会话。
比如，在上述图4a或图4c所示意的情形中，第一接入网设备可以根据第一指示信息，同时接纳会话1、会话2和会话3的建立请求或者同时拒绝会话1、会话2和会话3的建立请求；或者，同时接纳会话1、会话2和会话3的修改请求或者同时拒绝会话1、会话2和会话3的修改请求。在上述图4b所示意的情形中，第一接入网设备可以根据第一指示信息，同时接纳会话1和会话3的建立请求或者同时拒绝会话1和会话3的建立请求；或者，同时接纳会话1和会话3的修改请求或者同时拒绝会话1和会话3的修改请求；其中，会话2由于不涉及空口传输，假定不需要第一接入网设备进行接纳控制。如此，由于第一接入网设备可以根据会话之间的关联关系，来决定是否接纳或拒绝会话的建立请求或修改请求，从而能够有效避免第一接入网设备接纳或拒绝部分会话的建立请求或修改请求，而导致业务无法正常实现的问题。
(2)第一接入网设备根据第一指示信息、第二指示信息和第三指示信息，对M个PDU会话中的数据进行调度处理，可以是指：若第一接入网设备确定本地设备对接收到的第二会话中的数据进行边缘计算，则可以在第一时间调度第二会话中的数据(即分配第一接入网设备与本地设备之间、第一时间的无线资源传输第二会话的数据)，以及在第一时间之后的第二时间调度第三会话中的数据(即分配本地设备与终端设备之间、第二时间的无线资源传输第三会话的数据)；其中，第一时间和第二时间之间的时间间隔是根据本地设备进行边缘计算所需的时长得到的。或者，若第一接入网设备确定本地设备对接收到的第三会话中的数据进行边缘计算，则可以在第一时间调度第三会话中的数据，以及在第一时间之后的第二时间调度第二会话中的数据；其中，第一时间和第二时间之间的时间间隔是根据本地设备进行边缘计算所需的时长得到的。在一个示例中，第一时间和第二时间之间的时间间隔可以等于本地设备进行边缘计算所需的时长。如此，由于第一接入网设备可以根据边缘计算所需的时长来调度第二会话和第三会话中的数据，从而能够实现同步会话集内不同会话的业务数据按照一定的顺序和时间关系协同传输；比如，在第一时间之后的第二 时间调度第三会话中的数据，能够避免过早调度第三会话中的数据而导致本地设备可能尚未完成边缘计算，或者能够避免过晚调度第三会话中的数据而导致影响数据传输效率。
采用上述方法，本申请实施例中，第一接入网设备在对M个会话进行处理时，可以考虑M个会话之间的关联关系，从而便于满足不同会话之间的同步需求，有效保证用户对业务的体验质量(quality of experience，QoE)。
上述图5所描述的方法可以适用于图4a至图4c所示意的任一情形中，由于不同情形中的本地设备不同，从而在实现流程存在一些差异之处。下面将分别结合图4a至图4c所示意的情形，对本申请实施例提供的通信方法进行展开说明。
需要说明的是，实施例一至实施例六中所描述的接入网设备可以为基站、CU或CU-CP等具有RRC连接控制功能的设备。
实施例一
在实施例一中，将以图4a所示意的情形为例，描述一种可能的实现。图4a中本地设备可以包括辅助终端设备和EAS，为便于清楚示意各实施例之间的区别，在该实施例中，将本地设备直接称为辅助终端设备。
图6为本申请实施例一提供的通信方法所对应的流程示意图，如图6所示，该方法包括S600至S610，本申请实施例对S600至S610的执行顺序不作限制。
S600，接入网设备和/或第一核心网设备获取辅助终端设备的能力信息，辅助终端设备的能力信息用于指示辅助终端设备是否支持边缘计算。
在一个示例中，辅助终端设备可以向接入网设备和/或第一核心网设备发送能力信息。比如，辅助终端设备在与接入网设备完成RRC连接建立之后，或注册过程中，或注册完成之后，向接入网设备和/或第一核心网设备上报能力信息。
在又一个示例中，在辅助终端设备的注册过程中或注册完成之后，第一核心网设备也可以从UDM网元获取辅助终端设备的能力信息。
S601，终端设备向第一核心网设备发送第一请求消息；相应地，第一核心网设备可以接收第一请求消息。其中，该实施例中以第一请求消息为PDU会话建立请求消息为例。
此处，PDU会话建立请求消息可以用于请求建立M个PDU会话，比如PDU会话建立请求消息可以包括M个PDU会话(比如会话1、会话2和会话3)的信息和第一指示信息，第一指示信息指示会话1、会话2和会话3具有关联关系；其中，PDU会话的信息可以包括PDU会话标识(ID)、PDU会话的类型(type)信息和请求的SSC模式(requested SSC mode)中的至少一项。
可选地，PDU会话建立请求消息还可以包括第二指示信息和第三指示信息，其中，第二指示信息指示辅助终端设备用于对接收到的会话2或会话3的数据进行边缘计算；第三指示信息指示辅助终端设备进行本地边缘计算所需的时长。在一个示例中，终端设备的非接入层可以先通过应用层(可能经由操作系统)获得第二指示信息和/或第三指示信息，进而通过PDU会话建立请求消息发送给第一核心网设备。
一、针对第一指示信息进行解释说明。
示例性地，第一指示信息指示会话1、会话2和会话3具有关联关系的实现方式可以有多种，下面描述几种可能的实现方式。
实现方式1，第一指示信息包括M个PDU会话分别对应的M个关联信息。其中，PDU 会话对应的关联信息可以包括PDU会话的类型信息和/或PDU会话的关联标识(association ID)，类型信息相同和/或关联标识相同的PDU会话具有关联关系。其中，PDU会话的类型信息可以用于指示PDU会话的类型为分离渲染(针对于场景1)或分段计算(针对于场景2)；分离渲染(split rendering)也可以描述为本地渲染，类似地，分段计算也可以有其它描述，比如分离推理(split inference)，具体不做限定。比如，会话1、会话2和会话3的类型均为分离渲染，则说明会话1、会话2和会话3具有关联关系。
示例性地，PDU会话建立请求消息携带第一指示信息的方式可以有多种。比如，可以在M个PDU会话的每个PDU会话的信息中，重用现有信元(information element，IE)，比如每个PDU会话的类型信息中增加“分离渲染或分段计算”作为新的枚举值。又比如，可以在M个PDU会话的每个PDU会话的信息中，新增一个信元，该信元用于承载PDU会话的关联标识。
实现方式2，第一指示信息包括辅助终端设备的标识信息，在4a所示意的场景中，辅助终端设备的标识信息可以包括辅助终端设备的IP地址和/或MAC地址，或者也可以包括其它可能的信息，比如辅助终端设备的SUPI，具体不做限定，但凡是能够让第一核心网设备唯一识别辅助终端设备的信息均可以理解为辅助终端设备的标识信息。示例性地，辅助终端设备的标识信息可以承载于独立于PDU会话的信息的一个新增信元，比如通过在PDU会话建立请求消息中增加独立的信元“Local Device ID”来承载辅助终端设备的标识信息；或者，也可以是在M个PDU会话中每个PDU会话的信息中增加一个信元，用于承载辅助终端设备的标识信息。
实现方式3，第一指示信息包括M个PDU会话分别对应的M个关联信息和辅助终端设备的标识信息，具体实现可以参照上述实现方式1和实现方式2。
二、针对第二指示信息和第三指示信息进行解释说明。
示例性地，第二指示信息指示辅助终端设备用于对接收到的会话2或会话3的数据进行边缘计算的指示方式可以有多种。比如，第二指示信息可以包括移动边缘计算(mobile edge computing)的类型，移动边缘计算的类型指示辅助终端设备是对终端设备的上行业务数据进行边缘计算，还是对终端设备的下行业务数据进行边缘计算(其中，本地渲染和分段计算均属于边缘计算，都是在网络的边缘，即本地设备对应用层数据进行相关的“计算”，但在本发明中，可以不限定只针对应用层数据的边缘“计算”，也适用于其它协议层数据)。若该类型为下行(downlink)，则说明辅助终端设备是对终端设备的下行业务数据进行边缘计算，即辅助终端设备用于对接收到的会话2的数据进行边缘计算；若该类型为上行(uplink)，则说明辅助终端设备是对终端设备的上行业务数据进行边缘计算，即辅助终端设备用于对接收到的会话3的数据进行边缘计算。可以理解地，移动边缘计算的类型也可以替换为其它可能的描述，比如渲染业务方向等，具体不做限定。
示例性地，PDU会话建立请求消息携带第二指示信息和/或第三指示信息的方式可以有多种。在一个示例中，第二指示信息可以承载于独立于PDU会话的信息的一个新增信元，比如通过在PDU会话建立请求消息中增加独立的信元“MEC type”来承载第二指示信息；第三指示信息可以承载于独立于PDU会话的信息的一个新增信元，比如通过在PDU会话建立请求消息中增加独立的信元“Local Process Time”来承载第三指示信息。在又一个示例中，也可以是在M个PDU会话中每个PDU会话的信息中增加两个信元，分别用于承载第二指示信息和第三指示信息。
基于上述描述，作为一种具体例子，若PDU会话建立请求消息包括：三个PDU会话的信息，Local Device ID为IPv4地址10.10.10.1，MEC type为“downlink”，Local Process Time为5ms，则表示：由IPv4地址为10.10.10.1的辅助终端设备对终端设备的下行业务数据进行边缘计算，边缘计算所需的时长为5ms。
需要说明的是：(1)在其它可能的示例中，PDU会话建立请求消息也可以用于请求建立M个PDU会话(比如会话1、会话2和会话3)中的一个PDU会话，比如会话1。其中，PDU会话建立请求消息可以包括会话1的信息和第一指示信息，第一指示信息指示请求的是涉及边缘计算的会话，比如第一指示信息可以包括辅助终端设备的标识信息，以隐含指示会话1是涉及边缘计算的会话，其它实现可以参照上述上文。此种情形下，后续可以由第一核心网设备判断并触发其它会话建立，比如第一核心网设备接收到PDU会话建立请求消息后，确定PDU会话建立请求消息中携带第一指示信息，则可以根据第一指示信息触发会话1、会话2和会话3的建立(即执行S602)。
(2)上文中是以第一指示信息、第二指示信息和第三指示信息为PDU会话级别的信息为例进行描述的，在其它可能的示例中，第一指示信息、第二指示信息和第三指示信息也可以是QoS流级别的信息，即PDU会话包含的一个或多个QoS流的配置信息中包括这些信息，此种情形下，三个PDU会话内包含这些信息的QoS流有同步需求。示例性地，也可以通过5G服务质量标识(5G QoS identifier，5QI)的取值来约定哪些取值的5QI对应的QoS流属于同一个同步会话集，比如QoS流对应的QoS规则的5QI取值范围在64～71的所有QoS流属于同一个同步会话集。
此外，第一核心网设备接收到PDU会话建立请求消息，可以判断是否符合预设条件，若符合，则可以执行S602，否则，将不再执行S602。
比如，第一核心网设备接收到PDU会话建立请求消息后，可以判断辅助终端设备是否支持边缘计算，若辅助终端设备支持边缘计算，则可以执行S602，否则，将可以不执行S602。又比如，AMF网元在接收到PDU会话建立请求消息后，可以执行SMF网元选择，然后将PDU会话建立请求消息交给选中的SMF网元处理，SMF网元可以进一步从UDM网元获取终端设备的签约信息，以判断该终端设备是否被允许执行这些PDU会话(即M个PDU会话)。如果可以，则执行S602。AMF网元接收到PDU会话建立请求消息之后，核心网侧的处理过程可以参看3GPP技术标准(technical specification，TS)23.502版本16.4.0，本申请实施例对核心网的处理过程不做限制。
S602，第一核心网设备向接入网设备发送PDU会话资源建立请求消息；相应地，接入网设备接收PDU会话资源建立请求消息。
此处，PDU会话资源建立请求消息可以包括第一指示信息，有关第一指示信息的描述可以参见上文。可以理解地，PDU会话资源建立请求消息携带第一指示信息的方式可以与上文PDU会话建立请求消息携带第一指示信息的方式相同或者不相同，具体不做限定。
下面对PDU会话资源建立请求消息中携带第一指示信息的可能方式进行描述。此处，以第一指示信息包括M个PDU会话的关联标识为例，比如，PDU会话资源建立请求消息中包括PDU会话(比如会话1、会话2或会话3)对应的PDU会话资源建立请求项目(PDU Session Resource Setup Request Item)。PDU会话对应的PDU会话资源建立请求项目中可以包括PDU会话的标识(PDU Session ID)、PDU会话非接入层PDU(PDU Session NAS-PDU)、单网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)、 PDU会话资源建立请求传输(PDU Session Resource Setup Request Transfer)。本申请实施例中，PDU会话对应的PDU会话资源建立请求项目还可以包括关联标识。也就是说，PDU会话对应的PDU会话资源建立请求项目中可以新增一个信元(称为信元1)，该信元用于承载关联标识。
如下表1为PDU会话资源建立请求消息中携带第一指示信息的一个示例。
表1：PDU会话资源建立请求消息中携带第一指示信息的示例
>PDU Session Resource Setup Request Item
>>PDU Session ID
>>PDU Session NAS-PDU
>>S-NSSAI
>>PDU Session Resource Setup Request Transfer
>>Associated ID(信元1)
示例性地，PDU会话资源建立请求消息还可以包括第二指示信息和/或第三指示信息，有关第二指示信息和/或第三指示信息的描述可以参见上文。可以理解地，PDU会话资源建立请求消息携带第二指示信息和/或第三指示信息的方式可以与上文PDU会话建立请求消息携带第二指示信息和/或第三指示信息的方式相同或者不相同，具体不做限定。
下面对PDU会话资源建立请求消息携带第二指示信息和第三指示信息的可能方式进行描述。比如，PDU会话资源建立请求消息中包括PDU会话(比如会话1、会话2或会话3)对应的PDU会话资源建立请求项目，本申请实施例中，PDU会话对应的PDU会话资源建立请求项目还可以包括第二指示信息和第三指示信息。也就是说，PDU会话对应的PDU会话资源建立请求项目中可以新增两个信元(称为信元2和信元3)，信元2用于承载第二指示信息，信元3用于承载第三指示信息。
如下表2为PDU会话资源建立请求消息中携带第二指示信息和第三指示信息的一个示例。
表2：PDU会话资源建立请求消息中携带第二指示信息和第三指示信息的示例
>PDU Session Resource Setup Request Item
>>PDU Session ID
>>PDU Session NAS-PDU
>>S-NSSAI
>>PDU Session Resource Setup Request Transfer
>>MEC type(信元2)
>>Local Process Time(信元3)
需要说明的是，以会话1为例，若会话1与其他会话属于同步会话集，则会话1对应的会话资源建立请求项目中可以新增上述信元1、信元2、信元3；若会话1不与其他任何会话属于同步会话集，则会话1对应的会话资源建立请求项目中可以不再新增上述信元1、信元2、信元3。
S603，接入网设备根据第一指示信息对M个PDU会话进行接纳控制，并向第一核心 网设备发送PDU会话资源建立响应消息。
此处，接入网设备可以根据第一指示信息，对会话1、会话2和会话3采取同时接纳或同时拒绝的接纳控制；以及，接入网设备可以根据接纳结果向第一核心网设备发送PDU会话资源建立响应(PDU session establishment response)消息，该消息可以包含各个PDU会话是否被接入网设备接纳的信息。
本申请实施例中，接入网设备对M个PDU会话进行接纳控制的依据可以有多种。作为一种实现方式，接入网设备可以根据终端设备当前的服务小区、接入网设备的负载情况等信息来判断是否接纳能够M个PDU会话，进一步地，接入网设备还可以根据终端设备的能力和覆盖情况等信息来考虑是否可以通过配置更多服务小区或增加辅基站等方式来满足M个PDU会话的QoS要求，进而判断是否能够接纳M个PDU会话。此种情形下，接入网设备执行接纳控制过程可能会触发给终端设备配置辅载波和/或辅基站，其中，接入网设备给终端设备配置辅载波和/或辅基站的过程可以参照现有方案，此处不再赘述。
在一个示例中，接入网设备可以判断辅助终端设备是否支持边缘计算，若辅助终端设备支持边缘计算，则可以基于上述依据对M个PDU会话采取同时接纳或同时拒绝的接纳控制，若辅助终端设备不支持边缘计算，则可以拒绝M个PDU会话的建立请求或修改请求，或者也可以接纳会话1的建立请求或修改请求，而拒绝会话2和会话3的建立请求或修改请求，即回退到没有边缘计算的业务支持模式，具体不做限定。
S604，接入网设备向辅助终端设备发送RRC重配置(RRC reconfiguration)消息1。
此处，RRC重配置消息1可以携带一个或多个DRB的配置信息和一个或多个SLRB(sidelink radio bearer，边链路无线承载)的配置信息。其中，一个或多个DRB是会话2映射得到的，一个或多个SLRB是会话3映射得到的。具体如何映射，属于接入网设备的内部实现，比如可以根据会话中各QoS流的QoS要求进行QoS流到DRB或SLRB的映射，具体不做限定。
S605，辅助终端设备向终端设备发送RRC重配置边链路(RRC reconfiguration sidelink)消息。
此处，RRC重配置边链路消息可以携带一个或多个SLRB的配置信息，用于在终端设备和辅助终端设备之间建立D2D通信的无线承载。
S606，终端设备向辅助终端设备发送RRC重配置边链路完成(RRC reconfiguration sidelink complete)消息。
S607，辅助终端设备向接入网设备发送RRC重配置完成(RRC reconfiguration complete)消息1。
S608，接入网设备向终端设备发送RRC重配置消息2。
此处，RRC重配置消息2可以携带一个或多个DRB的配置信息，一个或多个DRB是会话1映射得到的。
进一步地，接入网设备在向终端设备发送RRC重配置消息2后，还可以向终端设备发送PDU会话建立接受(PDU session establishment accept)消息，该消息为第一核心网设备生成的NAS消息。
S609，终端设备向接入网设备发送RRC重配置完成消息2。
S610，接入网设备根据第一指示信息、第二指示信息和第三指示信息，对M个PDU会话中的数据进行调度。
此处，分别以场景1和场景2为例，描述接入网设备对M个PDU会话中的数据进行调度的具体实现。
(1)针对于场景1
接入网设备根据第一指示信息、第二指示信息和第三指示信息，可以确定会话2映射得到的一个或多个DRB与会话3映射得到的一个或多个SLRB有关联关系，以及可以确定辅助终端设备将对终端设备的下行业务数据进行边缘计算，以及边缘计算所需的时长。基于这些信息，接入网设备在调度所述DRB的下行数据在N时刻(即第一时间)发送时，调度所述SLRB的数据(辅助终端设备到终端设备的数据)在N+k时刻(即第一时间之后的第二时间)发送，以保证及时将边缘计算后的下行数据发送给终端设备。其中，k为辅助终端设备对终端设备的下行业务数据进行边缘计算所需的时长。
(2)针对于场景2
接入网设备根据第一指示信息、第二指示信息和第三指示信息，可以确定会话2映射得到的一个或多个DRB与会话3映射得到的一个或多个SLRB有关联关系，以及可以确定辅助终端设备将对终端设备的上行业务数据进行边缘计算，以及边缘计算所需的时长。基于这些信息，接入网设备在调度所述SLRB的数据(终端设备到辅助终端设备的数据)在N时刻发送时，调度所述DRB的上行数据在N+k时刻发送，以保证及时将边缘计算后的上行数据发送给应用服务器。其中，k为辅助终端设备对终端设备的上行业务数据进行边缘计算所需的时长。
本申请实施例中，辅助终端设备进行边缘计算所需的时长可以为一个相对保守的时长，以便于确保辅助终端设备能在该时长内完成边缘计算。
此外，在一个示例中，如果终端设备的业务图案(traffic pattern)有规律，比如数据突发按周期到达，则接入网设备还可以为终端设备和辅助终端设备配置相应的DRX周期，下面分别以场景1和场景2为例进行说明。
(1)针对于场景1
如果会话2的下行业务图案有规律，即会话2中的数据按照传输周期进行传输，则接入网设备可以向辅助终端设备发送第一配置信息，第一配置信息用于配置辅助终端设备接收会话2中数据的第一DRX。第一DRX周期与数据突发的周期(即会话2中数据的传输周期)相同，第一DRX的起始偏置(offset)也与数据突发起始偏置对齐。由于辅助终端设备进行边缘计算所需的时长为k，则接入网设备或辅助终端设备可以向终端设备发送第二配置信息，第二配置信息用于配置终端设备接收会话3中数据(即D2D通信)的第二DRX，第二DRX周期与第一DRX周期相同，但起始偏置为第一DRX起始偏置加k。如此，既可以使得终端设备避免连续监听从辅助终端设备发来的数据而耗电，又可以在辅助终端设备完成本地二次渲染后及时将数据发送给终端设备，保证VR业务的严格时延要求。
(2)针对于场景2
如果会话3的上行业务图案有规律，即会话3中的数据按照传输周期进行传输，则接入网设备可以向辅助终端设备发送第一配置信息，第一配置信息用于配置辅助终端设备接收会话3中数据的第一DRX周期。第一DRX周期与数据突发的周期(即会话3中数据的传输周期)相同，第一DRX周期的起始偏置(offset)也与数据突发起始偏置对齐。若往返时延为t，则接入网设备或辅助终端设备可以向终端设备发送第二配置信息，第二配置信息用于配置终端设备接收会话1中数据的第二DRX周期，第二DRX周期与第一DRX 周期相同，但起始偏置为第一DRX周期起始偏置加t。此处的往返时延可以为终端设备通过会话3发送第一数据的发送时间与终端设备通过会话1接收第二数据的接收时间之间的时间间隔，第二数据是根据第一数据得到的，比如，第一数据可以为监控摄像头采集的图像或经过监控摄像头初步处理的图像数据和/或计算上下文信息，第二数据可以为根据第一数据而得到的图像识别结果。
在又一个示例中，接入网设备可以向终端设备发送第五指示信息，第五指示信息指示往返时延；进而，终端设备可以根据往返时延进行省电等相关优化。该种方案可以适用于终端设备的业务图案不规律的情形，或者也可以适用于终端设备的业务图案有规律的情形，具体不做限定。在场景2中，往返时延可以为终端设备通过会话3发送第一数据的发送时间与终端设备通过会话1接收第二数据的接收时间之间的时间间隔，第二数据是根据第一数据得到的；比如，终端设备在发送第一数据后，可以进入休眠状态，并在休眠的时长到达阈值(该阈值是根据往返时延得到的，比如该阈值可以等于或略小于往返时延)后，可以从休眠状态醒来，以接收第二数据。在场景1中，往返时延为终端设备通过会话1发送第三数据的发送时间与终端设备通过会话3接收第四数据的接收时间之间的时间间隔，第四数据是根据第三数据得到的，比如第三数据可以为VR头盔采集的头盔移动或眼球姿势信息，第四数据可以为二次渲染后的VR媒体数据。
需要说明的是：上述S601至S610所描述的流程仅为一种可能的流程示例，具体实施中，可以在上述所描述的流程的基础上进行适应性调整。比如，接入网设备可以根据第一指示信息对M个PDU会话进行接纳控制；而不再根据第一指示信息、第二指示信息和第三指示信息对M个PDU会话中的数据进行调度，此种情形下，接入网设备可以参照现有技术对M个PDU会话中的数据进行调度。又比如，网络设备可以根据第一指示信息、第二指示信息和第三指示信息对M个PDU会话中的数据进行调度，而不再根据第一指示信息对M个PDU会话进行接纳控制，此种情形下，网络设备可以参照现有技术对M个PDU会话进行接纳控制。
根据上述实施例一中的内容可知，当通过辅助终端设备进行边缘计算时，接入网设备可以对会话1、会话2和会话3进行同时接纳或同时拒绝的接纳控制，以避免接纳部分会话而导致业务无法正常实现；以及，接入网设备还可以控制同步会话集的不同会话(比如会话2和会话3)中的数据按照一定顺序和时间关系协同传输，从而满足业务的时延要求。
实施例二
在实施例二中，将以图4a所示意的情形为例，描述一种可能的实现。
本申请实施例中，考虑到终端设备可能需要进行有边缘计算和无边缘计算之间的切换，比如以终端设备为VR头盔为例，当VR头盔没有外挂强计算能力设备时，需要由辅助终端设备进行二次渲染，此种情形下，VR头盔可以选择有边缘计算，即M个会话具有关联关系；而当VR头盔有外挂强计算能力设备时，则可以不再需要由辅助终端设备进行二次渲染，此种情形下，VR头盔可以选择无边缘计算，即M个会话不再具有关联关系。在其它可能的示例中，VR头盔也可以根据其它可能的原因(比如是否连接电源)进行有边缘计算和无边缘计算之间的切换。
上述实施例一中，描述了M个会话具有关联关系的相关实现，在实施例二中，将描述由M个会话具有关联关系切换至M个会话不再具有关联关系的可能的实现。需要说明的 是，实施例二可以与实施例一结合实施，或者也可以分别单独实施。
图7为本申请实施例二提供的通信方法所对应的流程示意图，如图7所示，该方法包括S701至S708，本申请实施例对S701至S708的执行顺序不作限制。
S701，终端设备向第一核心网设备发送第二请求消息；相应地，第一核心网设备可以接收第二请求消息。
此处，第二请求消息可以为PDU会话修改请求消息，PDU会话修改请求消息可以用于修改会话1，比如该消息可以携带会话1的信息。在一个示例中，PDU会话资源修改请求消息还可以携带第七指示信息，第七指示信息指示会话1与M个会话中的其它会话(即会话2、会话3)不再关联。
需要说明的，在其它可能的示例中，也可以通过隐式的方式来指示会话1与M个会话中的其它会话(即会话2、会话3)不再关联，比如，PDU会话资源修改请求消息中没有携带第一指示信息(可选地，也没有携带第二指示信息和第三指示信息)，则可以理解为隐式指示会话1与M个会话中的其它会话(即会话2、会话3)不再关联。
第一核心网设备在接收到该消息后，可以根据第七指示信息获知该消息要发起的是从有边缘计算到没有边缘计算的切换，进而可以执行S702。其中，第一核心网设备接收到该消息之后核心网侧的处理过程可以参看3GPP TS 23.502版本16.4.0，具体不做限制。
S702，第一核心网设备向接入网设备发送PDU会话资源释放命令消息；相应地，接入网设备可以接收PDU会话资源释放命令消息。
此处，PDU会话资源释放命令消息可以用于释放会话2和会话3，比如PDU会话资源释放命令消息中可以包括会话2和会话3的信息。在一个示例中，PDU会话资源释放命令消息中可以包括第六指示信息，第六指示信息指示M个会话不再关联。需要说明的是，在其它可能的示例中，也可以通过隐式的方式来指示M个会话不再关联，具体不做限定。
S703，接入网设备根据PDU会话资源释放命令消息释放会话2和会话3，并向第一核心网设备发送PDU会话资源释放响应消息。
S704，接入网设备向辅助终端设备发送RRC重配置消息。
此处，RRC重配置消息可以携带会话2和会话3对应的DRB和SLRB被释放的指示信息。进一步地，接入网设备在向辅助终端设备发送RRC重配置消息后，还可以向终端设备发送PDU会话修改接受(PDU session modification accept)消息，该消息为SMF网元生成的NAS消息。
S705，辅助终端设备向终端设备发送RRC重配置边链路消息。
此处，RRC重配置边链路消息可以携带会话3对应的SLRB被释放的指示信息，进而终端设备可以释放会话3对应的一个或多个SLRB相关的配置和资源。
S706，终端设备向辅助终端设备发送RRC重配置边链路完成消息。
S707，辅助终端设备向接入网设备发送RRC重配置完成消息。
S708，接入网设备取消根据第一指示信息、第二指示信息和第三指示信息对M个PDU会话中的数据进行调度。
如此，在S708之后，终端设备的业务将由有边缘计算切换到无边缘计算。如果后续又需要进行边缘计算，则终端设备可以触发PDU会话修改或PDU会话建立过程，比如上述实施例一所示意的流程，以切换到有边缘计算。
本申请实施例中，是由终端设备触发由有边缘计算切换到无边缘计算的，实际应用中 也可以由本地设备触发，比如本地设备在计算资源不足或存储资源不足或传输资源不足或已经完成边缘计算等情况下，向终端设备或接入网设备或核心网设备发送边缘计算释放请求。
采用上述方法，终端设备可以从有边缘计算切换到无边缘计算，或者从无边缘计算切换到有边缘计算，从而能够保证终端设备可以在不同工作方式(比如有无连接电源、有无外挂强计算能力设备等)下自由地选择相应模式，同时保证业务体验和用户体验。
实施例三
在实施例三中，将以图4b所示意的情形为例，描述一种可能的实现。图4b中本地设备可以包括接入网设备和EAS，为便于清楚示意各实施例之间的区别，在该实施例中，将本地设备直接称为接入网设备。
图8为本申请实施例三提供的通信方法所对应的流程示意图，如图8所示，该方法包括S800至S806，本申请实施例对S800至S806的执行顺序不作限制。
S800，第一核心网设备获取接入网设备的能力信息，接入网设备的能力信息用于指示接入网设备是否支持边缘计算。
在一个示例中，接入网设备可以向第一核心网设备上报能力信息。比如，接入网设备可以在N2接口建立时，上报能力信息。
S801，终端设备向第一核心网设备发送第一请求消息；相应地，第一核心网设备可以接收第一请求消息。其中，该实施例中以第一请求消息为PDU会话建立请求消息为例。
此处，PDU会话建立请求消息可以包括第一指示信息，还可以包括第二指示信息和/或第三指示信息。
S802，第一核心网设备向接入网设备发送PDU会话资源建立请求消息；相应地，接入网设备接收PDU会话资源建立请求消息。
此处，PDU会话资源建立请求消息可以包括第一指示信息，还可以包括第二指示信息和/或第三指示信息。
上述S801和S802的相关实现可以参见实施例一中的S601和S602。
S803，接入网设备根据第一指示信息对M个PDU会话进行接纳控制，并向第一核心网设备发送PDU会话资源建立响应消息。
此处，接入网设备可以根据第一指示信息，对会话1和会话3采取同时接纳或同时拒绝的接纳控制。这里，假定接入网设备不需要对会话2进行接纳控制，因为会话2不涉及无线资源使用，而无线资源通常是移动网络中的资源瓶颈。
S804，接入网设备向终端设备发送RRC重配置消息。
S805，终端设备向接入网设备发送RRC重配置完成消息。
上述S804和S805的相关实现可以参见实施例一中的S608和S609。
S806，接入网设备根据第一指示信息、第二指示信息和第三指示信息对M个PDU会话中的数据进行调度。
此处，分别以场景1和场景2为例，描述接入网设备对M个PDU会话中的数据进行调度的具体实现。
(1)针对于场景1
接入网设备根据第一指示信息、第二指示信息和第三指示信息，可以确定会话2和会话3有关联关系，以及可以确定将会对会话2的下行业务数据进行边缘计算，以及边缘计算所需的时长。基于这些信息，接入网设备可以在N时刻接收到会话2的下行数据时，调度会话3映射的DRB的下行数据(接入网设备到终端设备的数据)在N+k时刻发送，以保证及时将边缘计算后的下行数据发送给终端设备。其中，k为接入网设备对终端设备的下行业务数据进行边缘计算所需的时长。
(2)针对于场景2
接入网设备根据第一指示信息、第二指示信息和第三指示信息，可以确定会话2和会话3有关联关系，以及可以确定将会对会话3的上行业务数据进行边缘计算，以及边缘计算所需的时长。基于这些信息，接入网设备可以在N时刻接收到会话3的上行数据时，调度会话2的数据(接入网设备到应用服务器的数据)在N+k时刻发送，以保证及时将边缘计算后的数据发送给应用服务器。其中，k为接入网设备对终端设备的上行业务数据进行边缘计算所需的时长。
此外，在一个示例中，接入网设备可以向终端设备发送第五指示信息，第五指示信息指示往返时延；具体可以参见实施例一中的描述。
在又一个示例中，如果终端设备的业务图案有规律，比如数据突发按周期到达，则接入网设备还可以为终端设备配置相应的DRX周期，下面分别以场景1和场景2为例进行说明。
(1)针对于场景1
如果会话2的下行业务图案有规律，即会话2中的数据按照传输周期进行传输，则接入网设备可以向终端设备发送配置信息，配置信息用于配置终端设备接收会话3中数据的DRX周期，该DRX周期与会话2中数据的传输周期相同，但起始偏置为会话2中数据的起始偏置加k。如此，既可以使得终端设备避免连续监听从接入网设备发来的数据而耗电，又可以在接入网设备完成本地二次渲染后及时将数据发送给终端设备，保证VR业务的严格时延要求。
(2)针对于场景2
如果会话3的下行业务图案有规律，即会话3中的数据按照传输周期进行传输，则接入网设备可以向终端设备发送配置信息，配置信息用于配置终端设备接收会话1中数据的DRX周期，该DRX周期与会话3中数据的传输周期相同，但起始偏置为会话3中数据的起始偏置加往返时延(t)。此处的往返时延可以为终端设备通过会话3发送第一数据的发送时间与终端设备通过会话1接收第二数据的接收时间之间的时间间隔，第二数据是根据第一数据得到的。
根据上述实施例三中的内容可知，当通过接入网设备进行边缘计算时，接入网设备可以对会话1和会话3进行同时接纳或同时拒绝的接纳控制，以避免接纳部分会话而导致业务无法正常实现；以及，接入网设备还可以控制同步会话集的不同会话(比如会话2和会话3)中的数据按照一定顺序和时间关系协同传输，从而满足业务的时延要求。
实施例四
在实施例四中，将以图4b所示意的情形为例，描述一种可能的实现。
上述实施例三中，描述了M个会话具有关联关系的相关实现，在实施例四中，将描述 由M个会话具有关联关系切换至M个会话不再具有关联关系的可能的实现。需要说明的是，实施例四可以与实施例三结合实施，或者也可以分别单独实施。
图9为本申请实施例四提供的通信方法所对应的流程示意图，如图9所示，该方法包括S901至S906，本申请实施例对S901至S906的执行顺序不作限制。
S901，终端设备向第一核心网设备发送第二请求消息；相应地，第一核心网设备可以接收第二请求消息。
S902，第一核心网设备向接入网设备发送PDU会话资源释放命令消息；相应地，第一接入网设备可以接收PDU会话资源释放命令消息。
S903，接入网设备向第一核心网设备发送PDU会话资源释放响应消息。
S904，接入网设备向终端设备发送RRC重配置消息。
此处，RRC重配置消息可以携带会话3对应的DRB被释放的指示信息。进一步地，接入网设备在向终端设备发送该消息后，还可以向终端设备发送PDU会话修改接受消息，该消息为SMF网元生成的NAS消息。
S905，终端设备向接入网设备发送RRC重配置完成消息。
S906，接入网设备取消根据第一指示信息、第二指示信息和第三指示信息对M个PDU会话中的数据进行调度。
如此，在S906之后，终端设备的业务将由有边缘计算切换到无边缘计算。如果后续又需要进行边缘计算，则终端设备可以触发PDU会话修改或PDU会话建立过程，比如上述实施例三所示意的流程，以切换到有边缘计算。
采用上述方法，终端设备可以从有边缘计算切换到无边缘计算，或者从无边缘计算切换到有边缘计算，从而能够保证终端设备可以在不同工作方式(比如有无连接电源、有无外挂强计算能力设备等)下自由地选择相应模式，同时保证业务体验和用户体验。
实施例五
在实施例五中，将以图4c所示意的情形为例，描述一种可能的实现。图4c中本地设备可以包括IAB节点和EAS，为便于清楚示意各实施例之间的区别，在该实施例中，将本地设备直接称为IAB节点。
图10为本申请实施例五提供的通信方法所对应的流程示意图，如图10所示，该方法包括S1000至S1010，本申请实施例对S1000至S1010的执行顺序不作限制。
S1000，接入网设备和/或第一核心网设备获取IAB节点的能力信息，IAB节点的能力信息用于指示IAB节点是否支持边缘计算。
在一个示例中，IAB节点可以向接入网设备和/或第一核心网设备发送能力信息。比如，IAB节点在与接入网设备完成RRC连接建立之后，或注册过程中，或注册完成之后，向接入网设备和/或第一核心网设备上报能力信息。
在又一个示例中，在IAB节点的注册过程中或注册完成之后，第一核心网设备也可以从UDM网元获取IAB节点的能力信息。
S1001，终端设备向第一核心网设备发送第一请求消息；相应地，第一核心网设备可以接收第一请求消息。其中，该实施例中以第一请求消息为PDU会话建立请求消息为例。
此处，PDU会话建立请求消息可以包括第一指示信息，还可以包括第二指示信息和/或第三指示信息。
S1002，第一核心网设备向接入网设备发送PDU会话资源建立请求消息；相应地，接入网设备接收PDU会话资源建立请求消息。
此处，PDU会话资源建立请求消息可以包括第一指示信息，还可以包括第二指示信息和/或第三指示信息。
S1003，接入网设备根据第一指示信息对M个PDU会话进行接纳控制，并向第一核心网设备发送PDU会话资源建立响应消息。
上述S1001至S1003的相关实现可以参见实施例一中的S601至S603。
S1004，接入网设备向IAB节点发送终端设备的上下文修改请求(UE context modification request)消息。
此处，上下文修改请求消息可以包括会话1映射得到的DRB的配置信息，以便IAB节点进行这些DRB相关的配置，比如IAB节点与终端设备之间的RLC协议层等相关的配置。
S1005，IAB节点向接入网设备发送终端设备的上下文修改响应(UE context modification response)消息。
S1006，接入网设备向IAB节点发送RRC重配置消息1。
此处，RRC重配置消息可以包括会话2和会话3映射得到的DRB的配置信息和第四指示信息，第四指示信息指示会话2对应的DRB与会话3对应的DRB具有关联关系。比如，第四指示信息可以包括一对或多对DRB之间的关联信息(会话2映射得到的一个DRB与会话3映射得到的一个DRB构成一对DRB)。可选地，RRC重配置消息还可以包括第二指示信息和/或第三指示信息。
S1007，IAB节点向接入网设备发送RRC重配置完成消息1。
作为一种替代方案，接入网设备也可以分别向IAB节点发送会话2映射得到的DRB的配置信息、会话3映射得到的DRB的配置信息，即将S1006和S1007的配置过程拆分成两个配置过程，具体实现不做限定。
S1008，接入网设备向终端设备发送RRC重配置消息2。
此处，RRC重配置消息可以包括会话1和会话3映射得到的DRB相关的配置信息。
S1009，终端设备向接入网设备发送RRC重配置完成消息2。
S1010，IAB节点根据第一指示信息、第二指示信息和第三指示信息对M个PDU会话中的数据进行调度。
此处，分别以场景1和场景2为例，描述IAB节点对M个PDU会话中的数据进行调度的具体实现。
(1)针对于场景1
IAB节点根据第一指示信息、第二指示信息和第三指示信息，可以确定会话2映射得到的一个或多个DRB与会话3映射得到的一个或多个DRB有关联关系，以及可以确定IAB节点将对终端设备的下行业务数据进行边缘计算，以及边缘计算所需的时长。基于这些信息，如果IAB节点在N时刻接收到会话2映射得到的DRB的数据，则调度会话3映射得到的DRB的数据(IAB节点到终端设备的数据)在N+k时刻发送，以保证及时将边缘计算后的下行数据发送给终端设备。其中，k为IAB节点对终端设备的下行业务数据进行边缘计算所需的时长。
(2)针对于场景2
IAB节点根据第一指示信息、第二指示信息和第三指示信息，可以确定会话2映射得到的一个或多个DRB与会话3映射得到的一个或多个DRB有关联关系，以及可以确定IAB节点将对终端设备的上行业务数据进行边缘计算，以及边缘计算所需的时长。基于这些信息，如果IAB节点在N时刻接收到会话3映射得到的DRB的数据，则调度会话2映射得到的DRB的数据(IAB节点到应用服务器的数据)在N+k时刻发送，以保证及时将边缘计算后的上行数据发送给应用服务器。其中，k为IAB节点对终端设备的上行业务数据进行边缘计算所需的时长。
本申请实施例中，IAB节点进行边缘计算所需的时长可以为一个相对保守的时长，以便于确保IAB节点能在该时长内完成边缘计算。
此外，在一个示例中，如果终端设备的业务图案(traffic pattern)有规律，比如数据突发按周期到达，则接入网设备还可以为终端设备和IAB节点配置相应的DRX周期，下面分别以场景1和场景2为例进行说明。
(1)针对于场景1
如果会话2的下行业务图案有规律，即会话2中的数据按照传输周期进行传输，则接入网设备可以向IAB节点发送第一配置信息，第一配置信息用于配置IAB节点接收会话2中数据的第一DRX。第一DRX周期与数据突发的周期(即会话2中数据的传输周期)相同，第一DRX的起始偏置也与数据突发起始偏置对齐。由于IAB节点进行边缘计算所需的时长为k，则接入网设备可以通过IAB节点向终端设备发送第二配置信息，第二配置信息用于配置终端设备接收会话3中数据的第二DRX，第二DRX周期与第一DRX周期相同，但起始偏置为第一DRX起始偏置加k。如此，既可以使得终端设备避免连续监听从IAB节点发来的数据而耗电，又可以在IAB节点完成本地二次渲染后及时将数据发送给终端设备，保证VR业务的严格时延要求。
(2)针对于场景2
如果会话3的上行业务图案有规律，即会话3中的数据按照传输周期进行传输，则接入网设备可以向IAB节点发送第一配置信息，第一配置信息用于配置IAB节点接收会话3中数据的第一DRX周期。第一DRX周期与数据突发的周期(即会话3中数据的传输周期)相同，第一DRX周期的起始偏置也与数据突发起始偏置对齐。若往返时延为t，则接入网设备可以通过IAB节点可以向终端设备发送第二配置信息，第二配置信息用于配置终端设备接收会话1中数据的第二DRX周期，第二DRX周期与第一DRX周期相同，但起始偏置为第一DRX周期起始偏置加t。此处的往返时延可以为终端设备通过会话3发送第一数据的发送时间与终端设备通过会话1接收第二数据的接收时间之间的时间间隔，第二数据是根据第一数据得到的。
在又一个示例中，接入网设备可以向终端设备发送第五指示信息，第五指示信息指示往返时延；进而，终端设备可以根据往返时延进行省电等相关优化。比如，第五指示信息可以承载于上述S1008中的RRC重配置消息2。
需要说明的是：(1)上述S1001至S1010所描述的流程仅为一种可能的流程示例，具体实施中，可以在上述所描述的流程的基础上进行适应性调整。比如，接入网设备可以根据第一指示信息对M个PDU会话进行接纳控制；而IAB节点不根据第一指示信息、第二指示信息和第三指示信息对M个PDU会话中的数据进行调度，此种情形下，IAB节点可以参照现有技术对M个PDU会话中的数据进行调度。又比如，IAB节点可以根据第一指 示信息、第二指示信息和第三指示信息对M个PDU会话中的数据进行调度，而接入网设备不再根据第一指示信息对M个PDU会话进行接纳控制，此种情形下，接入网设备可以参照现有技术对M个PDU会话进行接纳控制。
(2)本申请实施例提供的方法既可以适用于一级IAB节点的场景，也适用于存在多级IAB节点的场景。针对多级IAB节点的场景，本申请实施例描述的IAB节点可以为任意一级IAB节点。多级IAB节点可以参照本申请实施例的描述进行适应性扩展，具体不再赘述。
根据上述实施例五中的内容可知，当通过IAB节点进行边缘计算时，接入网设备可以对会话1、会话2和会话3进行同时接纳或同时拒绝的接纳控制，以避免接纳部分会话而导致业务无法正常实现；以及，IAB节点可以控制同步会话集的不同会话(比如会话2和会话3)中的数据按照一定顺序和时间关系协同传输，从而满足业务的时延要求。
实施例六
在实施例六中，将以图4c所示意的情形为例，描述一种可能的实现。
上述实施例五中，描述了M个会话具有关联关系的相关实现，在实施例四中，将描述由M个会话具有关联关系切换至M个会话不再具有关联关系的可能的实现。需要说明的是，实施例六可以与实施例五结合实施，或者也可以分别单独实施。
图11为本申请实施例六提供的通信方法所对应的流程示意图，如图11所示，该方法包括S1101至S1108，本申请实施例对S1101至S1108的执行顺序不作限制。
S1101，终端设备向第一核心网设备发送第二请求消息；相应地，第一核心网设备可以接收第二请求消息。
S1102，第一核心网设备向接入网设备发送PDU会话资源释放命令消息；相应地，第一接入网设备可以接收PDU会话资源释放命令消息。
S1103，接入网设备向第一核心网设备发送PDU会话资源释放响应消息。
S1104，接入网设备向IAB节点发送RRC重配置消息1。
此处，RRC重配置消息可以携带会话2和会话3对应的DRB被释放的指示信息。
S1105，IAB节点释放会话2和会话3对应的DRB，并向接入网设备发送RRC重配置完成消息1。
S1106，接入网设备向终端设备发送RRC重配置消息2。
此处，RRC重配置消息可以携带会话3对应的DRB被释放的指示信息，进而终端设备可以释放会话3对应的一个或多个DRB相关的配置和资源。
S1107，终端设备向接入网设备发送RRC重配置完成消息2。
S1108，IAB节点取消根据第一指示信息、第二指示信息和第三指示信息对M个PDU会话中的数据进行调度。
在S1108之后，终端设备的业务将由有边缘计算切换到无边缘计算。如果后续又需要进行边缘计算，则终端设备可以触发PDU会话修改或PDU会话建立过程，比如上述实施例五所示意的流程，以切换到有边缘计算。
采用上述方法，终端设备可以从有边缘计算切换到无边缘计算，或者从无边缘计算切换到有边缘计算，从而能够保证终端设备可以在不同工作方式(比如有无连接电源、有无外挂强计算能力设备等)下自由地选择相应模式，同时保证业务体验和用户体验。
针对于上述内容，需要说明的是：
(1)本申请实施例提供的通信方法还可以适用于切换场景中，比如终端设备从第一接入网设备的小区切换到第二接入网设备的小区，第一接入网设备可以为源接入网设备，第二接入网设备可以为目标接入网设备，源接入网设备和目标接入网设备可以为同一AMF网元下的接入网设备，或者也可以为不同AMF网元下的接入网设备。
其中，源接入网设备可以从核心网设备或终端设备接收第一指示信息，可选地还可以接收第二指示信息和第三指示信息，并根据接收到的第一指示信息、第二指示信息和第三指示信息执行相应操作，比如上述实施例一、实施例三、实施例五中的接入网设备可以理解为终端设备的源网络设备。当终端设备发生切换时，源接入网设备可以向目标接入网设备发送第一指示信息，可选地还可以发送第二指示信息和第三指示信息，比如第一指示信息、第二指示信息和第三指示信息可以承载于切换命令中；进而目标接入网设备可以根据接收到的第一指示信息、第二指示信息和第三指示信息执行相应操作，具体可以参照源网络设备所执行的操作，比如目标接入网设备可以根据第一指示信息对M个PDU会话采取同时接纳或同时拒绝的接纳控制。在其它可能的场景中，目标接入网设备也可以从核心网设备接收第一指示信息，可选地还可以接收第二指示信息和第三指示信息，具体不做限定。
(2)在图4a所示意的场景中，是以终端设备和辅助终端设备接入同一接入网设备为例进行描述的，具体实施中，终端设备和辅助终端设备也可以分别接入不同的接入网设备。比如，终端设备接入接入网设备1，辅助终端设备接入接入网设备2，此种情形下还可能涉及接入网设备1和接入网设备2之间的交互，具体实现可以适应性参照终端设备和辅助终端设备接入同一接入网设备的描述。类似地，在图4b所示意的场景中，也是以一个接入网设备为例进行描述，具体实施中，终端设备可以接入接入网设备1，而本地设备包括接入网设备2；在图4c所示意的场景中，也是以一个接入网设备为例进行描述，具体实施中，终端设备可以接入接入网设备1，IAB节点可以接入接入网设备2。
(3)上述实施例所描述的各个流程图的操作编号仅为执行流程的一种示例，并不构成对操作执行的先后顺序的限制，本申请实施例中相互之间没有时序依赖关系的操作之间没有严格的执行顺序。此外，各个流程图中所示意的操作并非全部是必须执行的操作，可以根据实际需要在各个流程图的基础上增添或者删除部分操作。
(4)上述侧重描述了实施例一至实施例六中不同实施例之间的差异之处，除差异之处的其它内容，实施例一至实施例六之间可以相互参照。
(5)上述实施例一至实施例六中采用了一些5G通信系统中的消息，但在具体实施中，可能使用不同的消息或消息名称，本申请实施例对此不做限制。
上述主要从设备交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，为了实现上述功能，网络设备、核心网设备或终端设备可以包括执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请的实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对网络设备、核心网设备或终端设备进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
在采用集成的单元的情况下，图12示出了本申请实施例中所涉及的装置的可能的示例性框图。如图12所示，装置1200可以包括：处理单元1202和通信单元1203。处理单元1202用于对装置1200的动作进行控制管理。通信单元1203用于支持装置1200与其他设备的通信。可选地，通信单元1203也称为收发单元，可以包括接收单元和/或发送单元，分别用于执行接收和发送操作。装置1200还可以包括存储单元1201，用于存储装置1200的程序代码和/或数据。
该装置1200可以为上述实施例中的接入网设备、或者还可以为设置在接入网设备中的芯片。处理单元1202可以支持装置1200执行上文中各方法示例中接入网设备的动作。或者，处理单元1202主要执行方法示例中的接入网设备的内部动作，通信单元1203可以支持装置1200与其它设备之间的通信。
具体地，在一个实施例中，通信单元1203用于：接收第一指示信息，第一指示信息指示M个会话具有关联关系，M为大于1的整数；处理单元1202用于：根据第一指示信息，对M个会话进行处理。
在一种可能的设计中，处理单元1202具体用于：接纳M个会话中至少两个会话的建立请求或者拒绝M个会话中至少两个会话的建立请求；或者，接纳M个会话中至少两个会话的修改请求或者拒绝M个会话中至少两个会话的修改请求。
在一种可能的设计中，M个会话包括终端设备与应用服务器之间的第一会话、所述应用服务器与本地设备之间的第二会话、所述本地设备与终端设备之间的第三会话；其中，终端设备与第一接入网设备建立有无线资源控制RRC连接。
在一种可能的设计中，通信单元1203还用于：接收第二指示信息和/或第三指示信息；其中，第二指示信息指示所述本地设备对接收到的第二会话或第三会话中的数据进行边缘计算，第三指示信息指示所述本地设备进行本地边缘计算所需的时长。
在一种可能的设计中，处理单元1202具体用于：确定本地设备对接收到的第二会话中的数据进行边缘计算；在第一时间调度第二会话中的数据，以及在第一时间之后的第二时间调度第三会话中的数据；其中，第一时间和第二时间之间的时间间隔是根据本地设备进行边缘计算所需的时长得到的。
在一种可能的设计中，处理单元1202具体用于：确定本地设备对接收到的第三会话中的数据进行边缘计算；在第一时间调度第三会话中的数据，以及在第一时间之后的第二时间调度第二会话中的数据；其中，第一时间和第二时间之间的时间间隔是根据本地设备进行边缘计算所需的时长得到的。
在一种可能的设计中，本地设备包括辅助终端设备，或者，本地设备包括接入网设备。
在一种可能的设计中，通信单元1203还用于：向本地设备发送第四指示信息，第四指示信息指示第二会话对应的DRB与第三会话对应的DRB具有关联关系。
在一种可能的设计中，通信单元1203还用于：向本地设备发送第二指示信息和/或第三指示信息，其中，第二指示信息指示本地设备对接收到的第二会话或第三会话中的数据进行边缘计算，第三指示信息指示本地设备进行本地边缘计算所需的时长。
在一种可能的设计中，本地设备包括无线回传设备。
在一种可能的设计中，通信单元1203还用于：向终端设备发送第五指示信息，第五指示信息指示往返时延；其中，所述往返时延为终端设备通过第三会话发送第一数据的发送时间与终端设备通过第一会话接收第二数据的接收时间之间的时间间隔，第二数据是根据第一数据得到的；或者，所述往返时延为终端设备通过第一会话发送第三数据的发送时间与终端设备通过第三会话接收第四数据的接收时间之间的时间间隔，第四数据是根据第三数据得到的。
在一种可能的设计中，通信单元1203具体用于：从核心网设备或者第二接入网设备接收第一指示信息；其中，第二接入网设备为终端设备的源接入网设备，第一接入网设备为终端设备的目标接入网设备。
在一种可能的设计中，第一指示信息包括M个会话分别对应的M个关联信息，和/或，本地设备的标识信息；其中，M个关联信息相同。
在一种可能的设计中，M个会话包括第一会话，第一会话对应的关联信息包括第一会话的类型信息和/或第一会话的关联标识；其中，第一会话的类型信息用于指示第一会话的类型为分离渲染或分段计算。
在一种可能的设计中，通信单元1203还用于：接收第六指示信息，第六指示信息指示M个会话不再关联；以及根据第六指示信息，释放第二会话的资源和第三会话的资源。
该装置1200可以为上述实施例中的核心网设备、或者还可以为设置在核心网设备中的芯片。处理单元1202可以支持装置1200执行上文中各方法示例中核心网设备的动作。或者，处理单元1202主要执行方法示例中的核心网设备的内部动作，通信单元1203可以支持装置1200与其它设备之间的通信。
具体地，在一个实施例中，通信单元1203用于：获取第一指示信息，第一指示信息指示M个会话具有关联关系，M为大于1的整数；以及，向接入网设备发送第一指示信息。
在一种可能的设计中，M个会话包括终端设备与应用服务器之间的第一会话、所述应用服务器与本地设备之间的第二会话、本地设备与终端设备之间的第三会话；其中，终端设备与所述接入网设备建立有RRC连接。
在一种可能的设计中，通信单元1203还用于：向所述接入网设备发送第二指示信息和/或第三指示信息；其中，第二指示信息指示本地设备对接收到的第二会话或第三会话中的数据进行边缘计算，第三指示信息指示本地设备进行本地边缘计算所需的时长。
在一种可能的设计中，通信单元1203具体用于：从终端设备获取第一指示信息；或者，从第二核心网设备获取第一指示信息。
在一种可能的设计中，通信单元1203具体用于：接收来自终端设备的第一请求消息，第一请求消息用于请求建立或修改M个会话或者M个会话中的第一会话，所述请求消息包括第一指示信息。
在一种可能的设计中，通信单元1203还用于：向所述接入网设备发送第六指示信息，第六指示信息指示M个会话不再关联。
在一种可能的设计中，通信单元1203还用于：接收来自终端设备的第二请求消息，第二请求消息用于请求修改M个会话中的第一会话，第二请求消息包括第七指示信息，第七指示信息指示第一会话与M个会话中的其它会话不再关联；根据第二请求消息，确定第 六指示信息。
应理解以上装置中单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且装置中的单元可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元以软件通过处理元件调用的形式实现，部分单元以硬件的形式实现。例如，各个单元可以为单独设立的处理元件，也可以集成在装置的某一个芯片中实现，此外，也可以以程序的形式存储于存储器中，由装置的某一个处理元件调用并执行该单元的功能。此外这些单元全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件又可以成为处理器，可以是一种具有信号的处理能力的集成电路。在实现过程中，上述方法的各操作或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
在一个例子中，以上任一装置中的单元可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(application specific integrated circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)，或这些集成电路形式中至少两种的组合。再如，当装置中的单元可以通过处理元件调度程序的形式实现时，该处理元件可以是处理器，比如通用中央处理器(central processing unit，CPU)，或其它可以调用程序的处理器。再如，这些单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
以上用于接收的单元是一种该装置的接口电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该接收单元是该芯片用于从其它芯片或装置接收信号的接口电路。以上用于发送的单元是一种该装置的接口电路，用于向其它装置发送信号。例如，当该装置以芯片的方式实现时，该发送单元是该芯片用于向其它芯片或装置发送信号的接口电路。
参见图13，为本申请实施例提供的一种接入网设备的结构示意图，该接入网设备(或基站)可应用于如图1所示的系统架构中，执行上述方法实施例中接入网设备的功能。接入网设备130可包括一个或多个DU 1301和一个或多个CU 1302。所述DU 1301可以包括至少一个天线13011，至少一个射频单元13012，至少一个处理器13013和至少一个存储器13014。所述DU 1301部分主要用于射频信号的收发以及射频信号与基带信号的转换，以及部分基带处理。CU1302可以包括至少一个处理器13022和至少一个存储器13021。
所述CU 1302部分主要用于进行基带处理，对接入网设备进行控制等。所述DU 1301与CU 1302可以是物理上设置在一起，也可以物理上分离设置的，即分布式基站。所述CU 1302为接入网设备的控制中心，也可以称为处理单元，主要用于完成基带处理功能。例如所述CU 1302可以用于控制接入网设备执行上述方法实施例中关于接入网设备的操作流程。
此外，可选的，接入网设备130可以包括一个或多个射频单元，一个或多个DU和一个或多个CU。其中，DU可以包括至少一个处理器13013和至少一个存储器13014，射频单元可以包括至少一个天线13011和至少一个射频单元13012，CU可以包括至少一个处理器13022和至少一个存储器13021。
在一个实例中，所述CU1302可以由一个或多个单板构成，多个单板可以共同支持单一接入指示的无线接入网(如5G网)，也可以分别支持不同接入制式的无线接入网(如 LTE网，5G网或其他网)。所述存储器13021和处理器13022可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。所述DU1301可以由一个或多个单板构成，多个单板可以共同支持单一接入指示的无线接入网(如5G网)，也可以分别支持不同接入制式的无线接入网(如LTE网，5G网或其他网)。所述存储器13014和处理器13013可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。
图13所示的接入网设备能够实现图5至图11所示意的方法实施例中涉及接入网设备的各个过程。图13所示的接入网设备中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详述描述。
参考图14，为本申请实施例提供的一种核心网设备的结构示意图。其可以为以上实施例中的SMF网元或AMF网元，用于实现以上实施例中SMF网元或AMF网元的操作。
如图14所示，核心网设备1400可包括处理器1401、存储器1402以及接口电路1403。处理器1401可用于对通信协议以及通信数据进行处理，以及对通信装置进行控制。存储器1402可用于存储程序和数据，处理器1401可基于该程序执行本申请实施例中由AMF网元或SMF网元执行的方法。接口电路1403可用于核心网设备1400与其他设备进行通信，该通信可以为有线通信或无线通信，该接口电路例如可以是服务化通信接口。
以上存储器1402也可以是外接于核心网设备1400的，此时核心网设备1400可包括接口电路1403以及处理器1401。以上接口电路1403也可以是外接于核心网设备1400的，此时核心网设备1400可包括存储器1402以及处理器1401。当接口电路1403以及存储器1402均外接于核心网设备1400时，通信装置1400可包括处理器1401。
图14所示的核心网设备能够实现图5至图11所示意的方法实施例中涉及核心网设备的各个过程。图14所示的核心网设备中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详述描述。
本申请实施例中的术语“系统”和“网络”可被互换使用。“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A、同时存在A和B、单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如“A，B和C中的至少一个”包括A，B，C，AB，AC，BC或ABC。以及，除非有特别说明，本申请实施例提及“第一”、“第二”等序数词是用于对多个对象进行区分，不用于限定多个对象的顺序、时序、优先级或者重要程度。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程 序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (31)

  1. 一种通信方法，其特征在于，所述方法应用于第一接入网设备或者所述第一接入网设备中的芯片，所述方法包括：
    接收第一指示信息，所述第一指示信息指示M个会话具有关联关系，M为大于1的整数；
    根据所述第一指示信息，对所述M个会话进行处理。
  2. 根据权利要求1所述的方法，其特征在于，对所述M个会话进行处理，包括：
    接纳所述M个会话中至少两个会话的建立请求或者拒绝所述M个会话中至少两个会话的建立请求；或者，
    接纳所述M个会话中至少两个会话的修改请求或者拒绝所述M个会话中至少两个会话的修改请求。
  3. 根据权利要求1或2所述的方法，其特征在于，所述M个会话包括终端设备与应用服务器之间的第一会话、所述应用服务器与本地设备之间的第二会话、所述本地设备与所述终端设备之间的第三会话；
    其中，所述终端设备与所述第一接入网设备建立有无线资源控制RRC连接。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    接收第二指示信息和/或第三指示信息；其中，所述第二指示信息指示所述本地设备对接收到的所述第二会话或所述第三会话中的数据进行边缘计算，所述第三指示信息指示所述本地设备进行本地边缘计算所需的时长。
  5. 根据权利要求3或4所述的方法，其特征在于，对所述M个会话进行处理，包括：
    确定所述本地设备对接收到的所述第二会话中的数据进行边缘计算；
    在第一时间调度所述第二会话中的数据，以及在所述第一时间之后的第二时间调度所述第三会话中的数据；其中，所述第一时间和所述第二时间之间的时间间隔是根据所述本地设备进行边缘计算所需的时长得到的。
  6. 根据权利要求3或4所述的方法，其特征在于，对所述M个会话进行处理，包括：
    确定所述本地设备对接收到的所述第三会话中的数据进行边缘计算；
    在第一时间调度所述第三会话中的数据，以及在所述第一时间之后的第二时间调度所述第二会话中的数据；其中，所述第一时间和所述第二时间之间的时间间隔是根据所述本地设备进行边缘计算所需的时长得到的。
  7. 根据权利要求5或6所述的方法，其特征在于，所述本地设备包括辅助终端设备，或者，所述本地设备包括所述接入网设备。
  8. 根据权利要求3或4所述的方法，其特征在于，所述方法还包括：
    向所述本地设备发送第四指示信息，所述第四指示信息指示所述第二会话对应的数据无线承载DRB与所述第三会话对应的DRB具有关联关系。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    向所述本地设备发送第二指示信息和/或第三指示信息，其中，所述第二指示信息指示所述本地设备对接收到的所述第二会话或所述第三会话中的数据进行边缘计算，所述第三指示信息指示所述本地设备进行本地边缘计算所需的时长。
  10. 根据权利要求8或9所述的方法，其特征在于，所述本地设备包括无线回传设备。
  11. 根据权利要求3至10中任一项所述的方法，其特征在于，所述方法还包括：
    向所述终端设备发送第五指示信息，所述第五指示信息指示往返时延；
    其中，所述往返时延为所述终端设备通过所述第三会话发送第一数据的发送时间与所述终端设备通过所述第一会话接收第二数据的接收时间之间的时间间隔，所述第二数据是根据所述第一数据得到的；或者，
    所述往返时延为所述终端设备通过所述第一会话发送第三数据的发送时间与所述终端设备通过所述第三会话接收第四数据的接收时间之间的时间间隔，所述第四数据是根据所述第三数据得到的。
  12. 根据权利要求1至11中任一项所述的方法，其特征在于，所述接收第一指示信息，包括：
    从核心网设备或者第二接入网设备接收所述第一指示信息；
    其中，所述第二接入网设备为所述终端设备的源接入网设备，所述第一接入网设备为所述终端设备的目标接入网设备。
  13. 根据权利要求1至12中任一项所述的方法，其特征在于，所述第一指示信息包括所述M个会话分别对应的M个关联信息，和/或，本地设备的标识信息；其中，所述M个关联信息相同。
  14. 根据权利要求13所述的方法，其特征在于，所述M个会话包括第一会话，所述第一会话对应的关联信息包括所述第一会话的类型信息和/或所述第一会话的关联标识；
    其中，所述第一会话的类型信息用于指示所述第一会话的类型为分离渲染或分段计算。
  15. 根据权利要求3至14中任一项所述的方法，其特征在于，所述方法还包括：
    接收第六指示信息，所述第六指示信息指示所述M个会话不再关联；
    根据所述第六指示信息，释放所述第二会话的资源和所述第三会话的资源。
  16. 一种通信方法，其特征在于，所述方法应用于第一核心网设备或者所述第一核心网设备中的芯片，所述方法包括：
    获取第一指示信息，所述第一指示信息指示M个会话具有关联关系，M为大于1的整数；
    向接入网设备发送所述第一指示信息。
  17. 根据权利要求16所述的方法，其特征在于，所述M个会话包括终端设备与应用服务器之间的第一会话、所述应用服务器与本地设备之间的第二会话、所述本地设备与所述终端设备之间的第三会话；
    其中，所述终端设备与所述接入网设备建立有RRC连接。
  18. 根据权利要求17所述的方法，其特征在于，所述方法还包括：
    向所述接入网设备发送第二指示信息和/或第三指示信息；其中，所述第二指示信息指示所述本地设备对接收到的所述第二会话或所述第三会话中的数据进行边缘计算，所述第三指示信息指示所述本地设备进行本地边缘计算所需的时长。
  19. 根据权利要求16至18中任一项所述的方法，其特征在于，获取第一指示信息，包括：
    从所述终端设备获取所述第一指示信息；或者，
    从第二核心网设备获取所述第一指示信息。
  20. 根据权利要求19所述的方法，其特征在于，从所述终端设备获取所述第一指示信 息，包括：
    接收来自所述终端设备的第一请求消息，所述第一请求消息用于请求建立或请求修改所述M个会话或者所述M个会话中的第一会话，所述请求消息包括所述第一指示信息。
  21. 根据权利要求16至20中任一项所述的方法，其特征在于，所述方法还包括：
    向所述接入网设备发送第六指示信息，所述第六指示信息指示所述M个会话不再关联。
  22. 根据权利要求21所述的方法，其特征在于，所述方法还包括：
    接收来自所述终端设备的第二请求消息，所述第二请求消息请求修改所述M个会话中的第一会话，所述第二请求消息包括第七指示信息，所述第七指示信息指示所述第一会话与所述M个会话中的其它会话不再关联；
    根据所述第二请求消息，确定所述第六指示信息。
  23. 一种通信装置，其特征在于，包括用于执行如权利要求1至15中任一项所述方法的模块。
  24. 一种通信装置，其特征在于，包括用于执行如权利要求16至22中任一项所述方法的模块。
  25. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器和所述存储器耦合，所述处理器用于实现如权利要求1至15中任一项所述的方法。
  26. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器和所述存储器耦合，所述处理器用于实现如权利要求16至22中任一项所述的方法。
  27. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1至15中任一项所述的方法。
  28. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求16至22中任一项所述的方法。
  29. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至15中任一项所述的方法或者如权利要求16至22中任一项所述的方法。
  30. 一种通信系统，其特征在于，包括如权利要求23、25、27中任一项所述的通信装置，和如权利要求24、26、28中任一项所述的通信装置。
  31. 一种计算机程序产品，其特征在于，当计算机读取并执行所述计算机程序产品时，使得计算机执行如权利要求1至15中任一项所述的方法或者如权利要求16至22中任一项所述的方法。
PCT/CN2021/101563 2020-06-29 2021-06-22 一种通信方法及装置 WO2022001753A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010609711.4A CN113938985A (zh) 2020-06-29 2020-06-29 一种通信方法及装置
CN202010609711.4 2020-06-29

Publications (1)

Publication Number Publication Date
WO2022001753A1 true WO2022001753A1 (zh) 2022-01-06

Family

ID=79273170

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/101563 WO2022001753A1 (zh) 2020-06-29 2021-06-22 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN113938985A (zh)
WO (1) WO2022001753A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024055871A1 (zh) * 2022-09-14 2024-03-21 华为技术有限公司 一种通信系统中传输数据的方法和通信装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102356623A (zh) * 2009-01-19 2012-02-15 皇家Kpn公司 在网络中管理关联的会话
US20200053816A1 (en) * 2018-08-13 2020-02-13 Samsung Electronics Co., Ltd. Method and apparatus for managing pdu session connection
CN111148274A (zh) * 2018-11-01 2020-05-12 北京三星通信技术研究有限公司 用于会话建立的方法、会话管理功能实体、基站和存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102356623A (zh) * 2009-01-19 2012-02-15 皇家Kpn公司 在网络中管理关联的会话
US20200053816A1 (en) * 2018-08-13 2020-02-13 Samsung Electronics Co., Ltd. Method and apparatus for managing pdu session connection
CN111148274A (zh) * 2018-11-01 2020-05-12 北京三星通信技术研究有限公司 用于会话建立的方法、会话管理功能实体、基站和存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "TP for PDU Session Setup Procedure", 3GPP DRAFT; R3-171648, vol. RAN WG3, 6 May 2017 (2017-05-06), Hangzhou P R China, pages 1 - 6, XP051265565 *
TENCENT: "TSN UE Requested TSC", 3GPP DRAFT; S2-1909132 TS23.502 R16 TSN UE REQUESTED PDU SESSION MODIFICTAION FOR TSC TRAFFIC, vol. SA WG2, 4 October 2019 (2019-10-04), Split Croatia, pages 1 - 9, XP051787407 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024055871A1 (zh) * 2022-09-14 2024-03-21 华为技术有限公司 一种通信系统中传输数据的方法和通信装置

Also Published As

Publication number Publication date
CN113938985A (zh) 2022-01-14

Similar Documents

Publication Publication Date Title
WO2022178832A1 (zh) 信息传输方法、装置、通信设备和存储介质
JP2018514139A (ja) Ｄ２ｄ中継ノードの確定方法、使用方法及び装置
WO2022048505A1 (zh) 多流关联传输的方法、装置及系统
WO2022041285A1 (zh) 一种模型数据传输方法及通信装置
WO2021219098A1 (zh) 一种通信方法及装置
WO2021026704A1 (zh) 一种无线通信的方法和装置
WO2021088990A1 (zh) 中继连接建立方法及设备
WO2022252859A1 (zh) 一种算力资源调度的方法以及相关装置
WO2022001753A1 (zh) 一种通信方法及装置
WO2023125392A1 (zh) 一种通信方法及装置
WO2021087932A1 (zh) 通信方法、装置和系统
WO2023011004A1 (zh) 通信方法及通信装置
US20220104163A1 (en) Method and apparatus for connection management in wireless communication system
WO2022027523A1 (zh) 一种辅助信息的配置方法及通信装置
WO2021189496A1 (zh) 用于网络切片的数据传输方法及设备
CN114902730A (zh) 信息传输方法、装置、通信设备和存储介质
US20220408469A1 (en) Downlink control information configuration method and apparatus, and communication device and storage medium
KR20220028009A (ko) 데이터 송신 방법 및 사용자 기기
WO2022165813A1 (zh) 一种通信方法及装置
WO2024040411A1 (zh) 一种实现多接入的方法及其装置
WO2023246267A1 (zh) 通信方法、通信装置和系统
WO2023272669A1 (zh) 一种寻呼方法及相关装置
WO2023179262A1 (zh) 小区信息的配置方法、装置、可读存储介质及芯片系统
WO2023103958A1 (zh) 一种通信方法及装置
WO2023272670A1 (zh) 一种网络连接的方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21834536

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21834536

Country of ref document: EP

Kind code of ref document: A1