Communication method and device
By offloading the processing of terminal devices to access network devices for auxiliary calculations, the problem of excessive computational load on terminal devices is solved, thereby reducing computational load and improving data transmission efficiency.
Patent Information
- Application Number
- CN202410890970.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-03
- Publication Date
- 2026-01-06
AI Technical Summary
Terminal devices require excessive computation to process new applications such as XR and AI, making it difficult to provide effective support.
By offloading the processing content of the terminal device to the access network device, the access network device is used for auxiliary calculation, a tunnel is established for data transmission, and the identifier is implicitly carried to reduce signaling overhead.
It effectively reduces the computational load on terminal devices, reduces the overhead of carrying identifiers in data transmission, and improves computational efficiency.
Smart Images

Figure CN121284641A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and more specifically, to a communication method and apparatus. Background Technology
[0002] The emergence and widespread adoption of new applications such as extended reality (XR) and artificial intelligence (AI) have significantly improved the quality of work, entertainment, and life. However, the emergence and widespread adoption of these new applications have also placed higher demands on the computing power (or "computing power") of terminal devices. For example, new applications such as XR and AI require terminal devices to perform a large amount of computational processing, which may be difficult for terminal devices to support.
[0003] Therefore, how to effectively reduce the computing load of terminal devices is an urgent problem to be solved. Summary of the Invention
[0004] This application provides a communication method and apparatus that effectively reduces the computational load of the terminal device by offloading the processing content of the terminal device to the access network device.
[0005] Firstly, a communication method is provided. The implementing entity of the method provided in the first aspect can be a second access function. Unless otherwise specified, the second access function in this application can refer to the access network device itself capable of implementing the second access function, or to a component within the access network device (e.g., a processor, chip, or chip system), or it can be a logic module or software capable of implementing all or part of the second access function. For ease of description, the following description uses a second access function as an example.
[0006] The method includes: receiving first information from a first access function, the first information being used to indicate an identifier of a first process, the first information being used to request the second access function to perform the first process; and sending second information to the first access function, the second information being used to indicate that the second access function agrees to perform the first process.
[0007] Based on the above scheme, the first access function can request the second access function to perform auxiliary calculations for the first terminal device, thereby effectively reducing the computational load of the first terminal device.
[0008] In some implementations, the first process is the offloading of the first terminal device to the second access function, the first terminal device being used to communicate with the first access function.
[0009] Based on the above solution, the processing content of the first terminal device can be offloaded to the second access function, effectively reducing the computational load of the first terminal device. For example, without the above solution, the first terminal device needs to perform first processing on some data. With the above solution, the first terminal device can avoid performing first processing on this data; instead, the second access function can perform the first processing. Therefore, the above solution can effectively reduce the computational load of the terminal device.
[0010] In some implementations, the first information is also used to indicate a first identifier, which corresponds to the identifier of the first process.
[0011] Based on the above scheme, the first information indicates the first identifier and the identifier of the first processing. The first identifier corresponds to the identifier of the first processing. For example, when the second access function receives data carrying the first identifier, it can determine that the data will undergo first processing. In this way, the first access function does not need to additionally instruct the second access function to perform first processing on the data, thereby reducing signaling overhead.
[0012] In some implementations, the method further includes: determining a first tunnel, the identifier of which corresponds to a first identifier, the first tunnel being used for data transmission between the first access function and the second access function.
[0013] Based on the above scheme, a tunnel can be established between the first access function and the second access function, enabling data transmission between them and facilitating auxiliary calculations by the second access function. Furthermore, the identifier of the first tunnel corresponds to the first identifier. Thus, even when the data only carries the identifier of the first tunnel and not the first identifier, either the first or second access function can determine the first identifier based on the first tunnel identifier and perform subsequent operations accordingly. Therefore, the above scheme supports implicitly carrying the first identifier in the data, thereby reducing the overhead of carrying the first identifier.
[0014] In some implementations, the method further includes: receiving tenth information from the first access function, the tenth information indicating the identifier of the first tunnel, wherein determining the first tunnel includes: determining the first tunnel based on the tenth information.
[0015] Based on the above scheme, the first access function can indicate the identifier of the first tunnel to the second access function, so that the second access function can determine the first tunnel based on the identifier of the first tunnel.
[0016] In some implementations, the tenth piece of information is also used to indicate the identifier of the first access function.
[0017] In some scenarios, the identifiers used to distinguish tunnels are limited. For example, the identifier for the first tunnel can correspond to other tunnels as well. Based on the above solution, the first tunnel can be distinguished from other tunnels by using the identifier of the first tunnel and the identifier of the first access function. Thus, even with a limited number of identifiers, the first tunnel can be distinguished from other tunnels without needing to set a completely different tunnel identifier for it, thereby saving space for tunnel identifiers.
[0018] In some implementations, the method further includes sending the eleventh information to the first access function, the eleventh information being used to indicate the identifier of the first tunnel.
[0019] Based on the above scheme, the second access function can indicate the identifier of the first tunnel to the first access function, so that the first access function can determine the first tunnel based on the identifier of the first tunnel.
[0020] In some implementations, the method further includes: determining a second tunnel, the identifier of which corresponds to the first identifier, the second tunnel being used for data transmission between the second access function and the first core network function.
[0021] Based on the above scheme, a tunnel can be established between the second access function and the first core network function, enabling data transmission between them. For example, the second access function can send processed data to the first core network function through the second tunnel. Alternatively, the second access function can receive data from the first core network function through the second tunnel for auxiliary calculations. Furthermore, the identifier of the second tunnel corresponds to the first identifier. Thus, even when data only carries the identifier of the second tunnel and not the first identifier, the second access function can determine the first identifier based on the second tunnel identifier and perform subsequent operations accordingly. Therefore, the above scheme supports implicitly carrying the first identifier in the data, thereby reducing the overhead of carrying the first identifier.
[0022] In some implementations, the identifier of the first tunnel is the same as the identifier of the second tunnel; or, the identifier of the first tunnel is different from the identifier of the second tunnel.
[0023] The identifiers of the first and second tunnels are the same, which reduces the complexity of data transmission. For example, when the second access function receives data carrying the identifier of the first tunnel from the first access function, since the identifiers of the first and second tunnels are the same, the second access function can directly send the data to the first core network function through the second tunnel based on this identifier, without needing to determine the identifier of the second tunnel based on the identifier of the first tunnel. If the identifiers of the first and second tunnels are different, it allows for more flexible configuration of the first and second tunnels. For example, the second tunnel can be expanded independently without affecting the operation of the first tunnel.
[0024] In some implementations, the method further includes receiving twelfth information from the first access function, the twelfth information being used to indicate the identifier of the second tunnel.
[0025] Based on the above scheme, the first access function can indicate the identifier of the second tunnel to the second access function, so that the second access function can determine the second tunnel based on the identifier of the second tunnel.
[0026] In some implementations, the twelfth piece of information is also used to indicate the identifier of the first core network function; wherein, determining the second tunnel includes: determining the second tunnel based on the identifier of the first core network function.
[0027] In some implementations, the method further includes receiving thirteenth information from a second core network function, the thirteenth information being used to indicate the identifier of the second tunnel.
[0028] Based on the above scheme, the second access function can obtain the identifier of the second tunnel from the second core network function, thereby identifying the second tunnel.
[0029] In some implementations, the thirteenth information is also used to indicate the identifier of the first core network function, wherein determining the second tunnel includes: determining the second tunnel based on the identifier of the first core network function.
[0030] In some implementations, the method further includes sending a second request to the second core network function, the second request being used to request the identifier of the second tunnel.
[0031] In some implementations, the second request is used to indicate the identifier of the second access function.
[0032] In some implementations, the method further includes sending a fifteenth message to the first access function, the fifteenth message indicating TEID3, and the third tunnel being used for data transmission between the first access function and the first core network function.
[0033] Based on the above scheme, the second access function can indicate TEID3 to the first access function, so that the first access function can determine the third tunnel based on TEID3.
[0034] In some implementations, the identifier of the first tunnel is the same as that of TEID3; or, the identifier of the first tunnel is different from that of TEID3.
[0035] The identifier of the first tunnel is the same as TEID3, which reduces the complexity of data transmission. For example, when the first access function receives data carrying the identifier of the first tunnel from the second access function, since the identifier of the first tunnel is the same as TEID3, the first access function can directly send the data to the first core network function through the third tunnel based on this identifier, without needing to determine TEID3 based on the identifier of the first tunnel. The identifier of the first tunnel is different from TEID3, allowing for more flexible configuration of the first and third tunnels. For example, the third tunnel can be expanded independently without affecting the operation of the first tunnel.
[0036] In some implementations, the method further includes receiving sixteenth information from a second core network function, the sixteenth information being used to indicate the TEID3.
[0037] Based on the above scheme, the second access function can obtain TEID3 from the second core network function, and then indicate TEID3 to the first access function.
[0038] In some implementations, the method further includes sending a third request to the second core network function, the third request being used to request the TEID3.
[0039] In some implementations, the second request includes an identifier of the first access function.
[0040] In some implementations, the fifteenth piece of information is also used to indicate the identifier of the first core network function.
[0041] In some implementations, the sixteenth piece of information is also used to indicate the identifier of the first core network function.
[0042] In some implementations, the method further includes: receiving third information from the first access function, the third information including first data and first indication information, the first indication information being used to indicate at least one of a first identifier, an identifier of a first tunnel, or an identifier of the first processing, the first tunnel being used for data transmission between the first access function and the second access function; and performing the first processing on the first data according to the first indication information to obtain second data.
[0043] Based on the above scheme, the first data sent by the first access function can carry first indication information. In this way, the second access function can determine, based on the first indication information, to perform first processing on the first data, thereby achieving auxiliary calculation. Furthermore, the second access function can determine, based on the first indication information, to send the processed data to the corresponding function.
[0044] In some implementations, the first data is processed according to the first instruction information to obtain the second data, including: determining an identifier of the first processing according to the first instruction information; and performing the first processing on the first data according to the identifier of the first processing to obtain the second data.
[0045] In some implementations, the method further includes sending fourth information to a first core network function, the fourth information including the second data and second indication information, the second indication information being used to indicate the first identifier and / or the identifier of the second tunnel, the second tunnel being used for data transmission between the second access function and the first core network function.
[0046] Based on the above scheme, the second access function can send the processed second data to the first core network function. This second data can carry second indication information, which enables the first core network function to process the second data accordingly.
[0047] In some implementations, the method further includes: determining the first core network function based on the first instruction information.
[0048] In some implementations, determining the first core network function based on the first indication information includes: determining the first core network function based on the first indication information and the first mapping relationship, wherein the first mapping relationship includes a mapping relationship between at least one of the first identifier, the identifier of the first tunnel, or the identifier of the first process and the identifier of the first core network function.
[0049] In some implementations, at least one of the first identifier, the identifier of the first tunnel, or the identifier of the first process corresponds to the identifier of the second tunnel, wherein the method further includes: determining the identifier of the second tunnel based on the first indication information.
[0050] In some implementations, the method further includes: receiving sixth information from a first core network function, the sixth information including first data and fourth indication information, the fourth indication information being used to indicate the first identifier and / or the identifier of the second tunnel, the second tunnel being used for data transmission between the second access function and the first core network function; and performing the first processing on the first data according to the fourth indication information to obtain second data.
[0051] In some implementations, the first processing is performed on the first data according to the fourth instruction information to obtain the second data, including: determining the identifier of the first processing according to the fourth instruction information; and performing the first processing on the first data according to the identifier of the first processing to obtain the second data.
[0052] In some implementations, the method further includes: determining the first access function based on the first indication information.
[0053] In some implementations, determining the first access function based on the first indication information includes: determining the first access function based on the first indication information and a second mapping relationship, wherein the second mapping relationship includes a mapping relationship between at least one of the first identifier, the identifier of the first tunnel, or the identifier of the first process and the identifier of the first access function.
[0054] In some implementations, the method further includes: determining the first access function based on the fourth indication information.
[0055] In some implementations, determining the first access function based on the fourth indication information includes: determining the first access function based on the fourth indication information and the third mapping relationship, wherein the third mapping relationship includes the mapping relationship between the first identifier and / or the identifier of the second tunnel and the identifier of the first access function.
[0056] In some implementations, the first identifier and / or the identifier of the second tunnel corresponds to the identifier of the first tunnel, and the method further includes: determining the identifier of the first tunnel according to the fourth indication information.
[0057] In some implementations, the method further includes sending fifth information to the first access function, the fifth information including the second data and third indication information, the third indication information being used to indicate the first identifier and / or the identifier of the first tunnel, the third indication information being determined based on the first indication information.
[0058] Based on the above scheme, the second access function can send the processed second data to the first access function. This second data may carry third indication information, which enables the first access function to process the second data accordingly.
[0059] In some implementations, the fifth piece of information also includes information for indicating uplink or downlink transmission.
[0060] Based on the above scheme, the fifth piece of information can carry information indicating uplink or downlink transmission, enabling the first access function to determine whether the second data is uplink or downlink data, and thus send the second data to the corresponding function. For example, if the second data is uplink data, the first access function can send the second data to the first core network function. As another example, if the second data is downlink data, the first access function can send the second data to the first terminal device.
[0061] In some implementations, the third information also includes information for indicating uplink or downlink transmission.
[0062] In some implementations, the method further includes sending fifth information to the first access function, the fifth information including the second data and third indication information, the third indication information being used to indicate the first identifier and / or the identifier of the first tunnel, the first tunnel being used for data transmission between the first access function and the second access function.
[0063] In some implementations, the first identifier is used to indicate at least one of the following: the identifier of the first terminal device, downlink transmission, uplink transmission, quality of service flow identifier (QFI), data radio bearer (DRB) identifier, application (APP) type, APP stream identifier, APP identifier, or packet data unit (PDU) session identifier.
[0064] Secondly, a communication method is provided. The implementing entity of the method provided in this application can be a first access function. Unless otherwise specified, the first access function in this application can refer to the access network device itself capable of implementing the first access function, or to a component within the access network device (e.g., a processor, chip, or chip system), or it can be a logic module or software capable of implementing all or part of the first access function. For ease of description, the following description uses the first access function as an example.
[0065] The method includes: sending first information to a second access function, the first information being used to indicate an identifier of a first process, the first information being used to request the second access function to perform the first process; and receiving second information from the first access function, the second information being used to indicate that the second access function agrees to perform the first process.
[0066] In some implementations, the first process is the offloading of the first terminal device to the second access function, the first terminal device being used to communicate with the first access function.
[0067] In some implementations, the first information is also used to indicate a first identifier, which corresponds to the identifier of the first process.
[0068] In some implementations, the method further includes: receiving a first request from a first terminal device, the first request being used to indicate an identifier of the first process, the first request being used to request the first process to be performed.
[0069] Based on the above scheme, the first terminal device can send a first request to the first access function, thereby triggering the first access function to send first information to the second access function.
[0070] In some implementations, the method further includes: determining a first tunnel, the identifier of which corresponds to a first identifier, the first tunnel being used for data transmission between the first access function and the second access function.
[0071] In some implementations, the method further includes: sending tenth information to the second access function, the tenth information indicating the identifier of the first tunnel, wherein determining the first tunnel includes: determining the first tunnel based on the tenth information.
[0072] In some implementations, the method further includes receiving eleventh information from the second access function, the eleventh information being used to indicate the identifier of the first tunnel.
[0073] In some implementations, the method further includes: determining a third tunnel, the TEID3 corresponding to the first identifier, the third tunnel being used for data transmission between the first access function and the first core network function.
[0074] Based on the above scheme, a tunnel can be established between the first access function and the first core network function, enabling data transmission between them. For example, the first access function can receive processed data from the second access function and send it to the first core network function through the third tunnel. Alternatively, the first access function can receive data from the first core network function through the third tunnel and send it to the second access function for auxiliary calculations. Furthermore, TEID3 corresponds to the first identifier. Thus, even when data only carries TEID3 and not the first identifier, the first access function can determine the first identifier based on TEID3 and perform subsequent operations accordingly. Therefore, the above scheme supports implicitly carrying the first identifier in data, thereby reducing the overhead of carrying the first identifier.
[0075] In some implementations, the method further includes receiving fourteenth information from a second core network function, the fourteenth information being used to indicate the TEID3.
[0076] Based on the above scheme, the first access function can obtain TEID3 from the second core network function, thereby determining the third tunnel.
[0077] In some implementations, the fourteenth information is also used to indicate the identifier of the first core network function; wherein, determining the third tunnel includes: determining the third tunnel based on the identifier of the first core network function.
[0078] In some implementations, the method further includes sending a fourth request to the second core network function, the fourth request being used to request the TEID3.
[0079] In some implementations, the fourth request is used to indicate the identifier of the first access function.
[0080] In some implementations, the method further includes receiving fifteenth information from the second access function, the fifteenth information being used to indicate the TEID3.
[0081] In some implementations, the fifteenth piece of information is also used to indicate the identifier of the first core network function.
[0082] In some implementations, the method further includes sending a twelfth piece of information to the first access function, the twelfth piece of information being used to indicate the identifier of the second tunnel, the second tunnel being used for data transmission between the second access function and the first core network function.
[0083] In some implementations, the twelfth piece of information is also used to indicate the identifier of the first core network function.
[0084] In some implementations, the method further includes receiving a seventeenth piece of information from a second core network function, the seventeenth piece of information being used to indicate the identifier of the second tunnel.
[0085] Based on the above scheme, the first access function can obtain the identifier of the second tunnel from the second core network function, and then indicate the identifier of the second tunnel to the second access function.
[0086] In some implementations, the method further includes sending a fifth request to the second core network function, the fifth request being used to request the identifier of the second tunnel.
[0087] In some implementations, the fifth request is used to indicate the identifier of the second access function.
[0088] In some implementations, the seventeenth piece of information is also used to indicate the identifier of the first core network function.
[0089] In some implementations, the method further includes: sending third information to the second access function, the third information including the first data and first indication information, the first indication information being used to indicate at least one of a first identifier, an identifier of a first tunnel, or an identifier of the first processing, the first indication information being used to indicate the first processing of the first data, and the first tunnel being used for data transmission between the first access function and the second access function.
[0090] In some implementations, the method further includes: receiving seventh information from a first core network function, the seventh information including first data and seventh indication information, the seventh indication information being used to indicate the first identifier and / or TEID3, and the third tunnel being used for data transmission between the first access function and the first core network function.
[0091] In some implementations, the method further includes: determining the second access function based on the seventh indication information.
[0092] In some implementations, determining the second access function based on the seventh indication information includes: determining the second access function based on the seventh indication information and the twelfth mapping relationship, wherein the twelfth mapping relationship includes the mapping relationship between the first identifier and / or TEID3 and the identifier of the second access function.
[0093] In some implementations, the method further includes receiving eighth information from the first terminal device, the eighth information including the first data and the first identifier.
[0094] Based on the above scheme, the first data sent by the first terminal device can carry a first identifier. In this way, the first access function can use the first identifier to instruct the corresponding access function (e.g., the second access function) to perform auxiliary calculations on the first data.
[0095] In some implementations, the method further includes: determining the second access function based on the first identifier.
[0096] In some implementations, determining the second access function based on the first identifier includes: determining the second access function based on the first identifier and a fourth mapping relationship, wherein the fourth mapping relationship includes a mapping relationship between the first identifier and the identifier of the second access function.
[0097] In some implementations, the method further includes: receiving fifth information from the second access function, the fifth information including second data and third indication information, the third indication information being used to indicate the first identifier and / or the identifier of the first tunnel, the second data being obtained from the first data through the first processing.
[0098] In some implementations, the method further includes: sending the second data to the first terminal device according to the third instruction information.
[0099] In some implementations, sending the second data to the first terminal device according to the third instruction information includes: determining the first terminal device according to the third instruction information; and sending the second data to the first terminal device.
[0100] In some implementations, determining the first terminal device based on the third indication information includes: determining the first terminal device based on the third indication information and the fifth mapping relationship, wherein the fifth mapping relationship includes the mapping relationship between the first identifier and / or the identifier of the first tunnel and the identifier of the first terminal device.
[0101] In some implementations, the method further includes: sending a ninth message to a first core network function, the ninth message including the second data and a sixth indication message, the sixth indication message being used to indicate the first identifier and / or TEID3, and the third tunnel being used for data transmission between the first access function and the first core network function.
[0102] Based on the above scheme, the first access function can send the processed second data to the first core network function. This second data can carry sixth indication information, which enables the first core network function to process the second data accordingly.
[0103] In some implementations, the method further includes: determining the first core network function based on the third instruction information.
[0104] In some implementations, determining the first core network function based on the third indication information includes: determining the first core network function based on the third indication information and the sixth mapping relationship, wherein the sixth mapping relationship includes the mapping relationship between the first identifier and / or the identifier of the first tunnel and the identifier of the first core network function.
[0105] In some implementations, the fifth piece of information also includes information for indicating uplink or downlink transmission.
[0106] In some implementations, the third information also includes information for indicating uplink or downlink transmission.
[0107] In some implementations, the first identifier is used to indicate at least one of the following: the identifier of the first terminal device, the identifier of downlink transmission, the identifier of uplink transmission, the identifier of QFI, the identifier of DRB, the identifier of APP type, the identifier of APP stream, the identifier of APP, or the identifier of PDU session.
[0108] Thirdly, a communication method is provided. The execution entity of the method provided in this application can be a first terminal device. Unless otherwise specified, the first terminal device in this application can refer to the first terminal device itself, a component within the first terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the first terminal device. For ease of description, the following description uses a first terminal device as an example.
[0109] The method includes: generating a first request, the first request being used to indicate an identifier for a first process, the first request being used to request the first process to be performed; and sending the first request to a first access function.
[0110] Based on the above scheme, the first terminal device can send a first request to the first access function, thereby triggering the first access function to determine the node for auxiliary computing.
[0111] In some implementations, the first process is the offloading of the first terminal device to the access function.
[0112] In some implementations, the first request is also used to indicate a first identifier, which corresponds to the identifier of the first process.
[0113] In some implementations, the first identifier is used to indicate at least one of the following: the identifier of the first terminal device, the identifier of downlink transmission, the identifier of uplink transmission, the identifier of QFI, the identifier of DRB, the identifier of APP type, the identifier of APP stream, the identifier of APP, or the identifier of PDU session.
[0114] In some implementations, the method further includes receiving second data from the first access function, the second data being obtained by processing the first data.
[0115] In some implementations, the method further includes: sending eighth information to the first access function, the eighth information including the first data and the first identifier, the first data being used to obtain second data through the first processing.
[0116] Fourthly, a communication device is provided, including a processing circuit (or processor) and an input / output interface (also referred to as an interface circuit), the input / output interface being used for inputting and / or outputting signals, the processing circuit being used to perform the first aspect and any possible method of the first aspect, or the processing circuit being used to perform the second aspect and any possible method of the second aspect, or the processing circuit being used to perform the third aspect and any possible method of the third aspect, or the processing circuit being used to perform the eleventh aspect and any possible method of the eleventh aspect, or the processing circuit being used to perform the twelfth aspect and any possible method of the twelfth aspect.
[0117] In some implementations, the processing circuit is used to communicate with other devices through the interface circuit and to perform the first aspect and any possible method of the first aspect, or to perform the second aspect and any possible method of the second aspect, or to perform the third aspect and any possible method of the third aspect, or to perform the twelfth aspect and any possible method of the twelfth aspect, or to perform the twelfth aspect and any possible method of the twelfth aspect.
[0118] Fifthly, a communication device is provided. This communication device may include units or modules for performing the functions of the communication device.
[0119] In some implementations, the communication device may include modules, units, or means for performing the methods / operations / steps / actions described in the first aspect and any possible implementation of the first aspect. These modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software.
[0120] The device includes a transceiver unit. The transceiver unit can be used to receive first information from a first access function, the first information being used to indicate an identifier of a first process, the first information being used to request the second access function to perform the first process; the transceiver unit can also be used to send second information to the first access function, the second information being used to indicate that the second access function agrees to perform the first process.
[0121] In some implementations, the first process is the offloading of the first terminal device to the second access function, the first terminal device being used to communicate with the first access function.
[0122] In some implementations, the first information is also used to indicate a first identifier, which corresponds to the identifier of the first process.
[0123] In some implementations, the apparatus further includes a processing unit. The processing unit may be used to determine a first tunnel, the identifier of which corresponds to a first identifier, the first tunnel being used for data transmission between the first access function and the second access function.
[0124] In some implementations, the transceiver unit can also be used to receive tenth information from the first access function, the tenth information being used to indicate the identifier of the first tunnel, wherein the processing unit is specifically used to: determine the first tunnel based on the tenth information.
[0125] In some implementations, the tenth piece of information is also used to indicate the identifier of the first access function.
[0126] In some implementations, the transceiver unit can also be used to send the eleventh information to the first access function, the eleventh information being used to indicate the identifier of the first tunnel.
[0127] In some implementations, the processing unit may also be used to determine a second tunnel whose identifier corresponds to the first identifier, and the second tunnel is used for data transmission between the second access function and the first core network function.
[0128] In some implementations, the identifier of the first tunnel is the same as the identifier of the second tunnel; or, the identifier of the first tunnel is different from the identifier of the second tunnel.
[0129] In some implementations, the transceiver unit can also be used to receive twelfth information from the first access function, which is used to indicate the identifier of the second tunnel.
[0130] In some implementations, the twelfth piece of information is also used to indicate the identifier of the first core network function; wherein, the processing unit is specifically used to: determine the second tunnel based on the identifier of the first core network function.
[0131] In some implementations, the transceiver unit can also be used to receive thirteenth information from the second core network function, which is used to indicate the identifier of the second tunnel.
[0132] In some implementations, the thirteenth information is also used to indicate the identifier of the first core network function, wherein the processing unit is specifically used to: determine the second tunnel based on the identifier of the first core network function.
[0133] In some implementations, the transceiver unit can also be used to send a second request to the second core network function, the second request being used to request the identifier of the second tunnel.
[0134] In some implementations, the second request is used to indicate the identifier of the second access function.
[0135] In some implementations, the transceiver unit can also be used to send a fifteenth message to the first access function, the fifteenth message being used to indicate TEID3, and the third tunnel being used for data transmission between the first access function and the first core network function.
[0136] In some implementations, the identifier of the first tunnel is the same as that of TEID3; or, the identifier of the first tunnel is different from that of TEID3.
[0137] In some implementations, the transceiver unit can also be used to receive the sixteenth information from the second core network function, which is used to indicate the TEID3.
[0138] In some implementations, the transceiver unit can also be used to send a third request to the second core network function, which is used to request TEID3.
[0139] In some implementations, the second request includes an identifier of the first access function.
[0140] In some implementations, the fifteenth piece of information is also used to indicate the identifier of the first core network function.
[0141] In some implementations, the sixteenth piece of information is also used to indicate the identifier of the first core network function.
[0142] In some implementations, the transceiver unit can also be used to receive third information from the first access function, the third information including first data and first indication information, the first indication information being used to indicate at least one of a first identifier, an identifier of a first tunnel, or an identifier of the first processing, the first tunnel being used for data transmission between the first access function and the second access function; the processing unit is further used to perform the first processing on the first data according to the first indication information to obtain second data.
[0143] In some implementations, the processing unit is specifically used to: determine the identifier of the first processing according to the first instruction information; and perform the first processing on the first data according to the identifier of the first processing to obtain the second data.
[0144] In some implementations, the transceiver unit can also be used to send fourth information to the first core network function. The fourth information includes the second data and the second indication information. The second indication information is used to indicate the first identifier and / or the identifier of the second tunnel. The second tunnel is used for data transmission between the second access function and the first core network function.
[0145] In some implementations, the first core network function is determined based on the first instruction information.
[0146] In some implementations, the processing unit is specifically used to: determine the first core network function based on the first indication information and the first mapping relationship, wherein the first mapping relationship includes a mapping relationship between at least one of the first identifier, the identifier of the first tunnel, or the identifier of the first process and the identifier of the first core network function.
[0147] In some implementations, at least one of the first identifier, the identifier of the first tunnel, or the identifier of the first process corresponds to the identifier of the second tunnel, wherein the processing unit is further configured to: determine the identifier of the second tunnel based on the first indication information.
[0148] In some implementations, the transceiver unit can also be used to receive sixth information from the first core network function, the sixth information including first data and fourth indication information, the fourth indication information being used to indicate the first identifier and / or the identifier of the second tunnel, the second tunnel being used for data transmission between the second access function and the first core network function; the processing unit is also used to perform the first processing on the first data according to the fourth indication information to obtain the second data.
[0149] In some implementations, the processing unit is specifically used to: determine the identifier of the first processing according to the fourth instruction information; and perform the first processing on the first data according to the identifier of the first processing to obtain the second data.
[0150] In some implementations, the processing unit is further configured to: determine the first access function based on the first indication information.
[0151] In some implementations, the processing unit is specifically used to: determine the first access function based on the first indication information and the second mapping relationship, wherein the second mapping relationship includes a mapping relationship between at least one of the first identifier, the identifier of the first tunnel, or the identifier of the first process and the identifier of the first access function.
[0152] In some implementations, the processing unit is also used to: determine the first access function based on the fourth instruction information.
[0153] In some implementations, the processing unit is specifically used to: determine the first access function based on the fourth indication information and the third mapping relationship, wherein the third mapping relationship includes the mapping relationship between the first identifier and / or the identifier of the second tunnel and the identifier of the first access function.
[0154] In some implementations, the first identifier and / or the identifier of the second tunnel corresponds to the identifier of the first tunnel, and the processing unit is further configured to: determine the identifier of the first tunnel based on the fourth indication information.
[0155] In some implementations, the transceiver unit may also be used to: send fifth information to the first access function, the fifth information including the second data and third indication information, the third indication information being used to indicate the first identifier and / or the identifier of the first tunnel, the third indication information being determined based on the first indication information.
[0156] In some implementations, the fifth piece of information also includes information for indicating uplink or downlink transmission.
[0157] In some implementations, the third information also includes information for indicating uplink or downlink transmission.
[0158] In some implementations, the transceiver unit may also be used to: send fifth information to the first access function, the fifth information including the second data and third indication information, the third indication information being used to indicate the first identifier and / or the identifier of the first tunnel, the first tunnel being used for data transmission between the first access function and the second access function.
[0159] In some implementations, the first identifier is used to indicate at least one of the following: the identifier of the first terminal device, the identifier of downlink transmission, the identifier of uplink transmission, the identifier of QFI, the identifier of DRB, the identifier of APP type, the identifier of APP stream, the identifier of APP, or the identifier of PDU session.
[0160] In some implementations, the communication device may include modules, units, or means for performing the methods / operations / steps / actions described in the second aspect and any possible implementation of the second aspect. These modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software.
[0161] The device may include a transceiver unit. The transceiver unit may be used to: send first information to a second access function, the first information being used to indicate an identifier of a first process, the first information being used to request the second access function to perform the first process; and receive second information from the first access function, the second information being used to indicate that the second access function agrees to perform the first process.
[0162] In some implementations, the first process is the offloading of the first terminal device to the second access function, the first terminal device being used to communicate with the first access function.
[0163] In some implementations, the first information is also used to indicate a first identifier, which corresponds to the identifier of the first process.
[0164] In some implementations, the transceiver unit may also be used to: receive a first request from a first terminal device, the first request being used to indicate an identifier of the first process, the first request being used to request the first process to be performed.
[0165] In some implementations, the device may further include a processing unit that can be used to: determine a first tunnel, the identifier of which corresponds to a first identifier, the first tunnel being used for data transmission between the first access function and the second access function.
[0166] In some implementations, the transceiver unit can also be used to: send tenth information to the second access function, the tenth information being used to indicate the identifier of the first tunnel, wherein the processing unit is specifically used to: determine the first tunnel based on the tenth information.
[0167] In some implementations, the transceiver unit can also be used to: receive the eleventh information from the second access function, the eleventh information being used to indicate the identifier of the first tunnel.
[0168] In some implementations, the processing unit can also be used to: determine a third tunnel, the TEID3 corresponding to the first identifier, the third tunnel being used for data transmission between the first access function and the first core network function.
[0169] In some implementations, the transceiver unit can also be used to receive the fourteenth information from the second core network function, which is used to indicate the TEID3.
[0170] In some implementations, the fourteenth information is also used to indicate the identifier of the first core network function; wherein, the processing unit is specifically used to include: determining the third tunnel based on the identifier of the first core network function.
[0171] In some implementations, the transceiver unit can also be used to send a fourth request to the second core network function, the fourth request being used to request the TEID3.
[0172] In some implementations, the fourth request is used to indicate the identifier of the first access function.
[0173] In some implementations, the transceiver unit can also be used to receive fifteenth information from the second access function, the fifteenth information being used to indicate the TEID3.
[0174] In some implementations, the fifteenth piece of information is also used to indicate the identifier of the first core network function.
[0175] In some implementations, the transceiver unit can also be used to: send a twelfth message to the first access function, the twelfth message being used to indicate the identifier of the second tunnel, the second tunnel being used for data transmission between the second access function and the first core network function.
[0176] In some implementations, the twelfth piece of information is also used to indicate the identifier of the first core network function.
[0177] In some implementations, the transceiver unit can also be used to receive the seventeenth information from the second core network function, which is used to indicate the identifier of the second tunnel.
[0178] In some implementations, the transceiver unit can also be used to send a fifth request to the second core network function, the fifth request being used to request the identifier of the second tunnel.
[0179] In some implementations, the fifth request is used to indicate the identifier of the second access function.
[0180] In some implementations, the seventeenth piece of information is also used to indicate the identifier of the first core network function.
[0181] In some implementations, the transceiver unit may also be used to: send third information to the second access function, the third information including the first data and first indication information, the first indication information being used to indicate at least one of a first identifier, an identifier of a first tunnel, or an identifier of the first processing, the first indication information being used to indicate the first processing of the first data, and the first tunnel being used for data transmission between the first access function and the second access function.
[0182] In some implementations, the transceiver unit can also be used to: receive seventh information from the first core network function, the seventh information including first data and seventh indication information, the seventh indication information being used to indicate the first identifier and / or TEID3, and the third tunnel being used for data transmission between the first access function and the first core network function.
[0183] In some implementations, the processing unit can also be used to: determine the second access function based on the seventh indication information.
[0184] In some implementations, the processing unit may specifically be used to: determine the second access function based on the seventh indication information and the twelfth mapping relationship, wherein the twelfth mapping relationship includes the mapping relationship between the first identifier and / or TEID3 and the identifier of the second access function.
[0185] In some implementations, the transceiver unit can also be used to: receive eighth information from the first terminal device, the eighth information including the first data and the first identifier.
[0186] In some implementations, the processing unit can also be used to: determine the second access function based on the first identifier.
[0187] In some implementations, the processing unit may be specifically used to: determine the second access function based on the first identifier and the fourth mapping relationship, wherein the fourth mapping relationship includes the mapping relationship between the first identifier and the identifier of the second access function.
[0188] In some implementations, the transceiver unit may also be used to: receive fifth information from the second access function, the fifth information including second data and third indication information, the third indication information being used to indicate the first identifier and / or the identifier of the first tunnel, the second data being obtained from the first data through the first processing.
[0189] In some implementations, the processing unit can also be used to: send the second data to the first terminal device according to the third instruction information.
[0190] In some implementations, the processing unit may specifically be used to: determine the first terminal device based on the third instruction information; and send the second data to the first terminal device.
[0191] In some implementations, the processing unit may specifically be used to: determine the first terminal device based on the third indication information and the fifth mapping relationship, wherein the fifth mapping relationship includes the mapping relationship between the first identifier and / or the identifier of the first tunnel and the identifier of the first terminal device.
[0192] In some implementations, the transceiver unit can also be used to: send a ninth message to a first core network function, the ninth message including the second data and a sixth indication message, the sixth indication message being used to indicate the first identifier and / or TEID3, and the third tunnel being used for data transmission between the first access function and the first core network function.
[0193] In some implementations, the processing unit can also be used to: determine the first core network function based on the third instruction information.
[0194] In some implementations, the processing unit may specifically be used to: determine the first core network function based on the third indication information and the sixth mapping relationship, wherein the sixth mapping relationship includes the mapping relationship between the first identifier and / or the identifier of the first tunnel and the identifier of the first core network function.
[0195] In some implementations, the fifth piece of information also includes information for indicating uplink or downlink transmission.
[0196] In some implementations, the third information also includes information for indicating uplink or downlink transmission.
[0197] In some implementations, the first identifier is used to indicate at least one of the following: the identifier of the first terminal device, the identifier of downlink transmission, the identifier of uplink transmission, the identifier of QFI, the identifier of DRB, the identifier of APP type, the identifier of APP stream, the identifier of APP, or the identifier of PDU session.
[0198] In some implementations, the communication device may include modules, units, or means for performing the methods / operations / steps / actions described in the third aspect and any possible implementation of the third aspect. These modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software.
[0199] The device may include a processing unit and a transceiver unit. The processing unit may be used to: generate a first request, which indicates an identifier for a first process and requests the first process to be performed; the transceiver unit may be used to send the first request to a first access function.
[0200] In some implementations, the first process is the offloading of the first terminal device to the access function.
[0201] In some implementations, the first request is also used to indicate a first identifier, which corresponds to the identifier of the first process.
[0202] In some implementations, the first identifier is used to indicate at least one of the following: the identifier of the first terminal device, the identifier of downlink transmission, the identifier of uplink transmission, the identifier of QFI, the identifier of DRB, the identifier of APP type, the identifier of APP stream, the identifier of APP, or the identifier of PDU session.
[0203] In some implementations, the transceiver unit can also be used to: receive second data from the first access function, the second data being obtained by processing the first data.
[0204] In some implementations, the transceiver unit can also be used to send an eighth message to the first access function, the eighth message including the first data and the first identifier, the first data being used to obtain the second data through the first processing.
[0205] In some implementations, the communication device may include modules, units, or means corresponding to each of the methods / operations / steps / actions described in the eleventh aspect and any possible implementation of the eleventh aspect. These modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software.
[0206] The device may include a transceiver unit. The transceiver unit may be configured to: receive a first request from a first terminal device, the first request being used to indicate an identifier of the first processing, the first request being used to request the first processing; and send an eighteenth message to the first terminal device, the eighteenth message being used to indicate agreement to perform the first processing.
[0207] In some implementations, the first process is the offloading of the first terminal device to the fifth access function.
[0208] In some implementations, the first request is also used to indicate a first identifier, which corresponds to the identifier of the first process.
[0209] In some implementations, the transceiver unit can also be used to receive eighth information from the first terminal device, the eighth information including first data and a first identifier.
[0210] In some implementations, the device may further include a processing unit that can be used to perform a first processing on the first data to obtain second data.
[0211] In some implementations, the processing unit may specifically be used to: perform a first processing on the first data according to the first identifier to obtain the second data.
[0212] In some implementations, the processing unit may specifically be used to: determine the identifier of the first processing based on the first identifier; and perform a first processing on the first data based on the identifier of the first processing to obtain the second data.
[0213] In some implementations, the transceiver unit can also be used to send second data to the first core network function.
[0214] In some implementations, the transceiver unit can also be used to receive sixth information from the first core network function, the sixth information including first data and a first identifier.
[0215] In some implementations, the processing unit can also be used to: perform a first process on the first data to obtain the second data.
[0216] In some implementations, the processing unit may specifically be used to: perform a first processing on the first data according to the first identifier to obtain the second data.
[0217] In some implementations, the processing unit may specifically be used to: determine the identifier of the first processing based on the first identifier; and perform a first processing on the first data based on the identifier of the first processing to obtain the second data.
[0218] In some implementations, the transceiver unit can also be used to send second data to the first terminal device.
[0219] In some implementations, the first identifier is used to indicate at least one of the following: the identifier of the first terminal device, the identifier of downlink transmission, the identifier of uplink transmission, the identifier of QFI, the identifier of DRB, the identifier of APP type, the identifier of APP stream, the identifier of APP, or the identifier of PDU session.
[0220] In some implementations, the communication device may include modules, units, or means for performing the methods / operations / steps / actions described in the twelfth aspect and any possible implementation of the twelfth aspect, which may be hardware circuits, software, or a combination of hardware circuits and software.
[0221] The device may include a transceiver unit. The transceiver unit may be configured to: send a first request to a fifth access function, the first request being used to indicate an identifier of the first processing, the first request being used to request the first processing; and receive an eighteenth message from the fifth access function, the eighteenth message being used to indicate agreement to perform the first processing.
[0222] In some implementations, the first process is the offloading of the first terminal device to the fifth access function.
[0223] In some implementations, the first request is also used to indicate a first identifier, which corresponds to the identifier of the first process.
[0224] In some implementations, the transceiver unit can also be used to send eighth information to the fifth access function, the eighth information including first data and a first identifier.
[0225] In a sixth aspect, a computer-readable storage medium is provided, on which a computer program or instructions are stored, which, when executed, cause the first aspect and any possible method of the first aspect to be performed (or implemented), or cause the second aspect and any possible method of the second aspect to be performed (or implemented), or cause the third aspect and any possible method of the third aspect to be performed (or implemented), or cause the eleventh aspect and any possible method of the eleventh aspect to be performed (or implemented), or cause the third aspect and any possible method of the third aspect to be performed (or implemented).
[0226] In a seventh aspect, a computer program product is provided, comprising a computer program or instructions that, when executed, cause the first aspect and any possible method of the first aspect to be performed (or implemented), or cause the second aspect and any possible method of the second aspect to be performed (or implemented), or cause the third aspect and any possible method of the third aspect to be performed (or implemented), or cause the eleventh aspect and any possible method of the eleventh aspect to be performed (or implemented), or cause the third aspect and any possible method of the third aspect to be performed (or implemented).
[0227] Eighthly, a communication apparatus is provided, comprising a processor configured to execute (or implement) any of the possible methods of the first aspect, or any of the possible methods of the second aspect, or any of the possible methods of the third aspect, or any of the possible methods of the eleventh aspect and any of the possible methods of the eleventh aspect, or any of the possible methods of the third aspect and any of the possible methods of the third aspect, by executing a computer program (or computer-executable instructions) stored in a memory, and / or by logic circuitry.
[0228] In one possible implementation, the device also includes a memory. In another possible implementation, the processor and memory are integrated together. In yet another possible implementation, the memory is located outside the communication device. The processor may include one or more processors.
[0229] In one possible implementation, the communication device further includes a communication interface for communicating with other devices, such as transmitting or receiving data and / or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.
[0230] In one implementation, the communication device of the fourth, fifth, or eighth aspect mentioned above can be a chip or a chip system.
[0231] Ninth aspect, a chip is provided, including a processor, for calling a computer program or computer instructions in memory to cause any implementation of the first aspect to be executed (or implemented), or to cause any implementation of the second aspect to be executed (or implemented), or to cause any implementation of the third aspect to be executed (or implemented), or to cause the eleventh aspect and any possible method of the eleventh aspect to be executed (or implemented), or to cause the third aspect and any possible method of the third aspect to be executed (or implemented).
[0232] In some implementations, the processor is coupled to the memory via an interface.
[0233] In a tenth aspect, a communication system is provided, including a first access function and a second access function, wherein the first access function is used to perform the first aspect and any possible implementation thereof, and the second access function is used to perform the second aspect and any possible implementation thereof.
[0234] In some implementations, the communication system further includes a first terminal device, and a first measurer is used to perform the third aspect described above and any possible implementation thereof.
[0235] The description of the beneficial effects of any of the second to tenth aspects can be referred to the description of the beneficial effects of the first aspect.
[0236] Eleventhly, a communication method is provided. The execution entity of the method provided in the eleventh aspect can be a fifth access function. Unless otherwise specified, the fifth access function in this application can refer to the access network device itself capable of implementing the fifth access function, or to components within the access network device (e.g., processor, chip, or chip system), or it can be a logic module or software capable of implementing all or part of the fifth access function. For ease of description, the fifth access function will be used as an example in the following description.
[0237] The method includes: receiving a first request from a first terminal device, the first request being used to indicate an identifier of the first process, the first request being used to request the first process to be performed; and sending an eighteenth message to the first terminal device, the eighteenth message being used to indicate consent to the first process.
[0238] Based on the above scheme, the first terminal device can request the fifth access network element to perform auxiliary calculations, thereby effectively reducing the computational load of the first terminal device.
[0239] In some implementations, the first process is the offloading of the first terminal device to the fifth access function.
[0240] In some implementations, the first request is also used to indicate a first identifier, which corresponds to the identifier of the first process.
[0241] In some implementations, the method further includes receiving eighth information from the first terminal device, the eighth information including first data and a first identifier.
[0242] In some implementations, the method further includes: performing a first process on the first data to obtain the second data.
[0243] In some implementations, the first data is processed to obtain the second data, including: processing the first data according to a first identifier to obtain the second data.
[0244] In some implementations, the first data is processed according to the first identifier to obtain the second data, including: determining the identifier of the first processing according to the first identifier; and processing the first data according to the identifier of the first processing to obtain the second data.
[0245] In some implementations, the method also includes sending second data to the first core network function.
[0246] In some implementations, the method further includes receiving sixth information from a first core network function, the sixth information including first data and a first identifier.
[0247] In some implementations, the method further includes: performing a first process on the first data to obtain the second data.
[0248] In some implementations, the first data is processed to obtain the second data, including: processing the first data according to a first identifier to obtain the second data.
[0249] In some implementations, the first data is processed according to the first identifier to obtain the second data, including: determining the identifier of the first processing according to the first identifier; and processing the first data according to the identifier of the first processing to obtain the second data.
[0250] In some implementations, the method further includes sending second data to the first terminal device.
[0251] In some implementations, the first identifier is used to indicate at least one of the following: the identifier of the first terminal device, the identifier of downlink transmission, the identifier of uplink transmission, the identifier of QFI, the identifier of DRB, the identifier of APP type, the identifier of APP stream, the identifier of APP, or the identifier of PDU session.
[0252] In its twelfth aspect, a communication method is provided. The method provided in the twelfth aspect can be executed by a first terminal device. Unless otherwise specified, the first terminal device in this application can refer to the first terminal device itself, a component within the first terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the first terminal device. For ease of description, the following description uses a first terminal device as an example.
[0253] The method includes: sending a first request to a fifth access function, the first request indicating an identifier of the first process, the first request requesting the first process to be performed; and receiving an eighteenth message from the fifth access function, the eighteenth message indicating consent to perform the first process.
[0254] In some implementations, the first process is the offloading of the first terminal device to the fifth access function.
[0255] In some implementations, the first request is also used to indicate a first identifier, which corresponds to the identifier of the first process.
[0256] In some implementations, the method further includes sending eighth information to the fifth access function, the eighth information including first data and a first identifier.
[0257] In a thirteenth aspect, a communication system is provided, including a fifth access function and a first terminal device, wherein the fifth access function is configured to perform the eleventh aspect and any possible implementation thereof, and the first terminal device is configured to perform the twelfth aspect and any possible implementation thereof. Attached Figure Description
[0258] Figure 1 This is a schematic diagram of a communication system.
[0259] Figure 2 This is a schematic flowchart of a communication method.
[0260] Figure 3 This is a schematic flowchart of a communication method provided in an embodiment of this application.
[0261] Figure 4 This is a schematic diagram of a communication system provided in an embodiment of this application.
[0262] Figure 5 This is a schematic flowchart illustrating another communication method provided in an embodiment of this application.
[0263] Figure 6 This is a schematic flowchart of another communication method 600 provided in the embodiments of this application.
[0264] Figure 7 This is a schematic diagram of another communication system provided in an embodiment of this application.
[0265] Figure 8 This is a schematic block diagram of a communication device provided in an embodiment of this application.
[0266] Figure 9 This is a schematic diagram of another communication device provided in an embodiment of this application.
[0267] Figure 10 This is a schematic diagram of a chip system provided in an embodiment of this application.
[0268] Figure 11 This is a schematic diagram of another chip system provided in an embodiment of this application. Detailed Implementation
[0269] In this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.
[0270] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Here, a, b, and c can be single or multiple.
[0271] In this application, the terms "first," "second," and various numerical designations (e.g., #1, #2, etc.) indicate distinctions made for ease of description and are not intended to limit the scope of the embodiments of this application. For example, they may distinguish different messages, rather than describing a specific order or sequence. It should be understood that such descriptions can be interchanged where appropriate to describe solutions other than those in the embodiments of this application.
[0272] In this application, descriptions such as "when," "under the circumstances," and "if" all refer to the fact that the device will take corresponding actions under certain objective circumstances. They are not time-limited, nor do they require the device to perform a judgment action during implementation, nor do they imply any other limitations.
[0273] In this application, "instruction" or "for instruction" can include both direct and indirect instruction. When describing instruction information as being used to instruct A, it may include whether the instruction information directly or indirectly instructs A, but does not necessarily mean that the instruction information carries A.
[0274] The indication methods involved in the embodiments of this application should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. Moreover, the sending period and / or sending time of these sub-information can be the same or different. This application does not limit the sending method, for example.
[0275] The "instruction information" in the embodiments of this application can be an explicit instruction, that is, a direct instruction through signaling, or an instruction obtained by combining other rules or parameters with the parameters indicated by the signaling, or by deduction. It can also be an implicit instruction, that is, an instruction obtained based on rules or relationships, or based on other parameters, or by deduction. This application does not specifically limit it in this regard.
[0276] In this application, "protocol" can refer to standard protocols in the field of communications, such as 5G protocols, NR protocols, and related protocols applied in future communication systems; this application does not limit this term. "Predefined" can include predefined terms, such as protocol definitions. "Preconfiguration" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device; this application does not limit the implementation method.
[0277] In this application, "communication" can also be described as "data transmission," "information transmission," "data processing," etc. "Transmission" includes "sending" and "receiving." For example, transmission can be uplink transmission, such as a terminal device sending a signal to an access network device; transmission can also be downlink transmission, such as an access network device sending a signal to a terminal device; transmission can also be sidelink transmission, such as a terminal device sending a signal to another terminal device. For example, "transmission" can be air interface level transmission, or it can be signal transmission from a chip input (I) / output (O) port, rather than air interface level transmission.
[0278] In this application, terms such as "message," "information," "signal," or "information element (IE)" can be used interchangeably. There are no restrictions on the name of the message or information, as long as it can achieve the corresponding function.
[0279] "Sending information to XX (device)" can be understood as the destination of the information being that device. This can include sending information directly or indirectly to that device. "Receiving information from XX (device), or receiving information from XX (device)" can be understood as the source of the information being that device. This can include receiving information directly or indirectly from that device. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood in a similar way, and will not be repeated here. In addition, "sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface. In other words, "sending" or "receiving" can be performed between devices, for example, between access network devices and terminal devices through an air interface. "Sending" or "receiving" can also be performed within a device, for example, between components, modules, chips, software modules, or hardware modules within the device through a bus, wiring, or interface.
[0280] In this application, terms such as "exemplarily" and "for example" are used to indicate examples, illustrations, or descriptions to present concepts in a specific manner. Any embodiment or design described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. In the embodiments of this application, the terms "of," "corresponding (relevant)," "corresponding," and "associate" may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinctions are emphasized.
[0281] In this application, configuration can be signaling configuration or can be described as configuration signaling. For example, signaling configuration includes configuration using signaling sent by network devices, which can be radio resource control (RRC) messages, downlink control information (DCI) messages, or system information blocks (SIBs). Another example is signaling configuration between network devices. These network devices can include access network devices, core network devices, or management plane devices, etc. Optionally, signaling configuration can also be pre-configured signaling to terminal devices or network devices, or configured to terminal devices or network devices through pre-configuration. Here, pre-configuration refers to defining or configuring the values of corresponding parameters in advance using a protocol, and storing them in the terminal device or network device during communication. The pre-configured messages can be modified or updated when the terminal device or network device is connected to the network.
[0282] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. Each system may include devices, components, modules, etc., other than those illustrated, and / or may not include all and all of the devices, components, modules, etc. discussed in conjunction with the accompanying drawings.
[0283] The business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.
[0284] In the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The terms "comprising," "including," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.
[0285] The technical solutions of this application embodiment can be applied to various communication systems, including but not limited to: Long Term Evolution (LTE) systems, New Radio (NR) systems, and other fifth-generation (5G) systems. th This includes various mobile communication systems such as 5G, narrowband Internet of Things (NB-IoT), enhanced machine-type communication (eMTC), enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), satellite communication systems, LTE-machine-to-machine (LTE-M) systems, vehicle-to-everything (V2X), the Internet of Things (IoT), the industrial internet, and other systems that evolve after 5G, such as future mobile communication systems.
[0286] The technical solutions in this application will now be described with reference to the accompanying drawings.
[0287] Figure 1 This is a schematic diagram of a communication system 100. (For example...) Figure 1 As shown, the communication system 100 includes a wireless access network 110 and a core network 120. Optionally, the communication system 100 may also include an Internet 130. The wireless access network 110 may include at least one access network device (such as...). Figure 1 111a and 111b in the above), may also include at least one terminal device (such as Figure 1(112a-112j in the original text). The terminal device connects to the access network device wirelessly. The access network device connects to the core network 120 wirelessly or via a wired connection. The core network 120 may include one or more core network devices. The core network device and the access network device may be independent physical devices, or the functions of the core network device and the logical functions of the access network device may be integrated on the same physical device, or a single physical device may integrate some of the functions of the core network device and some of the functions of the access network device. Terminal devices and access network devices can be interconnected via wired or wireless means. Terminal devices can communicate wirelessly with each other, with each other, and with each other via air interface resources. For example, air interface resources may include at least one of time-domain resources, frequency-domain resources, code resources, and spatial resources. Figure 1 This is just an illustration; the communication system 100 may also include other access network equipment, such as wireless repeaters and wireless backhaul devices. Figure 1 It is not shown in the middle.
[0288] The core network, as the core component of a mobile communication network, plays a crucial role in connecting the upper and lower layers. For example, the core network is primarily responsible for handling end-user mobility management, session management, and data transmission (core functions). For example, a mobile communication network can be divided into three parts: the base station subsystem, the network subsystem, and the system support component. For instance, the system support component may include security management, etc. The core network can be located within the network subsystem. For example, the main function of the core network may be to route call requests or data requests from the air interface to different networks.
[0289] For example, the core network's functions may include providing user connectivity, managing users, carrying services, or providing interfaces to external networks as a bearer network, etc. For instance, user connectivity may include mobility management (MM), calling management (CM), switching / routing, and recording notifications (combined with intelligent network services to establish connections to intelligent network peripheral devices). As another example, user management may include user descriptions, quality of service (QoS), user accounting, virtual home environment (VHE) (providing a virtual home environment through dialogue with the intelligent network platform), and security (with corresponding security measures provided by the authentication center, including security management of mobile services and security processing of external network access). Furthermore, bearer connectivity may include external public switched telephone network (PSTN), external circuit-switched data networks and packet-switched data networks, the Internet and enterprise intranets, and short message service (SMS) servers, etc. For example, the basic services that the core network can provide include mobile office, e-commerce, communication, entertainment, travel, location-based services, telemetry, or simple messaging services, etc.
[0290] The core network may include one or more network functions (NFs). For example, at least one NF may include an access and mobility management function network element, a session management network element, or a user plane function network element, etc.
[0291] Access and mobility management (AMM) network elements, also known as access and mobility management function (AMF) network elements, are primarily used for terminal attachment and tracking area update procedures in mobile networks. AMM network elements can provide non-access stratum (NAS) messages, complete registration management, connection management, reachability management, allocate tracking area lists (TA lists), conduct lawful interception, grant access authorization, authenticate, and manage mobility, and transparently route session management (SM) messages to the session management network element. In 5G communication systems, AMM network elements can be access and mobility management functions (AMF). In future communication systems, AMM network elements may remain AMF network elements or have other names; this application does not limit this.
[0292] Session management network elements, also known as session management function network elements, are used for session and bearer management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating and managing Internet Protocol (IP) addresses for the UE and selecting user plane function network elements that provide packet forwarding capabilities. For example, a session management network element can select a suitable user plane function network element for the UE based on the UE's request and the policy control information of the policy control network element, establish a session with that user plane function network element, and generate QoS rules and charging rules. Session management network elements can control the data forwarding and processing behavior of user plane function network elements. In 5G communication systems, the session management network element can be a session management function (SMF). In future communication systems, the session management network element may still be an SMF network element, or it may have other names; this application is not limited to these.
[0293] User plane function network elements (MPFs) can be used to process user packets, such as forwarding, billing, and lawful interception. Furthermore, MPFs can handle user plane data packet routing, forwarding, QoS flow processing, threshold control, traffic monitoring, authentication, data packet detection, and reporting. MPFs can also manage UE IP addresses and core network (CN) tunnel information. Located in the 5G core network user plane, MPFs provide high-speed, efficient, and flexible data transmission services to the UE. In addition, MPFs can perform data packet filtering, traffic shaping, and billing according to control plane instructions, enabling fine-grained management and control of user data flows. MPFs can connect to access network equipment via the N3 interface and to the data network via the N6 interface, thus enabling data transmission between the UE and the external data network. MPFs can also be referred to as Protocol Data Unit (PDU) session anchors (PSAs). In 5G communication systems, user plane function network elements can be user plane functions (UPF). In future communication systems, user plane function network elements can still be UPF network elements, or they can have other names. This application does not limit this.
[0294] Access network equipment is sometimes also called radio access network (RAN) equipment, access network (AN), RAN node, or AN node. For ease of description, access network equipment may be simply referred to as RAN below. Access network equipment can be a radio base station in the network or a network element in the radio access network. Access network equipment can be responsible for air interface-related functions. For example, radio link maintenance functions may include maintaining the radio link with terminal equipment, and may also include protocol conversion between radio link data and Internet Protocol (IP) data; radio resource management functions may include establishing and releasing radio links, scheduling and allocating radio resources, etc.; and some mobility management functions may include configuring terminals to perform measurements, evaluating terminal radio link quality, and deciding on terminal handover between cells, etc.
[0295] In systems employing different wireless access technologies, the names of devices with access network functionality may differ. For ease of description, embodiments of this application may collectively refer to devices providing wireless communication access functionality to terminal devices as base stations. In embodiments of this application, access network devices include, but are not limited to: various forms of macro base stations (such as...) Figure 1 111a), micro base stations or indoor stations (such as Figure 1The types of base stations include 111b), pico base stations, micro / pico base stations, balloon base stations, relay stations, and access points. Among these, a micro base station can be referred to as a small base station. For example, a small base station can include a small next-generation base station node (gNB) or a small node B (NB). Access network equipment can include base transceiver stations (BTS) in Global System for Mobile Communication (GSM) or Code Division Multiple Access (CDMA) networks, Node Bs (NBs) in Wideband Code Division Multiple Access (WCDMA), evolved Node Bs (eNBs or eNodeBs) in LTE, radio controllers in cloud radio access networks (CRAN) scenarios, access network equipment in future public land mobile networks (PLMNs), access points (APs), radio relay nodes, radio backhaul nodes, transmission points (TPs) or transmission reception points (TRPs) in Wi-Fi systems, and more. It can also include next-generation base station nodes in 5G systems. Access network equipment (GNB) refers to network nodes that constitute a NodeB (gNB) or transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, network nodes such as baseband units (BBU) or distributed units (DU) that constitute a GNB or transmission point, and may also include access network equipment, servers, wearable devices, or vehicle-mounted equipment in future mobile communication systems and other networks that evolve after 5G. Access network equipment can also be modules or units that perform some functions of a base station; for example, it can be a central unit (CU) or a DU. Furthermore, access network equipment can be understood as a collective term for all network-side equipment (including sites); for example, multiple sites can be collectively referred to as access network equipment. A site refers to a transmission node located in a specific physical location. In other words, access network equipment conceptually includes sites.
[0296] In this embodiment, the device for implementing the function of the access network device can be the access network device itself, or it can be a device that supports the access network device in implementing the function, such as a chip system or a chip. This device can be installed in the access network device. The chip system can be composed of chips, or it can include chips and other discrete components.
[0297] In another possible scenario, multiple access network devices collaborate to assist the terminal in achieving wireless access, with each access network device performing a portion of the base station's functions. For example, the access network devices can be CU, DU, CU (control plane, CP), CU (user plane, UP), or radio unit (RU), etc. CU and DU can be configured separately or included in the same network element, such as in a BBU. RU can be included in radio equipment or radio units, such as in a remote radio unit (RRU), active antenna unit (AAU), or remote radio head (RRH).
[0298] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an open radio access network (O-RAN) system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules. The embodiments of this application do not limit the specific technology or specific device form used in the access network equipment.
[0299] The terminal device can be a device that provides voice and / or data connectivity to the user; it can also be a device with wireless connectivity. The terminal device itself can be completely independent of the mobile user. User-related information can be stored in a subscriber identity module (SIM) card. For example, this SIM card can be used on a mobile terminal.
[0300] For example, terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as ships); and it can also be deployed in the air (such as airplanes, balloons, and satellites). Terminal equipment can also be referred to as user equipment (UE), access terminal, terminal, subscriber unit, user station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, wireless network equipment, user agent, or user device. In this application embodiment, terminal devices include, but are not limited to: cellular phones, mobile phones, wireless data cards, wireless modems, tablets, laptop computers, notebook computers, handheld computers, mobile internet devices (MIDs), computers with wireless transceiver capabilities, cordless phones, session initiation protocol (SIP) phones, smartphones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handsets with wireless communication capabilities, computing devices or other devices connected to wireless modems, in-vehicle devices (e.g., cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), wearable devices (e.g., smartwatches, smart bracelets, pedometers, smart glasses, etc.), satellite terminals, terminal devices in the Internet of Things or the Internet of Vehicles, as well as any form of terminal in future networks, relay user equipment, or terminals in future evolved PLMNs, etc.Terminal devices can also be virtual reality (VR) devices, augmented reality (AR) devices, smart point-of-sale (POS) machines, customer-premises equipment (CPE), light UE, reduced capability UE (RedCap UE), machine-type communication (MTC) terminals, terminal devices in industrial control, terminal devices in self-driving, terminal devices in telemedicine or telehealth services, terminal devices in smart grids, wireless terminals in transportation safety, terminal devices in smart cities, terminal devices in smart homes, tactile terminal devices, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), smart robots, robotic arms, workshop equipment, wireless terminals in self-driving, or flying devices (e.g., smart robots, hot air balloons, drones, airplanes), etc. The terminal device can also be a vehicle device, such as a complete vehicle device, an in-vehicle module, an in-vehicle chip, an on-board unit (OBU), or a telematics box (T-BOX). The terminal device can also be other devices with terminal functions; for example, it can be a device that functions as a terminal in device-to-device (D2D) communication. This application does not limit the scope of the embodiments in this regard.
[0301] For example, the terminal device side may include a physical layer (PHY), a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP), an RRC layer, or a service data adaptation protocol (SDAP), etc.
[0302] In this application embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing the functions, such as a chip or chip system. This device can be installed in the terminal device. The chip system can consist of chips or include chips and other discrete components. In the technical solution of this application embodiment, the device for implementing the functions of the terminal device is referred to as the terminal device, which can also be called a terminal. The following description may use a UE (User Equipment) as an example to illustrate the technical solution provided in this application embodiment.
[0303] For example, the terminal side may include user plane protocols and control plane protocols. The base station side may include user plane protocols and control plane protocols. The various layers of the terminal side and the base station side can be interconnected to exchange information.
[0304] The roles of base stations and terminals can be relative, for example, Figure 1 The helicopter or drone 112i can be configured as a mobile base station. For terminals 112j that access the wireless access network 110 via 112i, terminal 112i is a base station; however, for base station 111a, 112i is a terminal, meaning that 111a and 112i communicate via a wireless air interface protocol. Of course, 111a and 112i can also communicate via a base station-to-base station interface protocol; in this case, relative to 111a, 112i is also a base station. Therefore, both base stations and terminals can be collectively referred to as communication devices. Figure 1 111a and 111b in the diagram can be referred to as communication devices with base station functionality. Figure 1 The 112a-112j in the text can be referred to as communication devices with terminal functions.
[0305] Access network devices and terminal devices can communicate via wireless links. The transmission link from the access network device to the terminal device can be called a downlink (DL) or downlink channel, used for transmitting downlink signals. The transmission link from the terminal device to the access network device can be called an uplink (UL) or uplink channel, used for transmitting uplink signals. The transmission link from the terminal device to the terminal device can be called a sidelink (SL) or sidelink channel. In this embodiment, multiple access network devices can send information to multiple different terminal devices and receive information from multiple different terminal devices; multiple access network devices can also send information to the same terminal device and receive information from the same terminal device, and this application is not limited in this respect.
[0306] The embodiments of this application are applicable to both homogeneous and heterogeneous network scenarios. This application does not limit the specific form of transmission; for example, it can be applied to multi-point cooperative transmission between macro base stations, micro base stations, or macro base stations and micro base stations, and can be applied to frequency division duplex (FDD) or time division duplex (TDD) systems. The embodiments of this application can be applied to low-frequency scenarios as well as high-frequency scenarios, such as terahertz and optical communication.
[0307] Figure 2 This is a schematic flowchart of a communication method 200. Method 200 can realize PDU session and tunnel establishment, as well as the transmission of uplink and / or downlink data. The following section combines... Figure 2 Method 200 is introduced.
[0308] S210, the UE sends a PDU session establishment request to the SMF. Correspondingly, the SMF receives the PDU session establishment request from the UE.
[0309] In some examples, the UE can send a PDU session establishment request to the AMF, which can then forward the request to the SMF. In other examples, the UE can send the PDU session establishment request directly to the SMF without the AMF intermediary.
[0310] For example, a PDU session establishment request may include information such as a PDU session identifier (ID). A PDU session establishment request can be used to request the establishment of a PDU session.
[0311] S220, the SMF sends an N4 session establishment request to the UPF. Correspondingly, the UPF receives the N4 session establishment request from the SMF.
[0312] The N4 session establishment request can be used to request the establishment of a PDU session. The N4 session establishment request can carry CN tunnel information. For example, the CN tunnel information may include a tunnel endpoint identifier (TEID) and / or a RAN IP address. Unless otherwise specified, the IP address will be referred to as "IP" below.
[0313] In some examples, before S220, method 200 may also include: SMF selects UPF.
[0314] S230, the SMF receives an N4 session establishment response from the UPF. Correspondingly, the UPF sends an N4 session establishment response to the SMF.
[0315] The N4 session establishment response may carry CN tunnel information. For example, the N4 session establishment response may indicate acceptance of the N4 session establishment request. Exemplarily, the CN tunnel information may include TEID and / or UPFIP.
[0316] S240, the SMF sends an N2PDU establishment request to the RAN. Correspondingly, the RAN receives the N2PDU establishment request from the SMF.
[0317] The N2PDU establishment request may include the PDU session ID and UPFIP.
[0318] S250, RAN establishes a General Packet Radioservice Tunneling Protocol (GTP) tunnel with UPF.
[0319] The GTP tunnel may include the user plane part of GTP (GTP-U).
[0320] For example, a GTP tunnel can be associated with a UE identifier (ID), a PDU session ID, and a TEID.
[0321] S260, the SMF sends the UE route selection policy (URSP) rules to the UE. Correspondingly, the UE receives the URSP rules from the SMF.
[0322] For example, the URSP rule may include a mapping between triples and PDU session IDs. The triples may include the protocol type (e.g., Transmission Control Protocol (TCP) or User Datagram Protocol (UDP)), the destination IP address, and the destination port number.
[0323] S270, RAN and UE establish DRB.
[0324] For example, the DRBID corresponds to the PDU session ID.
[0325] Thus, through the processes described in S210-S270 above, a PDU session and a GTP tunnel can be established. S210-S270 are merely examples; those skilled in the art will understand that the methods for establishing a PDU session and a GTP tunnel are not limited to S210-S270 and other methods are possible. Furthermore, establishing a PDU session and a GTP tunnel may also include other processes; for example, there may be a mapping relationship between the PDU session ID and SDAPID. Similarly, there may be a mapping relationship between QFI and DRBID.
[0326] The following is a schematic diagram of the uplink and downlink data transmission processes.
[0327] S280, the UE sends uplink data to the RAN. Correspondingly, the RAN receives the uplink data from the UE.
[0328] S282, the RAN sends uplink data to the UPF. Correspondingly, the UPF receives uplink data from the RAN.
[0329] For example, the RAN can determine the UEID and DRBID corresponding to the uplink data sent by the UE. The RAN can obtain the TEID through the mapping between the UEID and DRBID, and transmit the uplink data to the UPF based on the dedicated tunnel corresponding to the TEID. For example, the RAN can determine the SDPID corresponding to the uplink data through the mapping relationship between DRBID and SDPID, thereby determining the SDAP entity. As another example, the RAN can determine the PDU session ID and UPFIP through the DRBID.
[0330] S284, UPF processes uplink data.
[0331] For example, after receiving uplink data through the dedicated tunnel, the UPF obtains the TEID of the uplink data, determines that the uplink data is the UL data corresponding to the UE ID through the TEID, and then forwards it to the APP server in the corresponding data network (DN) and performs corresponding billing for the UE.
[0332] S290, the UPF sends downlink data to the RAN. Correspondingly, the RAN receives downlink data from the UPF.
[0333] For example, the UPF receives a DL data packet from the DN sent by the APP server to a certain UE, maps it to the dedicated tunnel corresponding to the UE according to the UE ID, and transmits it to the base station serving the corresponding UE, such as the RAN, through the dedicated tunnel.
[0334] S292, the RAN sends downlink data to the UE. Correspondingly, the UE receives downlink data from the RAN.
[0335] For example, after receiving the downlink data, the RAN determines the corresponding UE ID and DRB ID based on the TEID, and sends the downlink data to the UE corresponding to the UE ID via the air interface on the radio data bearer corresponding to the DRBID.
[0336] As mentioned earlier, emerging applications such as XR and AI require significant computational power from terminal devices, which is often insufficient to support such demands. In some examples, when the local computational load on a terminal device (e.g., an XR terminal) is high, a specific core network node can be requested to handle the computation. This core network node can be deployed closer to the terminal device. This reduces communication latency between the various application servers on that core network node and the terminal device. This approach can also be termed multi-access edge computing (MEC).
[0337] However, the MEC solution only moves the core network nodes to the edge of the network and cannot share the computing load of the terminal devices.
[0338] Therefore, how to effectively reduce the computing load of terminal devices is an urgent problem to be solved.
[0339] Figure 3 This is a schematic flowchart illustrating a communication method 300 provided in an embodiment of this application. Method 300 can effectively reduce the computational load on terminal devices. Optional operations in method 300 include... Figure 3 The middle part is indicated by a dashed line. The following is in conjunction with... Figure 3 Method 300 is introduced.
[0340] S320, the second access function receives first information from the first access function. Correspondingly, the first access function sends the first information to the second access function. This first information can be used to request the second access function to perform the first processing.
[0341] S330, RAN2 sends a second message to RAN1. Correspondingly, RAN1 receives the second message from RAN2. This second message can be used to instruct RAN2 to agree to perform the first process.
[0342] For example, the first access function may correspond to one or more access network devices (such as RAN1). For instance, the first access function may include one or more access network devices. As another example, the first access function may be a component (e.g., a processor, chip, or chip system) within one or more access network devices. Yet another example, the first access function may be a logic module or software capable of implementing all or part of the functions of one or more access network devices. For example, the first access function may be DU. For ease of description, the first access function is RAN, denoted as RAN1, as an example below.
[0343] For example, the second access function may correspond to one or more access network devices (such as RAN2). For instance, the second access function may include one or more access network devices. Another example is that the second access function may be a component (e.g., a processor, chip, or chip system) within one or more access network devices. Yet another example is that the second access function may be a logic module or software capable of implementing all or part of the functions of one or more access network devices. For example, the second access function may be a DU. The first access function and the second access function may be the same DU or different DUs; this application does not limit this. For ease of description, the second access function is denoted as RAN2 below, using RAN as an example.
[0344] In some possible implementations, RAN1 and RAN2 can be located in different access network devices. In other possible implementations, RAN1 and RAN2 can be located in the same access network device.
[0345] The following are some examples of S320.
[0346] Optionally, the first information is used to indicate the identifier of the first process. The first information can be direct indication information, for example, the first information may include the identifier of the first process. The first information can also be indirect indication information, for example, the first information may include information related to the identifier of the first process, so that RAN2 can determine the identifier of the first process based on the information related to the identifier of the first process.
[0347] For example, the identifier of the first process may include a processing identifier (processingID), an action identifier (actionID), or other forms, which are not limited in this application. For ease of description, the identifier of the first process is described below as actionID, which can be denoted as actionID1. However, those skilled in the art will understand that the identifier of the first process is not limited to the form of actionID.
[0348] Optionally, the first information is used to request RAN2 to perform the first process. The first information may explicitly request RAN2 to perform the first process. For example, the first information may include first request information, which is used to request RAN2 to perform the first process. The first information may also implicitly request RAN2 to perform the first process.
[0349] This application does not limit the specific name of the first information; the first information may also be referred to as an auxiliary calculation request, an auxiliary processing request, a request information, or other names. For ease of description, the following description takes a UE as the first terminal device, and is denoted as UE1.
[0350] Optionally, the first processing is the processing offloaded from UE1 to RAN2. In other words, the first processing is the processing transferred from UE1 to RAN2. For example, the first processing is a process that UE1 can execute, but UE1 does not perform the first processing on some data; instead, RAN2 performs the first processing on this data. Or, for another example, the first processing is a process that UE1 originally needed to execute, but UE1 does not perform the first processing on some data; instead, RAN2 performs the first processing on this data. Exemplarily, RAN2 is an access function that provides services to UE1. For example, RAN2 can provide auxiliary computing services to UE1.
[0351] For example, the first process can be used to process the data of UE1. The data of UE1 can be data sent by UE1 or data to be sent to UE1.
[0352] For example, the execution result of the first processing in UE1 and the execution result of RAN2 are the same or similar. For instance, suppose UE1 performs the first processing on data 1 to obtain data 2; RAN2 performs the first processing on data 1 to obtain data 3. Data 2 and data 3 can be the same or similar.
[0353] This application does not limit the specific name of the first process. For example, the first process may be called the first calculation, the first calculation task, the first auxiliary calculation, the first auxiliary calculation task, or other names.
[0354] In some possible implementations, UE1 does not perform the first process if RAN2 performs the first process. In other possible implementations, RAN2 does not perform the first process if UE1 performs the first process.
[0355] Optionally, the first information is used to indicate a first time period and / or a second time period.
[0356] For example, the first process can be offloaded from UE1 to RAN2 within a certain time period. For instance, during the first time period, RAN2 executes the first process, while UE1 does not. Or, for another example, during the second time period, UE1 executes the first process, while RAN2 does not. The first and second time periods can be different. For example, the first and second time periods may not overlap. The first and second time periods may not overlap at all, meaning that any moment within the first time period does not belong to the second time period. Alternatively, the first and second time periods may not overlap partially, meaning that some moments within the first time period do not belong to the second time period, while other moments do.
[0357] In some examples, "UE1 does not perform the first processing" includes UE1 not performing the first processing on a portion of the data. Here, "partial data" can be understood as a portion (hereinafter referred to as data B) of all the data that UE1 would normally need to process (hereinafter referred to as data A). For example, UE1 may not perform the first processing on data B. Correspondingly, "RAN2 performs the first processing" may include RAN2 performing the first processing on a portion of the data. For example, RAN2 may perform the first processing on data B. For ease of description, the data in data A other than data B is denoted as data C. That is, data A includes data B and data C. For example, during a first time period, UE1 does not perform the first processing on data B, but may perform the first processing on data C. For example, during a first time period, RAN2 performs the first processing on data B, but may not perform the first processing on data C.
[0358] In other examples, "UE1 does not perform first processing" means that UE1 does not perform first processing on all data. "RAN2 performs first processing" means that RAN2 performs first processing on all data. Here, "all data" can be understood as all the data that UE1 would normally need to process, such as data A mentioned above.
[0359] In some examples, "RAN2 does not perform first processing" means that RAN2 does not perform first processing on a portion of the data. Here, "partial data" can be understood as a portion (e.g., data B) of all the data that UE1 would normally need to process (e.g., data A). For example, RAN2 may not perform first processing on data B. Correspondingly, "UE1 performs first processing" may include UE1 performing first processing on a portion of the data. For example, UE1 may perform first processing on data B. For ease of description, the data in data A other than data B is denoted as data C. That is, data A includes data B and data C. Exemplarily, RAN2 does not perform first processing on data B, but may perform first processing on data C. Exemplarily, UE1 performs first processing on data B, but may not perform first processing on data C.
[0360] In other examples, "RAN2 does not perform first processing" means that RAN2 does not perform first processing on all data. "UE1 performs first processing" means that UE1 performs first processing on all data. Here, "all data" can be understood as all the data that UE1 would normally need to process, such as data A mentioned above.
[0361] For example, UE1 may include one or more terminal devices.
[0362] Optionally, UE1 is used to communicate with RAN1. For example, RAN1 can serve UE1. Or, for example, UE1 can be located within a cell of RAN1.
[0363] In some examples, UE1 can transmit data with RAN1. For example, UE1 can send data to RAN1 (e.g., first data). In other examples, UE1 can receive data from RAN1 (e.g., second data). In still other examples, UE1 can transmit signaling with RAN1. For example, UE1 can send signaling to RAN1 (e.g., a first request). In other examples, UE1 can receive signaling from RAN1 (e.g., a response to the first request).
[0364] The following are some examples of S330.
[0365] The second information can explicitly instruct RAN2 to agree to the first process. For example, the second information may include consent information that instructs RAN2 to agree to the first process. Alternatively, the second information can implicitly instruct RAN2 to agree to the first process.
[0366] For example, RAN2 can determine whether to agree to perform the first processing based on the first information. For instance, RAN2 may disagree with performing the first processing when the load is high, and agree to perform the first processing when the load is low. As another example, RAN2 may agree to perform the first processing if its capabilities support it, and refuse to perform it if its capabilities do not support it. In some possible implementations, RAN2 may send a rejection message to RAN1, indicating that RAN2 disagrees with (or does not accept, or refuses) performing the first processing. In other possible implementations, RAN2 may indicate its disagreement with performing the first processing by not responding.
[0367] This application does not limit the specific name of the second information; for example, the second information may also be called response information, consent information, or other names.
[0368] Based on the above scheme, RAN1 can request RAN2 to perform auxiliary calculations for UE1. In this way, the processing tasks of UE1 can be offloaded to RAN2, effectively reducing the computational load on UE1. For example, without the above scheme, UE1 needs to perform initial processing on some data. With the above scheme, UE1 can avoid performing initial processing on this data; instead, RAN2 can perform the initial processing. Therefore, the above scheme can effectively reduce the computational load on the terminal device.
[0369] In some possible implementations, method 300 further includes: S315, RAN1 determines RAN2. For example, S315 includes: RAN1 can select RAN2 from a plurality of RANs capable of performing auxiliary calculations for UE1 to perform auxiliary calculations for UE1. Optionally, S315 is executed before S320.
[0370] In some possible implementations, RAN1 can proactively execute S315 or S320. In some examples, RAN1 can trigger S315 or S320 itself. In other examples, RAN1 can trigger S315 or S320 without being based on any other request. For example, RAN1 can proactively select RAN2 to perform auxiliary calculations for UE1. For example, RAN1 can determine to send the first message to RAN2. In other possible implementations, RAN1 can execute S315 or S320 based on a request from UE1. For example, RAN1 can determine RAN2 based on a request from UE1. Yet another example is that RAN1 can send the first message to RAN2 based on a request from UE1.
[0371] Optionally, method 300 further includes: S310, a first access function (e.g., RAN1) receives a first request from a first terminal device (e.g., UE1). Correspondingly, the first terminal device (e.g., UE1) sends the first request to the first access function (e.g., RAN1). The first request can be used to request first processing.
[0372] Optionally, S310 is executed before S320. Optionally, S310 is executed before S315.
[0373] For example, the first request is used to indicate action ID1, which indicates a UE process requiring network assistance, such as calculation. The first request can be direct indication information; for example, the first request may include action ID1. The first request can also be indirect indication information; for example, the first request may include information related to action ID1, so that RAN2 can determine action ID1 based on the information related to action ID1.
[0374] For example, the first request is used to request that the first process be performed. For instance, the first request may be used to request RAN1 to determine the access function to perform the first process. As another example, the first request may be used to request RAN1 to determine that RAN2 will perform the first process.
[0375] This application does not limit the specific name of the first request. For example, the first request may also be called an auxiliary calculation request, an auxiliary processing request, an unloading request, a processing and unloading request, a request message, or other names.
[0376] In some possible implementations, prior to S310, method 300 also includes: UE1 generating a first request.
[0377] Optionally, S320 includes: in response to the first request, RAN1 sends first information to RAN2. Alternatively, RAN1 sends first information to RAN2 according to the first request. Optionally, S315 includes: in response to the first request, RAN1 determines RAN2. Alternatively, RAN1 determines RAN2 according to the first request. For example, RAN1 can select RAN2 which has the capability to support the first processing. Another example is that RAN1 can select RAN2 with a lower load.
[0378] Based on the above scheme, UE1 can send a first request to RAN1, thereby triggering RAN1 to send the first information to RAN2.
[0379] In some possible implementations, the first information is also used to indicate a first identifier. The first information can be direct information, for example, it may include information about the first identifier. Alternatively, the first information can be indirect information, for example, it may implicitly indicate the first identifier. Exemplarily, the first identifier is associated with UE1.
[0380] Optionally, the first request is used to indicate a first identifier. RAN1 can determine the first identifier based on the first request. For example, the first request is used to indicate action ID1 and the first identifier.
[0381] Optionally, the first identifier is used to indicate the attributes of the data. For example, if the first data carries a first identifier, then the first identifier can be used to indicate the attributes of the first data. For example, at least one of the following: the ownership, source, destination, transmission direction, or transmission mode of the first data.
[0382] For example, the first identifier is used to indicate at least one of the following: the identifier of UE1 (UE1ID), the identifier of downlink transmission, uplink transmission, QFI, DRB, APP type (APPtype), the identifier of APP flow (APPflowID), the identifier of APP (APPID), or the identifier of PDU session (PDU session ID).
[0383] For example, UE1ID may include the IP address of UE1. In some examples, UE1ID can be used to indicate at least one of the following: the origin, source, or destination of the first data. For example, in uplink transmission, UE1ID can be used to indicate the source of the first data. As another example, in downlink transmission, UE1ID can be used to indicate the destination of the first data. UE1ID can be used to indicate that the first data carrying the first identifier corresponds to UE1. Here, "the first data corresponds to UE1" can be understood as the first data originating from UE1. For example, the first data is uplink data sent by UE1. "The first data corresponds to UE1" can also be understood as the destination of the first data being UE1. For example, the first data is downlink data to be sent to UE1. "The first data corresponds to UE1" can also be understood as the first data belonging to UE1. For example, the first data is generated by UE1 or is to be used by UE1.
[0384] In other examples, at least one of the APP type, APP stream identifier, or APP identifier can be used to indicate at least one of the ownership, source, or destination of the first data. For example, the APP identifier can be used to indicate that the first data carrying the first identifier corresponds to the APP identifier. For example, the APP type can include XR, gaming, or web, etc. The APP type can be used to indicate that the first data carrying the first identifier corresponds to the APP type. The APP type can correspond to the identifiers of one or more APPs. For example, the APP stream identifier can be used to indicate that the first data carrying the first identifier corresponds to the identifier of the APP stream. The APP stream identifier can correspond to the identifiers of one or more APPs. The following example uses the APP identifier. The APP type and APP stream identifier have a correspondence with the APP identifier; therefore, examples of the APP type and APP stream identifier and the APP identifier can be found in the examples of APP identifiers, and will not be repeated here.
[0385] For example, the identifier of an app corresponds to one or more app servers. "The first data corresponds to an app server" can be understood as the first data originating from the app server. For example, the first data is downlink data sent by the app server. "The first data corresponds to an app server" can also be understood as the destination of the first data being the app server. For example, the first data is uplink data to be sent to the app server. "The first data corresponds to an app server" can also be understood as the first data belonging to the app server. For example, the first data is generated by the app server or is to be used by the app server.
[0386] In some other examples, the transmission direction of the first data includes downlink transmission or uplink transmission. For example, a first identifier is used to indicate downlink transmission, indicating that the first data carrying the first identifier is downlink data. As another example, the first identifier is used to indicate uplink transmission, indicating that the first data carrying the first identifier is uplink data. Exemplarily, the first identifier may include an indication of downlink transmission (e.g., a DL indication) or an indication of uplink transmission (e.g., a UL indication). Thus, the indication of downlink transmission or the indication of uplink transmission can respectively indicate that the first data carrying the first identifier is downlink data or uplink data.
[0387] In other examples, the transmission method of the first data may include quality requirements for the first data or transmission resources carrying the first data, and so on. For example, QFI can be used to indicate the quality requirements of the first data. As another example, DRBID can be used to indicate the transmission resources carrying the first data.
[0388] This application does not limit the specific name of the first identifier, which may also be referred to as granular information, granular identifier, identifier information, or other names. For ease of understanding, the first identifier will be referred to as granular identifier 1 below.
[0389] Optionally, the granularity identifier 1 corresponds to (or is associated with) the action ID 1. For example, the above "correspondence" can be understood as: there is a mapping relationship between action ID 1 and granularity identifier 1. Another example is that the above "correspondence" can be understood as: the first process can be used to execute on data carrying granularity identifier 1.
[0390] Here, action ID1 can be an execution code identifier calculated by the network side (e.g., the network side includes RAN2 and / or RAN1).
[0391] In some examples, the network side may send (e.g., broadcast) a list of supported processing identifiers to the terminal device (e.g., UE1). This list may include identifiers for at least one processing, and the at least one processing may include a first processing. The terminal device may decide whether to request auxiliary computation based on network capabilities and its computational load. If the terminal device determines to request auxiliary computation, it may also determine an offloading percentage (e.g., offloading 10%, 20%, 50%, or 100%). For example, the terminal device may determine to offload a processing that accounts for 10% of the computational load to the network side. Exemplarily, this 10% computational load processing may include the first processing. The terminal device may indicate to the network side the identifiers of one or more processing methods selected by the terminal device. These identifiers may belong to the processing identifier list. Optionally, the identifiers of the one or more processing methods may include action ID1.
[0392] In other examples, the terminal device can determine whether to request auxiliary computation independently, without relying on the network-side broadcast mentioned above. If the terminal device determines to request auxiliary computation, it can also determine the offload ratio. For example, the terminal device can request action ID1 from the network side, which can accept or reject it. If the network side accepts the request, it can indicate action ID1 to the terminal device. If the network side rejects the request, it can send a rejection message to the terminal device.
[0393] Based on the above scheme, the first information indicates granularity identifier 1 and action ID 1. Granularity identifier 1 corresponds to action ID 1. For example, when RAN2 receives data carrying granularity identifier 1, it can determine that the data will undergo first processing. In this way, RAN1 does not need to additionally instruct RAN2 to perform first processing on the data, thereby reducing signaling overhead.
[0394] In some possible implementations, RAN1 can determine a fourth mapping relationship, which includes the correspondence (or mapping) between granularity identifier 1 and the identifier (RAN2ID) of RAN2. For example, RAN1 can determine granularity identifier 1 based on a first request. RAN1 can then select RAN2 to perform auxiliary calculations for UE1. In this way, RAN1 can determine that there is a correspondence between granularity identifier 1 and RAN2. For example, the fourth mapping relationship can be represented as {granularity identifier 1, RAN2ID}.
[0395] For example, RAN2ID may include the index and / or IP of RAN2.
[0396] In some possible implementations, method 300 further includes: RAN2 determining a seventh mapping relationship based on the first information (indicating granularity identifier 1 and actionID1). The seventh mapping relationship may include the mapping relationship between granularity identifier 1 and actionID1. For example, the seventh mapping relationship may be represented as {granularity identifier 1, actionID1}.
[0397] Figure 4 This is a schematic diagram of a communication system provided in an embodiment of this application. Figure 4 In the communication system shown, RAN1, used to connect UE1, and RAN2, used for calculation, can be separated.
[0398] In some possible implementations, RAN2 can support on-path computing. For example, RAN2 can deploy computing functions. Exemplarily, RAN2 can perform processing that UE1 would normally need to perform; in other words, RAN2 can perform some processing on behalf of UE1, allowing UE1 to offload some processing to RAN2. For example, RAN2 can perform rendering, compression, or decompression of data packets from the terminal device. Therefore, Figure 4 The architecture shown supports offloading the processing content of terminal devices to access network devices, effectively reducing the computing load of terminal devices.
[0399] Figure 4 The architecture shown can also be called RAN (Everything as a Service, XaaS). The following section will combine... Figure 4 This application introduces two possible architectural approaches provided by its embodiments.
[0400] See Figure 4 In (a) of the diagram, UE1 is connected to RAN1, RAN1 is connected to RAN2, and RAN2 is connected to the first core network function. The tunnel between RAN1 and RAN2 can be referred to as the first tunnel, for example, tunnel 410. The tunnel between RAN2 and the first core network function can be referred to as the second tunnel, for example, tunnel 420. Exemplarily, uplink data can sequentially pass through UE1, RAN1, RAN2, and the first core network function; downlink data can sequentially pass through the first core network function, RAN2, RAN1, and UE1. For ease of description, the following will... Figure 4 The scheme shown in (a) is called architecture A.
[0401] Optionally, in architecture A, a tunnel exists between RAN1 and the first core network function, referred to as the fourth tunnel. For example, tunnel 430. Exemplarily, data requiring auxiliary computation can be transmitted via the first and second tunnels, while data not requiring auxiliary computation can be transmitted via the fourth tunnel.
[0402] See Figure 4 In (b) of the diagram, UE1 is connected to RAN1, RAN1 is connected to RAN2, and RAN1 is connected to the first core network function. The tunnel between RAN1 and RAN2 can be referred to as the first tunnel, for example, tunnel 440. The tunnel between RAN1 and the first core network function can be referred to as the third tunnel, for example, tunnel 450. Exemplarily, uplink data can sequentially pass through UE1, RAN1, RAN2, RAN1, and the first core network function; downlink data can sequentially pass through the first core network function, RAN1, RAN2, RAN1, and UE1. For ease of description, the following will... Figure 4 The scheme shown in (b) is called architecture B.
[0403] Unless otherwise specified, the first core network function in this application can refer to the core network device itself that can implement the first core network function, or to the components within the core network device that can implement the first core network function (e.g., processor, chip, or chip system), or it can be a logic module or software that can implement all or part of the first core network function. For ease of description, the following description uses the first core network function as an example.
[0404] The first core network function can be used to send downlink data or receive uplink data. For example, the first core network function can be a user plane network element. For instance, the first core network function can be a UPF (User Plane Function). For ease of description, the following description uses a UPF as an example of the first core network function. Figure 4 The first core network function shown is UPF. However, those skilled in the art will understand that the first core network function is not limited to UPF.
[0405] This application does not limit the compatibility of architecture A and architecture B. For example, RAN1 and RAN2 can be applied to either architecture A or architecture B, or both. In other words, Figure 4 The architectures A and B shown can be applied to different RAN1 and RAN2, or to the same RAN1 and RAN2. For example, in a communication system that includes RAN1 and RAN2, some data can be transmitted using architecture A, and other data can be transmitted using architecture B.
[0406] This application may refer to the first processing multiple times; however, those skilled in the art will understand that the specific implementation of the first processing may be the same or different in various implementation scenarios. The embodiments of this application involve at least four implementation scenarios, such as uplink transmission in architecture A, uplink transmission in architecture B, downlink transmission in architecture A, and downlink transmission in architecture B. In the above four implementation scenarios, the specific implementation of the first processing may be the same or different. For example, in uplink transmission in architecture A, the first processing may be used to execute calculation code 1 on the data; in uplink transmission in architecture B, the first processing may be used to execute calculation code 2 on the data. Calculation code 1 and calculation code 2 may be the same or different.
[0407] In the scheme shown in method 200, only one tunnel and corresponding route exist on the network side (e.g., between the RAN and UPF), while Figure 4 In the two illustrated architectures, there are two tunnels on the network side. For example, in architecture A, there is a first tunnel and a second tunnel. Similarly, in architecture B, there is a first tunnel and a third tunnel. Therefore, those skilled in the art will understand that, due to the different number of tunnels, method 200 cannot be directly applied. Figure 4 The two architectural approaches are shown.
[0408] Figure 5 This is a schematic flowchart of another communication method 500 provided in an embodiment of this application. Method 500 can be used to determine dual tunnels. For example, a first tunnel 410 and a second tunnel 420 in architecture A. Another example is a first tunnel 440 and a third tunnel 450 in architecture B. Method 500 can be combined with method 400. For example, method 500 can be executed after method 400, but this application is not limited to this; some operations of method 500 can also be executed simultaneously with some operations of method 400. Optional operations in method 500 are... Figure 5 The middle part is indicated by a dashed line. The following is in conjunction with... Figure 5 Method 500 is introduced.
[0409] This application does not limit the order in which the first tunnel 410 / 440 and the second tunnel 420 (or the third tunnel 450) are established. For example, the first tunnel 410 / 440 may be established before the second tunnel 420 (or the third tunnel 450). Another example is that the first tunnel 410 / 440 may be established after the second tunnel 420 (or the third tunnel 450). Yet another example is that the first tunnel 410 / 440 may be established simultaneously with the second tunnel 420 (or the third tunnel 450). The method for establishing the first tunnel will be described below.
[0410] Figure 5The first core network function shown is UPF, but this application is not limited to this. The first core network function can also be other functions, such as user plane network elements or other functions. Figure 5 The second core network function shown is SMF as an example, but this application is not limited to this. The second core network function can also be other functions, such as AMF, UPF or other functions.
[0411] S520, RAN1 determines a first tunnel between RAN1 and RAN2. Optionally, RAN2 determines the first tunnel. Exemplarily, the first tunnel is used for data transmission between RAN2 and RAN1.
[0412] In some possible implementations, S520 may include: RAN1 establishing a first tunnel. Optionally, RAN2 establishing a first tunnel. In other words, the first tunnel may be newly built. For example, the first tunnel may be a dedicated tunnel for transmitting data carrying granularity identifier 1.
[0413] In some other possible implementations, S520 may include: RAN1 searching for the first tunnel. Optionally, RAN2 searching for the first tunnel. In other words, the first tunnel may be pre-established. In S520, RAN1 and RAN2 may only search for the already established first tunnel. For example, the first tunnel may be a shared tunnel used to transmit data carrying granularity identifier 1 and data not carrying granularity identifier 1.
[0414] For example, the identifier of the first tunnel may include TEID. For ease of description, the identifier of the first tunnel may be referred to as TEID1 below. TEID1 may be assigned by the core network or determined by RAN1 and / or RAN2.
[0415] For example, the identifier of a tunnel assigned by the core network can be called TEID2 (or TEID3). For instance, TEID2 could be the identifier of a second tunnel; TEID3 could be the identifier of a third tunnel.
[0416] TEID1 and TEID2 (or TEID3) can be the same. This scheme can also be called a unified TEID scheme.
[0417] TEID1 and TEID2 (or TEID3) can be different. The above scheme can also be called an independent TEID scheme.
[0418] Optionally, TEID1 corresponds to granularity identifier 1. Thus, data received by RAN1 or RAN2 on the first tunnel (e.g., data carrying TEID1) can correspond to granularity identifier 1. For example, data transmitted on the first tunnel may not carry granularity identifier 1; however, since TEID1 corresponds to granularity identifier 1, RAN1 or RAN2 can perform subsequent operations based on TEID1. For instance, the data forwarded by RAN1 or RAN2 can carry granularity identifier 1. As another example, RAN1 or RAN2 can determine the network element corresponding to granularity identifier 1 based on TEID1, and thus forward the data to that network element.
[0419] Based on the above scheme, a tunnel can be established between RAN1 and RAN2, enabling data transmission between them and facilitating auxiliary calculations for RAN2. Furthermore, TEID1 corresponds to granularity identifier 1. Thus, even when data only carries TEID1 and not granularity identifier 1, RAN1 or RAN2 can determine granularity identifier 1 based on TEID1 and perform subsequent operations accordingly. Therefore, the above scheme supports implicitly carrying granularity identifier 1 in data, thereby reducing the overhead of carrying granularity identifier 1.
[0420] The following are two examples of RAN1 and RAN2 interacting with TEID1, denoted as Example 1-1 and Example 1-2 respectively.
[0421] Example 1-1: TEID1 can be indicated by RAN1. Optionally, TEID1 can be determined (or assigned) by RAN1.
[0422] In some possible implementations, method 500 further includes: S510, RAN2 receives tenth information from RAN1, the tenth information being used to indicate TEID1. Correspondingly, RAN1 sends the tenth information to RAN2. Optionally, S510 is executed before S520.
[0423] In some possible implementations, prior to S510, method 500 further includes: RAN1 determining TEID1. TEID1 may be the same as or different from TEID2 (or TEID3). In the above scheme, RAN1 may first determine TEID1 and then indicate TEID1 to RAN2.
[0424] In some possible implementations, S520 includes: RAN2 determining the first tunnel corresponding to the TEID based on the TEID1 indicated by the tenth information.
[0425] Optionally, the tenth information is also used to indicate the granularity identifier 1. For example, the tenth information can be used to indicate TEID1 and granularity identifier 1. Exemplarily, RAN2 can determine an eighth mapping relationship based on the tenth information, wherein the eighth mapping relationship includes the correspondence between granularity identifier 1 and TEID1. For example, the eighth mapping relationship can be represented as {granularity identifier 1, TEID1}.
[0426] For example, RAN2 can determine the correspondence between TEID1 and action ID1 based on granularity identifier 1 and the seventh mapping relationship ({granularity identifier 1, action ID1}). Thus, when RAN2 receives data carrying TEID1, RAN2 can perform the first processing corresponding to actionID1 on that data.
[0427] For example, the tenth information may be carried within the first information. For example, the tenth information may include the first information. For example, the tenth information and the first information may be sent simultaneously. However, this application is not limited in this respect, and the tenth information and the first information may also be sent separately.
[0428] In some possible implementations, this tenth information is also used to indicate the identifier (RAN1ID) of RAN1. Optionally, RAN1ID and TEID1 are used to indicate the first tunnel.
[0429] For example, when TEID1 cannot uniquely distinguish different tunnels, RAN1ID can be used in conjunction with TEID1 to distinguish different tunnels. For instance, the value of TEID is finite, such as 1-1000. Suppose TEID1 is 200, and the identifier "200" is not only TEID1 but also an identifier for other tunnels. Thus, using only the identifier "200" might not be sufficient to distinguish the first tunnel from other tunnels. For example, among the tunnels corresponding to the identifier "200," only the first tunnel is related to RAN1. Here, "related" can be understood as one end of the first tunnel being RAN1. Thus, the identifier "200" and RAN1ID can be used to indicate the first tunnel.
[0430] In some scenarios, the number of identifiers used to distinguish tunnels is limited. For example, TEID1 can correspond to not only the first tunnel but also other tunnels. Based on the above scheme, the first tunnel can be distinguished from other tunnels according to TEID1 and RAN1ID. Thus, even with a limited number of identifiers, the first tunnel can be distinguished from other tunnels without needing to set a completely different tunnel identifier for the first tunnel, thereby saving tunnel identifier space.
[0431] Example 1-2: TEID1 can be indicated by RAN2. Optionally, TEID1 is determined (or assigned) by RAN2.
[0432] In some possible implementations, method 500 further includes: S515, RAN2 sends the eleventh information to RAN1. Correspondingly, RAN1 receives the eleventh information from RAN2. The eleventh information can be used to indicate TEID1.
[0433] In some possible implementations, prior to S515, method 500 further includes: RAN2 determining TEID1. TEID1 may be the same as or different from TEID2 (or TEID3). In the above scheme, RAN2 may first determine TEID1 and then indicate TEID1 to RAN1.
[0434] In some possible implementations, S520 includes: RAN1 determining the first tunnel corresponding to the TEID based on the TEID1 indicated by the eleventh information.
[0435] Optionally, the eleventh information is also used to indicate the granularity identifier 1. For example, the eleventh information can be used to indicate TEID1 and granularity identifier 1. Exemplarily, RAN1 can determine the eighth mapping relationship ({granularity identifier 1, TEID1}) based on the eleventh information.
[0436] For example, the eleventh message may be carried within the second message. For example, the eleventh message may include the second message. For example, the eleventh message and the second message may be sent simultaneously. However, this application is not limited in this respect, and the eleventh message and the second message may also be sent separately.
[0437] In some possible implementations, this eleventh piece of information is also used to indicate the RAN2ID. Optionally, RAN2ID and TEID1 are used to indicate the first tunnel.
[0438] For example, when TEID1 cannot uniquely distinguish different tunnels, RAN2ID can be used in conjunction with TEID1 to distinguish different tunnels. For instance, the value of TEID is finite, such as 1-1000. Suppose TEID1 is 200, and the identifier "200" is not only TEID1 but also an identifier for other tunnels. Thus, using only the identifier "200" might not be sufficient to distinguish the first tunnel from other tunnels. For example, among the tunnels corresponding to the identifier "200," only the first tunnel is related to RAN2. Here, "related" can be understood as one end of the first tunnel being RAN2. Thus, the identifier "200" and RAN2ID can be used to indicate the first tunnel.
[0439] In some scenarios, the number of identifiers used to distinguish tunnels is limited. For example, TEID1 can correspond to not only the first tunnel but also other tunnels. Based on the above scheme, the first tunnel can be distinguished from other tunnels according to TEID1 and RAN2ID. Thus, even with a limited number of identifiers, the first tunnel can be distinguished from other tunnels without needing to set a completely different tunnel identifier for the first tunnel, thereby saving tunnel identifier space.
[0440] As mentioned earlier, architecture A may include a first tunnel and a second tunnel. An example of determining the first tunnel was given above; an example of determining the second tunnel is given below.
[0441] In some possible implementations, method 500 further includes: S550, RAN2 determines a second tunnel between RAN2 and a first core network function (e.g., UPF). Optionally, the first core network function (e.g., UPF) determines the second tunnel. Exemplarily, the second tunnel is used for data transmission between RAN2 and UPF.
[0442] In some possible implementations, S550 may include: RAN2 establishing a second tunnel. Optionally, UPF establishing a second tunnel. In other words, the second tunnel may be newly created. For example, the second tunnel may be a dedicated tunnel for transmitting data carrying granularity identifier 1.
[0443] In some other possible implementations, S550 may include: RAN2 searching for a second tunnel. Optionally, UPF searching for a second tunnel. In other words, the second tunnel may be pre-established. In S550, RAN2 and UPF may only search for the already established second tunnel. For example, the second tunnel may be a shared tunnel used to transmit data carrying granularity identifier 1 and data not carrying granularity identifier 1.
[0444] For example, the identifier of the second tunnel may include TEID. For ease of description, the identifier of the second tunnel may be referred to as TEID2 below. For example, TEID2 may be a tunnel identifier assigned by the core network.
[0445] Optionally, TEID2 corresponds to granularity identifier 1. In this way, data received by RAN2 or UPF on the second tunnel (e.g., data carrying TEID2) can correspond to granularity identifier 1. For example, data transmitted on the second tunnel may not carry granularity identifier 1; however, since TEID2 corresponds to granularity identifier 1, RAN2 or UPF can perform subsequent operations based on TEID2. For instance, RAN2 or UPF can determine the network element corresponding to granularity identifier 1 based on TEID2, and then forward the data to that network element.
[0446] Based on the above scheme, a tunnel can be established between RAN2 and UPF, enabling data transmission between them. For example, RAN2 can send processed data to UPF through the second tunnel. Alternatively, RAN2 can receive data from UPF through the second tunnel for auxiliary calculations. Furthermore, TEID2 corresponds to granularity identifier 1. Thus, even when data only carries TEID2 and not granularity identifier 1, RAN2 can determine granularity identifier 1 based on TEID2 and perform subsequent operations accordingly. Therefore, the above scheme supports implicitly carrying granularity identifier 1 in the data, thereby reducing the overhead of carrying granularity identifier 1.
[0447] The following are two examples of RAN2 obtaining TEID2, denoted as Example 2-1 and Example 2-2 respectively.
[0448] Example 2-1: TEID2 can be indicated by RAN1.
[0449] In some possible implementations, method 500 further includes: S530, RAN2 receives twelfth information from RAN1. Correspondingly, RAN1 sends twelfth information to RAN2. The twelfth information can be used to indicate TEID2.
[0450] In some possible implementations, S550 includes: RAN2 determining the second tunnel corresponding to the TEID based on the TEID2 indicated by the twelfth information.
[0451] Optionally, the twelfth information may also be used to indicate the granularity identifier 1. For example, the twelfth information may be used to indicate TEID2 and granularity identifier 1. Exemplarily, RAN2 may determine a ninth mapping relationship based on TEID2 and granularity identifier 1 indicated by the twelfth information, wherein the ninth mapping relationship includes the correspondence between granularity identifier 1 and TEID2. For example, the ninth mapping relationship may be represented as {granularity identifier 1, TEID2}.
[0452] In some examples, RAN2 can determine the correspondence between TEID2 and action ID1 based on the twelfth information (indicating TEID2 and granularity identifier 1) and the seventh mapping relationship ({granularity identifier 1, action ID1}). For example, when RAN2 receives data carrying TEID2, RAN2 can perform the first processing on that data.
[0453] In some examples, RAN2 can determine the correspondence between TEID1 and TEID2 based on the twelfth information (indicating TEID2 and granularity identifier 1) and the eighth mapping relationship ({granularity identifier 1, TEID1}). For example, if RAN2 receives data carrying TEID1, it can forward that data to the network element corresponding to TEID2. As another example, if RAN2 receives data carrying TEID2, it can forward that data to the network element corresponding to TEID1.
[0454] Optionally, the twelfth piece of information may also be used to indicate the identifier (UPFID) of the UPF. For example, the twelfth piece of information may be used to indicate TEID2 and UPF ID. Or, for example, the twelfth piece of information may be used to indicate TEID2, granularity identifier 1, and UPF ID.
[0455] In some possible implementations, S550 includes: RAN2 determining the second tunnel based on the UPF ID. Exemplarily, the UPF ID may include the UPF's index and / or IP address. For example, RAN2 can determine the UPF's IP address based on the UPF's index and pre-configured information. RAN2 can then determine the second tunnel based on the UPF's IP address. The pre-configured information may include a mapping between the indexes and IP addresses of core network functions (e.g., UPFs).
[0456] For example, TEID2 can be obtained by RAN1 from the core network.
[0457] In some possible implementations, method 500 further includes: S532, RAN1 receives the seventeenth message from a second core network function (e.g., SMF), the seventeenth message which can be used to indicate TEID2. Correspondingly, the second core network function sends the seventeenth message to RAN1. Optionally, S532 is executed before S530.
[0458] Unless otherwise specified, the second core network function in this application can refer to the core network device itself that can implement the second core network function, or to the components within the core network device that can implement the second core network function (e.g., processor, chip, or chip system), or it can be a logic module or software that can implement all or part of the second core network function. For ease of description, the following description uses the second core network function as an example.
[0459] For example, the second core network function can be a UPF, AMF, or SMF. For example, if the second core network function is an SMF, it can send information directly to the access function (e.g., RAN1) or send information to the access function through the AMF. For example, the second core network function sends the seventeenth message to the AMF, and the AMF sends the seventeenth message to RAN1.
[0460] Optionally, this seventeenth piece of information is used to indicate TEID2. In this way, RAN1 can determine TEID2. Further, RAN1 can indicate TEID2 to RAN2.
[0461] For example, if TEID1 is determined by RAN1, in a unified TEID scheme, method 500 further includes: RAN1 determining TEID1 based on TEID2 indicated by the seventeenth information. For example, RAN1 can use TEID2 as TEID1. In this way, TEID1 and TEID2 can be the same.
[0462] In the above scheme, TEID1 and TEID2 are the same, which can reduce the complexity of the data transmission process. For example, when RAN2 receives data carrying TEID1 from RAN1, since TEID1 and TEID2 are the same, RAN2 can directly route to UPF based on the TEID, and then send it to UPF through the second tunnel; without having to first determine another TEID (e.g., TEID2) based on one TEID (e.g., TEID1) and then route to UPF.
[0463] For example, if TEID1 is determined by RAN1, in a separate TEID scheme, RAN1 can use the new TEID1 as TEID1. In this way, TEID1 and TEID2 can be different.
[0464] In the above scheme, TEID1 and TEID2 differ, allowing for more flexible configuration of the first and second tunnels. For example, the second tunnel can be expanded independently without affecting the operation of the first tunnel.
[0465] Optionally, the seventeenth information may also be used to indicate the granularity identifier 1. For example, the seventeenth information may be used to indicate TEID2 and granularity identifier 1. Exemplarily, RAN1 may determine that TEID2 corresponds to granularity identifier 1 based on TEID2 and granularity identifier 1 indicated by the seventeenth information, and then perform subsequent processing.
[0466] In some examples, RAN1 can determine RAN2 based on the seventeenth piece of information (indicating TEID2 and granularity identifier 1) and the fourth mapping relationship ({granularity identifier 1, RAN2ID}). For example, RAN1 can determine the indication information for transmitting TEID2 to RAN2 based on granularity identifier 1 and the fourth mapping relationship ({granularity identifier 1, RAN2ID}).
[0467] Optionally, the seventeenth piece of information may also be used to indicate the UPF ID. For example, the seventeenth piece of information may be used to indicate TEID2 and UPF ID. As another example, the seventeenth piece of information may be used to indicate TEID2, granularity identifier 1, and UPF ID.
[0468] For example, RAN1 can indicate the UPF ID to RAN2 based on the UPF ID indicated in the seventeenth information.
[0469] The UPF can proactively send the seventeenth message to RAN1, or it can send the seventeenth message to RAN1 based on a request; this application does not limit this. The "request" can originate from RAN1, or from other network elements or devices; this application does not limit this either.
[0470] In some possible implementations, method 500 further includes: S534, RAN1 sends a fifth request to a second core network function (e.g., SMF), which can be used to request TEID2. Correspondingly, the second core network function receives the fifth request from RAN1. Optionally, S534 is executed before S532.
[0471] For example, the second core network function can be the SMF. In some examples, RAN1 can send the fifth request directly to the SMF. In other examples, RAN1 can send the fifth request to the AMF. The AMF then sends the fifth request to the SMF.
[0472] Optionally, the fifth request is used to request the TEID2. For example, the fifth request may be used to request the second core network function to issue or indicate the TEID2. Optionally, the fifth request is used to request the UPF ID. For example, the fifth request may be used to request the second core network function to issue or indicate the UPF ID. Optionally, the fifth request is used to request the second core network function to allocate UPF and / or TEID2.
[0473] Optionally, S532 includes: in response to the fifth request, the second core network function sends a seventeenth message to RAN1, the seventeenth message indicating TEID2. Alternatively, the second core network function sends the seventeenth message to RAN1 according to the fifth request. Other information indicated by the seventeenth message can be determined based on the information requested by the fifth request. For example, if the fifth request is used to request a UPFID, then the seventeenth message can indicate the UPFID.
[0474] Optionally, the fifth request is used to indicate the RAN2ID. In this way, the second core network function (e.g., SMF) can indicate the RAN2ID to the UPF, thereby enabling the UPF to obtain the RAN2ID. For example, if the second core network function is the UPF, then the UPF can determine the RAN2ID. In the case where the second core network function is the UPF, Figure 5 The “UPF” (corresponding to the first core network function) and “SMF” (corresponding to the second core network function) shown can be combined into one function.
[0475] For example, RAN2ID may include an index and / or IP of RAN2.
[0476] The second request can explicitly indicate RAN2ID or implicitly indicate RAN2ID.
[0477] For example, RAN2 has multiple identifiers (IDs), and the second request can be used to indicate one of these identifiers. In this way, the second tunnel between UPF and RAN2 can be determined based on the RAN2ID indicated by the second request.
[0478] In some possible implementations, S550 includes: the UPF determining the second tunnel based on the RAN2ID. For example, the RAN2ID includes the IP address of RAN2, and the UPF can determine the second tunnel based on the IP address of RAN2. Another example is that the RAN2ID includes an index of RAN2, and the UPF can determine the IP address of RAN2 based on the index of RAN2 and pre-configured information. Further, the UPF can determine the second tunnel based on the IP address of RAN2. The aforementioned pre-configured information may include a mapping relationship between the index and IP address of the access function (e.g., RAN2).
[0479] Optionally, the fifth request is used to indicate granularity identifier 1. Thus, the second core network function can generate the seventeenth information based on the granularity identifier 1 indicated by the fifth request, wherein the seventeenth information is used to indicate granularity identifier 1. However, this application is not limited in this respect; for example, the second core network function can determine the seventeenth information indicating granularity identifier 1 in other ways.
[0480] Example 2-2: TEID2 can be obtained by RAN2 from the core network.
[0481] In some possible implementations, method 500 further includes: S540, RAN2 receives thirteenth information from the second core network function, wherein the thirteenth information can be used to indicate TEID2. Correspondingly, the second core network function sends the thirteenth information to RAN2. Optionally, S540 is executed before S550.
[0482] Optionally, this thirteenth piece of information is used to indicate TEID2. In this way, RAN2 can determine the second tunnel based on TEID2.
[0483] For example, if TEID1 is determined by RAN2, in a unified TEID scheme, method 500 further includes: RAN2 determining TEID1 based on TEID2 indicated by the thirteenth information. In this way, RAN2 can use TEID2 as TEID1. Thus, TEID1 and TEID2 can be the same.
[0484] For example, if TEID1 is determined by RAN2, in a separate TEID scheme, RAN2 can use the new TEID1 as TEID1. TEID1 and TEID2 can be different.
[0485] Optionally, the thirteenth information may also be used to indicate the granularity identifier 1. For example, the thirteenth information may be used to indicate TEID2 and granularity identifier 1. Exemplarily, RAN2 may determine the ninth mapping relationship ({granularity identifier 1, TEID2}) based on TEID2 and granularity identifier 1 indicated by the thirteenth information.
[0486] In some examples, RAN2 can determine the correspondence between TEID2 and action ID1 based on the thirteenth information (indicating TEID2 and granularity identifier 1) and the seventh mapping relationship ({granularity identifier 1, action ID1}). For example, when RAN2 receives data carrying TEID2, RAN2 can perform the first processing corresponding to actionID1 on that data.
[0487] In some examples, RAN2 can determine the correspondence between TEID1 and TEID2 based on the thirteenth information (indicating TEID2 and granularity identifier 1) and the eighth mapping relationship ({granularity identifier 1, TEID1}). For example, if RAN2 receives data carrying TEID1, it can forward that data to the tunnel and network element corresponding to TEID2. As another example, if RAN2 receives data carrying TEID2, it can forward that data to the tunnel and network element corresponding to TEID1.
[0488] Optionally, the thirteenth piece of information may also be used to indicate the UPF ID. For example, the thirteenth piece of information may be used to indicate TEID2 and UPF ID. Yet another example is that the thirteenth piece of information may be used to indicate TEID2, granularity identifier 1, and UPF ID.
[0489] In some possible implementations, S550 includes: RAN2 determining the second tunnel based on the UPF ID.
[0490] UPF can proactively send the thirteenth message to RAN2, or it can send the thirteenth message to RAN2 upon request; this application does not limit this. The "request" can originate from RAN2, or from other network elements or devices; this application does not limit this either.
[0491] In some possible implementations, method 500 further includes: S542, RAN1 sends a second request to the second core network function, wherein the second request can be used to request TEID2. Correspondingly, the second core network function receives the second request from RAN1. Optionally, S542 is executed before S540.
[0492] For example, the second core network function can be the SMF. In some examples, RAN1 can send the second request directly to the SMF. In other examples, RAN1 can send the second request to the AMF. The AMF then sends the second request to the SMF.
[0493] Optionally, the second request is used to request the TEID2. For example, the second request may be used to request the second core network function to issue or indicate the TEID2. Optionally, the second request is used to request the UPF ID. For example, the second request may be used to request the second core network function to issue or indicate the UPF ID. Optionally, the second request is used to request the second core network function to allocate UPF and / or TEID2.
[0494] Optionally, S540 includes: in response to the second request, a second core network function (e.g., SMF) sends thirteenth information to RAN1, which may be used to indicate TEID2. Alternatively, the second core network function sends thirteenth information to RAN1 according to the second request. Other information indicated by the thirteenth information may be determined based on the information requested by the second request. For example, if the second request is used to request UPFID, then the thirteenth information may indicate UPFID.
[0495] Optionally, the second request is used to indicate the RAN2ID. In this way, the second core network function (e.g., SMF) can indicate the RAN2ID to the UPF, thereby enabling the UPF to obtain the RAN2ID. For example, if the second core network function is the UPF, then the UPF can determine the RAN2ID. In the case where the second core network function is the UPF, Figure 5 The “UPF” (corresponding to the first core network function) and “SMF” (corresponding to the second core network function) shown can be combined into one function.
[0496] The second request can explicitly indicate RAN2ID or implicitly indicate RAN2ID.
[0497] For example, RAN2 has multiple identifiers (IDs), and the second request can be used to indicate one of these identifiers. In this way, the second tunnel between UPF and RAN2 can be determined based on the RAN2ID indicated by the second request.
[0498] In some possible implementations, S550 includes: UPF determining the second tunnel based on RAN2ID.
[0499] Optionally, the second request is used to indicate granularity identifier 1. In this way, the second core network function can generate thirteenth information based on granularity identifier 1 indicated by the second request, wherein the thirteenth information can be used to indicate granularity identifier 1. However, this application is not limited in this respect; for example, the second core network function can determine the thirteenth information used to indicate granularity identifier 1 in other ways.
[0500] In some possible implementations, some operations in method 500 are, in order: S534, S532, S530, and S550. In other possible implementations, some operations in method 500 are, in order: S542, S540, and S550.
[0501] S534, S532, S530, S542, S540, or S550 pertain to the operation of establishing the second tunnel. S510, S515, or S520 pertain to the operation of establishing the first tunnel. As mentioned above, this application does not limit the order in which the first and second tunnels are established. For example, the first tunnel may be established before or after the second tunnel. Alternatively, the first tunnel may be established simultaneously with the second tunnel.
[0502] Optionally, a fourth tunnel also exists in architecture A. An example of determining the fourth tunnel can be found in the aforementioned example of determining the second tunnel, and will not be repeated here.
[0503] As mentioned earlier, architecture B may include a first tunnel and a third tunnel. Examples of determining the first and second tunnels were presented above; examples of determining the third tunnel are presented below.
[0504] In some possible implementations, method 500 further includes: S580, RAN1 determines a third tunnel between RAN1 and a first core network function (e.g., UPF). Optionally, the UPF determines the third tunnel. Exemplarily, the third tunnel is used for data transmission between RAN1 and the UPF.
[0505] In some possible implementations, S580 may include: RAN1 establishing a third tunnel. Optionally, UPF establishing a third tunnel. In other words, the third tunnel may be newly created. For example, the third tunnel may be a dedicated tunnel for transmitting data carrying granularity identifier 1.
[0506] In some other possible implementations, S580 may include: RAN1 searching for a third tunnel. Optionally, UPF searching for a third tunnel. In other words, the third tunnel may be pre-established. In S580, RAN1 and UPF may only search for third tunnels that have already been established. For example, the third tunnel may be a shared tunnel used to transmit data carrying granularity identifier 1 and data not carrying granularity identifier 1.
[0507] For example, the identifier of the third tunnel may include a TEID. For ease of description, the identifier of the third tunnel may be referred to as TEID3 below. For example, TEID3 may be a tunnel identifier assigned by the core network.
[0508] Optionally, TEID3 corresponds to granularity identifier 1. In this way, data received by RAN1 or UPF on the third tunnel (e.g., data carrying TEID3) can correspond to granularity identifier 1. For example, data transmitted on the third tunnel may not carry granularity identifier 1; however, since TEID3 corresponds to granularity identifier 1, RAN1 or UPF can perform subsequent operations based on TEID3. For instance, RAN1 or UPF can determine the network element corresponding to granularity identifier 1 based on TEID3, and then forward the data to that network element.
[0509] Based on the above scheme, a tunnel can be established between RAN1 and UPF, enabling data transmission between them. For example, RAN1 can receive processed data from RAN2 and send it to UPF through a third tunnel. Alternatively, RAN1 can receive data from UPF through the third tunnel and send it to RAN2 for auxiliary calculations. Furthermore, TEID3 corresponds to granularity identifier 1. Thus, even when data only carries TEID3 and not granularity identifier 1, RAN1 can determine granularity identifier 1 based on TEID3 and perform subsequent operations accordingly. Therefore, the above scheme supports implicitly carrying granularity identifier 1 in data, thereby reducing the overhead of carrying granularity identifier 1.
[0510] The following are two examples of RAN1 obtaining TEID3, denoted as Example 3-1 and Example 3-2 respectively.
[0511] Example 3-1: TEID3 can be indicated by RAN2.
[0512] In some possible implementations, method 500 further includes: S560, RAN1 receives fifteenth information from RAN2, wherein the fifteenth information can be used to indicate TEID3. Correspondingly, RAN2 sends the fifteenth information to RAN1.
[0513] In some possible implementations, S580 includes: RAN1 determining the third tunnel corresponding to the TEID based on the TEID3 indicated by the fifteenth information.
[0514] Optionally, the fifteenth information may also be used to indicate the granularity identifier 1. For example, the fifteenth information may be used to indicate TEID3 and granularity identifier 1. Exemplarily, RAN1 may determine the tenth mapping relationship based on TEID3 and granularity identifier 1 indicated by the fifteenth information, wherein the tenth mapping relationship includes the correspondence between granularity identifier 1 and TEID3. For example, the tenth mapping relationship may be represented as {granularity identifier 1, TEID3}.
[0515] In some examples, RAN1 can determine the correspondence between TEID1 and TEID3 based on the fifteenth piece of information (indicating TEID3 and granularity identifier 1) and the eighth mapping relationship ({granularity identifier 1, TEID1}). For example, when RAN1 receives data carrying TEID1, it can forward the data to the tunnel and network element corresponding to TEID3. As another example, when RAN1 receives data carrying TEID3, it can forward the data to the tunnel and network element corresponding to TEID1.
[0516] Optionally, the fifteenth piece of information may also be used to indicate the UPF ID. For example, the fifteenth piece of information may be used to indicate TEID3 and UPF ID. Alternatively, the fifteenth piece of information may be used to indicate TEID3, granularity identifier 1, and UPF ID.
[0517] In some possible implementations, S580 includes: RAN1 determining the third tunnel based on the UPF ID. Exemplarily, the UPF ID may include the UPF's index and / or IP address. For example, RAN1 can determine the UPF's IP address based on the UPF's index and pre-configured information. RAN1 can then determine the third tunnel based on the UPF's IP address. The pre-configured information may include a mapping between the indexes and IP addresses of core network functions (e.g., UPFs).
[0518] For example, TEID3 can be obtained by RAN2 from the core network.
[0519] In some possible implementations, method 500 further includes: S562, RAN2 receives sixteenth information from a second core network function, wherein the sixteenth information can be used to indicate TEID3. Correspondingly, the second core network function sends the sixteenth information to RAN2. Optionally, S562 is executed before S560.
[0520] This sixteenth message is used to indicate TEID3. In this way, RAN2 can indicate TEID3 to RAN1.
[0521] For example, if TEID1 is determined by RAN2, in a unified TEID scheme, method 500 further includes: RAN2 determining TEID1 based on TEID3 indicated by the sixteenth information. For example, RAN2 can use TEID3 as TEID1. In this way, TEID1 and TEID3 can be the same.
[0522] In the above scheme, TEID1 and TEID3 are the same, which can reduce the complexity of the data transmission process. For example, when RAN1 receives data carrying TEID1 from RAN2, since TEID1 and TEID3 are the same, RAN1 can directly route to UPF based on this TEID, and then send it to UPF through the third tunnel; without having to first determine another TEID (e.g., TEID3) based on one TEID (e.g., TEID1) and then route to UPF.
[0523] For example, if TEID1 is determined by RAN2, in a separate TEID scheme, RAN2 can use the new TEID1 as TEID1. In this way, TEID1 and TEID3 can be different.
[0524] In the above scheme, TEID1 and TEID3 differ, allowing for more flexible configuration of the first and third tunnels. For example, the third tunnel can be expanded independently without affecting the operation of the first tunnel.
[0525] Optionally, the sixteenth information may also be used to indicate the granularity identifier 1. For example, the sixteenth information may be used to indicate TEID3 and granularity identifier 1. Exemplarily, RAN2 may determine that TEID3 corresponds to granularity identifier 1 based on the TEID3 indicated by the sixteenth information and granularity identifier 1, and then perform subsequent processing. For example, RAN2 may determine that TEID3 should be indicated to RAN1 based on granularity identifier 1.
[0526] For example, when the first information indicates granularity identifier 1, RAN2 can determine the eleventh mapping relationship after receiving the first information (indicating granularity identifier 1) from RAN1. This eleventh mapping relationship includes the mapping relationship between granularity identifier 1 and RAN1ID. For example, the eleventh mapping relationship can be represented as {granularity identifier 1, RAN1ID}. RAN2 can determine RAN1ID based on the network element from which the first information originates.
[0527] For example, RAN2 can determine RAN1 based on granularity identifier 1 and the eleventh mapping relationship ({granularity identifier 1, RAN1ID}). For instance, RAN2 determines that it needs to transmit the indication information of TEID3 to RAN1.
[0528] Optionally, the sixteenth piece of information may also be used to indicate the UPF ID. For example, the sixteenth piece of information may be used to indicate TEID3 and UPF ID. Alternatively, the sixteenth piece of information may be used to indicate TEID3, granularity identifier 1, and UPF ID.
[0529] For example, RAN2 can indicate the UPF ID to RAN1 based on the UPF ID indicated by the sixteenth information.
[0530] The UPF can proactively send the sixteenth message to RAN2, or it can send the sixteenth message to RAN2 upon request; this application does not limit this. The "request" can originate from RAN2, or from other network elements or devices; this application does not limit this either.
[0531] In some possible implementations, method 500 further includes: S564, RAN2 sends a third request to a second core network function (e.g., SMF), which can be used to request TEID3. Correspondingly, the second core network function receives the third request from RAN2. Optionally, S564 is executed before S562.
[0532] For example, the second core network function can be the SMF. In some examples, RAN2 can directly send a third request to the SMF. In other examples, RAN2 can send a third request to the AMF. The AMF then sends the third request to the SMF.
[0533] Optionally, the third request is used to request the TEID3. For example, the third request may be used to request the second core network function to issue or indicate the TEID3. Optionally, the third request is used to request the UPF ID. For example, the third request may be used to request the second core network function to issue or indicate the UPF ID. Optionally, the third request is used to request the second core network function to allocate UPF and / or TEID3.
[0534] Optionally, S562 includes: in response to a third request, the second core network function sends a sixteenth message to RAN2, the sixteenth message indicating TEID3. Alternatively, the second core network function sends the sixteenth message to RAN2 according to the third request. Other information indicated by the sixteenth message can be determined based on the information requested by the third request. For example, if the third request is for requesting a UPFID, then the sixteenth message can indicate the UPFID.
[0535] Optionally, the third request is used to indicate the RAN1ID. In this way, the second core network function (e.g., SMF) can indicate the RAN1ID to the UPF, thereby enabling the UPF to obtain the RAN1ID. For example, if the second core network function is the UPF, then the UPF can determine the RAN1ID. In the case where the second core network function is the UPF, Figure 5 The “UPF” (corresponding to the first core network function) and “SMF” (corresponding to the second core network function) shown can be combined into one function.
[0536] For example, RAN1ID may include the index and / or IP of RAN1.
[0537] The fourth request can explicitly indicate RAN1ID or implicitly indicate RAN1ID.
[0538] For example, RAN1 has multiple identifiers (IDs), and the fourth request can be used to indicate one of these identifiers. In this way, the third tunnel between UPF and RAN1 can be determined based on the RAN1ID indicated by the fourth request.
[0539] In some possible implementations, S580 includes: the UPF determining the third tunnel based on the RAN1ID. For example, the RAN1ID includes the IP address of RAN1, and the UPF can determine the third tunnel based on the IP address of RAN1. Another example is that the RAN1ID includes an index of RAN1, and the UPF can determine the IP address of RAN1 based on the index of RAN1 and pre-configured information. Further, the UPF can determine the third tunnel based on the IP address of RAN1. The aforementioned pre-configured information may include a mapping relationship between the index of the access function (e.g., RAN1) and its IP address.
[0540] Optionally, the third request is used to indicate granularity identifier 1. Thus, the second core network function can generate sixteenth information based on granularity identifier 1 indicated by the third request, and the sixteenth information is used to indicate granularity identifier 1. However, this application is not limited in this respect; for example, the second core network function can determine the sixteenth information used to indicate granularity identifier 1 in other ways.
[0541] Example 3-2: TEID3 can be obtained by RAN1 from the core network.
[0542] In some possible implementations, method 500 further includes: S570, RAN1 receives fourteenth information from the second core network function, wherein the fourteenth information can be used to indicate TEID3. Correspondingly, the second core network function sends the fourteenth information to RAN1. Optionally, S570 is executed before S580.
[0543] The fourteenth piece of information is used to indicate TEID3. In this way, RAN1 can determine the third tunnel corresponding to TEID based on TEID3 indicated by the fourteenth piece of information.
[0544] For example, if TEID1 is determined by RAN1, in a unified TEID scheme, method 500 further includes: RAN1 determining TEID1 based on TEID3 indicated by the fourteenth information. In this way, RAN1 can use TEID3 as TEID1. Thus, TEID1 and TEID3 can be the same.
[0545] For example, if TEID1 is determined by RAN1, in a separate TEID scheme, RAN1 can use the new TEID1 as TEID1. In this way, TEID1 and TEID3 can be different.
[0546] Optionally, the fourteenth information may also be used to indicate the granularity identifier 1. For example, the fourteenth information may be used to indicate TEID3 and granularity identifier 1. Exemplarily, RAN1 may determine the tenth mapping relationship ({granularity identifier 1, TEID3}) based on TEID3 and granularity identifier 1 indicated by the fourteenth information.
[0547] In some examples, RAN1 can determine the correspondence between TEID1 and TEID3 based on the fourteenth information (indicating TEID3 and granularity identifier 1) and the eighth mapping relationship ({granularity identifier 1, TEID1}). For example, if RAN1 receives data carrying TEID1, it can forward that data to the tunnel and network element corresponding to TEID3. As another example, if RAN1 receives data carrying TEID3, it can forward that data to the tunnel and network element corresponding to TEID1.
[0548] Optionally, the fourteenth piece of information may also be used to indicate the UPF ID. For example, the fourteenth piece of information may be used to indicate TEID3 and UPF ID. Alternatively, the fourteenth piece of information may be used to indicate TEID3, granularity identifier 1, and UPF ID.
[0549] In some possible implementations, S580 includes: RAN1 determining the third tunnel based on the UPF ID.
[0550] The UPF can proactively send the fourteenth message to RAN1, or it can send the fourteenth message to RAN1 based on a request; this application does not limit this. The "request" can originate from RAN1, or from other network elements or devices; this application does not limit this either.
[0551] In some possible implementations, method 500 further includes: S572, RAN1 sends a fourth request to the second core network function, which can be used to request TEID3. Correspondingly, the second core network function receives the fourth request from RAN1. Optionally, S572 is executed before S570.
[0552] For example, the second core network function can be the SMF. In some examples, RAN1 can directly send the fourth request to the SMF. In other examples, RAN1 can send the fourth request to the AMF. The AMF then sends the fourth request to the SMF.
[0553] The fourth request is used to request the TEID3. For example, the fourth request can be used to request the second core network function to issue or indicate the TEID3. Optionally, the fourth request is used to request the UPF ID. For example, the fourth request can be used to request the second core network function to issue or indicate the UPF ID. Optionally, the fourth request is used to request the second core network function to allocate UPF and / or TEID3.
[0554] Optionally, S570 includes: in response to the fourth request, the second core network function sends fourteenth information to RAN1, the fourteenth information being used to indicate TEID3. Alternatively, the second core network function sends fourteenth information to RAN1 according to the fourth request. Other information indicated by the fourteenth information can be determined based on the information requested by the fourth request. For example, if the fourth request is used to request UPFID, then the fourteenth information can indicate UPFID.
[0555] Optionally, the fourth request is used to indicate the RAN1ID. In this way, the second core network function (e.g., SMF) can indicate the RAN1ID to the UPF, thereby enabling the UPF to obtain the RAN1ID. For example, if the second core network function is the UPF, then the UPF can determine the RAN1ID. In the case where the second core network function is the UPF, Figure 5 The “UPF” (corresponding to the first core network function) and “SMF” (corresponding to the second core network function) shown can be combined into one function.
[0556] The fourth request can explicitly indicate RAN1ID or implicitly indicate RAN1ID.
[0557] For example, RAN1 has multiple identifiers, and the fourth request can be used to indicate one of these identifiers. In this way, the third tunnel between UPF and RAN1 can be determined based on the RAN1ID indicated by the fourth request.
[0558] In some possible implementations, S580 includes: UPF determining a third tunnel based on RAN1ID.
[0559] Optionally, the fourth request is used to indicate granularity identifier 1. Thus, the second core network function can generate fourteenth information based on the granularity identifier 1 indicated by the fourth request, and the fourteenth information is used to indicate granularity identifier 1. However, this application is not limited in this respect; for example, the second core network function can determine the fourteenth information used to indicate granularity identifier 1 in other ways.
[0560] In some possible implementations, some operations in method 500 are, in order: S564, S562, S560, and S580. In other possible implementations, some operations in method 500 are, in order: S572, S570, and S580.
[0561] S564, S562, S560, S572, S570, or S580 pertain to the operation of determining (e.g., establishing or finding) a third tunnel. S510, S515, or S520 pertain to the operation of determining a first tunnel. As mentioned above, this application does not limit the order in which the first and third tunnels are determined. For example, the first tunnel may be determined before or after the third tunnel. Alternatively, the first tunnel may be determined simultaneously with the third tunnel.
[0562] Furthermore, this application does not limit the execution order of the various operations in method 500. For example, after some operations for determining the first tunnel are executed, the operation for determining the second tunnel (or the third tunnel) can be executed. Or, after some operations for determining the second tunnel (or the third tunnel) are executed, the operation for determining the first tunnel can be executed. Or, after all operations for determining the first tunnel are executed, the operation for determining the second tunnel (or the third tunnel) can be executed. Or, after all operations for determining the second tunnel (or the third tunnel) are executed, the operation for determining the first tunnel can be executed.
[0563] Figure 6 This is a schematic flowchart illustrating another communication method 600 provided in this application embodiment. Method 600 can be used to transmit data. Method 600 can be combined with methods 400 and 500. For example, method 600 can be executed after method 500, but this application is not limited, and method 600 can also have other execution orders. Optional operations in method 600 are described in... Figure 6 The middle part is indicated by a dashed line. The following is in conjunction with... Figure 6 Method 600 is introduced.
[0564] Figure 6 The first core network function shown is UPF, but this application does not limit the first core network function. The first core network function can also be other functions, such as user plane network elements or other functions.
[0565] For ease of understanding, Figure 6 The content indicated / included by each piece of information is shown in the form of "()". For example, the eighth piece of information may include the first data and granularity identifier 1, or the eighth piece of information may include the first data and be used to indicate the granularity identifier. Thus, the eighth piece of information can be represented as the eighth piece of information (first data, granularity identifier 1). Furthermore, Figure 6 In this context, a / b / c can be understood as at least one of a, b, or c. Figure 6 In this context, a / b can be understood as a and / or b.
[0566] Below, we will first introduce an example of uplink transmission, and then introduce an example of downlink transmission.
[0567] First, we will introduce an example of uplink transmission in Architecture A. In Architecture A, the devices or network elements that the data passes through can be: UE1, RAN1, RAN2, and UPF in sequence.
[0568] S610, RAN1 receives the eighth information from UE1. Correspondingly, UE1 sends the eighth information to RAN1. Optionally, the eighth information may include the first data and the granularity identifier 1.
[0569] Optionally, the eighth information includes the first data. Optionally, the eighth information is used to indicate granularity identifier 1. The eighth information may directly or explicitly indicate granularity identifier 1, or indirectly or implicitly indicate granularity identifier 1; this application does not limit this.
[0570] Optionally, the eighth piece of information is used to indicate action ID1. In this way, RAN1 can determine, based on action ID1, that the first data needs to undergo the first processing corresponding to actionID1.
[0571] For example, the first data may be data determined (e.g., generated) by UE1. The first data may be uplink data. In some possible implementations, UE1 may determine RAN1 according to pre-configured or pre-defined rules. In this way, UE1 may send the eighth information to RAN1.
[0572] This application may refer to "first data" multiple times, but those skilled in the art will understand that "first data" has different meanings in different implementation scenarios. For example, in uplink transmission, "first data" can be data sent by UE1 to RAN1; "first data" can also be data sent by RAN1 to RAN2. As another example, in downlink transmission of architecture A, "first data" can be data sent by UPF to RAN2. Yet another example, in downlink transmission of architecture B, "first data" can be data sent by UPF to RAN1, and "first data" can also be data sent by RAN1 to RAN2.
[0573] This application does not limit the specific name of the first data; for example, the first data may be called the first data packet or other names.
[0574] Based on the above scheme, the first data sent by UE1 can carry a granularity identifier 1. In this way, RAN1 can perform auxiliary calculations on the first data according to the corresponding access function (e.g., RAN2) indicated by the granularity identifier 1.
[0575] S620, RAN1 sends third information to RAN2. Correspondingly, RAN2 receives the third information from RAN1. Optionally, the third information includes first data and first indication information. The first indication information is used to indicate at least one of granularity identifier 1, TEID1, or action ID1.
[0576] Optionally, the third information includes the first data. The third information functions as first indication information. The third information can be transmitted through the first tunnel. Optionally, the first indication information is used to instruct RAN2 to perform first processing on the first data.
[0577] The following describes an example of RAN1 generating the first indication information. In some possible implementations, method 600 further includes: RAN1 generating the first indication information based on the granularity identifier 1 indicated by the eighth information, the first indication information indicating at least one of granularity identifier 1, TEID1, or action ID1. For example, if the first indication information indicates TEID1, RAN1 can generate the first indication information based on the granularity identifier 1 indicated by the eighth information and the eighth mapping relationship ({granularity identifier 1, TEID1}), the first indication information indicating TEID1. As another example, if the first indication information indicates action ID1, RAN1 can generate the first indication information based on the granularity identifier 1 indicated by the eighth information and the seventh mapping relationship ({granularity identifier 1, action ID1}), the first indication information indicating action ID1.
[0578] The following describes an example of determining RAN1 and RAN2. In some possible implementations, method 600 further includes: S622, RAN1 determines RAN2 based on the granularity identifier 1. For example, RAN1 routes to RAN2 based on the granularity identifier 1 and a pre-determined correspondence. Thus, RAN1 can send third information to RAN2, the third information including first data and the aforementioned first indication information indicating at least one of the first granularity identifier 1, TEID1, or action ID1. Optionally, S622 is executed before S620. In other possible implementations, S620 includes: RAN1 sending third information to RAN2 based on the granularity identifier 1. The following describes an example of determining RAN2 based on the granularity identifier 1.
[0579] In some possible implementations, S622 includes: RAN1 determines RAN2 based on the granularity identifier 1 and the fourth mapping relationship ({granularity identifier 1, RAN2ID}). Thus, RAN1 can send the aforementioned third information to RAN2. In other possible implementations, S620 includes: RAN1 sends the third information to RAN2 based on the granularity identifier 1 and the fourth mapping relationship ({granularity identifier 1, RAN2ID}).
[0580] The fourth mapping relationship ({granularity identifier 1, RAN2ID}) includes the mapping relationship between granularity identifier 1 and RAN2ID.
[0581] Based on the above scheme, the first data sent by RAN1 can carry first indication information. In this way, RAN2 can determine, based on the first indication information, to perform first processing on the first data, thereby achieving auxiliary calculation. Furthermore, RAN2 can determine, based on the first indication information, to send the processed data to the corresponding network element.
[0582] S624, RAN2 performs the first processing on the first data to obtain the second data.
[0583] In some possible implementations, S624 includes: S625, RAN2 performs the first processing on the first data according to the first indication information to obtain second data. For example, RAN2 determines action ID1 according to at least one of granularity identifier 1, TEID1, or action ID1 indicated by the first indication information, thereby performing the first processing on the first data to obtain second data.
[0584] In some possible implementations, S625 includes: S626, RAN2 determines the action ID1 according to the first instruction information; S628, RAN2 performs the first processing on the first data according to the action ID1 to obtain the second data.
[0585] In some examples, the first indication information is used to indicate granularity identifier 1. Optionally, S626 includes: RAN2 can determine action ID1 based on granularity identifier 1 and the seventh mapping relationship ({granularity identifier 1, action ID1}).
[0586] In other examples, the first indication information is used to indicate TEID1. Optionally, S626 includes: RAN2 can determine action ID1 based on the correspondence between TEID1 and action ID1. For example, RAN2 can determine the correspondence between TEID1 and action ID1 based on the tenth information (indicating TEID1 and granularity identifier 1) and the seventh mapping relationship ({granularity identifier 1, action ID1}).
[0587] In some further examples, the first indication information is used to indicate action ID1. Optionally, S626 includes: RAN2 can determine action ID1 based on the first indication information.
[0588] For example, the second data can be obtained by processing the first data. The second data can be uplink data. The second data can be used to send to the UPF.
[0589] This application may refer to "second data" multiple times, but those skilled in the art will understand that "second data" has different meanings in different implementation scenarios. For example, in uplink transmission of architecture A, the second data can be data sent from RAN2 to UPF. As another example, in uplink transmission of architecture B, the second data can be data sent from RAN2 to RAN1; the second data can also be data sent from RAN1 to UPF. Yet another example, in downlink transmission, the second data can be data sent from RAN2 to RAN1; the second data can also be data sent from RAN1 to UE1.
[0590] This application does not limit the specific name of the second data; for example, the second data may be called the second data packet or other names.
[0591] In some examples, in architectures A and B, RAN2 can send uplink data to different network elements. For instance, in architecture A, RAN2 can send uplink data to the UPF. In architecture B, RAN2 can send uplink data to RAN1. The uplink transmission scheme for architecture A will be described below.
[0592] In some possible implementations, method 600 further includes: S630, RAN2 sends fourth information to UPF. Correspondingly, UPF receives the fourth information from RAN2. Optionally, the fourth information includes the second data and the second indication information. The second indication information is used to indicate the granularity identifier 1 and / or TEID2.
[0593] Optionally, the fourth information includes the second data. The fourth information functions as second indication information. The fourth information can be transmitted via the second tunnel.
[0594] The second indication information is used to indicate the granularity identifier 1 and / or TEID2. Thus, the UPF can process the second data accordingly based on the second indication information. For example, the UPF can determine the corresponding APP server based on the granularity identifier 1 indicated by the second indication information. The UPF can then send the second data to the aforementioned APP server. As another example, the UPF can send the second data to the corresponding APP server based on the TEID2 indicated by the second indication information and a pre-determined correspondence. Exemplarily, the sequence number (SN) of the second data can be the same as the SN of the first data.
[0595] Based on the above scheme, RAN2 can send the processed second data to UPF. This second data can carry second indication information, which enables UPF to process the second data accordingly.
[0596] The following describes an example of RAN2 determining the UPF. Optionally, in the uplink transmission of architecture A, the first indication information is used to determine the UPF. In some possible implementations, method 600 further includes: S632, RAN2 determines the UPF based on the first indication information. For example, RAN2 routes to the UPF based on at least one of the granularity identifier 1, TEID1, or actionID1 indicated by the first indication information, and a pre-determined correspondence. In this way, RAN2 can send the aforementioned fourth information to the UPF. Optionally, S632 is executed before S630. In other possible implementations, S630 includes: RAN2 sending the fourth information to the UPF based on the first indication information.
[0597] In some possible implementations, S632 includes: RAN2 determining the UPF based on the first indication information and the first mapping relationship. In other possible implementations, S630 includes: RAN1 sending fourth information to the UPF based on the first indication information and the first mapping relationship.
[0598] The first mapping relationship may include a mapping relationship between at least one of the granularity identifier 1, the TEID1, or the action ID1 and the UPF ID. For example, the first mapping relationship may be represented as {granularity identifier 1 / TEID1 / actionID1, UPFID}. For example, granularity identifier 1 / TEID1 / actionID1 may represent at least one of the granularity identifier 1, the TEID1, or the action ID1.
[0599] The following describes an example of RAN2 determining the first mapping relationship. In some possible implementations, RAN2 can determine the first mapping relationship ({granularity identifier 1 / TEID1 / action ID1, UPFID}) based on the twelfth (or seventeenth) piece of information. For example, the twelfth (or seventeenth) piece of information can be used to indicate UPF ID and granularity identifier 1. Thus, RAN2 can determine the correspondence between UPF ID and granularity identifier 1 based on the twelfth (or seventeenth) piece of information. As an example, RAN2 can determine the correspondence between UPF ID, granularity identifier 1, and action ID1 based on the above correspondence between UPFID and granularity identifier 1, and the seventh mapping relationship ({granularity identifier 1, action ID1}). As another example, RAN2 can determine the correspondence between UPF ID, granularity identifier 1, and TEID1 based on the above correspondence between UPFID and granularity identifier 1, and the eighth mapping relationship ({granularity identifier 1, TEID1}). As another example, RAN2 can determine the mapping relationship between granularity identifier 1, TEID1, action ID1 and UPF ID based on the above correspondence between UPFID and granularity identifier 1, as well as the seventh mapping relationship ({granularity identifier 1, action ID1}) and the eighth mapping relationship ({granularity identifier 1, TEID1}).
[0600] The following describes an example of RAN2 generating the second indication information. In some possible implementations, method 600 further includes: RAN2 determining the second indication information (for indicating granularity identifier 1 and / or TEID2) based on the first indication information (for indicating at least one of granularity identifier 1, TEID1, or actionID1).
[0601] In some examples, the second indication information is used to indicate the granularity identifier 1 and / or TEID2, including: the second indication information is used to indicate granularity identifier 1. Exemplarily, the first indication information can be used to indicate at least one of granularity identifier 1, TEID1, or action ID1. Exemplarily, RAN2 can determine granularity identifier 1 based on the granularity identifier 1, TEID1, or action ID1 indicated by the first indication information, thereby determining the second indication information. Three cases are described below.
[0602] When the first indication information is used to indicate granularity identifier 1, RAN2 can generate second indication information based on the granularity identifier 1 indicated by the first indication information, and the second indication information is used to indicate granularity identifier 1.
[0603] When the first indication information is used to indicate TEID1, RAN2 can determine granularity identifier 1 based on TEID1 and the eighth mapping relationship ({granularity identifier 1, TEID1}). Further, RAN2 can generate second indication information based on granularity identifier 1, which is used to indicate granularity identifier 1.
[0604] When the first indication information is used to indicate action ID1, RAN2 can determine granularity identifier 1 based on action ID1 and the seventh mapping relationship ({granularity identifier 1, action ID1}). Further, RAN2 can generate second indication information based on granularity identifier 1, which is used to indicate granularity identifier 1.
[0605] In some examples, the second indication information is used to indicate the granularity identifier 1 and / or TEID2, including: the second indication information is used to indicate TEID2. Wherein, at least one of the granularity identifier 1, TEID1, or action ID1 indicated by the first indication information corresponds to TEID2.
[0606] In some possible implementations, RAN2 determines TEID2 based on the first indication information. For example, as mentioned above, RAN2 can determine granularity identifier 1 based on the first indication information. Further, RAN2 can determine TEID2 based on granularity identifier 1 and the ninth mapping relationship ({granularity identifier 1, TEID2}). Here, TEID1 and TEID2 can be the same or different.
[0607] In some other possible implementations, RAN2 can determine TEID2 based on TEID1. TEID1 and TEID2 can be the same.
[0608] In some possible implementations, the uplink transmission scheme of architecture A may sequentially include: S610, S620, S624, and S630. Optionally, before S620, the uplink transmission scheme of architecture A may further include: S622. Optionally, before S630, the uplink transmission scheme of architecture A may further include: S632. Exemplarily, in the uplink transmission scheme of architecture A, the devices or network elements through which the data passes may sequentially be: UE1, RAN1, RAN2, and UPF.
[0609] For example, in the uplink transmission scheme of architecture A, RAN1, RAN2 and UPF can perform the following routing operations respectively. Here, "->" can represent "mapping".
[0610] RAN1: Granularity identifier 1 -> RAN2ID. Granularity identifier 1 -> TEID1.
[0611] RAN2: At least one of granularity identifier 1, TEID1, or action ID1 -> action ID1. At least one of granularity identifier 1, TEID1, or action ID1 -> UPF ID. At least one of granularity identifier 1, TEID1, or action ID1 -> TEID2.
[0612] UPF: Granularity identifier 1 and / or TEID2->UE1ID.
[0613] The uplink transmission scheme of Architecture B is described below. In the uplink transmission scheme of Architecture B, the devices or network elements that the data passes through can be: UE1, RAN1, RAN2, RAN1 and UPF in sequence.
[0614] In the uplink transmission scheme of Architecture B, method 600 includes: S610, S620, and S624. Optionally, before S620, method 600 also includes: S622. Optionally, S624 includes S625. Other descriptions are as above and will not be repeated here.
[0615] In some possible implementations, method 600 further includes: S640, RAN2 sends fifth information to RAN1. Correspondingly, RAN1 receives the fifth information from RAN2. Optionally, the fifth information includes the second data and third indication information. The third indication information is used to indicate the granularity identifier 1 and / or the TEID1.
[0616] Optionally, the fifth information includes the second data. The fifth information also functions as the third indication information. The fifth information can be transmitted through the first tunnel.
[0617] The third indication information is used to indicate the granularity identifier 1 and / or the TEID1. Thus, RAN1 can process the second data accordingly based on the third indication information. For example, in an uplink transmission scenario, RAN1 can determine the UPF based on the third indication information. RAN1 can then send the second data to the UPF. As another example, in a downlink transmission scenario, RAN1 can determine the UE1 based on the third indication information. RAN1 can then send the second data to the UE1.
[0618] Based on the above scheme, RAN2 can send the processed second data to RAN1. This second data can carry third indication information, which enables RAN1 to process the second data accordingly.
[0619] The following describes an example of RAN2 determining RAN1. Optionally, in the uplink transmission of architecture B, the first indication information is used to determine RAN1. In some possible implementations, method 600 further includes: S642, RAN2 determines RAN1 based on the first indication information. For example, RAN2 can route to RAN1 based on at least one of the granularity identifier 1 indicated by the first indication information, the TEID1, or the action ID1, and a pre-determined correspondence. In this way, RAN2 can send fifth information to RAN1. Optionally, S642 is executed before S640. In some other possible implementations, S640 includes: RAN2 sending fifth information to RAN1 based on the first indication information.
[0620] In some possible implementations, S642 includes: RAN2 determining RAN1 based on the first indication information and the second mapping relationship. In other possible implementations, S640 includes: RAN2 sending fifth information to RAN1 based on the first indication information and the second mapping relationship.
[0621] The second mapping relationship may include a mapping relationship between at least one of the granularity identifier 1, the TEID1, or the action ID1 and the RAN1ID. For example, the second mapping relationship may be represented as {granularity identifier 1 / TEID1 / actionID1, RAN1ID}. For example, granularity identifier 1 / TEID1 / actionID1 may represent at least one of the granularity identifier 1, the TEID1, or the action ID1.
[0622] In some possible implementations, RAN2 can determine the second mapping relationship ({granularity identifier 1 / TEID1 / action ID1, RAN1ID}) based on the first information (or the tenth information, or the twelfth information). For example, the first information (or the tenth information, or the twelfth information) comes from RAN1 and can be used to indicate granularity identifier 1. Thus, RAN2 can determine the correspondence between RAN1 and granularity identifier 1 based on the granularity identifier 1 indicated by the first information (or the tenth information, or the twelfth information) and the network element from which the first information (or the tenth information, or the twelfth information) originates. As an example, RAN2 can determine the correspondence between RAN1, granularity identifier 1, and action ID1 based on the seventh mapping relationship ({granularity identifier 1, action ID1}). As another example, RAN2 can determine the correspondence between RAN1, granularity identifier 1, and TEID1 based on the above-mentioned correspondence between RAN1 and granularity identifier 1, and the eighth mapping relationship ({granularity identifier 1, TEID1}). As another example, RAN2 can determine the mapping relationship between granularity identifier 1, TEID1, action ID1 and RAN1 based on the correspondence between RAN1 and granularity identifier 1, as well as the seventh mapping relationship ({granularity identifier 1, action ID1}) and the eighth mapping relationship ({granularity identifier 1, TEID1}).
[0623] The following describes an example of RAN2 generating third indication information. In some possible implementations, method 600 further includes: RAN2 determining the third indication information based on the first indication information.
[0624] In some examples, the third indication information is used to indicate granularity identifier 1 and / or TEID1, including: the third indication information is used to indicate granularity identifier 1. Exemplarily, the first indication information can be used to indicate at least one of granularity identifier 1, TEID1, or action ID1. Exemplarily, RAN2 can determine granularity identifier 1 based on the granularity identifier 1, TEID1, or action ID1 indicated by the first indication information, thereby determining the third indication information. Three cases are described below.
[0625] When the first indication information is used to indicate granularity identifier 1, RAN2 can generate third indication information based on the granularity identifier 1 indicated by the first indication information, and the third indication information is used to indicate granularity identifier 1.
[0626] When the first indication information is used to indicate TEID1, RAN2 can determine granularity identifier 1 based on TEID1 and the eighth mapping relationship ({granularity identifier 1, TEID1}). Further, RAN2 can generate third indication information based on granularity identifier 1, which is used to indicate granularity identifier 1.
[0627] When the first indication information is used to indicate action ID1, RAN2 can determine granularity identifier 1 based on action ID1 and the seventh mapping relationship ({granularity identifier 1, action ID1}). Further, RAN2 can generate third indication information based on granularity identifier 1, which is used to indicate granularity identifier 1.
[0628] In some examples, the third indication information is used to indicate the granularity identifier 1 and / or TEID1, including: the third indication information is used to indicate TEID1.
[0629] In some possible implementations, RAN2 can determine TEID1 based on the granularity identifier 1, TEID1, or action ID1 indicated by the first indication information. For example, as mentioned above, RAN2 can determine granularity identifier 1 based on the first indication information. For example, further, RAN2 can determine TEID1 based on granularity identifier 1 and the eighth mapping relationship ({granularity identifier 1, TEID1}).
[0630] In some possible implementations, method 600 further includes: S650, RAN1 sends ninth information to UPF. Correspondingly, UPF receives the ninth information from RAN1. Optionally, the ninth information includes the second data and sixth indication information. The sixth indication information is used to indicate the granularity identifier 1 and / or the TEID 3.
[0631] Optionally, the ninth information includes the second data. The ninth information has the function of the sixth indication information. The ninth information can be transmitted through the third tunnel.
[0632] The sixth indication information is used to indicate the granularity identifier 1 and / or the TEID3. Thus, the UPF can process the second data accordingly based on the sixth indication information. For example, the UPF can determine the corresponding APP server based on the granularity identifier 1 indicated by the sixth indication information. The UPF can then send the second data to the aforementioned APP server. As another example, the UPF can send the second data to the corresponding APP server based on the TEID3 indicated by the sixth indication information and a pre-determined correspondence.
[0633] Based on the above scheme, RAN1 can send the processed second data to UPF. This second data can carry sixth indication information, which enables UPF to perform corresponding processing on the second data.
[0634] The following describes an example of RAN1 determining the UPF. Optionally, in uplink transmission, third indication information is used to determine the UPF. In some possible implementations, method 600 further includes: S652, RAN1 determines the UPF based on the third indication information. For example, RAN1 routes to the UPF based on the granularity identifier 1 indicated by the third indication information and / or the TEID3, and a pre-determined correspondence. Thus, RAN1 can send ninth information to the UPF. Optionally, S652 is performed before S650. In other possible implementations, S650 includes: RAN1 sending ninth information to the UPF based on the third indication information.
[0635] In some possible implementations, S652 includes: RAN1 determining the UPF based on the third indication information and the sixth mapping relationship. In other possible implementations, S650 includes: RAN1 sending ninth information to the UPF based on the third indication information and the sixth mapping relationship.
[0636] The sixth mapping relationship may include the mapping relationship between the granularity identifier 1 and / or the TEID1 and the UPF ID. For example, the sixth mapping relationship may be represented as {granularity identifier 1 / TEID1, UPFID}. Here, granularity identifier 1 / TEID1 may represent granularity identifier 1 and / or the TEID1.
[0637] The following describes an example of RAN1 determining the sixth mapping relationship. In some possible implementations, RAN1 can determine the sixth mapping relationship ({granularity identifier 1 / TEID1, UPF ID}) based on the fourteenth (or fifteenth) information. For example, the fourteenth (or fifteenth) information can be used to indicate UPF ID and granularity identifier 1. In this way, RAN1 can determine the correspondence between UPF ID and granularity identifier 1 based on the fourteenth (or fifteenth) information. As an example, RAN1 can determine the correspondence between granularity identifier 1 and / or TEID1 and UPF ID based on the above correspondence between UPF ID and granularity identifier 1, and the eighth mapping relationship ({granularity identifier 1, TEID1}).
[0638] The following describes an example of RAN1 generating the sixth indication information. In some possible implementations, method 600 further includes: RAN1 can determine the sixth indication information (for indicating granularity identifier 1 and / or TEID 3) based on the third indication information (for indicating the granularity identifier 1 and / or the TEID 1).
[0639] In some examples, the sixth indication information is used to indicate granularity identifier 1 and / or the TEID 3, including: the sixth indication information is used to indicate granularity identifier 1. Exemplarily, the third indication information can be used to indicate granularity identifier 1 and / or the TEID 1. Exemplarily, RAN1 can determine granularity identifier 1 based on granularity identifier 1 or the TEID 1 indicated by the third indication information, thereby determining the sixth indication information. The two cases are described below.
[0640] When the third indication information is used to indicate granularity identifier 1, RAN1 can generate a sixth indication information based on the granularity identifier 1 indicated by the third indication information, and the sixth indication information is used to indicate granularity identifier 1.
[0641] When the third indication information is used to indicate TEID1, RAN1 can determine granularity identifier 1 based on TEID1 and the eighth mapping relationship ({granularity identifier 1, TEID1}). Further, RAN2 can generate a sixth indication information based on granularity identifier 1, which is used to indicate granularity identifier 1.
[0642] In some examples, the sixth indication information is used to indicate granularity identifier 1 and / or the TEID3, including: the sixth indication information is used to indicate TEID3. Wherein, the granularity identifier 1 and / or TEID1 indicated by the third indication information corresponds to the TEID3.
[0643] In some possible implementations, RAN1 determines TEID3 based on the third indication information. For example, as mentioned above, RAN1 can determine granularity identifier 1 based on either granularity identifier 1 indicated by the third indication information or TEID1. Further, RAN1 can determine TEID3 based on granularity identifier 1 and the tenth mapping relationship ({granularity identifier 1, TEID3}). Here, TEID1 and TEID3 can be the same or different.
[0644] In some other possible implementations, RAN2 can determine TEID3 based on TEID1. TEID1 and TEID3 can be the same.
[0645] In some possible implementations, the uplink transmission scheme of Architecture B may sequentially include: S610, S620, S624, S640, and S650. Optionally, before S620, the uplink transmission scheme of Architecture B further includes: S622. Optionally, before S640, the uplink transmission scheme of Architecture B further includes: S642. Optionally, before S650, the uplink transmission scheme of Architecture B further includes: S652. Exemplarily, in the uplink transmission scheme of Architecture B, the devices or network elements through which the data passes may sequentially be: UE1, RAN1, RAN2, RAN1, and UPF.
[0646] For example, in the downlink transmission scheme of architecture B, RAN1, RAN2, RAN1, and UPF can each perform the following routing operations. Here, "->" can represent "mapping".
[0647] RAN1: Granularity identifier 1 -> TEID1. Granularity identifier 1 -> RAN2ID.
[0648] RAN2: At least one of granularity identifier 1, TEID1, or action ID1 -> action ID1. At least one of granularity identifier 1, TEID1, or action ID1 -> RAN1ID.
[0649] RAN1: Granularity identifier 1 and / or TEID1 -> UPF ID. Granularity identifier 1 and / or TEID1 -> TEID3.
[0650] UPF: Granularity identifier 1 and / or TEID3->UE1ID.
[0651] The above section introduced an example of uplink data transmission; the following section introduces an example of downlink data transmission. In architectures A and B, the UPF can send downlink data to different network elements. For example, in architecture A, the UPF can send downlink data to RAN2. Similarly, in architecture B, the UPF can send downlink data to RAN1. These will be described in detail below.
[0652] First, we will introduce the downlink transmission scheme of Architecture A. In the downlink transmission scheme of Architecture A, the devices or network elements that the data passes through can be: UPF, RAN2, RAN1, UE1 in sequence.
[0653] In some possible implementations, method 600 further includes: S660, RAN2 receives sixth information from UPF. Correspondingly, UPF sends sixth information to RAN2. Optionally, the sixth information includes first data and fourth indication information. The fourth indication information is used to indicate the granularity identifier 1 and / or TEID2.
[0654] Optionally, the sixth information includes the first data. The sixth information functions as the fourth indication information. The sixth information can be transmitted via the second tunnel.
[0655] The fourth indication information is used to indicate the granularity identifier 1 and / or TEID2. Thus, RAN2 can process the first data accordingly based on the fourth indication information. For example, RAN2 can determine RAN1 based on the granularity identifier 1 and / or TEID2 indicated by the fourth indication information. RAN2 can then send the processed data to RAN1. Further details are provided below and will not be repeated here.
[0656] Optionally, the fourth indication information is used to indicate action ID1. In this way, RAN2 can determine that the first data requires first processing based on action ID1, and thus proceed with subsequent operations. For example, RAN2 can perform the first processing corresponding to action ID1 on the first data.
[0657] For example, the first data can be data determined by the UPF. For instance, the first data could be data received by the UPF from the DN. The first data could be downlink data. In some possible implementations, the UPF can determine RAN2 according to pre-configured or pre-defined rules. In this way, the UPF can send the sixth information to RAN2.
[0658] This application may refer to "first data" multiple times, but those skilled in the art will understand that "first data" has different meanings in different implementation scenarios. For example, in uplink transmission, "first data" can be data sent by UE1 to RAN1; "first data" can also be data sent by RAN1 to RAN2. As another example, in downlink transmission of architecture A, "first data" can be data sent by UPF to RAN2. Yet another example, in downlink transmission of architecture B, "first data" can be data sent by UPF to RAN1, and "first data" can also be data sent by RAN1 to RAN2.
[0659] In some possible implementations, method 600 further includes S624. In some possible implementations, S624 includes: S662, RAN2 performs the first processing on the first data according to the fourth instruction information to obtain the second data.
[0660] In some possible implementations, S662 includes: S664, RAN2 determines the action ID1 according to the fourth instruction information; S666, RAN2 performs the first processing on the first data according to the action ID1 to obtain the second data.
[0661] The following is an example of how RAN2 determines actionID1.
[0662] In some examples, the fourth indication information is used to indicate granularity identifier 1. Optionally, S664 includes: RAN2 can determine action ID1 based on granularity identifier 1 and the seventh mapping relationship ({granularity identifier 1, action ID1}).
[0663] In other examples, the fourth indication information is used to indicate TEID2. Optionally, S664 includes: RAN2 can determine action ID1 based on the correspondence between TEID2 and action ID. For example, RAN2 can determine the correspondence between TEID2 and action ID1 based on the twelfth information (used to indicate TEID2 and granularity identifier 1) and the seventh mapping relationship ({granularity identifier 1, action ID1}).
[0664] In some further examples, the fourth indication information is used to indicate action ID1. Optionally, S664 includes: RAN2 can determine action ID1 based on the fourth indication information.
[0665] For example, the second data may be obtained by processing the first data. The second data may be downlink data. The second data may be used to send to UE1.
[0666] This application may refer to "second data" multiple times, but those skilled in the art will understand that "second data" has different meanings in different implementation scenarios. For example, in uplink transmission of architecture A, the second data can be data sent from RAN2 to UPF. As another example, in uplink transmission of architecture B, the second data can be data sent from RAN2 to RAN1; the second data can also be data sent from RAN1 to UPF. Yet another example, in downlink transmission, the second data can be data sent from RAN2 to RAN1; the second data can also be data sent from RAN1 to UE1.
[0667] In some possible implementations, method 600 further includes: S640, RAN2 sends fifth information to RAN1. Correspondingly, RAN1 receives the fifth information from RAN2.
[0668] Optionally, the fifth information includes the second data and the third indication information. Optionally, the third indication information is used to indicate the granularity identifier 1 and / or the TEID1. Other descriptions are as described above and will not be repeated here.
[0669] The following describes an example of determining RAN1 based on RAN2. Optionally, fourth indication information is used to determine RAN1. In some possible implementations, method 600 further includes: S644, RAN2 determines RAN1 based on the fourth indication information. For example, RAN2 routes to RAN1 based on the granularity identifier 1 and / or TEID1 indicated by the fourth indication information and a pre-determined correspondence. In this way, RAN2 can send fifth information to RAN1. Optionally, S644 is performed before S640. In some other possible implementations, S640 includes: RAN2 sending fifth information to RAN1 based on the fourth indication information.
[0670] In some possible implementations, S644 includes: RAN2 determining RAN1 based on the fourth indication information and the third mapping relationship. In other possible implementations, S640 includes: RAN2 sending fifth information to RAN1 based on the fourth indication information and the third mapping relationship.
[0671] The third mapping relationship includes the mapping relationship between granularity identifier 1 and / or TEID2 and RAN1ID. For example, the third mapping relationship can be represented as {granularity identifier 1 / TEID2, RAN1ID}. Here, granularity identifier 1 / TEID2 can represent granularity identifier 1 and / or TEID2.
[0672] The following describes an example of RAN2 determining the third mapping relationship. In some possible implementations, RAN2 can determine the third mapping relationship ({granularity identifier 1 / TEID2, RAN1ID}) based on the first information (or the tenth information, or the twelfth information, or the fifteenth information). For example, the first information (or the tenth information, or the twelfth information, or the fifteenth information) comes from RAN1 and can be used to indicate granularity identifier 1. In this way, RAN2 can determine the correspondence between RAN1ID and granularity identifier 1 based on the granularity identifier 1 indicated by the first information (or the tenth information, or the twelfth information, or the fifteenth information) and the network element from which the first information (or the tenth information, or the twelfth information, or the fifteenth information) comes. As an example, RAN2 can determine the correspondence between RAN1, granularity identifier 1, and TEID2 based on the above correspondence between RAN1ID and granularity identifier 1, and the ninth mapping relationship ({granularity identifier 1, TEID2}).
[0673] The following describes an example of RAN2 generating third indication information. In some possible implementations, method 600 further includes: RAN2 determining third indication information (for indicating granularity identifier 1 and / or TEID1) based on fourth indication information (for indicating granularity identifier 1 and / or TEID2).
[0674] In some examples, the third indication information is used to indicate granularity identifier 1 and / or TEID1, including: the third indication information is used to indicate granularity identifier 1. Exemplarily, the fourth indication information can be used to indicate granularity identifier 1 and / or TEID2. Exemplarily, RAN2 can determine granularity identifier 1 based on granularity identifier 1 or TEID2 indicated by the fourth indication information, thereby determining the third indication information. Two cases are described below.
[0675] When the fourth indication information is used to indicate granularity identifier 1, RAN2 can generate third indication information based on the granularity identifier 1 indicated by the fourth indication information, and the third indication information is used to indicate granularity identifier 1.
[0676] When the fourth indication information is used to indicate TEID2, RAN2 can determine granularity identifier 1 based on TEID1 and the ninth mapping relationship ({granularity identifier 1, TEID2}). Further, RAN2 can generate third indication information based on granularity identifier 1, which is used to indicate granularity identifier 1.
[0677] In some examples, the third indication information is used to indicate the granularity identifier 1 and / or TEID1, including: the third indication information is used to indicate TEID1. Wherein, the granularity identifier 1 and / or TEID2 indicated by the fourth indication information corresponds to TEID1.
[0678] In some possible implementations, RAN2 determines TEID1 based on the fourth indication information. For example, as mentioned above, RAN2 can determine granularity identifier 1 based on granularity identifier 1 and / or TEID2 indicated by the fourth indication information. Further, RAN2 can determine TEID1 based on granularity identifier 1 and the eighth mapping relationship ({granularity identifier 1, TEID1}). Here, TEID1 and TEID2 can be the same or different.
[0679] In some other possible implementations, RAN2 can determine TEID2 based on TEID1 indicated by the fourth instruction information. TEID1 and TEID2 can be the same.
[0680] In some possible implementations, method 600 further includes: S670, RAN1 sends the second data to UE1. Correspondingly, UE1 receives the second data from RAN1.
[0681] The following describes an example of RAN1 determining UE1. Optionally, in the downlink transmission of architecture A, third indication information is used to determine UE1. In some possible implementations, method 600 further includes: S672, RAN1 determines UE1 according to the third indication information. For example, RAN1 routes to UE1 according to the granularity identifier 1 and / or TEID1 indicated by the third indication information, and a pre-determined correspondence. In this way, RAN1 can send second data to UE1. Optionally, S672 is performed before S670. In some other possible implementations, S670 includes: S674, RAN1 sends second data to UE1 according to the third indication information.
[0682] In some possible implementations, S672 includes: RAN1 determining UE1 based on the third indication information and the fifth mapping relationship.
[0683] The fifth mapping relationship may include the mapping relationship between the granularity identifier 1 and / or the TEID1 and the UE1ID. For example, the fifth mapping relationship may be represented as {granularity identifier 1 / TEID1, UE1ID}. Here, granularity identifier 1 / TEID1 may represent granularity identifier 1 and / or the TEID1.
[0684] The following describes an example of RAN1 determining the fifth mapping relationship. In some possible implementations, RAN1 can determine the fifth mapping relationship ({granularity identifier 1 / TEID1, UE1ID}) based on the first request. For example, the first request comes from UE1 and can be used to indicate granularity identifier 1. In this way, RAN1 can determine the correspondence between UE1 and granularity identifier 1 based on the granularity identifier 1 indicated by the first request and the device from which the first request came (i.e., UE1). As an example, RAN2 can determine the correspondence between UE1, granularity identifier 1, and TEID1 based on the above correspondence between UE1 and granularity identifier 1, and the eighth mapping relationship ({granularity identifier 1, TEID1}).
[0685] In some possible implementations, the downlink transmission scheme of architecture A may sequentially include: S660, S624, S640, and S670. Optionally, before S640, the downlink transmission scheme of architecture A may further include: S644. Optionally, before S670, the downlink transmission scheme of architecture A may further include: S672. Exemplarily, in the downlink transmission scheme of architecture A, the devices or network elements through which the data passes may sequentially be: UPF, RAN2, RAN1, and UE1.
[0686] For example, in the downlink transmission scheme of architecture A, UPF, RAN2, and RAN1 can each perform the following routing operations. Here, "->" can represent "mapping".
[0687] UPF: Granularity identifier 1 and / or TEID2->RAN2ID.
[0688] RAN2: At least one of granularity identifier 1, TEID2, or action ID1 -> action ID1. At least one of granularity identifier 1, TEID2, or action ID1 -> RAN1ID. At least one of granularity identifier 1, TEID2, or action ID1 -> TEID1.
[0689] RAN1: Granularity identifier 1 and / or TEID1->UE1ID.
[0690] The downlink transmission scheme of Architecture B is described below. In the downlink transmission scheme of Architecture B, the devices or network elements that the data passes through can be UPF, RAN1, RAN2, RAN1 and UE1 in sequence.
[0691] In some possible implementations, method 600 further includes: S680, RAN1 receives seventh information from UPF. Correspondingly, UPF sends seventh information to RAN1. Optionally, the seventh information includes first data and seventh indication information. The seventh indication information is used to indicate the granularity identifier 1 and / or TEID3.
[0692] Optionally, the seventh information includes the first data. The seventh information functions as a seventh indication. The seventh information can be transmitted via a third tunnel.
[0693] The seventh indication information is used to indicate the granularity identifier 1 and / or TEID3. Thus, RAN1 can process the first data accordingly based on the seventh indication information. For example, RAN1 can determine RAN2 based on the granularity identifier 1 and / or TEID3 indicated by the seventh indication information. RAN1 can then send the first data to RAN2. Further details are provided below and will not be repeated here.
[0694] Optionally, the seventh indication information is used to indicate action ID1. In this way, RAN1 can determine, based on action ID1, that the first data requires first processing, and thus proceed with subsequent operations. For example, RAN1 can determine RAN2, which is capable of performing the first processing corresponding to action ID1, and send the first data to RAN2.
[0695] In some possible implementations, the method further includes: S620, RAN1 sends third information to RAN2. Correspondingly, RAN2 receives the third information from RAN1. Optionally, the third information includes first data and first indication information. The first indication information is used to indicate at least one of granularity identifier 1, TEID1, or action ID1.
[0696] For further descriptions of the third information and the first instruction information, please refer to the preceding text, which will not be repeated here.
[0697] The following describes an example of RAN1 determining RAN2. Optionally, in the downlink transmission of architecture B, the seventh indication information is used to determine RAN2. In some possible implementations, method 600 further includes: S682, RAN1 determines RAN2 based on the seventh indication information. For example, RAN1 routes to RAN2 based on the granularity identifier 1 and / or the TEID3 indicated by the seventh indication information, and a pre-determined correspondence. In this way, RAN1 can send third information to RAN2. Optionally, S620 is performed before S682. In some other possible implementations, S620 includes: RAN1 sending third information to RAN2 based on the seventh indication information.
[0698] In some possible implementations, S682 includes: RAN1 determining RAN2 based on the seventh indication information and the twelfth mapping relationship. In other possible implementations, S620 includes: RAN1 sending third information to RAN2 based on the seventh indication information and the twelfth mapping relationship.
[0699] The twelfth mapping relationship includes the mapping relationship between the granularity identifier 1 and / or TEID3 and the RAN2ID. For example, the twelfth mapping relationship can be represented as {granularity identifier 1 / TEID3, RAN2ID}. Here, granularity identifier 1 / TEID3 can represent granularity identifier 1 and / or TEID3.
[0700] The following describes an example of RAN1 determining the twelfth mapping relationship. In some possible implementations, RAN1 can determine the twelfth mapping relationship ({granularity identifier 1 / TEID3, RAN2ID}) based on the eleventh (or fifteenth) information. For example, the eleventh (or fifteenth) information comes from RAN2 and can be used to indicate granularity identifier 1. Thus, RAN1 can determine the correspondence between RAN2 and granularity identifier 1 based on the granularity identifier 1 indicated by the eleventh (or fifteenth) information and the network element from which the eleventh (or fifteenth) information originates. As an example, RAN1 can determine the correspondence between RAN2, granularity identifier 1, and TEID3 based on the aforementioned correspondence between RAN2 and granularity identifier 1, and the tenth mapping relationship ({granularity identifier 1, TEID3}).
[0701] The following describes an example of RAN1 generating the first indication information. In some possible implementations, method 600 also includes RAN1 determining the first indication information (for indicating at least one of granularity identifier 1, TEID1, or action ID1) based on the seventh indication information (for indicating granularity identifier 1 and / or the TEID3).
[0702] In some examples, the first indication information is used to indicate at least one of granularity identifier 1, TEID1, or action ID1, including: the first indication information is used to indicate granularity identifier 1. Exemplarily, the seventh indication information can be used to indicate granularity identifier 1 and / or TEID3. Exemplarily, RAN1 can determine granularity identifier 1 based on granularity identifier 1 or TEID3 indicated by the seventh indication information, thereby determining the first indication information. Two cases are described below.
[0703] When the seventh indication information is used to indicate granularity identifier 1, RAN1 can generate first indication information based on the granularity identifier 1 indicated by the seventh indication information, and the first indication information is used to indicate granularity identifier 1.
[0704] When the seventh indication information is used to indicate TEID3, RAN1 can determine granularity identifier 1 based on TEID3 and the tenth mapping relationship ({granularity identifier 1, TEID3}). Further, RAN2 can generate first indication information based on granularity identifier 1, which is used to indicate granularity identifier 1.
[0705] In some examples, the first indication information is used to indicate at least one of granularity identifier 1, TEID1, or action ID1, including: the first indication information is used to indicate TEID1. Wherein, the granularity identifier 1 and / or TEID3 indicated by the seventh indication information correspond to TEID1.
[0706] In some possible implementations, RAN1 determines TEID1 based on the seventh indication information. For example, as mentioned above, RAN1 can determine granularity identifier 1 based on either granularity identifier 1 indicated by the seventh indication information or TEID3. Further, RAN1 can determine TEID1 based on granularity identifier 1 and the eighth mapping relationship ({granularity identifier 1, TEID1}). Here, TEID3 and TEID1 can be the same or different.
[0707] In some other possible implementations, RAN1 can determine TEID1 based on TEID3 indicated by the seventh instruction information. TEID3 and TEID1 can be the same.
[0708] In some examples, the first indication information is used to indicate at least one of granularity identifier 1, TEID1, or action ID1, including: the first indication information is used to indicate action ID1. In some possible implementations, RAN1 determines the action ID1 based on the seventh indication information. For example, as mentioned above, RAN1 can determine granularity identifier 1 based on granularity identifier 1 indicated by the seventh indication information or the TEID3. For example, further, RAN1 can determine action ID1 based on granularity identifier 1 and the seventh mapping relationship ({granularity identifier 1, action ID1}).
[0709] In some possible implementations, method 600 further includes: S625, RAN2 performs the first processing on the first data according to the first instruction information to obtain the second data.
[0710] For a detailed description, please refer to the previous text; it will not be repeated here.
[0711] In some possible implementations, method 600 further includes: S640, RAN2 sends fifth information to RAN1. Correspondingly, RAN1 receives the fifth information from RAN2.
[0712] Optionally, the fifth information includes the second data and the third indication information. Optionally, the third indication information is used to indicate the granularity identifier 1 and / or the TEID1. A detailed description of the fifth information is provided above and will not be repeated here.
[0713] The following describes an example of RAN2 determining RAN1. Optionally, in the downlink transmission of architecture B, the first indication information is used to determine RAN1. In some possible implementations, method 600 further includes: S642, whereby RAN2 determines RAN1 based on the first indication information. For example, RAN1 can route to RAN1 based on at least one of the granularity identifier 1 indicated by the first indication information, the TEID1, or the action ID1, and a pre-determined correspondence. In this way, RAN2 can send fifth information to RAN1. Optionally, S642 is executed before S640. In some other possible implementations, S640 includes: RAN2 sending fifth information to RAN1 based on the first indication information. Other descriptions, such as the determination method of S642, the second mapping relationship {granularity identifier 1 / TEID1 / action ID1, RAN1ID}, or the determination method of the third indication information, etc., are described above and will not be repeated here.
[0714] In some possible implementations, method 600 further includes: S670, RAN1 sends the second data to UE1. Correspondingly, UE1 receives the second data from RAN1.
[0715] The following describes an example of RAN1 determining UE1. Optionally, in the downlink transmission of Architecture B, third indication information is used to determine UE1. In some possible implementations, method 600 further includes: S672, RAN1 determines UE1 according to the third indication information. For example, RAN1 routes to UE1 according to the granularity identifier 1 and / or TEID1 indicated by the third indication information, and a pre-determined correspondence. In this way, RAN1 can send second data to UE1. Optionally, S672 is performed before S670. In some other possible implementations, S670 includes: S674, RAN1 sends second data to UE1 according to the third indication information. Other descriptions, such as the method for determining the fifth mapping relationship ({granularity identifier 1 / TEID1, UE1ID}), etc., are provided above and will not be repeated here.
[0716] In some possible implementations, the downlink transmission scheme of Architecture B may sequentially include: S680, S620, S625, S640, and S670. Optionally, before S620, the downlink transmission scheme of Architecture B further includes: S682. Optionally, before S640, the downlink transmission scheme of Architecture B further includes: S642. Optionally, before S670, the downlink transmission scheme of Architecture B further includes: S672. Exemplarily, in the downlink transmission scheme of Architecture B, the devices or network elements through which the data passes can sequentially be: UPF, RAN1, RAN2, RAN1, and UE1.
[0717] For example, in the downlink transmission scheme of architecture B, UPF, RAN1, RAN2, and RAN1 can each perform the following routing operations. Here, "->" can represent "mapping".
[0718] UPF: Granularity identifier 1 and / or TEID3->RAN1ID.
[0719] RAN1: Granularity identifier 1 and / or TEID3->RAN2ID. Granularity identifier 1 and / or TEID3->TEID1.
[0720] RAN2: At least one of granularity identifier 1, TEID1, or action ID1 -> action ID1. At least one of granularity identifier 1, TEID1, or action ID1 -> RAN1ID.
[0721] RAN1: Granularity identifier 1 and / or TEID1->UE1ID.
[0722] For example, in architecture B, the data that RAN1 may receive from RAN2 could be either uplink data or downlink data. In some possible implementations, the fifth information may also include information indicating whether it is an uplink or downlink transmission. The fifth information can be used by RAN1 to determine whether the second data is uplink or downlink data.
[0723] The information used to indicate uplink transmission may include a UL indicator. For example, a UL indicator is used to indicate that the second data is uplink data. The information used to indicate downlink transmission may include a DL indicator. For example, a DL indicator is used to indicate that the second data is downlink data.
[0724] In some examples, if the fifth information includes information indicating uplink transmission, RAN1 can determine that the second data in the fifth information is uplink data. In some possible implementations, if the fifth information includes information indicating uplink transmission, RAN1 determines to execute S650.
[0725] In other examples, if the fifth information includes information indicating downlink transmission, RAN1 can determine that the second data in the fifth information is downlink data. In some possible implementations, if the fifth information includes information indicating downlink transmission, RAN1 determines to execute S670.
[0726] For example, the information used to indicate uplink or downlink transmission may be third indication information. For instance, the third indication information may also be used to indicate uplink or downlink transmission. However, this application is not limited to this; for example, the information used to indicate uplink or downlink transmission may also be other information.
[0727] Based on the above scheme, the fifth piece of information can carry information indicating uplink or downlink transmission, enabling RAN1 to determine whether the second data is uplink or downlink data, and thus send the second data to the corresponding network element. For example, if the second data is uplink data, RAN1 can send the second data to UPF. As another example, if the second data is downlink data, RAN1 can send the second data to UE1.
[0728] However, this application is not limited in this respect. Even if the fifth information does not include information for indicating uplink transmission or information for indicating downlink transmission, RAN1 may still distinguish between uplink data and downlink data. For example, RAN2 may not send downlink data to RAN1. In this way, RAN1 can determine that all data from RAN2 is uplink data, and thus execute S650.
[0729] In some possible implementations, the third information may also include information indicating uplink or downlink transmission. In some possible implementations, RAN2 may determine the fifth information based on the third information. For example, if the third information includes information indicating uplink transmission, RAN2 may determine that the fifth information includes information indicating uplink transmission. As another example, if the third information includes information indicating downlink transmission, RAN2 may determine that the fifth information includes information indicating downlink transmission.
[0730] For example, the information used to indicate uplink or downlink transmission may be first indication information. For instance, the first indication information may also be used to indicate uplink or downlink transmission. However, this application is not limited to this; for example, the information used to indicate uplink or downlink transmission may also be other information.
[0731] Figure 7 This is a schematic diagram of another communication system provided in an embodiment of this application. The following is in conjunction with… Figure 7 This section introduces Architecture A and Architecture B, which are applicable to various third-party access scenarios.
[0732] As an extension of Architecture A, in some possible implementation scenarios, multiple first tunnels can be used for data transmission between RAN1 and multiple third access functions, respectively. Multiple second tunnels can be used for data transmission between the aforementioned multiple third access functions and multiple core network functions, respectively.
[0733] As an extension of Architecture B, in some possible implementation scenarios, multiple first tunnels can be used for data transmission between RAN1 and multiple third access functions, respectively. Multiple third tunnels can be used for data transmission between RAN1 and multiple core network functions, respectively.
[0734] For example, the aforementioned plurality of third access functions may include RAN2. The aforementioned plurality of core network functions may include UPF. At least two of the aforementioned plurality of core network functions may be the same, or the aforementioned plurality of core network functions may be different.
[0735] Optionally, the multiple third access functions include RAN2 and a fourth access function (hereinafter referred to as RAN4). RAN2 and RAN4 can be different. For example, the processing performed by RAN2 may differ from the processing performed by RAN4. In some examples, RAN2 and RAN4 can be different components (e.g., chips) or functions within the same access network device. In other examples, RAN2 and RAN4 are different access network devices.
[0736] RAN2 can correspond to granularity identifier 1, and RAN4 can correspond to the second identifier (hereinafter referred to as granularity identifier 2). For example, RAN2 is used to process data carrying granularity identifier 1; RAN4 is used to process data carrying granularity identifier 2. "Carrying granularity identifier 1" can be explicitly carried, for example, the data and granularity identifier 1 are carried in the same information; "Carrying granularity identifier 1" can also be implicitly carried, for example, the data and tunnel identifier (e.g., TEID1, TEID2, or TEID3) are carried in the same information, and RAN2 can determine granularity identifier 1 based on the tunnel identifier.
[0737] In some implementations, granularity identifier 2 is used to indicate at least one of the following: identifier of the second terminal device, downlink transmission, uplink transmission, QFI, DRB identifier, APP type, APP stream identifier, APP identifier, or PDU session identifier.
[0738] For example, the second terminal device may include one or more terminal devices. A description of the second terminal device can be found in the aforementioned description of the first terminal device. For ease of description, the second terminal device will be described below as a UE, referred to as UE2.
[0739] Optionally, granularity identifier 1 and granularity identifier 2 are different. For example, granularity identifier 1 and granularity identifier 2 can be used to indicate different information of the same type. For instance, both granularity identifier 1 and granularity identifier 2 are used to indicate the identifier of the terminal device, but granularity identifier 1 indicates UE1ID, and granularity identifier 2 indicates the identifier of UE2 (UE2ID), where UE1ID and UE2ID are different. As another example, both granularity identifier 1 and granularity identifier 2 are used to indicate QFI, but granularity identifier 1 indicates QFI1, and granularity identifier 2 indicates QFI2, where QFI1 is different from QFI2.
[0740] Granularity identifier 1 or granularity identifier 2, also referred to as granularity information, is used to indicate the granularity of RANXaaS. Examples of the three granularities are described below using RAN2 and RAN4 as examples, denoted as Example 4-1, Example 4-2, and Example 4-3, respectively. Those skilled in the art will understand that this application is not limited to two third access functions; architecture A or architecture B may also include more or fewer third access functions.
[0741] Example 4-1: Terminal device granularity. Figure 7 (a) and (b) in the figure show the data transmission direction of the third access function allocated at the terminal device level in architecture A and architecture B, respectively. Figure 7 In (a) and (b), UE1 and UE2 can be different.
[0742] See Figure 7 In (a), RAN2 can be an auxiliary computing node assigned to UE1. RAN2 can provide auxiliary computing services for UE1's uplink and downlink data.
[0743] See Figure 7 In (b), RAN4 can be an auxiliary computing node assigned to UE2. RAN4 can provide auxiliary computing services for UE2's uplink and downlink data.
[0744] The aforementioned auxiliary computing service may also be referred to as RAN computing or other names, and this application does not limit the specific name of the auxiliary computing service.
[0745] Example 4-2: UL / DL granularity. Figure 7 (c) and (d) in the diagram illustrate the data transmission direction of the third access function assigned at the granularity of transmission direction (e.g., UL or DL) in architectures A and B, respectively. Figure 7 In (c) and (d), UE1 and UE2 can be the same, and will be referred to as UE1 below.
[0746] See Figure 7 In (c), RAN2 can be an auxiliary computing node allocated for the uplink transmission of UE1. RAN2 can provide auxiliary computing services for the uplink data of UE1.
[0747] See Figure 7 In (d), RAN4 can be an auxiliary computing node allocated for the downlink transmission of UE1. RAN4 can provide auxiliary computing services for the downlink data of UE1.
[0748] For example, RAN2 and RAN4 can be the same or different.
[0749] This application does not limit the UL / DL granularity to the granularity of a single terminal device. For example, RAN2 can provide auxiliary calculation services for uplink data from multiple terminal devices. For example, RAN4 can provide auxiliary calculation services for downlink data from multiple terminal devices.
[0750] Example 4-3: Finer granularity. Figure 7 (e) and (f) in the diagram illustrate the data transmission direction of the third access function in architectures A and B, respectively, which is assigned at a finer granularity (e.g., QFI, DRB identifier, APP type, APP stream identifier, APP identifier, or PDU session identifier). Figure 7 In (e) and (f), UE1 and UE2 can be the same, and will be referred to as UE1 below.
[0751] See Figure 7 In (e), RAN2 can be an auxiliary computing node allocated for a more fine-grained (e.g., QFI1) uplink transmission of UE1. RAN2 can provide auxiliary computing services for a portion of the data transmitted by UE1 uplink.
[0752] See Figure 7 In (f), RAN4 can be an auxiliary computing node allocated for a more fine-grained (e.g., QFI2) uplink transmission of UE1. RAN4 can provide auxiliary computing services for a portion of the data transmitted by UE1 in its uplink transmission.
[0753] For example, RAN2 and RAN4 can be the same or different.
[0754] This application does not limit the finer granularity to the same terminal device. For example, RAN2 can provide auxiliary computing services for finer-grained data from multiple terminal devices. For instance, RAN2 can provide auxiliary computing services for QFI1 data from multiple terminal devices. Furthermore, although... Figure 7 (e) and (f) illustrate a finer-grained allocation scheme in uplink transmission; however, this application does not limit the finer granularity to the same transmission direction. For example, RAN2 can provide auxiliary calculation services for both uplink and downlink data of QFI1.
[0755] The tunnels in the embodiments of this application (e.g., the first tunnel, the second tunnel, and the third tunnel) can be dedicated tunnels or shared tunnels, and this application does not limit them.
[0756] For example, a dedicated tunnel can be used to transmit data carrying granularity identifier 1. For instance, when granularity identifier 1 is used to indicate UE1ID, the dedicated tunnel can be used only to transmit data for that UE1, which carries the UE1ID. As another example, when granularity identifier 1 is used to indicate uplink transmission, the dedicated tunnel can be used only to transmit uplink data, which carries granularity identifier 1.
[0757] For example, a shared tunnel can be used to transmit data. This data may or may not carry a granularity identifier 1. In other words, a shared tunnel can be used to transmit data carrying a granularity identifier 1, as well as data without a granularity identifier 1. For instance, a shared tunnel can be used to transmit uplink and downlink data from multiple terminal devices. As another example, a shared tunnel can be used to transmit data from multiple streams (e.g., multiple QFIs) from a single terminal device.
[0758] Optionally, the granularity identifier 1 is also used to indicate at least one of RAN1ID, RAN2ID, UPF ID, TEID1, TEID2, TEID3, or action ID1. Optionally, the granularity identifier 1 can display an indication of the above. Optionally, data (e.g., first data or second data) can display carrying the granularity identifier 1.
[0759] For example, in the uplink transmission of architecture A, granularity identifier 1 can be used to indicate granularity information, RAN1ID, RAN2ID, UPF ID, and action ID1. For example, the eighth information includes first data and the aforementioned granularity identifier 1. Thus, granularity identifier 1 can indicate that the first data will pass through the nodes RAN1, RAN2, and UPF, and indicate that the data will undergo first processing.
[0760] For example, upon receiving the aforementioned eighth information, RAN1 can determine the next-hop node as RAN2 based on this eighth information. Further, RAN1 can send third information to RAN2. This third information may include the first data and first indication information. The first indication information can be used to indicate granularity identifier 1.
[0761] Furthermore, RAN2 can determine the first processing of the first data and the next hop node as UPF based on the granularity identifier 1.
[0762] Based on the above scheme, each node related to data transmission can perform routing (e.g., next-hop node mapping) and / or auxiliary calculations (e.g., processing identifier mapping) based on the granularity identifier carried by the data, thereby realizing data transmission over the shared tunnel. The shared tunnel can be used to transmit data at multiple granularities; therefore, the above scheme can reduce the number of tunnels in the communication system, thus saving the overhead of configuring tunnels.
[0763] Those skilled in the art will recognize that, based on the units and algorithm steps described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0764] The following, combined with Figures 8 to 11 This application provides a detailed description of the communication device provided in the embodiments. The descriptions of the device embodiments correspond to the descriptions of the method embodiments; therefore, for content not described in detail, please refer to the above method embodiments. For the sake of brevity, some content will not be repeated.
[0765] This application embodiment can divide the communication device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware, software, or a combination of both. The module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The following description uses the division of functional modules according to each function as an example.
[0766] Figure 8 This is an exemplary block diagram of the communication device 10 provided in the embodiments of this application.
[0767] like Figure 8 As shown, for example, the communication device 10 may include a chip system 110, a memory 120, a bus 130, a power management module 140, or a transceiver 150, etc.
[0768] The chip system 110 can be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed through integrated logic circuits in the hardware of the chip system 110 or through software instructions.
[0769] By way of example and not limitation, chip system 110 may include circuitry or chips responsible for signal processing (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core).
[0770] Optionally, the chip system 110 may also include a memory (such as a cache) for storing instructions and data. In some embodiments, the memory in the chip system 110 is a cache memory. This memory can store instructions or data that the chip system 110 has just used or that are used repeatedly. If the chip system 110 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the chip system 110, and thus improves the efficiency of the system.
[0771] In some embodiments, the chip system 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a SIM interface, and / or a universal serial bus (USB) interface, etc.
[0772] Memory 120 may include random access memory (RAM) and read-only memory (ROM). Memory 120 may store computer-readable, computer-executable code, including instructions that, when executed, cause the processor to perform the various functions described in this application.
[0773] Optionally, the code may include instructions for implementing various aspects of the embodiments of this application, such as instructions for sending first information. The code may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, the code may not be directly executable by the chip system 110, but may enable a computer (e.g., at compile and execution time) to perform the functions described in this application. In some cases, memory 120 may contain a basic I / O system that controls basic hardware or software operations, such as interaction with peripheral components or devices.
[0774] For example, the chip system 110 executes various functional applications and data processing of the communication device 10 by running instructions stored in the memory 120. For instance, when the communication device 10 transfers files with other devices (which may also be terminals or access network devices), the chip system 110 of the communication device 10 can call the computer-executable program code stored in the memory 120 to implement the communication method provided in the embodiments of this application.
[0775] In addition, the memory 120 can be integrated into the chip system 110 or independent of the chip system 110.
[0776] For example, bus 130 may be USB for supporting communication between various parts of communication device 10.
[0777] The power management module 140 is used to receive charging input from the charger. Optionally, the power management module 140 can also supply power to the communication device 10 while charging it (e.g., the battery module of the communication device 10). By way of example and not limitation, the power management module 140 can also supply power to other devices besides the communication device 10.
[0778] Transceiver 150 can communicate bidirectionally via one or more antennas, wired links, or wireless links. For example, transceiver 150 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 150 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and for demodulating packets received from the antenna. Transceiver 150 may include a receiver and a transmitter, the receiver performing the function of receiving information and the transmitter performing the function of transmitting information.
[0779] In some cases, a wireless device may include a single antenna. However, in other cases, a device may have more than one antenna, such as... Figure 8 Antennas 1 and 2 shown may be capable of simultaneously transmitting or receiving multiple wireless transmissions. Exemplarily, antennas 1 and 2 are used to transmit and receive electromagnetic wave signals. Each antenna in communication device 10 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch. Communication device 10 can transfer files to other devices via wireless communication functions.
[0780] In one design, the communication device 20 may correspond to the second access function in the above method embodiments.
[0781] The device 10 can implement the steps or processes corresponding to the second access function in the above method embodiments. The transceiver 150 can be used to perform the transmission and reception related operations of the second access function in the above method embodiments, such as performing steps S320 and S330 in the above method embodiments. The chip system 110 can be used to perform the processing related operations of the second access function in the above method embodiments, such as performing step S624 in the above method embodiments.
[0782] In another design, the communication device 10 may correspond to the first access function in the above method embodiment.
[0783] The device 10 can implement the steps or processes corresponding to the first access function in the above method embodiment. The transceiver 150 can be used to perform the transmission and reception related operations of the first access function in the above method embodiment, such as performing steps S320 and S330 in the above method embodiment. The chip system 110 can be used to perform the processing related operations of the first access function in the above method embodiment, such as performing step S315 in the above method embodiment.
[0784] In another design, the communication device 10 may correspond to the first terminal device in the above method embodiment.
[0785] The device 10 can implement the steps or processes corresponding to those executed by the first terminal device in the above method embodiments. The transceiver 150 can be used to perform the transmission and reception related operations of the first terminal device in the above method embodiments, such as executing step S310 in the above method embodiments. The chip system 110 can be used to perform the processing related operations of the first terminal device in the above method embodiments, such as generating a first request.
[0786] Under this design, the communication device 10 may include, for example: Figure 8 The short-range communication module 164, sensor 161, display 162, or camera 163 shown are examples of such modules.
[0787] The short-range communication module 164 may include modules that support short-range communication, such as WiFi and Bluetooth.
[0788] For example, sensor 161 may include pressure sensor, gyroscope sensor, barometric pressure sensor, magnetic sensor, accelerometer, distance sensor, proximity sensor, fingerprint sensor, temperature sensor, touch sensor, ambient light sensor, bone conduction sensor, etc.
[0789] For example, display 162 is used to display images, videos, etc. The display includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a mini light-emitting diode (LED), a microLED, a microOLED, a quantum dot light-emitting diode (QLED), etc. For example, in this embodiment, the display can be used to display the interface required by the communication device 10. For example, the communication device 10 implements display functions through a graphics processing unit (GPU), a display, and an application processor. The GPU is a microprocessor for image processing, connected to the display and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The chip system 110 may include one or more GPUs that execute program instructions to generate or modify display information.
[0790] For example, camera 163 is used to acquire images, videos, etc.
[0791] Understandable Figure 8 The structure shown does not constitute a specific limitation on the communication device 10. The specific structure of the terminal equipment and / or access network equipment can be referred to Figure 8 As shown. In some embodiments, the communication device 10 may also include a... Figure 8 This could mean having more or fewer components, combining some components, separating some components, or having different component arrangements. Or, Figure 8 Some of the components shown can be implemented in hardware, software, or a combination of software and hardware. Terminal devices and / or access network devices can be implemented in… Figure 8 The components were added or removed based on the given structure.
[0792] Figure 9 This is a schematic block diagram of the communication device 20 provided in the embodiments of this application.
[0793] like Figure 9As shown, the communication device 20 may include a baseband unit 210, which can communicate with external devices via a cellular radio frequency (RF) transceiver 220 (e.g., if the communication device 20 is a terminal device, the baseband unit 210 can communicate with access network devices via the cellular RF transceiver 220; or, if the communication device 20 is an access network device, the baseband unit 210 can communicate with terminal devices and / or core network devices via the cellular RF transceiver 220).
[0794] Exemplarily, baseband unit 210 may include a computer-readable medium / memory. Baseband unit 210 may be responsible for general processing, including the execution of software stored on the computer-readable medium / memory. When executed by baseband unit 304, the software causes baseband unit 210 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by baseband unit 210 during software execution.
[0795] Optionally, the baseband unit 210 further includes a receiving unit 201, a management unit 202, and a transmitting unit 203. The management unit 202 includes one or more of these units. Figure 9 The sub-units shown (e.g., mapping sub-unit and processing sub-unit), wherein the mapping sub-unit can be used to determine the corresponding network element or determine indication information (e.g., first indication information) in the above method embodiments, and the processing sub-unit can be used to process the first data in the above method embodiments. The units within the management unit 201 can be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 210. The receiving unit 201 and the transmitting unit 203 can be referred to as transceiver units.
[0796] When the communication device 20 is used to implement the function of the second access function in the above method embodiments, the receiving unit 201 is used to perform the receiving step of the second access function, the sending unit 203 is used to perform the sending step of the second access function, and the management unit 202 is used to perform the processing step of the second access function.
[0797] For example, when the communication device 20 is used to implement the function of the second access function in the above method embodiments, the receiving unit 201 is used to receive first information from the first access function, the first information is used to indicate the identifier of the first processing, and the first information is used to request the second access function to perform the first processing; the sending unit 203 is used to send second information to the first access function, the second information is used to indicate that the second access function agrees to perform the first processing.
[0798] For example, when the device 20 is used to perform Figure 3 , Figure 5 or Figure 6When the method is in use, the receiving unit 201 can be used to execute the step of receiving information in the method; the management unit 202 can be used to execute the processing step in the method; and the sending unit 203 can be used to execute the step of sending information in the method.
[0799] When the communication device 20 is used to implement the first access function in the above method embodiments, the receiving unit 201 is used to perform the receiving step of the first access function, the sending unit 203 is used to perform the sending step of the first access function, and the management unit 202 is used to perform the processing step of the first access function.
[0800] For example, when the communication device 20 is used to implement the function of the first access function in the above method embodiments, the sending unit 203 is used to send first information to the second access function, the first information is used to indicate the identifier of the first processing, the first information is used to request the second access function to perform the first processing; the receiving unit 201 is used to receive second information from the first access function, the second information is used to indicate that the second access function agrees to perform the first processing.
[0801] For example, when the device 20 is used to perform Figure 3 , Figure 5 or Figure 6 When the method is in use, the receiving unit 201 can be used to execute the step of receiving information in the method; the management unit 202 can be used to execute the processing step in the method; and the sending unit 203 can be used to execute the step of sending information in the method.
[0802] When the communication device 20 is used to implement the functions of the first terminal device in the above method embodiments, the receiving unit 201 is used to execute the receiving step of the first terminal device, the sending unit 203 is used to execute the sending step of the first terminal device, and the management unit 202 is used to execute the processing step of the first terminal device.
[0803] For example, when the communication device 20 is used to implement the functions of the first terminal device in the above method embodiments, the management unit 202 is used to generate a first request, which is used to indicate the identifier of the first processing and to request the first processing; the sending unit 203 is used to send the first request to the first access function.
[0804] For example, when the device 20 is used to perform Figure 3 , Figure 5 or Figure 6 When the method is in use, the receiving unit 201 can be used to execute the step of receiving information in the method; the management unit 202 can be used to execute the processing step in the method; and the sending unit 203 can be used to execute the step of sending information in the method.
[0805] For a more detailed description of the receiving unit 201, management unit 202 and sending unit 203, please refer to the relevant descriptions in the above method embodiments, which will not be repeated here.
[0806] From the aforementioned Figure 8 As can be seen from the communication device shown, the communication device may include a chip system. Unless otherwise specified, the aforementioned "first access function" may refer to the access network device itself capable of implementing the first access function, or it may refer to a device capable of supporting the implementation of the second access function. Optionally, the first access function may be an access network device; or, the first access function may be a chip system within the access network device.
[0807] In addition, unless otherwise specified, the "second access function" mentioned above can refer to the access network equipment itself capable of implementing the second access function, or it can refer to a device capable of supporting the implementation of the second access function. Optionally, the second access function can be an access network equipment; or, the second access function can be a chip system in the access network equipment.
[0808] In addition, unless otherwise specified, the term "first terminal device" may refer to the first terminal device itself or to a device capable of supporting the functions of the first terminal device. Optionally, the first terminal device may be the first terminal device itself; or, the first terminal device may be a chip system within the first terminal device.
[0809] As an example and not a limitation, the chip system in this application is as follows: Figure 10 As shown, Figure 10 This is a schematic block diagram of the chip system 30 provided in the embodiments of this application. The chip system includes, but is not limited to, a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core.
[0810] from Figure 10 As can be seen, the chip system (or processing system) includes a processor 310, a memory 320, and an input / output interface 330.
[0811] The processor 310 can be a processing circuit in a chip system (including at least one processor, such as...). Figure 10(Shown as processor 1 and processor 2, etc.). Processor 310 can be coupled to memory 320, calling instructions in memory 320, so that the chip system can implement the methods and functions of the various embodiments of this application. Input / output interface 330 can be an input / output circuit in the chip system, outputting information processed by the chip system, or inputting data or signaling information to be processed into the chip system for processing.
[0812] As one approach, the chip system is used to implement the operations performed by the second access function, the first access function, or the first terminal device in the various method embodiments described above.
[0813] For example, processor 310 is used to implement processing-related operations performed by the second access function, the first access function, or the first terminal device in the above method embodiments, as described in the foregoing embodiments; input / output interface 330 is used to implement sending and / or receiving-related operations performed by the second access function, the first access function, or the first terminal device in the above method embodiments, as described in the foregoing embodiments.
[0814] As an example and not a limitation, the chip system in this application is as follows: Figure 11 As shown, Figure 11 This is a schematic block diagram of the chip system 40 provided in an embodiment of this application.
[0815] from Figure 11 As can be seen, the chip system (or processing system) includes an input / output interface 410 and logic circuits 420. The input / output interface 410 can be an input / output circuit within the chip system, outputting processed information or inputting data or signaling information to be processed into the chip system for processing. For details, please refer to the description in the foregoing embodiments, for example, performing... Figure 3 , Figure 5 or Figure 6 The embodiment described above; the logic circuit 420 is used to execute the communication method described above, and can be referred to the description in the foregoing embodiment for details.
[0816] As one approach, the chip system is used to implement the operations performed by the second access function, the first access function, or the first terminal device in the various method embodiments described above.
[0817] For example, logic circuit 420 is used to implement processing-related operations performed by the second access function, the first access function, or the first terminal device in the above method embodiments; input / output interface 410 is used to implement sending and / or receiving-related operations performed by the second access function, the first access function, or the first terminal device in the above method embodiments.
[0818] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by the device in the above-described method embodiments.
[0819] For example, when the computer program is executed by a computer, it enables the computer to implement the methods executed by the second access function, the first access function, or the first terminal device in the various embodiments of the above methods.
[0820] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods performed by the second access function, the first access function, or the first terminal device in the above-described method embodiments.
[0821] This application also provides a communication system including the aforementioned second access function and first access function. Optionally, the communication system further includes a first terminal device.
[0822] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.
[0823] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0824] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0825] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0826] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0827] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0828] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
Claims
1. A communication method characterized by comprising: The method is applied to a second access function, and the method comprises: receiving first information from a first access function, the first information being used to indicate an identity of a first process and being used to request the second access function to perform the first process; sending second information to the first access function, the second information being used to indicate that the second access function agrees to perform the first process.
2. The method of claim 1, wherein, The first process is a process offloaded from a first terminal device to the second access function, the first terminal device being used to communicate with the first access function.
3. The method according to claim 1 or 2, characterized in that, The first information is also used to indicate a first identity corresponding to the identity of the first process.
4. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: receiving third information from the first access function, the third information comprising first data and first indication information, the first indication information being used to indicate at least one of a first identity, an identity of a first tunnel or the identity of the first process, the first tunnel being used for data transmission between the first access function and the second access function; performing the first process on the first data according to the first indication information to obtain second data.
5. The method of claim 4, wherein, The method further comprises: sending fourth information to a first core network function, the fourth information comprising the second data and second indication information, the second indication information being used to indicate the first identity and / or an identity of a second tunnel, the second tunnel being used for data transmission between the second access function and the first core network function.
6. The method of claim 5, wherein, The method further comprises: determining the first core network function according to the first indication information.
7. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: receiving sixth information from a first core network function, the sixth information comprising first data and fourth indication information, the fourth indication information being used to indicate the first identity and / or an identity of a second tunnel, the second tunnel being used for data transmission between the second access function and the first core network function; performing the first process on the first data according to the fourth indication information to obtain second data.
8. The method of claim 4, wherein, The method further comprises: determining the first access function according to the first indication information.
9. The method of claim 7, wherein, The method further comprises: determining the first access function according to the fourth indication information.
10. The method according to any one of claims 4, 7-9, characterized in that, The method further comprises: sending fifth information to the first access function, the fifth information comprising the second data and third indication information, the third indication information being used to indicate the first identity and / or an identity of a first tunnel, the first tunnel being used for data transmission between the first access function and the second access function.
11. The method according to any one of claims 1 to 10, characterized in that, The first identity is used to indicate at least one of an identity of a first terminal device, downlink transmission, uplink transmission, a quality of service flow identity QFI, an identity of a data radio bearer DRB, an application program APP type, an identity of an APP flow, an identity of an APP, or an identity of a packet data unit PDU session, the first terminal device being used to communicate with the first access function.
12. A communication method characterized by comprising: The method is applied to a first access function, and the method comprises: sending first information to a second access function, the first information being used for indicating an identity of a first processing, and the first information being used for requesting the second access function to perform the first processing; receiving second information from the first access function, the second information being used for indicating that the second access function agrees to perform the first processing.
13. The method of claim 12, wherein, The first information is further used for indicating a first identity, the first identity corresponding to the identity of the first processing.
14. The method according to claim 12 or 13, characterized in that, The method further comprises: receiving a first request from a first terminal device, the first request being used for indicating an identity of a first processing, and the first request being used for requesting to perform the first processing.
15. The method according to any one of claims 12 to 14, characterized in that, The method further comprises: sending third information to the second access function, the third information comprising the first data and first indication information, the first indication information being used for indicating at least one of a first identity, an identity of a first tunnel, or the identity of the first processing, and the first indication information being used for indicating that the first processing is performed on the first data, and the first tunnel being used for data transmission between the first access function and the second access function.
16. The method of claim 15, wherein, The method further comprises: receiving seventh information from a first core network function, the seventh information comprising the first data and seventh indication information, the seventh indication information being used for indicating the first identity and / or TEID3, and the third tunnel being used for data transmission between the first access function and the first core network function.
17. The method of claim 16, wherein, The method further comprises: determining the second access function according to the seventh indication information.
18. The method of claim 15, wherein, The method further comprises: receiving eighth information from the first terminal device, the eighth information comprising the first data and the first identity.
19. The method of claim 18, wherein, The method further comprises: determining the second access function according to the first identity.
20. The method of any one of claims 12-19, wherein, The method further comprises: receiving fifth information from the second access function, the fifth information comprising second data and third indication information, the third indication information being used for indicating the first identity and / or an identity of the first tunnel, and the second data being obtained by performing the first processing on the first data.
21. The method of claim 20, wherein, The method further comprises: sending the second data to the first terminal device according to the third indication information.
22. The method of claim 20, wherein, The method further comprises: sending ninth information to a first core network function, the ninth information comprising the second data and sixth indication information, the sixth indication information being used for indicating the first identity and / or TEID3, and the third tunnel being used for data transmission between the first access function and the first core network function.
23. The method of any one of claims 20-22, wherein, The fifth information further comprises information used for indicating uplink transmission or downlink transmission.
24. The method of any one of claims 12-23, wherein, The first identity is used for indicating at least one of an identity of the first terminal device, downlink transmission, uplink transmission, a quality of service flow identity QFI, an identity of a data radio bearer DRB, an application APP type, an identity of an APP flow, an identity of an APP, or an identity of a packet data unit PDU session.
25. A method of communication, comprising: The method is applied to a first terminal device, and the method comprises: generating a first request, the first request being used to indicate an identity of a first processing, the first request being used to request to perform the first processing; sending the first request to a first access function.
26. The method of claim 25, wherein, The first request is further used to indicate a first identity, the first identity corresponding to the identity of the first processing.
27. The method of claim 26, wherein, The first identity is used to indicate at least one of an identity of the first terminal device, downlink transmission, uplink transmission, a quality of service flow identity (QFI), an identity of a data radio bearer (DRB), an application program (APP) type, an identity of an APP flow, an identity of an APP, or an identity of a packet data unit (PDU) session.
28. The method of any one of claims 25-27, wherein, The method further includes: receiving second data from the first access function, the second data being obtained by performing the first processing on first data.
29. The method of any one of claims 25-28, wherein, The method further includes: sending eighth information to the first access function, the eighth information including the first data and a first identity, the first data being used to obtain second data by performing the first processing.
30. A communications device, characterized by at least one module or at least one unit, the at least one module or the at least one unit being used to execute the method in any one of claims 1 to 11, or the at least one module or the at least one unit being used to execute the method in any one of claims 12 to 24, or the at least one module or the at least one unit being used to execute the method in any one of claims 25 to 29.
31. A communications device, characterized by comprising: a processor, the processor being used to execute the method in any one of claims 1 to 11, or the method in any one of claims 12 to 24, or the method in any one of claims 25 to 29, by executing computer programs or instructions.
32. The communication apparatus of claim 31, wherein The communication device further includes a memory, the memory being used to store the computer programs or the instructions.
33. A computer-readable storage medium, comprising: The computer readable storage medium has stored thereon computer programs or instructions, which, when run on a computer, cause the method in any one of claims 1 to 11 to be executed, or the method in any one of claims 12 to 24 to be executed, or the method in any one of claims 25 to 29 to be executed.
34. A computer program product, characterised in that, comprising computer programs or instructions, which, when run, implement the method in any one of claims 1 to 11, or the method in any one of claims 12 to 24, or the method in any one of claims 25 to 29.