Data unit processing

By adopting a service-based architecture and network function interface in the wireless communication network, flexible access and service quality management between the wireless device and the core network are achieved, and the problem of communication complexity of various wireless devices and base stations in the prior art is solved. , improves the flexibility and management efficiency of the network, and enhances the performance and security in roaming and untrusted access scenarios.

CN118923099APending Publication Date: 2024-11-08OFINNO LLC
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202380018020.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-01-21
Filing Date
2023-01-20
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

The prior art is difficult to effectively manage communication between a variety of wireless devices and base stations in wireless communication networks, especially in roaming situations and untrusted access scenarios, resulting in complex network slice selection and service quality management.

Method used

It adopts a service-based architecture, provides services through the interface between network functions (NF), realizes flexible access and service quality management between wireless devices and core networks, and supports customized management of multiple network slicing and service types.

Benefits of technology

It improves the flexibility and management efficiency of wireless communication networks, supports the customization of multiple network slicing and service types, and enhances network performance and security in roaming and untrusted access scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118923099A_ABST
    Figure CN118923099A_ABST
Patent Text Reader

Abstract

A first device discards a plurality of packets associated with a data unit of a data stream based on a transmission failure of at least one of the plurality of packets. The first device transmits an indication that the plurality of packets are discarded.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is a continuation of U.S. Provisional Application No. 63 / 301,541 filed on January 21, 2022, the entire contents of which are hereby incorporated by reference. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Figure 1A and Figure 1B An example communication network including an access network and a core network is shown.

[0004] Figure 2A , Figure 2B , Figure 2C and Figure 2D Various examples of frameworks for service-based architectures within a core network are shown.

[0005] Figure 3 An example communication network including core network functionality is shown.

[0006] Figure 4A and Figure 4B An example of a core network architecture with multiple user plane functions and untrusted access is shown.

[0007] Figure 5 An example of a core network architecture for a roaming scenario is shown.

[0008] Figure 6 An example of network slicing is shown.

[0009] Fig. 7A , Figure 7B and Figure 7C A user plane protocol stack, a control plane protocol stack, and services provided between protocol layers of the user plane protocol stack are shown.

[0010] Figure 8 An example of a quality of service model for data exchange is shown.

[0011] Fig. 9A , Fig. 9B , Fig. 9C and Fig.9D Example states and state transitions of a wireless device are shown.

[0012] Fig.10 An example of a registration procedure for a wireless device is shown.

[0013] Fig.11 An example of a service request procedure for a wireless device is shown.

[0014] Fig.12 An example of a protocol data unit session establishment procedure for a wireless device is shown.

[0015] Fig.13 An example of an assembly of elements in a communication network is shown.

[0016] Fig.14A , Fig. 14B , Fig. 14C and Fig.14D Various examples of physical core network deployments, each having one or more network functions or portions thereof, are shown.

[0017] Fig.15 are diagrams of aspects of exemplary embodiments of the present disclosure.

[0018] Fig.16 are diagrams of aspects of exemplary embodiments of the present disclosure.

[0019] Fig.17 are diagrams of aspects of exemplary embodiments of the present disclosure.

[0020] Fig.18 are diagrams of aspects of exemplary embodiments of the present disclosure.

[0021] Fig.19 are diagrams of aspects of exemplary embodiments of the present disclosure.

[0022] Fig. 20 are diagrams of aspects of exemplary embodiments of the present disclosure.

[0023] Fig.21 are diagrams of aspects of exemplary embodiments of the present disclosure.

[0024] Fig. 22 are diagrams of aspects of exemplary embodiments of the present disclosure.

[0025] Fig.23 are diagrams of aspects of exemplary embodiments of the present disclosure.

[0026] Fig.24 are diagrams of aspects of exemplary embodiments of the present disclosure.

[0027] Fig.25 are diagrams of aspects of exemplary embodiments of the present disclosure.

[0028] Fig.26 are diagrams of aspects of exemplary embodiments of the present disclosure.

[0029] Fig. 27 are diagrams of aspects of exemplary embodiments of the present disclosure. DETAILED DESCRIPTION

[0030] In the present disclosure, various embodiments are presented in the form of examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in environments and scenarios. It will be apparent to those skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope of the present invention. In fact, after reading the specification, it will be apparent to those skilled in the relevant art how to implement alternative embodiments. The embodiments of the present invention should not be limited to any described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Restrictions, features and / or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of the present disclosure. Any figure highlighting functionality and advantages is provided only for illustrative purposes. The disclosed architecture is flexible and configurable enough so that it can be utilized in a manner different from that shown. For example, the actions listed in any flow chart can be reordered or only optionally used in certain embodiments.

[0031] Embodiments may be configured to operate as desired. For example, in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., when certain criteria are met, the disclosed mechanism may be executed. Exemplary criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. When one or more criteria are met, various exemplary embodiments may be applied. Therefore, exemplary embodiments that selectively implement the disclosed protocol may be implemented.

[0032] A base station may communicate with a mixture of wireless devices. A wireless device and / or a base station may support multiple technologies and / or multiple versions of the same technology. A wireless device may have one or more specific capabilities. When the present disclosure refers to a base station communicating with multiple wireless devices, the present disclosure may mean a subset of the total wireless devices in the coverage area. For example, the present disclosure may mean multiple wireless devices of a given LTE or 5G version with a given capability and in a given sector of a base station. The multiple wireless devices in the present disclosure may refer to a selected plurality of wireless devices, and / or a subset of the total wireless devices in the coverage area that perform according to the disclosed method, etc. There may be multiple base stations or multiple wireless devices in the coverage area that may not comply with the disclosed method, for example, these wireless devices or base stations may perform based on older versions of LTE or 5G technology.

[0033] In the present disclosure, "a" and "an" and similar phrases refer to a single instance of a particular element, but should not be interpreted as excluding other instances of the element. For example, a bicycle with two wheels may be described as having "wheels". Any term ending with the suffix "(s)" will be interpreted as "at least one" and / or "one or more". In the present disclosure, the term "may" is interpreted as "may, for example". In other words, the term "may" indicates that the phrase following the term "may" is an example of a suitable possibility among a plurality of suitable possibilities that may or may not be used for one or more embodiments in various embodiments. As used herein, the terms "comprising" and "consisting of..." list one or more components of the element being described. The terms "comprising" and "including" are interchangeable and do not exclude that unlisted components are included in the element being described. In contrast, "consisting of..." provides a complete listing of the one or more components of the element being described.

[0034] The phrases "based on," "in response to," "depending on," "using," "using," and similar phrases indicate the presence and / or influence of certain factors and / or conditions on an event and / or action, but do not exclude the presence and / or influence of uncounted factors and / or conditions. For example, if action X is performed "based on" condition Y, this is interpreted as performing the action "based at least on" condition Y. For example, if action X is performed when conditions Y and Z are both met, then the performance of action X can be described as "based on Y."

[0035] The term "configured" may relate to the capabilities of a device, whether the device is in an operational state or a non-operational state. "Configured" may also mean a specific setting in a device that affects the operating characteristics of the device, whether the device is in an operational state or a non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. may be "configured" within a device to provide specific characteristics to the device, whether the device is in an operational state or a non-operational state. Terms such as "a control message caused in a device" may mean that the control message has parameters that can be used to configure specific characteristics in the device or parameters that can be used to implement certain actions in the device, whether the device is in an operational state or a non-operational state.

[0036] In the present disclosure, a parameter may include one or more information objects, and an information object may include one or more other objects. For example, if parameter J includes parameter K, and parameter K includes parameter L, and parameter L includes parameter M, then J includes L, and J includes M. Parameters may be referred to as fields or information elements. In an example embodiment, when one or more messages include multiple parameters, it means that a parameter in the multiple parameters is in at least one of the one or more messages, but not necessarily in each of the one or more messages.

[0037] The present disclosure may relate to possible combinations of enumerated elements. For the sake of brevity and readability, the present disclosure does not explicitly describe each arrangement that can be obtained by selecting from the set of optional features. The present disclosure should be interpreted as explicitly disclosing all such arrangements. For example, seven possible combinations of enumerated elements A, B, and C are composed of the following: (1) "A"; (2) "B"; (3) "C"; (4) "A and B"; (5) "A and C"; (6) "B and C"; and (7) "A, B, and C". For the sake of brevity and readability, these seven possible combinations can be described using any of the following interchangeable expressions: "at least one of A, B, and C"; "at least one of A, B, or C"; "one or more of A, B, and C"; "one or more of A, B, or C"; "A, B, and / or C". It should be understood that impossible combinations are excluded. For example, "X and / or non-X" should be interpreted as "X or non-X". It should also be understood that these expressions may describe alternative wordings of overlapping and / or synonymous concepts, for example, "identifier, identification and / or ID number."

[0038] The present disclosure may relate to sets and / or subsets. As an example, a set X may be an element set comprising one or more elements. If each element of X is also an element of Y, then X may be referred to as a subset of Y. In the present disclosure, only non-empty sets and subsets are considered. For example, if Y is composed of elements Y1, Y2, and Y3, then the possible subsets of Y are {Y1, Y2, Y3}, {Y1, Y2}, {Y1, Y3}, {Y2, Y3}, {Y1}, {Y2}, and {Y3}.

[0039] Figure 1A 1 shows an example of a communication network 100 in which embodiments of the present disclosure may be implemented. The communication network 100 may include, for example, a public land mobile network (PLMN) operated by a network operator. Figure 1A As shown in , the communication network 100 includes a wireless device 101 , an access network (AN) 102 , a core network (CN) 105 , and one or more data networks (DN) 108 .

[0040] The wireless device 101 may communicate with the DN 108 via the AN 102 and the CN 105. In the present disclosure, the term wireless device may refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is required or can be used. For example, the wireless device may be a phone, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a vehicle roadside unit (RSU), a relay node, a car, a drone, an urban air traffic, and / or any combination thereof. The term "wireless device" encompasses other terms including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmission and reception unit (WTRU), and / or wireless communication device.

[0041] AN 102 may connect the wireless device 101 to CN 105 in any suitable manner. The direction of communication from AN 102 to the wireless device 101 is referred to as downlink, while the direction of communication from the wireless device 101 to AN 102 is referred to as uplink. Downlink transmissions may be separated from uplink transmissions using frequency division duplex (FDD), time division duplex (TDD), and / or some combination of the two duplex technologies. AN 102 may be connected to the wireless device 101 by radio communication via an air interface. An access network that operates at least partially via an air interface may be referred to as a radio access network (RAN). CN 105 may set up one or more end-to-end connections between the wireless device 101 and the one or more DNs 108. CN 105 may authenticate the wireless device 101 and provide billing functionality.

[0042] In the present disclosure, the term base station may refer to and encompass any element of AN102 that facilitates communication between wireless device 101 and AN 102. Access networks and base stations have many different names and implementations. A base station may be a terrestrial base station fixed to the ground. A base station may be a mobile base station with a mobile coverage area. A base station may be in space, such as on a satellite. For example, WiFi and other standards may use the term access point. As another example, the third generation partnership project (3GPP) has produced specifications for three generations of mobile networks, each of which uses different terms. The third generation (3G) and / or universal mobile telecommunications system (UMTS) standards may use the term node B. 4G, long term evolution (LTE), and / or evolved universal terrestrial radio access (E-UTRA) standards may use the term evolved node B (eNB). 5G and / or New Radio (NR) standards may describe AN 102 as a next generation radio access network (NG-RAN), and the base station may be referred to as a next generation eNB (ng-eNB) and / or gNB (Generation Node B). Future standards (e.g., 6G, 7G, 8G) may use new terms to refer to elements (e.g., wireless devices, base stations, AN, CN, and / or components thereof) that implement the methods described in the present disclosure. The base station may be implemented as a repeater or relay node for extending the coverage area of ​​the donor node. The repeater node may amplify and rebroadcast the radio signal received from the donor node. The relay node may perform the same / similar functions as the repeater node, but may decode the radio signal received from the donor node to eliminate noise before amplifying and rebroadcasting the radio signal.

[0043] AN 102 may include one or more base stations, each of which has one or more coverage areas. The geographical size and / or range of the coverage area may be defined according to the range in which the receiver of AN 102 can successfully receive transmissions from a transmitter (e.g., wireless device 101) operating within the coverage area (and / or vice versa). The coverage area may be referred to as a partition or cell (but in some contexts, the term cell refers to the carrier frequency used in a particular coverage area, not the coverage area itself). A base station with a large coverage area may be referred to as a macrocell base station. Other base stations cover smaller areas to provide coverage, for example, in areas with weak macrocell coverage, or to provide additional coverage in areas with high traffic (sometimes referred to as hotspots). Examples of small cell base stations include, in descending order of coverage area: microcell base stations, picocell base stations, and femtocell base stations or home base stations. The coverage areas of the base stations may together provide wireless coverage to the wireless device 101 over a wide geographic area to support wireless device mobility.

[0044] The base station may include one or more groups of antennas for communicating with the wireless device 101 via an air interface. Each group of antennas may be controlled individually by the base station. Each group of antennas may have a corresponding coverage area. As an example, the base station may include three groups of antennas to respectively control three coverage areas on three different sides of the base station. The entire base station (and its corresponding antennas) may be deployed at a single location. Alternatively, a controller at a central location may control one or more groups of antennas at one or more distributed locations. The controller may be, for example, a baseband processing unit that is part of a centralized or cloud RAN architecture. The baseband processing unit may be concentrated in a pool of baseband processing units or virtualized. A group of antennas at a distributed location may be referred to as a remote radio head (RRH).

[0045] Figure 1B 1 shows another example communication network 150 in which embodiments of the present disclosure may be implemented. The communication network 150 may include, for example, a PLMN operated by a network operator. Figure 1B As shown in , the communication network 150 includes a UE 151, a next generation radio access network (NG-RAN) 152, a 5G core network (5G-CN) 155, and one or more DNs 158. The NG-RAN 152 includes one or more base stations, shown as a next generation node B (gNB) 152A and a next generation evolved node B (ng eNB) 152B. The 5G-CN 155 includes one or more network functions (NFs), which include a control plane function 155A and a user plane function 155B. The one or more DNs 158 may include a public DN (e.g., the Internet), a dedicated DN, and / or an intra-operator DN. With respect to Figure 1A , and the corresponding components shown in the figure may represent specific implementations and / or terms.

[0046] The base stations of NG-RAN 152 may be connected to UE 151 via a Uu interface. The base stations of NG-RAN 152 may be connected to each other via an Xn interface. The base stations of NG-RAN 152 may be connected to 5G CN 155 via an NG interface. The Uu interface may include an air interface. The NG and Xn interfaces may include an air interface, or may consist of a direct physical connection and / or an indirect connection via an underlying transport network (e.g., an Internet Protocol (IP) transport network).

[0047] Each of the Uu, Xn, and NG interfaces may be associated with a protocol stack. The protocol stack may include a user plane (UP) and a control plane (CP). Typically, user plane data may include data about a user of UE 151, such as Internet content downloaded via a web browser application, sensor data uploaded via a tracking application, or email data transmitted to or from an email server. In contrast, control plane data may include signaling and messages that facilitate the packaging and routing of user plane data so that it can be exchanged with a DN. For example, the NG interface may be divided into an NG user plane interface (NG-U) and an NG control plane interface (NG-C). The NG-U interface may provide for the delivery of user plane data between a base station and the one or more user plane network functions 155B. The NG-C interface may be used for control signaling between a base station and the one or more control plane network functions 155A. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transmission of NAS messages, paging, PDU session management, and configuration delivery and / or warning message transmission. In some cases, the NG-C interface may support the transmission of user data (e.g., small data transmission for IoT devices).

[0048] One or more of the base stations of the NG-RAN 152 may be split into a central unit (CU) and one or more distributed units (DUs). The CU may be connected to the one or more DUs via an F1 interface. The CU may process one or more upper layers in the protocol stack, and the DU may process one or more lower layers in the protocol stack. For example, the CU may process RRC, PDCP, and SDAP, and the DU may process RLC, MAC, and PHY. The one or more DUs may be in geographically distinct locations relative to the CU and / or relative to each other. Accordingly, the CU / DU split architecture may allow for increased coverage and / or better coordination.

[0049] gNB 152A and ng-eNB 152B may provide different user plane and control plane protocol terminations toward UE 151. For example, gNB 154A may provide new air interface (NR) protocol termination via a Uu interface associated with a first protocol stack. ng-eNB 152B may provide evolved UMTS terrestrial radio access (E-UTRA) protocol termination via a Uu interface associated with a second protocol stack.

[0050] 5G-CN 155 may authenticate UE 151, set up end-to-end connection between UE 151 and the one or more DNs 158, and provide charging functionality. 5G-CN 155 may be based on a service-based architecture, in which the NFs that make up 5G-CN 155 provide services to each other and to other elements of the communication network 150 via interfaces. 5G-CN 155 may include any number of other NFs and any number of instances of each NF.

[0051] Figure 2A , Figure 2B , Figure 2C and Figure 2D Various examples of frameworks for a service-based architecture within a core network are shown. In a service-based architecture, service consumers may seek services and services are provided by service producers. Before obtaining a particular service, the NF may determine where this service can be obtained. In order to discover services, the NF may communicate with a network repository function (NRF). As an example, a NF that provides one or more services may register with a network repository function (NRF). The NRF may store data related to the one or more services that the NF is preparing to provide to other NFs in the service-based architecture. A consumer NF may query the NRF to discover a producer NF (e.g., by obtaining a list of NF instances that provide a particular service from the NRF).

[0052] exist Figure 2A In the example of , NF 211 (in this example, a consumer NF) may send a request 221 to NF 212 (a producer NF). Request 221 may be a request for a specific service and may be sent based on the discovery that NF 212 is a producer of the service. Request 221 may include data related to NF 211 and / or the requested service. NF 212 may receive request 221, perform one or more actions associated with the requested service (e.g., retrieve data), and provide response 221. The one or more actions performed by NF 212 may be based on the request data contained in request 221, data stored by NF 212, and / or data retrieved by NF 212. Response 222 may notify NF 211 that the one or more actions have been completed. Response 222 may include response data related to NF 212, the one or more actions, and / or the requested service.

[0053] exist Figure 2B In the example of FIG. 24 , NF 231 sends request 241 to NF 232. In this example, part of the service generated by NF 232 will be to send request 242 to NF 233. NF 233 may perform one or more actions and provide response 243 to NF 232. Based on response 243, NF 232 may send response 244 to NF 231. Figure 2B It will be understood that a single NF may perform the role of a service producer, a service consumer, or both. A particular NF service may contain any number of nested NF services produced by one or more other NFs.

[0054] Figure 2C An example of a subscription-notification interaction between a consumer NF and a producer NF is shown. Figure 2C , NF 251 sends subscription 261 to NF 252. NF 253 sends subscription 262 to NF 252. For illustrative purposes, Figure 2C 252 may provide multiple subscription services to different NFs), but it should be understood that the subscription-notification interaction requires only one subscriber. NFs 251, 253 may be independent of each other. For example, NFs 251, 253 may independently discover NF 252 and / or independently determine to subscribe to services provided by NF 252. In response to receiving a subscription, NF 252 may provide a notification to the subscribing NF. For example, NF 252 may send notification 263 to NF 251 based on subscription 261, and may send notification 264 to NF 253 based on subscription 262.

[0055] like Figure 2C As shown in the example diagram of , the sending of notifications 263, 264 may be based on determining that a certain condition has occurred. For example, notifications 263, 264 may be based on determining that a particular event has occurred, determining that a particular condition is pending, and / or determining that a duration associated with a subscription has elapsed (e.g., a period associated with a subscription for periodic notifications). Figure 2C As shown in the example illustration of , NF 252 may send notifications 263, 264 to NF 251, 253 simultaneously and / or in response to the same condition. However, it should be understood that NF 252 may provide notifications at different times and / or in response to different notification conditions. In the example, NF 251 may request notification when a specific parameter as measured by NF 252 exceeds a first threshold, and NF 252 may request notification when the parameter exceeds a second threshold different from the first threshold. In the example, the parameters of interest and / or the corresponding thresholds may be indicated in the subscriptions 261, 262.

[0056] Figure 2D Another example of a subscribe-notify interaction is shown. Figure 2D In the example, NF 271 sends a subscription 281 to NF 272. In response to receiving the subscription 281 and / or determining that a notification condition has occurred, NF 272 may send a notification 284. Notification 284 may be sent to NF 273. Figure 2C Example in (where notification is sent to subscribing NF), Figure 2DPresentation, subscription and its corresponding notification can be associated with different NFs. For example, NF 271 can subscribe to the service provided by NF 272 on behalf of NF 273.

[0057] Figure 3 Another example communication network 300 is shown in which embodiments of the present disclosure may be implemented. The communication network 300 includes a user equipment (UE) 301 , an access network (AN) 302 , and a data network (DN) 308 . Figure 3 The remaining elements depicted in the figure may be included in and / or associated with the core network. Each element of the core network may be referred to as a network function (NF).

[0058] Figure 3 The NF depicted in FIG. 3 includes a user plane function (UPF) 305, an access and mobility management function (AMF) 312, a session management function (SMF) 314, a policy control function (PCF) 320, a network repository function (NRF) 330, a network exposure function (NEF) 340, a unified data management (UDM) 350, an authentication server function (AUSF) 360, a network slice selection function (NSSF) 370, a charging function (CHF) 380, a network data analysis function (NWDAF) 390, and an application function (AF) 399. UPF 305 may be a user plane core network function, and NFs 312, 314, and 320-390 may be control plane core network functions. Although Figure 3 Not shown in the example of FIG, the core network may include additional instances of any of the depicted NFs and / or one or more different NF types providing different services. Other examples of NF types include Gateway Mobile Location Center (GMLC), Location Management Function (LMF), Operation, Administration and Maintenance Function (OAM), Public Warning System (PWS), Short Message Service Function (SMSF), Unified Data Repository (UDR), and Unstructured Data Storage Function (UDSF).

[0059] Figure 3 Each element depicted in has an interface with at least one other element. The interface may be a logical connection rather than, for example, a direct physical connection. Any interface may be identified using a reference point representation and / or a service-based representation. In a reference point representation, the letter 'N' followed by a number indicates an interface between two specific elements. For example, Figure 3As shown, AN 302 and UPF 305 are interfaced via 'N3', while UPF 305 and DN 308 are interfaced via 'N6'. In contrast, in a service-based representation, the letter 'N' is followed by a letter. The letter identifies the NF that provides services to the core network. For example, PCF 320 can provide services via interface 'Npcf'. PCF 320 can provide services to any NF in the core network via 'Npcf'. Accordingly, the service-based representation can correspond to a set of reference point representations. For example, the Npcf interface between PCF 320 and the core network can generally correspond to the N7 interface between PCF 320 and SMF 314, the N30 interface between PCF 320 and NEF 340, and so on.

[0060] The UPF 305 may act as a gateway for user plane traffic between the AN 302 and the DN 308. The UE 301 may be connected to the UPF 305 via the Uu interface and the N3 interface (also described as the NG-U interface). The UPF 305 may be connected to the DN 308 via the N6 interface. The UPF 305 may be connected to one or more other UPFs (not shown) via the N9 interface. The UE 301 may be configured to receive services via a protocol data unit (PDU) session, which is a logical connection between the UE 301 and the DN 308. The UPF 305 (or multiple UPFs, as required) may be selected by the SMF 314 to handle a specific PDU session between the UE 301 and the DN 308. The SMF 314 may control the functions of the UPF 305 with respect to the PDU session. The SMF 314 may be connected to the UPF 305 via the N4 interface. The UPF 305 may handle any number of PDU sessions associated with any number of UEs (via any number of ANs). For the purpose of handling the one or more PDU sessions, the UPF 305 may be controlled by any number of SMFs via any number of corresponding N4 interfaces.

[0061] Figure 3 The AMF 312 depicted in FIG. 3 may control the UE's access to the core network. The UE 301 may register with the network via the AMF 312. The UE 301 may have to register before establishing a PDU session. The AMF 312 may manage the registration area of ​​the UE 301, thereby enabling the network to track the physical location of the UE 301 within the network. For a UE in connected mode, the AMF 312 may manage UE mobility, such as handover from one AN or part thereof to another AN. For a UE in idle mode, the AMF 312 may perform registration updates and / or paging the UE to transition the UE to connected mode.

[0062] AMF 312 may receive non-access stratum (NAS) messages transmitted according to the NAS protocol from UE 301. NAS messages relate to communications between UE 301 and the core network. Although NAS messages may be relayed to AMF 312 via AN 302, they may be described as communications via the N1 interface. NAS messages may facilitate UE registration and mobility management, for example, by authenticating, identifying, configuring and / or managing the connection of UE 301. NAS messages may support session management procedures for maintaining user plane connectivity and quality of service (QoS) for sessions between UE 301 and DN 309. If the NAS message relates to session management, AMF 312 may send the NAS message to SMF 314. NAS messages may be used to transmit messages between UE 301 and other components of the core network (e.g., core network components other than AMF 312 and SMF 314). AMF 312 may act on a specific NAS message itself, or forward the NAS message to an appropriate core network function (e.g., SMF 314, etc.).

[0063] Figure 3 The SMF 314 depicted in FIG. 314 may establish, modify and / or publish a PDU session based on the messaging received at the UE 301. The SMF 314 may, for example, allocate, manage and / or assign an IP address to the UE 301 after establishing the PDU session. There may be multiple SMFs in the network, each of which may be associated with a wireless device, a base station and / or a UPF of a corresponding group. A UE with multiple PDU sessions may be associated with a different SMF for each PDU session. As described above, the SMF 314 may select one or more UPFs to process the PDU session, and may control the processing of the PDU session by the selected UPF by providing rules (PDR, FAR, QER, etc.) for packet processing. Rules related to QoS and / or charging for a specific PDU session may be obtained from the PCF 320 and provided to the UPF 305.

[0064] PCF 320 may provide services related to policy rules to other NFs. PCF 320 may use subscription data and information about network conditions to determine policy rules, and then provide the policy rules to specific NFs that may be responsible for enforcing those rules. Policy rules may relate to policy control for access and mobility, and may be enforced by AMF. Policy rules may relate to session management, and may be enforced by SMF 314. Policy rules may be, for example, network-specific, wireless device-specific, session-specific, or data flow-specific.

[0065] The NRF 330 may provide service discovery. The NRF 330 may belong to a specific PLMN. The NRF 330 may maintain NF profiles related to other NFs in the communication network 300. The NF profile may contain, for example, the address of the NF, the PLMN and / or type, a slice identifier, a list of the one or more services provided by the NF, and the authorization required to access the service.

[0066] Figure 3 The NEF 340 depicted in FIG. 3 may provide an interface to an external domain, thereby allowing the external domain to selectively access the control plane of the communication network 300. The external domain may include, for example, third-party network functions, application functions, etc. The NEF 340 may act as a proxy between external elements and network functions such as AMF 312, SMF 314, PCF 320, UDM 350, etc. As an example, the NEF 340 may determine the location or reachability status of the UE 301 based on a report from the AMF 312, and provide the status information to the external element. As an example, the external element may provide information via the NEF 340 that facilitates setting parameters for establishing a PDU session. The NEF 340 may determine which data and capabilities of the control plane are open to the external domain. The NEF 340 may provide a secure opening that authenticates and / or authorizes the data or capabilities of the communication network 300 to be opened to the external entity. The NEF 340 may selectively control the opening so that the internal architecture of the core network is hidden from the external domain.

[0067] The UDM 350 may provide data storage for other NFs. The UDM 350 may allow a consolidated view of network information, which may be used to ensure that the most relevant information may be made available to different NFs from a single resource. The UDM 350 may store and / or retrieve information from a unified data repository (UDR). For example, the UDM 350 may obtain user subscription data associated with the UE 301 from the UDR.

[0068] AUSF 360 may support mutual core network authentication of UE 301 and authentication of UE 301 to the core network. AUSF 360 may perform key agreement procedures and provide key material that may be used to improve security.

[0069] NSSF 370 may select one or more network slices to be used by UE 301. NSSF 370 may select a slice based on slice selection information. For example, NSSF 370 may receive single network slice selection assistance information (S-NSSAI) and map the S-NSSAI to a network slice instance identifier (NSI).

[0070] The CHF 380 may control accounting-related tasks associated with the UE 301. For example, the UPF 305 may report the service usage associated with the UE 301 to the SMF 314. The SMF 314 may collect usage data from the UPF 305 and one or more other UPFs. The usage data may indicate how much data is exchanged, with what DN the data is exchanged, the network slice associated with the data, or any other information that may affect accounting. The SMF 314 may share the collected usage data with the CHF. The CHF may use the collected usage data to perform accounting-related tasks associated with the UE 301. The CHF may instruct the SMF 314 to restrict or affect the access of the UE 301 and / or provide accounting-related notifications to the UE 301 depending on the accounting status of the UE 301.

[0071] The NWDAF 390 may collect and analyze data from other network functions and provide data analysis services to other network functions. As an example, the NWDAF 390 may collect data related to the load level of a specific network slice instance from the UPF 305, the AMF 312, and / or the SMF 314. Based on the collected data, the NWDAF 390 may provide the load level data to the PCF 320 and / or the NSSF 370, and / or notify the PCF 320 and / or the NSSF 370 whether the load level of the slice reaches and / or exceeds a load level threshold.

[0072] AF 399 may be external to the core network but may interact with the core network to provide information about QoS requirements or traffic routing preferences associated with a particular application. AF 399 may access the core network based on open constraints imposed by NEF 340. However, the operator of the core network may view AF 399 as a trusted domain that may directly access the network.

[0073] Figure 4A , 4B and 5 show in some respects similar Figure 3 For the sake of brevity, other examples of core network architectures of the core network architecture 300 are omitted. Figure 3 Some core network elements depicted in . Figure 4A , 4B Many of the elements depicted in and 5 are similar in some respects to Figure 3 For the sake of brevity, some details related to their functions or operations are omitted.

[0074] Figure 4AAn example of a core network architecture 400A including an arrangement of multiple UPFs is shown. The core network architecture 400A includes a UE 401, an AN 402, an AMF 412, and an SMF 414. Different from the previous examples of the core network architecture described above, Figure 4A A plurality of UPFs including UPF 405, UPF 406, and UPF 407, and a plurality of DNs including DN 408 and DN 409 are depicted. Each of the plurality of UPFs 405, 406, 407 may communicate with SMF 414 via an N4 interface. DN 408, 409 may communicate with UPF 405, 406, respectively, via an N6 interface. Figure 4A As shown, multiple UPFs 405, 406, 407 can communicate with each other via the N9 interface.

[0075] The UPFs 405, 406, 407 may perform traffic detection, wherein the UPF identifies and / or classifies packets. Packet identification may be performed based on packet detection rules (PDRs) provided by the SMF 414. The PDR may include packet detection information including one or more of the following: a source interface, a UE IP address, core network (CN) tunnel information (e.g., a CN address of an N3 / N9 tunnel corresponding to a PDU session), a network instance identifier, a quality of service flow identifier (QFI), a filter set (e.g., an IP packet filter set or an Ethernet packet filter set), and / or an application identifier.

[0076] In addition to indicating how a particular packet will be detected, the PDR may further indicate rules for handling the packet after the packet is detected. The rules may include, for example, forwarding action rules (FARs), multiple access rules (MARs), usage reporting rules (URRs), QoS enforcement rules (QERs), etc. For example, the PDR may include one or more FAR identifiers, MAR identifiers, URR identifiers, and / or QER identifiers. These identifiers may indicate rules that are specified for handling a particular packet that is detected.

[0077] The UPF 405 may perform traffic forwarding based on the FAR. For example, the FAR may indicate that packets associated with a particular PDR will be forwarded, copied, discarded, and / or buffered. The FAR may indicate a destination interface, such as "access" for a downlink or "core" for an uplink. If a packet is to be buffered, the FAR may indicate a buffer action rule (BAR). As an example, the UPF 405 may perform data buffering of a specific number of downlink packets in the case of a PDU session being released.

[0078] UPF 405 may perform QoS enforcement based on the QER. For example, the QER may indicate an authorized guaranteed bit rate and / or a maximum bit rate to be enforced for packets associated with a particular PDR. The QER may indicate that a particular guaranteed and / or maximum bit rate may be used for uplink packets and / or downlink packets. UPF 405 may mark packets belonging to a particular QoS flow with a corresponding QFI. The marking may enable the receiver of the packet to determine the QoS of the packet.

[0079] UPF 405 may provide the usage report to SMF 414 based on the URR. The URR may indicate one or more trigger conditions for the generation and reporting of the usage report, such as immediate reporting, periodic reporting, a threshold for incoming uplink traffic, or any other suitable trigger condition. The URR may indicate a method for measuring the usage of network resources, such as data volume, duration, and / or event.

[0080] As described above, DN 408, 409 may include a public DN (e.g., the Internet), a private DN (e.g., a private, internal company-owned DN), and / or an intra-operator DN. Each DN may provide operator services and / or third-party services. The services provided by the DN may be the Internet, an IP Multimedia Subsystem (IMS), an augmented or virtual reality network, an edge computing or mobile edge computing (MEC) network, etc. Each DN may be identified using a data network name (DNN). UE 401 may be configured to establish a first logical connection (a first PDU session) with DN 408, a second logical connection (a second PDU session) with DN 409, or both (a first and a second PDU session) at the same time.

[0081] Each PDU Session may be associated with at least one UPF configured to operate as a PDU Session Anchor (PSA or "anchor"). The anchor may be a UPF that provides an N6 interface with the DN.

[0082] exist Figure 4AIn the example of , UPF 405 may be an anchor for a first PDU session between UE 401 and DN 408, and UPF 406 may be an anchor for a second PDU session between UE 401 and DN 409. The core network may use anchors to provide service continuity (e.g., IP address continuity) for a particular PDU session as UE 401 moves from one access network to another. For example, assume that UE 401 establishes a PDU session using a data path to DN 408 using an access network other than AN 402. The data path may include UPF 405 acting as an anchor. Further assume that UE 401 later moves into the coverage area of ​​AN 402. In this scenario, SMF 414 may select a new UPF (UPF 407) to bridge the gap between the newly entered access network (AN 402) and the anchor UPF (UPF 405). The continuity of the PDU session can be maintained as any number of UPFs are added or removed from the data path. Figure 4A As shown, it can be described as an intermediate UPF and / or a cascaded UPF.

[0083] As described above, UPF 406 may be the anchor for the second PDU session between UE 401 and DN 409. Figure 4A The anchors for the first and second PDU sessions in FIG. 4 are associated with different UPFs, but it should be understood that this is only an example. It will also be understood that multiple PDU sessions with a single DN may correspond to any number of anchors. When multiple UPFs are present, the UPF at the branch point (UPF 407 in FIG. 4) may operate as an uplink classifier (UL-CL). The UL-CL may divert uplink user plane traffic to different UPFs.

[0084] SMF 414 may allocate, manage and / or assign an IP address to UE 401, for example, after establishing a PDU session. SMF 414 may maintain an internal pool of IP addresses to be assigned. If necessary, SMF 414 may assign an IP address provided by a Dynamic Host Configuration Protocol (DHCP) server or an Authentication, Authorization and Accounting (AAA) server. IP address management may be performed according to a Session and Service Continuity (SSC) mode. In SSC Mode 1, the IP address of UE 401 may be maintained as the wireless device moves within the network (and the same anchor UPF may be used). In SSC Mode 2, the IP address of UE 401 changes as UE 401 moves within the network (e.g., the old IP address and UPF may be discarded, and a new IP address and anchor UPF may be established). In SSC Mode 3, it is possible to temporarily maintain the old IP address (similar to SSC Mode 1) while establishing a new IP address (similar to SSC Mode 2), thus combining the features of SSC Modes 1 and 2. Applications that are sensitive to IP address changes can operate according to SSC Mode 1.

[0085] UPF selection may be controlled by SMF 414. For example, after establishing and / or modifying a PDU session between UE 401 and DN 408, SMF 414 may select UPF 405 as an anchor for the PDU session and / or select UPF 407 as an intermediate UPF. Criteria for UPF selection include path efficiency and / or speed between AN 402 and DN 408. Reliability, load status, location, slice support, and / or other capabilities of candidate UPFs may also be considered.

[0086] Figure 4B An example of a core network architecture 400B that accommodates untrusted access is shown. Figure 4A ,like Figure 4B 408 is connected to DN 408 via AN 402 and UPF 405. AN 402 and UPF 405 constitute a trusted (e.g., 3GPP) access to DN 408. In contrast, UE 401 can also access DN 408 using an untrusted access network, AN 403 and a non-3GPP network interworking function (N3IWF) 404.

[0087] AN 403 may be, for example, a wireless land area network (WLAN) operating according to the IEEE 802.11 standard. UE 401 may be connected to AN 403 via interface Y1 in any manner specified by AN 403. The connection to AN 403 may or may not involve authentication. UE 401 may obtain an IP address from AN 403. UE 401 may determine to connect to core network 400B and select untrusted access for this purpose. AN 403 may communicate with N3IWF 404 via Y2 interface. After selecting untrusted access, UE 401 may provide N3IWF 404 with sufficient information to select AMF. The selected AMF may be, for example, the same AMF (in the current example, AMF 412) used by UE 401 for 3GPP access. N3IWF 404 may communicate with AMF 412 via N2 interface. The UPF 405 may be selected, and the N3IWF 404 may communicate with the UPF 405 via the N3 interface. The UPF 405 may be a PDU Session Anchor (PSA) and maintain an anchor for a PDU session even as the UE 401 transitions between trusted access and untrusted access.

[0088] Figure 5 An example of a core network architecture 500 is shown in which a UE 501 is in a roaming scenario. In the roaming scenario, the UE 501 is a subscriber to a first PLMN (home PLMN or HPLMN), but is attached to a second PLMN (visited PLMN or VPLMN). The core network architecture 500 includes a UE 501, an AN 502, a UPF 505, and a DN 508. The AN 502 and the UPF 505 may be associated with the VPLMN. The VPLMN may manage the AN 502 and the UPF 505 using core network elements associated with the VPLMN, including an AMF 512, an SMF 514, a PCF 520, an NRF 530, a NEF 540, and a NSSF 570. The AF 599 may be adjacent to the core network of the VPLMN.

[0089] UE 501 may not be a subscriber of the VPLMN. AMF 512 may authorize UE 501 to access the network based on, for example, roaming restrictions imposed on UE 501. In order to obtain network services provided by the VPLMN, the core network of the VPLMN may have to interact with the core network elements of the HPLMN of UE 501, specifically PCF 521, NRF 531, NEF 541, UDM 551 and / or AUSF 561. The VPLMN and the HPLMN may communicate using the N32 interface connected to the corresponding security edge protection proxy (SEPP). Figure 5, the corresponding SEPPs are depicted as VSEPP 590 and HSEPP 591 .

[0090] VSEPP 590 and HSEPP 591 communicate via the N32 interface for defined purposes while hiding information about each PLMN from another PLMN. SEPP can apply roaming policies based on communications via the N32 interface. PCF 520 and PCF521 can communicate via SEPP to exchange policy-related signaling. NRF 530 and NRF 531 can communicate via SEPP to enable service discovery of NFs in the corresponding PLMN. VPLMN and HPLMN can independently maintain NEF 540 and NEF 541. NSSF 570 and NSSF571 can communicate via SEPP to coordinate slice selection for UE 501. HPLMN can handle all authentication and subscription-related signaling. For example, when UE 501 registers or requests services via VPLMN, VPLMN can authenticate UE 501 and / or obtain subscription data of UE 501 by accessing UDM 551 and AUSF 561 of HPLMN via SEPP.

[0091] Figure 5 The core network architecture 500 depicted in FIG. 5 may be referred to as a local breakout configuration, where the UE 501 uses one or more UPFs (i.e., UPF 505) of the VPLMN to access the DN 508. However, other configurations are possible. For example, in a home-routed configuration ( Figure 5 In the home routing configuration, the N9 interface may run in parallel with the N32 interface, crossing the boundary between the VPLMN and the HPLMN to carry user plane data. One or more SMFs of the corresponding PLMN may communicate via the N32 interface to coordinate session management for UE 501. The SMF may control its corresponding UPF on either side of the boundary.

[0092] Figure 6 An example of network slicing is shown. Network slicing may refer to dividing a shared infrastructure (e.g., physical infrastructure) into distinct logical networks. These distinct logical networks may be controlled independently, isolated from each other, and / or in association with dedicated resources.

[0093] The network architecture 600A shows a non-sliced ​​physical network corresponding to a single logical network. The network architecture 600A includes a user plane, where UE 601A, 601B, 601C (collectively referred to as UE 601) has a physical and logical connection to DN 608 via AN 602 and UPF 605. The network architecture 600A includes a control plane, where AMF 612 and SMF 614 control various aspects of the user plane.

[0094] The network architecture 600A may have a specific set of characteristics (e.g., related to maximum bit rate, reliability, latency, bandwidth usage, power consumption, etc.). This set of characteristics may be affected by the nature of the network elements themselves (e.g., processing power, availability of free memory, proximity to other network elements, etc.) or their management (e.g., optimized to maximize bit rate or reliability, reduce latency or power bandwidth usage, etc.). The characteristics of the network architecture 600A may change over time, such as by upgrading equipment or by modifying programs to target specific characteristics. However, at any given time, the network architecture 600A will have a single set of characteristics that may or may not be optimized for a specific use case. For example, UEs 601A, 601B, 601C may have different requirements, but the network architecture 600A may be optimized for only one of the three.

[0095] Network architecture 600B is an example of a sliced ​​physical network divided into multiple logical networks. Figure 6 In the example, the physical network is divided into three logical networks, referred to as slice A, slice B, and slice C. For example, UE 601A may be served by AN 602A, UPF 605A, AMF 612, and SMF 614A. UE 601B may be served by AN 602B, UPF 605B, AMF 612, and SMF 614B. UE 601C may be served by AN 602C, UPF 605C, AMF 612, and SMF 614C. Although from a logical perspective, the respective UEs 601 communicate with different network elements, these network elements may be deployed by the network operator using the same physical network elements.

[0096] Each network slice may be customized for a network service with a different set of characteristics. For example, slice A may correspond to an enhanced mobile broadband (eMBB) service. Mobile broadband may refer to Internet access by mobile users, typically associated with smartphones. Slice B may correspond to ultra-reliable low-latency communications (URLLC), which focuses on reliability and speed. Relative to eMBB, URLLC may improve the feasibility of use cases such as autonomous driving and remote surgery. Slice C may correspond to massive machine type communications (mMTC), which focuses on low-power services delivered to a large number of users. For example, slice C may be optimized for a dense network of battery-powered sensors that provide small amounts of data at regular intervals. Many mMTC use cases would be prohibitively expensive to operate using eMBB or URLLC networks.

[0097] If the service requirement for one of the UEs 601 changes, the network slice serving the UE may be updated to provide better service. In addition, the set of network features corresponding to eMBB, URLLC, and mMTC may vary so that differentiated types of eMBB, URLLC, and mMTC are provided. Alternatively, the network operator may provide a completely new service in response to, for example, customer demand.

[0098] Figure 6 6, each of the UEs 601 has its own network slice. However, it should be understood that a single slice may serve any number of UEs, and a single UE may operate using any number of slices. Furthermore, in the example network architecture 600B, the AN 602, UPF 605, and SMF 614 are divided into three separate slices, while the AMF 612 is non-slicing. However, it should be understood that a network operator may deploy any architecture that selectively utilizes any mix of slicing and non-slicing network elements, where different network elements are divided into different numbers of slices. Although Figure 6 Only three core network functions are depicted, but it should be understood that other core network functions may also be sliced. A PLMN supporting multiple network slices may maintain a separate network repository function (NFR) for each slice, enabling other NFs to discover network services associated with the slice.

[0099] The network slice selection may be controlled by the AMF or by a separate network slice selection function (NSSF). For example, a network operator may define and implement distinct network slice instances (NSIs). Each NSI may be associated with a single network slice selection assistance information (S-NSSAI). The S-NSSAI may include a specific slice / service type (SST) indicator (indicating eMBB, URLLC, mMTC, etc.). As an example, a specific tracking area may be associated with one or more configured S-NSSAIs. The UE may identify one or more requested and / or subscribed S-NSSAIs (e.g., during registration). The network may indicate to the UE one or more allowed and / or rejected S-NSSAIs.

[0100] The S-NSSAI may further include a slice differentiator (SD) to distinguish different tenants of a particular slice and / or service type. For example, a tenant may be a customer (e.g., a vehicle manufacturer, a service provider, etc.) of a network operator that obtains (e.g., purchases) guaranteed network resources and / or specific policies for handling its subscribers. The network operator may configure different slices and / or slice types and use the SD to determine which tenant is associated with a particular slice.

[0101] Fig. 7A , Figure 7B and Figure 7C A user plane (UP) protocol stack, a control plane (CP) protocol stack, and services provided between protocol layers of the UP protocol stack are shown.

[0102] The layers may be associated with an open systems interconnection (OSI) model of computer networking functionality. In the OSI model, layer 1 may correspond to the bottom layer, with higher layers on top of the bottom layer. Layer 1 may correspond to the physical layer, which is related to the physical infrastructure (e.g., cables, optical fibers, and / or radio frequency transceivers) used to transmit signals. In a new radio (NR), layer 1 may include a physical layer (PHY). Layer 2 may correspond to a data link layer. Layer 2 may be related to packaging data (e.g., into data frames) for transmission between nodes of a network using the physical infrastructure of layer 1. In NR, layer 2 may include a media access control layer (MAC), a radio link control layer (RLC), a packet data convergence layer (PDCP), and a service data application protocol layer (SDAP).

[0103] Layer 3 may correspond to the network layer. Layer 3 may be related to the routing of data that has been encapsulated in layer 2. Layer 3 may handle prioritization of data and traffic avoidance. In NR, layer 3 may include a radio resource control layer (RRC) and a non-access layer layer (NAS). Layers 4 to 7 may correspond to a transport layer, a session layer, a presentation layer, and an application layer. The application layer interacts with the end user to provide data associated with the application. In an example, an end user implementing an application may generate data associated with the application and initiate the sending of the information to a target data network (e.g., the Internet, an application server, etc.). Starting at the application layer, each layer in the OS I model may manipulate and / or repackage information and deliver it to the lower layers. At the lowest layer, the manipulated and / or repackaged information may be exchanged via a physical infrastructure (e.g., electrically, optically, and / or electromagnetically). As it approaches the target data network, the information will be decapsulated and provided to higher and higher layers until it reaches the application layer again in a form that is usable by the target data network (e.g., the same form as when it was provided by the end user). The data network may reverse this process in order to respond to the end user.

[0104] Fig. 7A A user plane protocol stack is shown. The user plane protocol stack may be a new air interface (NR) protocol stack for the Uu interface between the UE 701 and the gNB 702. In layer 1 of the UP protocol stack, the UE 701 may implement PHY 731 and the gNB 702 may implement PHY 732. In layer 2 of the UP protocol stack, the UE 701 may implement MAC 741, RLC 751, PDCP 761, and SDAP 771. The gNB 702 may implement MAC 742, RLC 752, PDCP 762, and SDAP 772.

[0105] Figure 7B The control plane protocol stack is shown. The control plane protocol stack may be an NR protocol stack for the Uu interface between the UE 701 and the gNB 702 and / or the N1 interface between the UE 701 and the AMF 712. In layer 1 of the CP protocol stack, the UE 701 may implement the PHY 731 and the gNB 702 may implement the PHY 732. In layer 2 of the CP protocol stack, the UE 701 may implement the MAC 741, the RLC 751, the PDCP 761, the RRC 781, and the NAS 791. The gNB 702 may implement the MAC 742, the RLC 752, the PDCP 762, and the RRC 782. The AMF 712 may implement the NAS 792.

[0106] NAS may be related to the non-access layer, specifically, the communication between the UE 701 and the core network (e.g., AMF 712). The lower layer may be related to the access layer, such as the communication between the UE 701 and the gNB 702. The message sent between the UE 701 and the core network may be referred to as a NAS message. In an example, the NAS message may be relayed by the gNB 702, but the content of the NAS message (e.g., the information element of the NAS message) may not be visible to the gNB 702.

[0107] Figure 7C Shown set at Fig. 7A 771 and 772 may perform mapping and / or demapping between the one or more QoS flows and one or more radio bearers (e.g., data radio bearers) of the PDU session. The mapping between the QoS flows and the data radio bearers may be determined by the gNB 702 in the SDAP 772, and the UE 701 may be notified of the mapping (e.g., based on control signaling and / or reflection mapping). For reflection mapping, the SDAP 772 of the gNB 220 may mark the downlink packet with a QoS flow indicator (QFI) and deliver the downlink packet to the UE 701. The UE 701 may determine the mapping based on the QFI of the downlink packet.

[0108] PDCP 761 and PDCP 762 may perform header compression and / or decompression. Header compression may reduce the amount of data transmitted on the physical layer. PDCP 761 and PDCP 762 may perform encryption and / or decryption. Encryption may reduce unauthorized decoding of data transmitted on the physical layer (e.g., intercepted on the air interface) and protect data integrity (e.g., to ensure that control messages originate from intended sources). PDCP 761 and PDCP 762 may perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, duplication of packets, and / or identification and removal of duplicate packets. In a dual connectivity scenario, PDCP 761 and PDCP 762 may perform mapping between split radio bearers and RLC channels.

[0109] RLC 751 and RLC 752 may perform segmentation, retransmission via automatic repeat request (ARQ). RLC 751 and RLC 752 may perform removal of duplicate data units received from MAC 741 and MAC 742, respectively. RLC 213 and 223 may provide RLC channels as services to PDCP 214 and 224, respectively.

[0110] MAC 741 and MAC 742 may perform multiplexing and / or demultiplexing of logical channels. MAC 741 and MAC 742 may map logical channels to transport channels. In an example, UE 701 may multiplex data units of one or more logical channels into a transport block in MAC 741. UE 701 may transmit the transport block to gNB 702 using PHY 731. gNB 702 may receive the transport block using PHY 732 and demultiplex the data units of the transport block back into the logical channels. MAC 741 and MAC 742 may perform error correction via hybrid automatic repeat request (HARQ), logical channel prioritization, and / or padding.

[0111] PHY 731 and PHY 732 may perform mapping of transport channels to physical channels. PHY 731 and PHY 732 may perform digital and analog signal processing functions (e.g., coding / decoding and modulation / demodulation) for sending and receiving information (e.g., transmitted via an air interface). PHY 731 and PHY 732 may perform multi-antenna mapping.

[0112] Figure 8 An example of a Quality of Service (QoS) model for differentiated data exchange is shown. Figure 8 In the QoS model of FIG. 801 , there are UE 801, AN 802, and UPF 805. The QoS model facilitates prioritization of certain packets or protocol data units (PDUs) (also referred to as packets). For example, higher priority packets can be switched faster and / or more reliably than lower priority packets. The network can devote more resources to switching high QoS packets.

[0113] exist Figure 8In the example of , a PDU session 810 is established between UE 801 and UPF 805. PDU session 810 may be a logical connection that enables UE 801 to exchange data with a specific data network (e.g., the Internet). UE 801 may request to establish PDU session 810. When establishing PDU session 810, UE 801 may identify the target data network, for example, based on its data network name (DNN). PDU session 810 may be managed, for example, by a session management function (SMF, not shown). In order to facilitate the exchange of data associated with PDU session 810 between UE 801 and the data network, SMF may select UPF 805 (and optionally, one or more other UPFs, not shown).

[0114] One or more applications associated with the UE 801 may generate uplink packets 812A-812E associated with the PDU session 810. To operate within the QoS model, the UE 801 may apply QoS rules 814 to the uplink packets 812A-812E. The QoS rules 814 may be associated with the PDU session 810 and may be determined and / or provided to the UE 801 when establishing and / or modifying the PDU session 810. Based on the QoS rules 814, the UE 801 may classify the uplink packets 812A-812E, map each of the uplink packets 812A-812E to a QoS flow, and / or mark the uplink packets 812A-812E with a QoS flow indicator (QFI). As the packets travel through the network, and potentially mix with other packets from other UEs having potentially different priorities, the QFI indicates how the packets should be handled according to the QoS model. In the current illustration, uplink packets 812A, 812B are mapped to QoS flow 816A, uplink packet 812C is mapped to QoS flow 816B, and the remaining packets are mapped to QoS flow 816C.

[0115] QoS flow can be the finest granularity of QoS differentiation in PDU session. In the figure, three QoS flows 816A-816C are shown. However, it should be understood that there may be any number of QoS flows. Some QoS flows may be associated with guaranteed bit rates (GBR QoS flows), and other QoS flows may have non-guaranteed bit rates (non-GBR QoS flows). QoS flows may also experience per UE and per session total bit rates. One of the QoS flows may be a default QoS flow. QoS flows may have different priorities. For example, QoS flow 816A may have a higher priority than QoS flow 816B, and QoS flow 816B may have a higher priority than QoS flow 816C. Different priorities may be reflected by different QoS flow characteristics. For example, QoS flows may be associated with flow bit rates. A specific QoS flow may be associated with a guaranteed flow bit rate (GFBR) and / or a maximum flow bit rate (MFBR). QoS flows may be associated with a specific packet delay budget (PDB), a packet error rate (PER), and / or a maximum packet loss rate. QoS flows may also experience per-UE and per-session aggregate bit rates.

[0116] In order to work within the QoS model, UE 801 may apply resource mapping rules 818 to QoS flows 816A-816C. The air interface between UE 801 and AN 802 may be associated with resources 820. In the current illustration, QoS flow 816A is mapped to resource 820A, while QoS flows 816B, 816C are mapped to resource 820B. Resource mapping rules 818 may be provided by AN 802. In order to meet QoS requirements, resource mapping rules 818 may specify more resources for relatively high priority QoS flows. With more resources, high priority QoS flows such as QoS flow 816A may be more likely to obtain high flow bit rates, low packet delay budgets, or other characteristics associated with QoS rules 814. Resources 820 may include, for example, radio bearers. Radio bearers (e.g., data radio bearers) may be established between UE 801 and AN 802. The 5G radio bearer between UE 801 and AN 802 may be different from the LTE bearer, such as an Evolved Packet System (EPS) bearer between the UE and a Packet Data Network Gateway (PGW), an S1 bearer between an eNB and a Serving Gateway (SGW), and / or an S5 / S8 bearer between an SGW and a PGW.

[0117] Once a packet associated with a particular QoS flow is received at AN 802 via resource 820A or resource 820B, AN 802 separates the packet into corresponding QoS flows 856A-856C based on the QoS profile 828. The QoS profile 828 may be received from the SMF. Each QoS profile may correspond to a QFI, such as the QFI marked on the uplink packets 812A-812E. Each QoS profile may include QoS parameters such as a 5G QoS identifier (5QI) and an allocation and retention priority (ARP). The QoS profile for non-GBR QoS flows may further include additional QoS parameters such as reflective QoS attributes (RQA). The QoS profile for GBR QoS flows may further include additional QoS parameters such as a guaranteed flow bit rate (GFBR), a maximum flow bit rate (MFBR) and / or a maximum packet loss rate. The 5QI may be a standardized 5QI with a one-to-one mapping of each well-known service to a standardized combination of 5G QoS characteristics. 5QI may be a dynamically assigned 5QI, for which a standardized 5QI value is not defined. 5QI may represent 5G QoS characteristics. 5QI may include resource type, default priority, packet delay budget (PDB), packet error rate (PER), maximum data burst, and / or averaging window. Resource type may indicate a non-GBR QoS flow, a GBR QoS flow, or a delay-critical GBR QoS flow. The averaging window may represent the duration over which GFBR and / or MFBR are calculated. ARP may be a priority including preemptive capability and preemptible capability. Based on ARP, AN 802 may apply admission control for QoS flows in the case of resource limitations.

[0118] AN 802 may select one or more N3 tunnels 850 for transporting QoS flows 856A-856C. After the packets are divided into QoS flows 856A-856C, the packets may be sent to UPF 805 (e.g., toward DN) via the selected one or more N3 tunnels 850. UPF 805 may verify that the QFI of the uplink packets 812A-812E is aligned with the QoS rules 814 provided to UE 801. UPF 805 may measure the packets and / or count the packets and / or provide the packet metrics to, for example, PCF.

[0119] The figure also shows a process for downlink. Specifically, one or more applications may generate downlink packets 852A-852E. UPF 805 may receive downlink packets 852A-852E from one or more DNs and / or one or more other UPFs. According to the QoS model, UPF 805 may apply packet detection rules (PDRs) 854 to downlink packets 852A-852E. Based on PDR 854, UPF 805 may map packets 852A-852E to QoS flows. In the current illustration, downlink packets 852A, 852B are mapped to QoS flow 856A, downlink packet 852C is mapped to QoS flow 856B, and the remaining packets are mapped to QoS flow 856C.

[0120] QoS flows 856A-856C may be sent to AN 802. AN 802 may apply resource mapping rules to QoS flows 856A-856C. In the current illustration, QoS flow 856A is mapped to resource 820A, while QoS flows 856B, 856C are mapped to resource 820B. To meet QoS requirements, resource mapping rules may specify more resources for high priority QoS flows.

[0121] 9A to 9D Example states and state transitions of a wireless device (eg, UE) are shown. At any given time, a wireless device may have a radio resource control (RRC) state, a registration management (RM) state, and a connection management (CM) state.

[0122] Fig. 9A 9 is an example diagram showing RRC state transitions of a wireless device (e.g., UE). The UE may be in one of three RRC states: RRC idle 910 (e.g., RRC_IDLE), RRC inactive 920 (e.g., RRC_INACTIVE), or RRC connected 930 (e.g., RRC_CONNECTED). The UE may implement different RAN-related control plane procedures depending on its RRC state. Other elements of the network (e.g., base stations) may track the RRC states of one or more UEs and implement RAN-related control plane procedures appropriate for the RRC state of each UE.

[0123] In the RRC connection 930, it is possible for the UE to exchange data with the network (e.g., a base station). Parameters necessary for data exchange may be established, and these parameters are known to both the UE and the network. Parameters may be referred to and / or included in the RRC context of the UE (sometimes referred to as the UE context). These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., involving data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. The base station connected to the UE may store the RRC context of the UE.

[0124] When in RRC connection 930, the mobility of the UE may be managed by the access network, while the UE itself may manage mobility when in RRC idle 910 and / or RRC inactive 920. When in RRC connection 930, the UE may manage mobility by measuring signal levels (e.g., reference signal levels) from serving cells and neighboring cells and reporting these measurements to the base station currently serving the UE. The network may initiate a handover based on the reported measurements. The RRC state may transition from RRC connection 930 to RRC idle 910 via a connection release procedure 930, and to RRC inactive 920 via a connection cancellation procedure 932.

[0125] In RRC idle 910, an RRC context may not be established for the UE. In RRC idle 910, the UE may not have an RRC connection with a base station. When in RRC idle 910, the UE may be in a dormant state most of the time (e.g., to save battery power). The UE may wake up periodically (e.g., once per discontinuous reception cycle) to monitor paging messages from the access network. The mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 910 to RRC connected 930 via a connection establishment procedure 913, which may involve a random access procedure, as discussed in more detail below.

[0126] In RRC Inactive 920, the previously established RRC context is maintained in the UE and the base station. This may allow a quick transition to RRC Connected 930 with reduced signaling overhead compared to the transition from RRC Idle 910 to RRC Connected 930. The RRC state may transition to RRC Connected 930 via a Connection Recovery Procedure 923. The RRC state may transition to RRC Idle 910 via a Connection Release Procedure 921, which may be the same as or similar to a Connection Release Procedure 931.

[0127] The RRC state can be associated with a mobility management mechanism. In RRC idle 910 and RRC inactive 920, mobility can be managed by the UE via cell reselection. The purpose of mobility management in RRC idle 910 and / or RRC inactive 920 is to allow the network to notify the UE of an event via a paging message without broadcasting the paging message on the entire mobile communication network. The mobility management mechanism used in RRC idle 910 and / or RRC inactive 920 can allow the network to track the UE at the cell-group level, so that the paging message can be broadcast on the cell of the cell group where the UE currently resides rather than on the entire communication network. Tracking can be based on different grouping granularities. For example, there can be three levels of cell grouping granularity: a single cell; a cell within a RAN area identified by a RAN area identifier (RAI); and a cell within a group of RAN areas referred to as tracking areas and identified by a tracking area identifier (TAI).

[0128] Tracking areas may be used to track UEs at the CN level. The CN may provide the UE with a list of TAIs associated with the UE registration area. If the UE moves through cell reselection to a cell associated with a TAI that is not included in the list of TAIs associated with the UE registration area, the UE may perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new UE registration area.

[0129] The RAN area may be used to track the UE at the RAN level. For a UE in the RRC inactive 920 state, a RAN notification area may be assigned to the UE. The RAN notification area may include one or more cell identities, a list of RAIs, and / or a list of TAIs. In an example, a base station may belong to one or more RAN notification areas. In an example, a cell may belong to one or more RAN notification areas. If the UE moves to a cell not included in the RAN notification area assigned to the UE through cell reselection, the UE may perform a notification area update on the RAN to update the RAN notification area of ​​the UE.

[0130] The base station storing the RRC context for the UE or the last serving base station of the UE may be referred to as the anchor base station. The anchor base station may maintain the RRC context of the UE at least during the time period that the UE remains in the RAN notification area of ​​the anchor base station and / or during the time period that the UE remains in RRC inactivity 920.

[0131] Fig. 9B is an example diagram showing registration management (RM) state transitions of a wireless device (eg, UE). The states are RM deregistration 940 (eg, RM-DEREGISTERED) and RM registration 950 (eg, RM-REGISTERED).

[0132] In RM deregistration 940, the UE is not registered with the network, and the network is not reachable. In order to be reachable by the network, the UE must perform an initial registration. As an example, the UE may register with the AMF of the network. If the registration is rejected (registration rejection 944), the UE remains in RM deregistration 940. If the registration is accepted (registration acceptance 945), the UE transitions to RM registration 950. When the UE is in RM registration 950, the network may store, maintain and / or maintain the UE context of the UE. The UE context may be referred to as a wireless device context. The UE context corresponding to the network registration (maintained by the core network) may be different from the RRC context corresponding to the RRC state (maintained by an access network such as a base station). The UE context may include a record of the UE identifier and various information related to the UE, such as UE capability information, policy information for access and mobility management of the UE, a list of slices or PDU sessions allowed or established, and / or a registration area of ​​the UE (i.e., a list of tracking areas covering geographical areas where wireless devices are likely to be found).

[0133] When the UE is in RM registration 950, the network may store the UE context of the UE and use the UE context to reach the UE when necessary. In addition, some services cannot be provided by the network unless the UE is registered. The UE may update its UE context (Registration Update Accept 955) while remaining in RM registration 950. For example, if the UE leaves one tracking area and enters another tracking area, the UE may provide the tracking area identifier to the network. The network may deregister the UE, or the UE may deregister itself (Deregister 954). For example, the network may automatically deregister the wireless device if the wireless device is inactive for a certain amount of time. After deregistration, the UE may transition to RM deregistration 940.

[0134] Fig. 9C is an example diagram showing connection management (CM) state transitions of a wireless device (e.g., UE) shown from the perspective of the wireless device. The UE can be in CM idle 960 (e.g., CM-IDLE) or CM connected 970 (e.g., CM-CONNECTED).

[0135] In CM Idle 960, the UE does not have a non-access stratum (NAS) signaling connection with the network. Therefore, the UE may not communicate with the core network function. The UE may transition to CM Connected 970 by establishing an AN signaling connection (AN Signaling Connection Establishment 967). This transition may be initiated by sending an initial NAS message. The initial NAS message may be a registration request (e.g., if the UE is in RM Deregistration 940) or a service request (e.g., if the UE is in RM Registration 950). If the UE is in RM Registration 950, the UE may initiate AN signaling connection establishment by sending a service request, or the network may send a page, thereby triggering the UE to send a service request.

[0136] In CM Connected 970, the UE may communicate with core network functions using NAS signaling. As an example, the UE may exchange NAS signaling with the AMF for registration management purposes, service request procedures, and / or authentication procedures. As another example, the UE may exchange NAS signaling with the SMF to establish and / or modify PDU sessions. The network may disconnect the UE, or the UE may disconnect itself (AN signaling connection release 976). For example, if the UE transitions to RM Deregistration 940, the UE may also transition to CM Idle 960. When the UE transitions to CM Idle 960, the network may release the user plane connection of the UE's PDU session.

[0137] Fig.9D is an example diagram showing CM state transitions of a wireless device (e.g., UE) from a network perspective (e.g., AMF). The CM state of the UE tracked by the AMF may be in CM-IDLE 980 (e.g., CM-IDLE) or CM-CONNECTED 990 (e.g., CM-CONNECTED). When the UE transitions from CM-IDLE 980 to CM-CONNECTED 990, the AMF may establish an N2 context of the UE (N2 context establishment 989). When the UE transitions from CM-CONNECTED 990 to CM-IDLE 980, the AMF may release the N2 context of the UE (N2 context release 998).

[0138] Figure 10-12 Example procedures for registration, service request and PDU session establishment for a UE are shown.

[0139] Fig.10 An example of a registration procedure for a wireless device (eg, UE) is shown. Based on the registration procedure, the UE may transition from, for example, RM deregistration 940 to RM registration 950.

[0140] Registration may be initiated by the UE for the purpose of obtaining authorization to receive services, enabling mobility tracking, enabling reachability, or other purposes. The UE may perform an initial registration as the first step to connect to the network (e.g., when the UE is powered on, airplane mode is disconnected, etc.). Registration may also be performed periodically to keep the network aware of the UE's presence (e.g., when in CM-IDLE state), or in response to changes in UE capabilities or registration areas. Deregistration may be performed ( Fig.10 (not shown) to stop network access.

[0141] At 1010, the UE transmits a registration request to the AN. As an example, the UE may have moved from the coverage area of ​​a previous AMF (shown as AMF#1) to the coverage area of ​​a new AMF (shown as AMF#2). The registration request may be a NAS message. The registration request may include a UE identifier. The AN may select an AMF for registration of the UE. For example, the AN may select a default AMF. For example, the AN may select an AMF that has been mapped to the UE (e.g., a previous AMF). The NAS registration request may include a network slice identifier, and the AN may select an AMF based on the requested slice. After selecting the AMF, the AN may send the registration request to the selected AMF.

[0142] At 1020, the AMF (AMF#2) that receives the registration request performs a context transfer. The context may be a UE context, such as an RRC context of the UE. As an example, AMF#2 may send a message to AMF#1 requesting the context of the UE. The message may include a UE identifier. The message may be a Namf_Communication_UEContextTransfer message. AMF#1 may send a message containing the requested UE context to AMF#2. This message may be a Namf_Communication_UEContextTransfer message. After receiving the UE context, AMF#2 may coordinate the authentication of the UE. After the authentication is completed, AMF#2 may send a message to AMF#1 indicating that the UE context transfer is complete. This message may be a Namf_Communication_UEContextTransfer response message.

[0143] Authentication may require participation of the UE, AUSF, UDM, and / or UDR (not shown). For example, the AMF may request the AUSF to authenticate the UE. For example, the AUSF may perform authentication of the UE. For example, the AUSF may obtain authentication data from the UDM. For example, the AUSF may send a subscription permanent identifier (SUPI) to the AMF based on successful authentication. For example, the AUSF may provide an intermediate key to the AMF. The intermediate key may be used to derive access-specific security keys for the UE, thereby enabling the AMF to perform security context management (SCM). The AUSF may obtain subscription data from the UDM. The subscription data may be based on information obtained from the UDM (and / or UDR). The subscription data may include a subscription identifier, security credentials, access and mobility related subscription data, and / or session related data.

[0144] At 1030, the new AMF (AMF#2) registers and / or subscribes to the UDM. AMF#2 may perform the registration using the UE context management service (Nudm_UECM) of the UDM. AMF#2 may obtain the subscription information of the UE using the subscriber data management service (Nudm_SDM) of the UDM. AMF#2 may further request the UDM to notify AMF#2 whether the subscription information of the UE has changed. With the new AMF registered and subscribed, the old AMF (AMF#1) may deregister and unsubscribe. After deregistration, AMF#1 has no responsibility for the mobility management of the UE.

[0145] At 1040, AMF#2 retrieves access and mobility (AM) policies from PCF. As an example, AMF#2 may provide the subscription data of the UE to PCF. PCF may determine access and mobility policies for the UE based on subscription data, network operator data, current network conditions, and / or other suitable information. For example, the owner of the first UE may purchase a higher level of service than the owner of the second UE. PCF may provide rules associated with different service levels. Based on the subscription data of the corresponding UE, the network may apply different policies that promote different service levels.

[0146] For example, access and mobility policies may involve service area restrictions, RAT / frequency selection priorities (RFSP, where RAT stands for radio access technology), authorization and prioritization of access types (e.g., LTE compared to NR), and / or selection of non-3GPP access (e.g., access network discovery and selection policy (ANDSP)). Service area restrictions may include a list of tracking areas in which the UE is allowed to be served (and prohibited from being served). Access and mobility policies may include UE route selection policies (URSP) that affect the routing of established PDU sessions or new PDU sessions. As described above, different policies may be obtained and / or implemented based on the UE's subscription data, the UE's location (i.e., the location of the AN and / or AMF), or other suitable factors.

[0147] At 1050, AMF#2 may update the context of the PDU session. For example, if the UE has an existing PDU session, AMF#2 may coordinate with the SMF to activate the user plane connection associated with the existing PDU session. The SMF may update and / or release the session management context of the PDU session (Nsmf_PDUSess ion_UpdateSMContext, Nsmf_PDUSess ion_ReleaseSMContext).

[0148] At 1060, AMF#2 sends a Registration Accept message to the AN, which forwards the Registration Accept message to the UE. The Registration Accept message may include the new UE identifier and / or the new configured slice identifier. The UE may transmit a Registration Complete message to the AN, which forwards the Registration Complete message to AMF#2. The Registration Complete message may confirm receipt of the new UE identifier and / or the new configured slice identifier.

[0149] At 1070, AMF#2 may obtain UE policy control information from PCF. PCF may provide an access network discovery and selection policy (ANDSP) to facilitate non-3GPP access. PCF may provide a UE route selection policy (URSP) to facilitate mapping of specific data services to specific PDU session connectivity parameters. As an example, the URSP may indicate that data services associated with a specific application should be mapped to a specific SSC mode, network slice, PDU session type, or preferred access type (3GPP or non-3GPP).

[0150] Fig.11 An example of a service request procedure for a wireless device (eg, UE) is shown. Fig.11 The service request procedure depicted in is a network-triggered service request procedure for a UE in CM-IDLE state. Fig.11Other service request procedures (eg, UE-triggered service request procedures) are understood, as will be discussed in more detail below.

[0151] At 1110, the UPF receives data. The data may be downlink data for transmission to the UE. The data may be associated with an existing PDU session between the UE and the DN. The data may be received, for example, from the DN and / or another UPF. The UPF may buffer the received data. In response to receiving the data, the UPF may notify the SMF of the received data. The identity of the SMF to be notified may be determined based on the received data. The notification may be, for example, an N4 session report. The notification may indicate that the UPF has received data associated with the UE and / or a specific PDU session associated with the UE. In response to receiving the notification, the SMF may send PDU session information to the AMF. The PDU session information may be sent in N1N2 messaging for forwarding to the AN. The PDU session information may include, for example, UPF tunnel endpoint information and / or QoS information.

[0152] At 1120, the AMF determines that the UE is in CM-IDLE state. The determination at 1120 may be in response to receiving the PDU session information. Based on the determination that the UE is in CM-IDLE, the service request procedure may proceed to 1130 and 1140, as shown in FIG. Fig.11 However, if the UE is not in CM-IDLE (eg, the UE is in CM-CONNECTED), 1130 and 1140 may be skipped, and the service request procedure may proceed directly to 1150.

[0153] At 1130, the AMF pages the UE. The paging at 1130 may be performed based on the UE being in CM-IDLE. To perform the paging, the AMF may send a page to the AN. The page may be referred to as a paging or a paging message. The paging may be an N2 request message. The AN may be one of a plurality of ANs in the RAN notification area of ​​the UE. The AN may send the page to the UE. The UE may be in the coverage area of ​​the AN and may receive the page.

[0154] At 1140, the UE may request a service. The UE may transmit the service request to the AMF via the AN. Fig.11 , the UE may request service at 1140 in response to receiving the paging at 1130. However, as described above, this is a specific case for a network-triggered service request procedure. In some scenarios (e.g., if uplink data becomes available at the UE), the UE may start a UE-triggered service request procedure. The UE-triggered service request procedure may start at 1140.

[0155] At 1150, the network may authenticate the UE. Authentication may require participation of the UE, AUSF, and / or UDM, such as similar to authentication described elsewhere in this disclosure. In some cases (e.g., if the UE has recently authenticated), authentication at 1150 may be skipped.

[0156] At 1160, the AMF and SMF may perform a PDU session update. As part of the PDU session update, the SMF may provide one or more UPF tunnel endpoint identifiers to the AMF. In some cases ( Fig.11 (not shown in the figure), the SMF may have to coordinate with one or more other SMFs and / or one or more other UPFs to set up the user plane.

[0157] At 1170, the AMF may send the PDU session information to the AN. The PDU session information may be included in the N2 request message. Based on the PDU session information, the AN may configure user plane resources for the UE. To configure the user plane resources, the AN may, for example, perform an RRC reconfiguration of the UE. The AN may confirm to the AMF that the PDU session information has been received. The AN may notify the AMF that the user plane resources have been configured, and / or provide information related to the configuration of the user plane resources.

[0158] In the case of a UE-triggered service request procedure, the UE may receive a NAS service accept message from the AMF via the AN at 1170. After configuring the user plane resources, the UE may transmit uplink data (eg, uplink data that causes the UE to trigger the service request procedure).

[0159] At 1180, the AMF may update the session management (SM) context of the PDU session. For example, the AMF may notify the SMF (and / or one or more other associated SMFs) that user plane resources have been configured, and / or provide information related to the user plane resource configuration. The AMF may provide the SMF (and / or one or more other associated SMFs) with one or more AN tunnel endpoint identifiers of the AN. After the SM context update is completed, the SMF may send an update SM context response message to the AMF.

[0160] Based on the update of the session management context, the SMF may update the PCF for policy control purposes. For example, if the location of the UE has changed, the SMF may inform the PCF of the new location of the UE.

[0161] Based on the update of the session management context, the SMF and the UPF may perform session modification. The session modification may be performed using an N4 session modification message. After the session modification is completed, the UPF may transmit downlink data (e.g., downlink data that causes the UPF to trigger a network-triggered service request procedure) to the UE. The transmission of the downlink data may be based on the one or more AN tunnel endpoint identifiers of the AN.

[0162] Fig.12 An example of a protocol data unit (PDU) session establishment procedure for a wireless device (eg, UE) is shown. The UE may determine to transmit a PDU session establishment request to create a new PDU session, to handover an existing PDU session to a 3GPP network, or for any other suitable reason.

[0163] At 1210, the UE initiates a PDU session establishment. The UE may transmit a PDU session establishment request to the AMF via the AN. The PDU session establishment request may be a NAS message. The PDU session establishment request may indicate: a PDU session ID; a requested PDU session type (new or existing); a requested DN (DNN); a requested network slice (S-NSSAI); a requested SSC mode; and / or any other suitable information. The PDU session ID may be generated by the UE. The PDU session type may be, for example, an Internet Protocol (IP)-based type (e.g., IPv4, IPv6, or dual stack IPv4 / IPv6), an Ethernet type, or an unstructured type.

[0164] The AMF may select an SMF based on the PDU session establishment request. In some scenarios, the requested PDU session may already be associated with a specific SMF. For example, the AMF may store the UE context of the UE, and the UE context may indicate that the PDU session ID of the requested PDU session is already associated with a specific SMF. In some scenarios, the AMF may select an SMF based on determining that the SMF is ready to handle the requested PDU session. For example, the requested PDU session may be associated with a specific DNN and / or S-NSSAI, and the SMF may be selected based on determining that the SMF can manage the PDU session associated with the specific DNN and / or S-NSSAI.

[0165] At 1220, the network manages the context of the PDU session. After selecting the SMF at 1210, the AMF sends a PDU session context request to the SMF. The PDU session context request may include the PDU session establishment request received from the UE at 1210. The PDU session context request may be a Nsmf_PDUSess ion_CreateSMContext request and / or a Nsmf_PDUSess ion_UpdateSMContext request. The PDU session context request may indicate an identifier of the UE; a requested DN; and / or a requested network slice. Based on the PDU session context request, the SMF may retrieve subscription data from the UDM. The subscription data may be session management subscription data of the UE. The SMF may subscribe to updates to the subscription data so that the PCF will send new information if the UE's subscription data changes. After obtaining the UE's subscription data, the SMF may transmit a PDU session context response to the AMG. The PDU session context response may be a Nsmf_PDUSess ion_CreateSMContext response and / or a Nsmf_PDUSess ion_UpdateSMContext response. The PDU Session Context Response may contain a Session Management Context ID.

[0166] At 1230, secondary authorization / authentication may be performed if necessary. Secondary authorization / authentication may involve UE, AMF, SMF, and DN. SMF may access DN via a data network authentication, authorization, and accounting (DN AAA) server.

[0167] At 1240, the network sets up a data path for uplink data associated with the PDU session. The SMF may select a PCF and establish a session management policy association. Based on the association, the PCF may provide an initial set of policy control and charging rules (PCC rules) for the PDU session. When targeting a specific PDU session, the PCF may indicate to the SMF a method for assigning an IP address to the PDU session, a default charging method for the PDU session, an address of a corresponding charging entity, a trigger for requesting a new policy, etc. The PCF may also target a service data flow (SDF) that includes one or more PDU sessions. When targeting an SDF, the PCF may indicate to the SMF a policy for applying QoS requirements, monitoring services (e.g., for charging purposes) and / or diverting services (e.g., by using one or more specific N6 interfaces).

[0168] The SMF may determine and / or allocate IP addresses for PDU sessions. The SMF may select one or more UPFs (in Fig.12In the example of FIG. 1 , a single UPF) is used to handle the PDU session. The SMF may send an N4 session message to the selected UPF. The N4 session message may be an N4 session establishment request and / or an N4 session modification request. The N4 session message may include packet detection, enforcement, and reporting rules associated with the PDU session. In response, the UPF may confirm by sending an N4 session establishment response and / or an N4 session modification response.

[0169] The SMF may send the PDU session management information to the AMF. The PDU session management information may be a session service request (e.g., Namf_Communication_N1N2MessageTransfer) message. The PDU session management information may include a PDU session ID. The PDU session management information may be a NAS message. The PDU session management information may include N1 session management information and / or N2 session management information. The N1 session management information may include a PDU session establishment accept message. The PDU session establishment accept message may include the tunneling endpoint information of the UPF and the quality of service (QoS) information associated with the PDU session.

[0170] The AMF may send an N2 request to the AN. The N2 request may include a PDU session establishment accept message. Based on the N2 request, the AN may determine AN resources for the UE. The AN resources may be used by the UE to establish a PDU session with the DN via the AN. The AN may determine the resources to be used for the PDU session and indicate the determined resources to the UE. The AN may send a PDU session establishment accept message to the UE. For example, the AN may perform RRC reconfiguration of the UE. After setting up the AN resources, the AN may send an N2 request confirmation to the AMF. The N2 request confirmation may include N2 session management information, such as the PDU session ID and the tunneling endpoint information of the AN.

[0171] After setting up the data path for uplink data at 1240, the UE may optionally send uplink data associated with the PDU session. Fig.12 As shown in , uplink data can be sent via the AN and UPF to the DN associated with the PDU session.

[0172] At 1250, the network may update the PDU session context. The AMF may transmit a PDU session context update request to the SMF. The PDU session context update request may be a Nsmf_PDUSess ion_UpdateSMContext request. The PDU session context update request may include the N2 session management information received from the AN. The SMF may confirm the PDU session context update. The confirmation may be a Nsmf_PDUSess ion_UpdateSMContext response. The confirmation may include a subscription requesting notification of any UE mobility events to the SMF. Based on the PDU session context update request, the SMF may send an N4 session message to the UPF. The N4 session message may be an N4 session modification request. The N4 session message may include the tunneling endpoint information of the AN. The N4 session message may include forwarding rules associated with the PDU session. In response, the UPF may confirm by sending an N4 session modification response.

[0173] After the UPF receives the tunneling endpoint information of the AN, the UPF may relay the downlink data associated with the PDU session. Fig.12 As shown in , downlink data can be received from the DN associated with the PDU session via the AN and UPF.

[0174] Fig.13 An example of an assembly of elements in a communication network is shown. Fig.13 A physical deployment 1330 (hereinafter "deployment 1330") including a wireless device 1310, a base station 1320, and one or more network functions. Any wireless device described in this disclosure may have similar components and may be implemented in a similar manner to the wireless device 1310. Any other base station (or any portion thereof, depending on the architecture of the base station) described in this disclosure may have similar components and may be implemented in a similar manner to the base station 1320. Any physical core network deployment (or any portion thereof, depending on the architecture of the base station) in this disclosure may have similar components and may be implemented in a similar manner to the deployment 1330.

[0175] Wireless device 1310 may communicate with base station 1320 via air interface 1370. The direction of communication from wireless device 1310 to base station 1320 via air interface 1370 is referred to as uplink, and the direction of communication from base station 1320 to wireless device 1310 via air interface 1370 is referred to as downlink. Downlink transmissions may be separated from uplink transmissions using some combination of FDD, TDD, and / or duplexing techniques. Fig.13A single wireless device 1310 and a single base station 1320 are shown, but it is understood that the wireless device 1310 may communicate with any number of base stations or other access network components via the air interface 1370 , and the base station 1320 may communicate with any number of wireless devices via the air interface 1370 .

[0176] Wireless device 1310 may include processing system 1311 and memory 1312. Memory 1312 may include one or more computer-readable media, such as one or more non-transitory computer-readable media. Memory 1312 may include instructions 1313. Processing system 1311 may process and / or execute instructions 1313. Processing and / or execution of instructions 1313 may cause wireless device 1310 and / or processing system 1311 to perform one or more functions or activities. Memory 1312 may include data (not shown). One of the functions or activities performed by processing system 1311 may be storing data in memory 1312 and / or retrieving previously stored data from memory 1312. In an example, downlink data received from base station 1320 may be stored in memory 1312, and uplink data for transmission to base station 1320 may be retrieved from memory 1312. Fig.13 As shown in , wireless device 1310 may communicate with base station 1320 using transmit processing system 1314 and / or receive processing system 1315. Alternatively, transmit processing system 1314 and receive processing system 1315 may be implemented as a single processing system, or both may be omitted, and all processing in wireless device 1310 may be performed by processing system 1311. Although Fig.13 1314 and / or the receive processing system 1315 may be coupled to a dedicated memory that is similar to but separate from the memory 1312 and includes instructions that may be processed and / or executed to perform one or more of their respective functionalities. The wireless device 1310 may include one or more antennas 1316 to access the air interface 1370.

[0177] The wireless device 1310 may include one or more other elements 1319. The one or more other elements 1319 may include software and / or hardware that provides features and / or functionality, such as a speaker, a microphone, a keypad, a display, a touch pad, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, a global positioning sensor (GPS), etc.). The wireless device 1310 may receive user input data from the one or more other elements 1319 and / or provide user output data to the one or more other elements. The one or more other elements 1319 may include a power source. The wireless device 1310 may receive power from the power source and may be configured to distribute power to other components in the wireless device 1310. The power source may include one or more power sources, such as batteries, solar cells, fuel cells, or any combination thereof.

[0178] The wireless device 1310 may transmit uplink data to the base station 1320 and / or receive downlink data from the base station via the air interface 1370. To perform transmission and / or reception, one or more of the processing system 1311, the transmission processing system 1314, and / or the reception system 1315 may implement open system interconnection (OSI) functionality. As an example, the transmission processing system 1314 and / or the reception system 1315 may perform layer 1 OSI functionality, and the processing system 1311 may perform higher layer functionality. The wireless device 1310 may transmit and / or receive data via the air interface 1370 using one or more antennas 1316. For scenarios where the one or more antennas 1316 include multiple antennas, the multiple antennas may be used to perform one or more multi-antenna techniques, such as spatial multiplexing (e.g., single-user multiple input multiple output (MIMO) or multi-user MIMO), transmit / receive diversity, and / or beamforming.

[0179] Base station 1320 may include a processing system 1321 and a memory 1322. Memory 1322 may include one or more computer-readable media, such as one or more non-transitory computer-readable media. Memory 1322 may include instructions 1323. Processing system 1321 may process and / or execute instructions 1323. Processing and / or execution of instructions 1323 may cause base station 1320 and / or processing system 1321 to perform one or more functions or activities. Memory 1322 may include data (not shown). One of the functions or activities performed by processing system 1321 may be storing data in memory 1322 and / or retrieving previously stored data from memory 1322. Base station 1320 may communicate with wireless device 1310 using transmission processing system 1324 and reception processing system 1325. Although Fig.13 1320. Although not shown, the transmit processing system 1324 and / or the receive processing system 1325 may be coupled to a dedicated memory that is similar to but separate from the memory 1322 and includes instructions that may be processed and / or executed to perform one or more of their respective functionalities. The wireless device 1320 may include one or more antennas 1326 to access the air interface 1370.

[0180] Base station 1320 may transmit downlink data to wireless device 1310 and / or receive uplink data from the wireless device via air interface 1370. To perform transmission and / or reception, one or more of processing system 1321, transmission processing system 1324, and / or reception system 1325 may implement OSI functionality. As an example, transmission processing system 1324 and / or reception system 1325 may perform layer 1 OSI functionality, and processing system 1321 may perform higher layer functionality. Base station 1320 may transmit and / or receive data via air interface 1370 using one or more antennas 1326. For scenarios where the one or more antennas 1326 include multiple antennas, the multiple antennas may be used to perform one or more multi-antenna techniques, such as spatial multiplexing (e.g., single-user multiple input multiple output (MIMO) or multi-user MIMO), transmit / receive diversity, and / or beamforming.

[0181] Base station 1320 may include interface system 1327. Interface system 1327 may communicate with one or more base stations and / or one or more elements of the core network via interface 1380. Interface 1380 may be wired and / or wireless, and interface system 1327 may include one or more components suitable for communicating via interface 1380. Fig.1313, interface 1380 connects base station 1320 to a single deployment 1330, but it should be understood that wireless device 1310 can communicate with any number of base stations and / or CN deployments via interface 1380, and deployment 1330 can communicate with any number of base stations and / or other CN deployments via interface 1380. Base station 1320 may include one or more other elements 1329 similar to one or more of the one or more other elements 1319.

[0182] The deployment 1330 may include any number of parts of any number of instances of one or more network functions (NFs). The deployment 1330 may include a processing system 1331 and a memory 1332. The memory 1332 may include one or more computer-readable media, such as one or more non-transitory computer-readable media. The memory 1332 may include instructions 1333. The processing system 1331 may process and / or execute the instructions 1333. The processing and / or execution of the instructions 1333 may cause the deployment 1330 and / or the processing system 1331 to perform one or more functions or activities. The memory 1332 may contain data (not shown). One of the functions or activities performed by the processing system 1331 may be to store data in the memory 1332 and / or to retrieve previously stored data from the memory 1332. The deployment 1330 may access the interface 1380 using the interface system 1337. The deployment 1330 may include one or more other elements 1339 similar to one or more of the one or more other elements 1319.

[0183] One or more of the systems 1311, 1314, 1315, 1321, 1324, 1325, and / or 1331 may include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may include, for example, a general purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and / or other programmable logic devices, discrete gates and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. One or more of the systems 1311, 1314, 1315, 1321, 1324, 1325, and / or 1331 may perform signal decoding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 1310, the base station 1320, and / or the deployment 1330 to operate in a mobile communication system.

[0184] Many elements described in the disclosed embodiments can be implemented as modules.Modules are defined here as elements that perform defined functions and have defined interfaces to other elements.Modules described in the present disclosure can be implemented with hardware, software, firmware, wetware (for example, hardware with biological elements) or combinations thereof in combination with hardware, all of which can be equivalent in behavior.For example, modules can be implemented as software routines written in computer languages, which are configured to be performed by hardware machines (such as, C, C++, Fortran, Java, Basic, Matlab, etc.) or modeling / simulation programs such as Simu link, Stateflow, GNU Octave or LabVIEW MathScript.It is possible to implement modules using physical hardware that is incorporated with discrete or programmable analog, digital and / or quantum hardware.Examples of programmable hardware include computers, microcontrollers, microprocessors, DSPs, ASICs, FPGAs, and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors can be programmed using languages ​​such as assembly, C, C++, etc. FPGAs, ASICs and CPLDs are often programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configure the connections between internal hardware modules with fewer functions on the programmable devices. The mentioned techniques are often used in combination to achieve the results of the functional modules.

[0185] The wireless device 1310, the base station 1320 and / or the deployment 1330 may implement a timer and / or a counter. The timer / counter may be started at an initial value. As used herein, starting may include restarting. Once started, the timer / counter may run. The operation of the timer / counter may be associated with an event. When an event occurs, the value of the timer / counter may change (e.g., increase or decrease). The event may be, for example, an exogenous event (e.g., receiving a signal, measuring a condition, etc.), an endogenous event (e.g., transmitting a signal, calculating, comparing, performing an action or a decision so performed, etc.), or any combination thereof. In the case of a timer, the event may be the passage of a specific amount of time. However, it should be understood that the timer may be described and / or implemented as a counter that counts the passage of a specific unit of time. The timer / counter may run in the direction of the final value until it reaches the final value. The reaching of the final value may be referred to as the expiration of the timer / counter. The final value may be referred to as a threshold. The timer / counter may be paused, wherein the current value of the timer / counter is maintained, maintained and / or continued, even after one or more events that would otherwise change the value of the timer / counter occur. The timer / counter may unpause or continue, wherein the value maintained, maintained and / or continued begins to change again when the one or more events occur. The timer / counter may be set and / or reset. As used herein, setting may include resetting. When setting and / or resetting the timer / counter, the value of the timer / counter may be set to an initial value. The timer / counter may be started and / or restarted. As used herein, starting may include restarting. In some embodiments, when the timer / counter is restarted, the value of the timer / counter may be set to an initial value and the timer / counter may begin to run.

[0186] Fig.14A , 14B , 14C and 14D show various example arrangements of physical core network deployments each having one or more network functions or portions thereof. The core network deployments include deployment 1410, deployment 1420, deployment 1430, deployment 1440 and / or deployment 1450. Each deployment may be similar to Fig.131330 depicted in . Specifically, each deployment may include a processing system for performing one or more functions or activities, a memory for storing data and / or instructions, and an interface system for communicating with other network elements (e.g., other core network deployments). Each deployment may include one or more network functions (NFs). The term NF may refer to a specific set of functionalities and / or one or more physical elements configured to perform those functionalities (e.g., a processing system and memory including instructions that, when executed by a processing system, cause the processing system to perform the functionality). For example, in the present disclosure, when a network function is described as performing X, Y, and Z, it should be understood that this means that the one or more physical elements are configured to perform X, Y, and Z, regardless of how or where the one or more physical elements are deployed. The term NF may refer to a network node, a network element, and / or a network device.

[0187] As will be discussed in more detail below, there are many different types of NFs, and each type of NF may be associated with a different set of functionality. Multiple different NFs may be flexibly deployed at different locations (e.g., in different physical core network deployments) or in the same location (e.g., co-located in the same deployment). A single NF may be flexibly deployed at different locations (implemented using different physical core network deployments) or in the same location. In addition, a physical core network deployment may also implement one or more base stations, application functions (AFs), data networks (DNs), or any portion thereof. NFs may be implemented in many ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtual functions instantiated on a platform (e.g., a cloud-based platform).

[0188] Fig.14A An example arrangement of core network deployments is shown, where each deployment includes one network function. Deployment 1410 includes NF 1411, deployment 1420 includes NF 1421, and deployment 1430 includes NF 1431. Deployments 1410, 1420, 1430 communicate via interface 1490. Deployments 1410, 1420, 1430 may have different physical locations with different signal propagation delays relative to other network elements. The diversity of physical locations of deployments 1410, 1420, 1430 may enable services to be provided to a wide area with improved speed, coverage, security, and / or efficiency.

[0189] Fig. 14B An example arrangement is shown where a single deployment includes more than one NF. Fig.14A (where each NF is deployed in a separate deployment), Fig. 14BMultiple NFs are shown in deployments 1410, 1420. In an example, deployments 1410, 1420 may implement software defined networking (SDN) and / or network function virtualization (NFV).

[0190] For example, the deployment 1410 includes an additional network function NF 1411A. NFs 1411, 1411A may consist of multiple instances of the same NF type co-located at the same physical location within the same deployment 1410. NFs 1411, 1411A may be implemented independently of each other (e.g., isolated and / or independently controlled). For example, NFs 1411, 1411A may be associated with different network slices. The processing system and memory associated with the deployment 1410 may perform all functionality associated with NF 1411 in addition to all functionality associated with NF 1411A. In an example, NFs 1411, 1411A may be associated with different PLMNs, but the deployment 1410 implementing NFs 1411, 1411A may be owned and / or operated by a single entity.

[0191] exist Fig. 14B Elsewhere in the figure, the deployment 1420 includes NF 1421 and additional network functions NF 1422. NF 1421, 1422 may be different NF types. Similar to NF 1411, 1411A, NF 1421, 1422 may be co-located within the same deployment 1420, but implemented separately. As an example, a first PLMN may own and / or operate a deployment 1420 having NF 1421, 1422. As another example, the first PLMN may implement NF 1421, and the second PLMN may obtain (e.g., rent, lease, obtain, etc.) at least a portion of the capabilities of the deployment 1420 (e.g., processing power, data storage, etc.) from the first PLMN in order to implement NF 1422. As yet another example, the deployment may be owned and / or operated by one or more third parties, and the first PLMN and / or the second PLMN may obtain corresponding portions of the capabilities of the deployment 1420. When multiple NFs are provided at a single deployment, the network may operate at greater speed, coverage, security, and / or efficiency.

[0192] Fig. 14C An example arrangement of a core network deployment is shown, in which a single instance of a NF is implemented using multiple different deployments. Specifically, a single instance of NF 1422 is implemented at deployments 1420, 1440. As an example, the functionality provided by NF 1422 can be implemented as a bundle or a series of sub-services. Each sub-service can be implemented independently, for example, at different deployments. Each sub-service can be implemented in different physical locations. By distributing the implementation of the sub-services of a single NF across different physical locations, the mobile communication network can operate at greater speed, coverage, security and / or efficiency.

[0193] Fig.14D An example arrangement of a core network deployment is shown, in which one or more network functions are implemented using data processing services. Fig.14D In the embodiment, NFs 1411, 1411A, 1421, 1422 are included in a deployment 1450 implemented as a data processing service. The deployment 1450 may include, for example, a cloud network and / or a data center. The deployment 1450 may be owned and / or operated by a PLMN or by a non-PLMN third party. The NFs 1411, 1411A, 1421, 1422 implemented using the deployment 1450 may belong to the same PLMN or to different PLMNs. The PLMN may obtain (e.g., rent, lease, acquire, etc.) at least a portion of the capabilities of the deployment 1450 (e.g., processing power, data storage, etc.). By providing one or more NFs using data processing services, the mobile communication network may operate at a greater speed, coverage, security, and / or efficiency.

[0194] As shown in the figure, different network elements (e.g., NFs) may be located in different physical deployments, or co-located in a single physical deployment. It should be understood that in the present disclosure, the sending and receiving of messages between different network elements is not limited to inter-deployment transmission or intra-deployment transmission, unless explicitly indicated.

[0195] In an example, a deployment may be a 'black box' that is pre-configured with one or more NFs and pre-configured to communicate with other 'black box' deployments (e.g., via interface 1490) in a prescribed manner. Additionally or alternatively, a deployment may be configured to operate according to open source instructions (e.g., software) designed to implement the NFs and communicate with other deployments in a transparent manner. A deployment may operate according to an open RAN (O-RAN) standard.

[0196] Fig.15 The exemplary embodiments depicted in show how an application data unit (ADU) is delivered from a sender to a receiver. The ADU may include, for example, a picture file, a video frame, a text file, and the like. For example, the ADU may include a data unit generated by one or more protocols (e.g., RTP, DASH, TCP, UDP, etc.). The ADU may be generated and / or created, for example, by a first instance of a particular application, used and / or enjoyed by a second instance of the application, or processed by an application server of the application. The middle layer may be responsible for encapsulating and / or formatting the ADU for delivery from the sender to the receiver. For example, the middle layer may provide the functionality of one or more protocols (e.g., IP, etc.). After formatting the ADU into one or more packets based on one or more protocols, the middle layer may forward the one or more packets to the lower layer. The lower layer may provide, for example, the functionality of forwarding one or more packets from one node to another node via a specific interface. The second instance of the application may be located at another node.

[0197] like Fig.15 As depicted in , for example, an upper layer (e.g., an application) in a UE may generate an ADU 1. The upper layer in the UE may deliver the ADU 1 to an intermediate layer of the UE. For the delivered ADU 1, the intermediate layer of the UE may process the ADU 1 and may encapsulate the ADU 1 into one or more packets based on one or more protocols. For example, the one or more packets may include a packet 1 and a packet 2. For example, if an IP protocol is used, the ADU 1 may be processed into one or more IP packets. Each IP packet may include at least a portion of the ADU 1.

[0198] The middle layer may deliver the generated one or more packets to the lower layer. The lower layer may be an access layer (AS), which is responsible for transmitting data between the UE and the NG-RAN. For example, the SDAP entity of the AS may receive packet 1 and / or packet 2 as SDU1 and SDU 2 from the middle layer. The AS of the UE may process and send SDU 1 and SDU 2. For example, the AS of the UE may send SDU 1 and SDU 2 to the AS of the NG-RAN. For example, the RLC entity of the AS of the UE may process and generate one or more PDUs from SDU 1 and SDU 2. For example, based on the amount of radio resources allocated by the NG-RAN, the RLC layer of the AS may segment SDU 1 into PDU 1 and PDU 2, and segment SDU 2 into PDU 3 and PDU 4. The MAC entity of the AS may receive one or more PDUs from the RLC entity. The MAC entity may transmit the received one or more PDUs to the NG-RAN.

[0199] Each layer has different functions, such as Figure 7C The data that makes up the ADU 1 may be partitioned, subdivided, compressed, encrypted, reordered, multiplexed, encoded, etc. After the ADU 1 passes through these layers, the end result (e.g., one or more PDUs) may be suitable for transmission. However, the PDUs may be undecipherable (literally) to the application associated with the ADU 1. After transmission, which is described in more detail below, the process may be reversed and the ADU 1 may be transmitted on the other side (e.g., Fig.15 ) so that it becomes available for use by the application.

[0200] return Fig.15, the MAC entity of the NG-RAN may receive one or more PDUs sent by the UE. The received one or more PDUs may be reassembled into one or more SDUs. For example, using the received PDU 1 and PDU 2, the AS of the NG-RAN may reassemble SDU 1. For example, using the received PDU 3 and PDU 4, the AS of the NG-RAN may reassemble SDU 2. Packet 1 of SDU 1 and packet 2 of SDU 2 may be delivered from the NG-RAN to the core network (e.g., UPF). The core network may send packet 1 and packet 2 to a recipient (e.g., an application server associated with the ADU) via the Internet. After receiving packet 1 and packet 2, the middle layer of the application server may restore ADU 1 and deliver ADU 1 to an upper layer. The application layer may perform application-specific processing using the received ADU 1.

[0201] In the prior art, one or more protocol entities and / or one or more layers may be unaware of the differentiated characteristics of differentiated applications. In the prior art, one or more protocol entities and / or one or more layers may be unaware of the differentiated characteristics of one or more types of ADUs of an application. For example, the AS may not consider the different characteristics of different applications. For example, the AS may not consider the differences and / or similarities and / or relationships between one or more ADUs of an application. For example, a data unit in a lower layer (e.g., Fig.15 1, SDU 1, PDU 2) can be associated with an ADU associated with a specific application (e.g., Fig.15 1). However, within the lower layers, the data unit may not be recognizable as being associated with a specific application data unit or even a specific application. At the lower layers, the data unit may simply be a series of ones and zeros encapsulated for delivery. This application-agnostic approach (e.g., an ADU-agnostic approach) can help support independent enhancements of one or more layers and / or one or more entities. For example, by not tying the operation of the AS to a certain application characteristic, the AS can evolve without changing the behavior of one or more applications. Due to this application-agnostic approach, the AS can support the introduction of new, later-developed applications. However, as new advanced use cases emerge and the QoS requirements of applications are strengthened to provide users with an enhanced experience, the application-agnostic approach of the AS may not be able to support the efficient use of radio resources and network resources, as will be discussed in more detail below.

[0202] Fig.16An example of data delivery in which one or more SDUs are not delivered from the UE to the NG-RAN is shown. For one or more generated PDUs (e.g., PDU 1, PDU 2, PDU 3, PDU 4), ​​the lower layer RLC entity and / or the lower layer MAC entity may transmit the one or more PDUs. When the transmission of the PDU fails, the RLC entity and / or the MAC entity may perform retransmission of the PDU. For example, if the RLC entity of the sender receives a negative acknowledgment of one or more SDUs from the RLC entity of the receiver, the RLC entity of the sender may perform retransmission of the one or more SDUs. For example, if the MAC entity of the sender receives a negative HARQ acknowledgment of the HARQ process from the receiver, the MAC entity of the sender may perform HARQ retransmission of the HARQ process.

[0203] exist Fig.16 In the example of , at time t=t1, the RLC entity of the sender can transmit PDU 1 and can receive an acknowledgment for PDU 1. At time t=t2, the RLC entity can transmit the next PDU, namely PDU 2. After detecting the transmission failure of PDU 2, the RLC entity can perform retransmission of PDU 2 at time t=t2' and t=t2". After several failed transmissions of PDU 2, the RLC entity can stop the transmission of PDU 2, and can start the transmission of PDU 3 at t=t3 and start the transmission of PDU 4 at t=t4. For the received PDUs (e.g., PDU 1, PDU 3, and PDU 4), ​​the receiver can perform assembly of one or more SDUs using the received one or more PDUs. The receiver can deliver the one or more assembled SDUs to the next hop (e.g., UPF, NG-RAN, UE, Internet router, upper layer).

[0204] like Fig.15 As shown, in order to deliver an ADU from a sender to a receiver, all PDUs associated with the ADU may need to be delivered from the UE to the NG-RAN. If one of the PDUs is not successfully delivered, the ADU may not be recovered. For example, Fig.16In the example of , ADU 1 is associated with PDU 1, PDU 2, and PDU 3. ADU 2 is associated with PDU 4. In the example, because PDU 2 was not successfully delivered from the UE to the NG-RAN, the NG-RAN may not be able to reassemble SDU 1 (e.g., package 1). In the example, the NG-RAN may receive PDU 3 and PDU 4. Because PDU 2 was not successfully delivered from the UE to the NG-RAN, the NG-RAN may wait for reception of PDU 2. For example, the NG-RAN may start a timer for PDU 3 and / or PDU 4. Before the timer expires, PDU 2 may not be received. Upon expiration of the timer, the NG-RAN may process PDU 3 and PDU 4.

[0205] In the example, because PDU 3 and PDU 4 are successfully delivered from the UE to the NG-RAN, the NG-RAN may be able to reassemble SDU 2 (e.g., package 2) and SDU 3 (e.g., package 3). The NG-RAN may forward package 2 and package 3 to the application server via the core network. Because package 1 was not received, the application server cannot recover ADU 1 with the received package 2. In the example, because PDU 3 and PDU 4 are received from the UE to the NG-RAN and PDU 2 is not received, the NG-RAN may wait for the reception of PDU 2 until the timer expires. Because the UE can stop the transmission of PDU 2, the NG-RAN may not have to wait for PDU 2.

[0206] However, if Fig.16 As shown in the example of , the inefficient operation of the prior art causes one or more network nodes to deliver one or more packets and / or one or more PDUs associated with an unrecoverable ADU. Fig.16 As shown in the example of , inefficient operation of the prior art causes one or more network nodes to delay delivery of one or more packets and / or one or more PDUs.

[0207] For example, after receiving PDU 1, the receiving RLC entity of the NG-RAN may wait for the reception of PDU 2. For PDU2, at t=t2", the transmitting RLC entity of the UE may determine that the transmission of PDU 2 has failed. However, the receiving RLC entity may unnecessarily wait for the reception of PDU 2. Later, the transmitting RLC entity may transmit PDU 3 at t=t3 and PDU4 at t=t4. PDU 3 and PDU 4 may be received by the receiving RLC entity. However, because PDU 2 has not yet been received, the receiving RLC entity may unnecessarily delay the processing of receiving PDU 3 and PDU 4. Later, the NG-RAN may reassemble SDU 2 (e.g., packet 2) and SDU 3 (e.g., packet 3) using PDU 3 and PDU 4. The NG-RAN may forward packet 2 and packet 3 to the core network. The core network may forward packet 2 and packet 3 to the application server. Due to the lack of packet 1, the application server may not be able to use packet 2. Therefore, in the operation of the prior art, radio resources and network resources may be unnecessarily wasted for the delivery of packet 2. 2. The delivery of package 3 to the application server may be delayed. Therefore, in the operation of the prior art, unnecessary delays in data delivery may reduce the user experience.

[0208] Exemplary embodiments of the present disclosure improve system efficiency through enhancements in the operation of the network and / or UE. In an example, a sending protocol entity may exchange information about one or more protocol data units and / or one or more service data units associated with a failed transmission of a service data unit and / or a protocol data unit with a receiving protocol entity. This can improve the efficiency of buffer management and reduce delays in data delivery. In an example, one or more protocol entities may perform data processing based on exchange information about one or more protocol data units and / or one or more service data units associated with a failed transmission of a service data unit and / or a protocol data unit. This can reduce unnecessary use of radio resources and / or network resources of the system. This can support reducing overall latency.

[0209] In this specification, the term NG-RAN can be interpreted as a base station, which may include at least one of gNB, eNB, ng-eNB, NodeB, access node, access point, N3IWF, relay node, base station central unit (e.g., gNB-CU), base station distributed unit (e.g., gNB-DU), etc.

[0210] In this specification, the term AMF may be interpreted as a core network device, which may include at least one of a mobility management function / entity, an access management function, etc. In this specification, the term SMF may be interpreted as a core network device, which may include at least one of a session management function / entity, a serving gateway, a PDN gateway, etc.

[0211] In the specification, the term of core network node may be interpreted as a core network device, which may include at least one of AMF, SMF, NSSF, UPF, NRF, UDM, PCF, etc. The term of core network may be interpreted as a core network node. In the specification, the term of access node may be interpreted as a base station that may include NG-RAN, etc. In the specification, the term of network node may be interpreted as a core network node and / or access node and / or UE, etc.

[0212] In the specification, a protocol entity may be interpreted as an entity that performs a set of specific functions related to wireless access (e.g., LTE access, NR access) and / or wired access (e.g., Ethernet) and / or communication (e.g., TCP, IP). In an example, an entity may be interpreted as a protocol entity. In an example, the protocol entity of LTE and / or NR may include an SDAP entity and / or a PDCP entity and / or an RLC entity and / or a MAC entity and / or a PHY entity. In an example, a layer (e.g., an SDAP layer, a PDCP layer, an RLC layer, a MAC layer, a PHY layer) may be interpreted as a protocol entity (e.g., an SDAP entity, a PDCP entity, an RLC entity, a MAC entity, a PHY entity).

[0213] In the specification, a service data unit may be interpreted as a unit of data received by a protocol entity. In the specification, a protocol data unit may be interpreted as a unit of data sent by a protocol entity. A protocol entity may receive one or more service data units (SDUs) from other protocol entities, and a protocol entity may send one or more protocol service data units (PDUs) to another protocol entity of the same host or another host. For example, a PDCP entity may receive one or more PDCP SDUs from a higher entity (e.g., an SDAP entity), and the PDCP entity may send one or more PDCP PDUs to a lower entity (e.g., an RLC entity). A lower entity (e.g., an RLC entity) may receive one or more SDUs (e.g., RLC SDUs) from a higher layer. One or more SDUs received by a lower layer may be the same as one or more PDUs sent by a higher layer.

[0214] In this specification, the term AF (Application Function) may be interpreted as AS (Application Server), which may host and / or run one or more applications.

[0215] In this specification, the term ADU can be interpreted as a data unit exchanged between one or more hosts serving an application. In an example, an application (e.g., an Internet browser, an instant messaging application, a video player application, etc.) can be run on a first host (e.g., a smartphone, a computer, an application server, etc.), and the same application can be run on a second host (e.g., another smartphone, a computer, an application server, etc.). The application on the first host can generate application data (e.g., picture files, text messages, etc.) including one or more ADUs. In order to deliver application data from the first host to the second host, the application of the first host can deliver the application data to a first type protocol entity (e.g., an HTTP entity, etc.). In order to deliver application data to the second host, the first type protocol entity of the first host can process the application data and can generate one or more first type protocol data units (e.g., HTTP request messages, HTTP response messages, etc.). The first type protocol entity can deliver one or more first type protocol data units to a first type access (e.g., LTE access, NR access, WIFI access, etc.). The first type of access of the first host can process one or more first type protocol data units, and can generate one or more first type access protocol data units (e.g., SDAP PDU, PDCP PDU, RLC PDU, MAC PDU, etc.). The first type of access of the first host can transmit one or more first type access protocol data units. The first type of access of the third host (e.g., NG-RAN, UE, etc.) can receive one or more first type access protocol data units. The third host can reassemble one or more first type protocol data units, and can deliver one or more first type protocol data units to the second type of access of the third host (e.g., LTE access, NR access, WI FI access, Ethernet access, ATM access, GTP access, etc.). The second type of access of the third host can process one or more first type protocol data units, and can generate one or more second type access protocol data units (e.g., Ethernet frame, ATM cell, LTE access PDU, NR access PDU, WI FI access packet, etc.). The second type of access of the third host can transmit one or more second type access protocol data units. The second type of access of the second host can receive one or more second type access protocol data units. The second type of access of the second host can reassemble one or more first type protocol data units using one or more second type access protocol data units. The second type access of the second host may deliver the reassembled one or more first type protocol data units to the first type protocol entity of the second host.The first type protocol entity of the second host may reassemble the application data using the one or more received first type protocol data units. The first type protocol entity of the second host may deliver the application data to an application of the second host.

[0216] In the example, one or more protocol entities (e.g., TCP entity, UDP entity, RTP entity, etc.) may exist between the application and the access (e.g., LTE access, NR access, WI FI access). In the above description, for the purpose of simple description, only one protocol entity (e.g., first type protocol entity) is described. In the example, one or more protocol entities (e.g., second type protocol entity, third type protocol entity, etc.) may exist between the first type protocol entity and the access. Similarly, in an example, one or more hosts (e.g., NG-RAN, UPF, Internet router, etc.) may exist between the first host and the second host. In the above description, for the purpose of simple description, only one host (e.g., third host) is described. In the example, there may be additional one or more hosts (e.g., fourth host (e.g., UPF), fifth host (e.g., Internet router), etc.) between the third host and the second host. In the example, a pair of hosts may use the same or different types of access. For example, in order to communicate between the third host and the fourth host, a third type of access (e.g., optical fiber, satellite, etc.) may be used.

[0217] In an example, the ADU may be interpreted as application data. In an example, the ADU may be interpreted as a first type protocol data unit. In an example, the ADU may be interpreted as a second type protocol data unit, etc. In an example, the ADU may be interpreted as a data unit of a protocol entity. In an example, the first host and the second host may maintain one or more contexts of the protocol entity. For example, an application of the first host may communicate with an application of the second host. An application of the first host may have a context of the second host. An application of the second host may have a context of the first host. Therefore, the application data may be an ADU. For example, a first type protocol entity of the first host may communicate with a first type protocol entity of the second host. A first type protocol entity of the first host may have a context of the second host. A first type protocol of the second host may have a context of the first host. Therefore, the first type protocol data unit may be an ADU. For example, a first type access of the first host may not communicate with a second type access of the second host. The first type access of the first host may not have a context of the second type access of the second host. The second type access of the second host may not have a context of the first type access of the first host. Therefore, the first type access protocol data unit may not be an ADU. Therefore, the second type access protocol data unit may not be an ADU.

[0218] In this specification, the term service data flow may be interpreted as a set of data units exchanged between one or more hosts. For example, a first service data flow may be interpreted as a set of one or more data units from a second host to a first host. For example, a second service data flow may be interpreted as a set of one or more data units from a third host to a first host. For example, one or more data units of a service data flow may include the same share on one or more attributes (e.g., the same source IP address, the same destination IP address, the same UDP port, etc.).

[0219] In the specification, the term of part may be interpreted as part. For example, a part of an SDU may be interpreted as one or more parts of an SDU. For example, a part of an SDU may be interpreted as one or more bytes / bits of an SDU. For example, a part of a PDU may be interpreted as one or more parts of a PDU. For example, a part of a PDU may be interpreted as one or more bytes / bits of a PDU. In the specification, the term of a segment may be interpreted as a part. For example, a segment of an RLC SDU and / or an RLC SDU segment may be one or more bytes / bits of an RLC SDU.

[0220] Fig.17 An exemplary embodiment of the present disclosure may be depicted.

[0221] In an example, a first transport protocol entity (e.g., a PDCP entity, an RLC entity, an SDAP entity) may receive one or more packets (e.g., SDUs) from a higher layer (e.g., an SDAP entity, a PDCP entity, an IP entity, a TCP entity, etc.). The one or more packets may include at least one or more packet headers and / or one or more packet payloads. The one or more packet payloads may include one or more ADUs and / or one or more bytes of one or more ADUs and / or one or more SDUs (e.g., PDCP SDUs, SDAP SDUs, RLC SDUs). The one or more packets may include a first packet and / or a second packet and / or a third packet. When the first transport protocol entity receives the one or more packets, the first transport protocol entity may further receive one or more associated ADU information together with the one or more packets. The first transport protocol entity may receive a first packet with first associated ADU information. The first transport protocol entity may receive a second packet with second associated ADU information. The first transport protocol entity may receive a third packet with third associated ADU information. For example, the first associated ADU information may indicate that the identity of the ADU associated with the first packet is 1. For example, the second associated ADU information may indicate that the identity of the ADU associated with the second packet is 1. For example, the third associated ADU information may indicate that the identity of the ADU associated with the third packet is 2. For example, the one or more associated ADU information may indicate that the first packet and the second packet are associated. For example, the one or more associated ADU information may indicate that the first packet and the third packet are not associated.

[0222] In an example, a first transport protocol entity may process one or more received packets and / or one or more associated ADU information. After processing, the first transport protocol entity may form one or more PDUs (e.g., PDCP PDUs, RLC PDUs, SDAP PDUs). For example, one or more PDUs may include a first PDU and / or a second PDU and / or a third PDU. A first PDU (e.g., a first PDCP PDU) may include at least a portion of a first SDU (e.g., a first packet). A second PDU (e.g., a second PDCP PDU) may include at least a portion of a second SDU (e.g., a second packet). A third PDU (e.g., a third PDCP PDU) may include at least a portion of a third SDU (e.g., a third packet).

[0223] In an example, a first transmission protocol entity (e.g., a transmission PDCP entity) may deliver one or more PDUs (e.g., PDCP PDUs) to a second transmission protocol entity (e.g., a transmission RLC entity). The transmission RLC entity may receive one or more RLC SDUs (e.g., one or more PDCP PDUs). For the received one or more RLC SDUs, the transmission RLC entity may construct one or more RLC PDUs. The one or more RLC PDUs may include at least one fragment of one or more RLC SDUs (e.g., RLC SDU 1 fragment 1, RLC SDU 1 fragment 2, RLC SDU 1, RLC SDU 2 fragment 1, RLC SDU 2). Based on the size information indicated by the MAC entity, the transmission RLC entity may construct one or more RLC PDUs from one or more RLC SDUs. For example, if the MAC entity requests the transmission RLC entity to deliver a data block smaller than 500 bytes, the transmission RLC entity may construct an RLC PDU that may be smaller than 500 bytes. The RLC PDU may include at least one fragment of one or more RLC SDUs and / or control information.

[0224] In an example, after constructing one or more RLC PDUs, the transmitting RLC entity may deliver the one or more RLC PDUs to the MAC entity for transmission. For example, the transmitting RLC entity may use one or more fragments of one or more RLC SDUs to construct the one or more RLC PDUs. For example, for a first RLC SDU (e.g., a first PDCP PDU), the transmitting RLC entity may generate one or more RLC PDUs. The one or more RLC PDUs may include a first RLC PDU and / or a second RLC PDU. The first RLC PDU may include a first fragment of RLC SDU 1 (e.g., a first part of the first PDCP PDU). The second RLC PDU may include a second fragment of RLC SDU 1 (e.g., a second part of the first PDCP PDU).

[0225] In an example, a transmitting RLC entity may send one or more RLC PDUs. One or more RLC PDUs sent by the transmitting RLC entity may be successfully delivered to a receiving RLC entity. One or more RLC PDUs sent by the transmitting RLC entity may not be successfully delivered to a receiving RLC entity. For example, a first RLC PDU (e.g., RLC SDU 1 fragment 1) may be successfully delivered to a receiving RLC entity. For example, a second RLC PDU (e.g., RLC SDU 1 fragment 2) may not be successfully delivered to a receiving RLC entity. In order to deliver RLC SDU 1 fragment 2 to the receiving RLC entity, the transmitting RLC entity may retransmit RLC SDU 1 fragment 2 multiple times.

[0226] In an example, after several unsuccessful retransmission attempts to deliver RLC SDU 1 fragment 2 to the receiving RLC entity, the transmitting RLC entity may determine that transmission of the RLC SDU 1 has failed. The determination of transmission failure of the RLC SDU 1 may be that the transmitting RLC entity stops transmission of the RLC SDU 1 and / or fragments of the RLC SDU 1. The determination of transmission failure of the RLC SDU 1 may be that the transmitting RLC entity aborts delivery of the RLC SDU 1 and / or fragments of the RLC SDU 1. The determination of transmission failure of the RLC SDU 1 may be that delivery of the RLC SDU 1 has failed. The determination of transmission failure of the RLC SDU 1 may be that delivery of the RLC SDU 1 has not been successful within a configured amount of time.

[0227] In an example, based on the determination of the transmission failure of RLC SDU 1, the transmitting RLC entity may send an RLC control PDU (e.g., an RLC status PDU, an RLC sender status report, an RLC status PDU) to the receiving RLC entity. The RLC control PDU may include information about one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs that the transmitting RLC entity does not transmit. The RLC control PDU may include information about one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs that the transmitting RLC entity stops transmitting. The RLC control PDU may include information about one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs that the transmitting RLC entity stops transmitting. The information about one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs may include one or more sequence numbers associated with one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs. For example, the RLC control PDU may include information that the RLC SDU 1 may not be transmitted and / or may be discarded.

[0228] In an example, a receiving RLC entity may receive an RLC control PDU. Based on the received RLC control PDU, the receiving RLC entity may identify one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs that the transmitting RLC entity does not transmit and / or stops transmitting and / or suspends transmitting. For example, for the identified one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs, the receiving RLC entity may behave as if one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs were received. For example, the receiving RLC entity may update local variables associated with the operation of the receiving RLC entity. For example, the receiving RLC entity may update local variables associated with one or more sequence numbers (e.g., the sequence number of the next expected RLC PDU / SDU, and / or the sequence number of the confirmed RLC PDU / SDU and / or the sequence number associated with the receiving window). For example, for the identified one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs, the receiving RLC entity may determine one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or RLC PDU fragments associated with the identified one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs. The receiving RLC entity may discard the determined one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC PDU fragments. For example, if the RLC control PDU indicates that the transmission of RLC SDU 1 is aborted, the receiving RLC entity may discard the first RLC SDU 1 fragment 1. For example, for the identified one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs, the receiving RLC entity may indicate to the receiving PDCP entity information of the identified one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs. Based on the indication from the receiving RLC entity, the receiving PDCP entity may determine one or more PDCP PDUs / SDUs associated with the indicated one or more RLC SDUs and / or one or more fragments of the one or more RLC SDUs. The receiving PDCP entity may discard the determined one or more PDCP PDUs.

[0229] Fig.18 An exemplary embodiment of the present disclosure may be depicted.

[0230] In an example, a first transport protocol entity (e.g., a PDCP entity, an RLC entity, an SDAP entity) may receive one or more packets (e.g., SDUs) from a higher layer (e.g., an SDAP entity, a PDCP entity, an IP entity, a TCP entity, etc.). The one or more packets may include at least one or more packet headers and / or one or more packet payloads. The one or more packet payloads may include one or more ADUs and / or one or more bytes of one or more ADUs and / or one or more SDUs (e.g., PDCP SDUs, SDAP SDUs, RLC SDUs). The one or more packets may include a first packet and / or a second packet and / or a third packet. When the first transport protocol entity receives the one or more packets, the first transport protocol entity may further receive one or more associated ADU information together with the one or more packets. The first transport protocol entity may receive a first packet with first associated ADU information. The first transport protocol entity may receive a second packet with second associated ADU information. The first transport protocol entity may receive a third packet with third associated ADU information. For example, the first associated ADU information may indicate that the identity of the ADU associated with the first packet is 1. For example, the second associated ADU information may indicate that the identity of the ADU associated with the second packet is 1. For example, the third associated ADU information may indicate that the identity of the ADU associated with the third packet is 2. For example, the one or more associated ADU information may indicate that the first packet and the second packet are associated. For example, the one or more associated ADU information may indicate that the first packet and the third packet are not associated.

[0231] In an example, a first transport protocol entity may process one or more received packets and / or one or more associated ADU information. After processing, the first transport protocol entity may form one or more PDUs (e.g., PDCP PDUs, RLC PDUs, SDAP PDUs). For example, one or more PDUs may include a first PDU and / or a second PDU and / or a third PDU. A first PDU (e.g., a first PDCP PDU) may include at least a portion of a first SDU (e.g., a first packet). A second PDU (e.g., a second PDCP PDU) may include at least a portion of a second SDU (e.g., a second packet). A third PDU (e.g., a third PDCP PDU) may include at least a portion of a third SDU (e.g., a third packet).

[0232] In an example, a transmitting PDCP entity may deliver a first PDCP PDU to a transmitting RLC entity. The transmitting RLC entity may receive a first RLC SDU (e.g., a first PDCP PDU, RLC SDU 1). For the received first RLC SDU, the transmitting RLC entity may process the first RLC SDU and may construct one or more RLC PDUs. The one or more RLC PDUs may include at least one or more fragments of the first RLC SDU. For example, the one or more RLC PDUs may include a first RLC PDU (e.g., RLC PDU 1, RLC SDU 1 fragment 1) and / or a second RLC PDU (e.g., RLC PDU 2, RLC SDU 1 fragment 2).

[0233] In an example, after constructing one or more RLC PDUs, the transmitting RLC entity may deliver the one or more RLC PDUs to the MAC entity for transmission. For example, the transmitting RLC entity may construct a first RLC PDU (e.g., RLC PDU 1) using a first segment of a first RLC SDU. For example, the transmitting RLC entity may construct a second RLC PDU (e.g., RLC PDU 2) using a second segment of the first RLC SDU.

[0234] In an example, a transmitting RLC entity may transmit one or more RLC PDUs. One or more RLC PDUs sent by the transmitting RLC entity may be successfully delivered to a receiving RLC entity. One or more RLC PDUs sent by the transmitting RLC entity may not be successfully delivered to the receiving RLC entity. For example, a first RLC PDU may be successfully delivered to the receiving RLC entity. For example, a second RLC PDU may not be successfully delivered to the receiving RLC entity. In order to deliver a second segment of a first RLC SDU to the receiving RLC entity, the transmitting RLC entity may retransmit the second segment of the first RLC SDU multiple times.

[0235] In an example, after several unsuccessful retransmission attempts to deliver the second segment of the first RLC SDU to the receiving RLC entity, the transmitting RLC entity may determine that the transmission of the RLC SDU 1 has failed. The determination of the transmission failure of the RLC SDU 1 may be that the transmitting RLC entity stops the transmission of the RLC SDU 1 and / or one or more segments of the RLC SDU 1. The determination of the transmission failure of the RLC SDU 1 may be that the transmitting RLC entity aborts the transmission of the RLC SDU 1 and / or one or more segments of the RLC SDU 1. The determination of the transmission failure of the RLC SDU 1 may be a delivery failure of the RLC SDU 1 and / or one or more segments of the RLC SDU 1.

[0236] In an example, based on the determination of the transmission failure of RLC SDU 1, the transmitting RLC entity may indicate delivery information to the transmitting PDCP entity. The delivery information may indicate a delivery failure of a PDCP PDU (e.g., a first PDCP PDU) and / or a delivery failure of an RLC SDU (e.g., a first RLC SDU). The delivery information may indicate that an error occurred in the delivery of the PDCP PDU and / or the RLC SDU.

[0237] In an example, based on the delivery information, the transmitting PDCP entity may determine to discard the PDCP PDU indicated by the delivery information and / or the PDCP SDU associated with the PDCP PDU. In an example, based on the delivery information, the transmitting PDCP entity may determine to discard the PDCP SDU (e.g., the first PDCP SDU, the first packet) associated with the PDCP PDU indicated by the delivery information (e.g., the first PDCP PDU). Based on the delivery information from the transmitting RLC entity, the transmitting PDCP entity may determine the ADU information associated with the PDCP PDU. For example, based on the delivery information indicating that the first PDCP PDU and / or the first PDCP SDU is associated with the first PDCP PDU and / or the first packet is associated with the first PDCP SDU, the transmitting PDCP entity may determine the ADU information associated with the first packet (e.g., the identity of the ADU). For example, the transmitting PDCP entity may determine that the identity of the ADU associated with the first packet may be 1. Based on the identified ADU information associated with the PDCP PDU, the transmitting PDCP entity may further determine one or more PDCP SDUs (e.g., packets) associated with the ADU information. For example, based on the ADU information associated with the second packet, the transmitting PDCP entity may determine that the second packet (e.g., the second PDCP SDU) is associated with the first packet. Based on the determination, the transmitting PDCP entity may discard the second packet (e.g., the second PDCP SDU) and / or the second PDCP PDU. For example, based on the ADU information associated with the third packet, the transmitting PDCP entity may determine that the third packet (e.g., the third PDCP SDU) is not associated with the first packet. Based on the determination, the transmitting PDCP entity may not discard the third packet (e.g., the third PDCP SDU) and / or the third PDCP PDU.

[0238] Fig.19 An exemplary embodiment of the present disclosure may be depicted.

[0239] In an example, a first transport protocol entity (e.g., a PDCP entity, an RLC entity, an SDAP entity) may receive one or more packets (e.g., SDUs) from a higher layer (e.g., an SDAP entity, a PDCP entity, an IP entity, a TCP entity, etc.). The one or more packets may include at least one or more packet headers and / or one or more packet payloads. The one or more packet payloads may include one or more ADUs and / or one or more bytes of one or more ADUs and / or one or more SDUs (e.g., PDCP SDUs, SDAP SDUs, RLC SDUs). The one or more packets may include a first packet and / or a second packet and / or a third packet. When the first transport protocol entity receives the one or more packets, the first transport protocol entity may further receive one or more associated ADU information together with the one or more packets. The first transport protocol entity may receive a first packet with first associated ADU information. The first transport protocol entity may receive a second packet with second associated ADU information. The first transport protocol entity may receive a third packet with third associated ADU information. For example, the first associated ADU information may indicate that the identity of the ADU associated with the first packet is 1. For example, the second associated ADU information may indicate that the identity of the ADU associated with the second packet is 1. For example, the third associated ADU information may indicate that the identity of the ADU associated with the third packet is 2. For example, the one or more associated ADU information may indicate that the first packet and the second packet are associated. For example, the one or more associated ADU information may indicate that the first packet and the third packet are not associated.

[0240] In an example, a first transport protocol entity may process one or more received packets and / or one or more associated ADU information. After processing, the first transport protocol entity may form one or more PDUs (e.g., PDCP PDUs, RLC PDUs, SDAP PDUs). For example, one or more PDUs may include a first PDU and / or a second PDU and / or a third PDU. A first PDU (e.g., a first PDCP PDU) may include at least a portion of a first SDU (e.g., a first packet). A second PDU (e.g., a second PDCP PDU) may include at least a portion of a second SDU (e.g., a second packet). A third PDU (e.g., a third PDCP PDU) may include at least a portion of a third SDU (e.g., a third packet).

[0241] In an example, the transmitting PDCP entity may deliver a first PDCP PDU to a transmitting RLC entity. The transmitting RLC entity may receive a first RLC SDU (e.g., a first PDCP PDU, RLC SDU 1). For the received first RLC SDU, the transmitting RLC entity may process the first RLC SDU and may construct a first RLC PDU (RLC PDU 1).

[0242] In an example, the transmitting PDCP entity may deliver a second PDCP PDU to the transmitting RLC entity. The transmitting RLC entity may receive a second RLC SDU (e.g., a second PDCP PDU, PDCP PDU 2, RLC SDU 2). For the received second RLC SDU, the transmitting RLC entity may process the second RLC SDU and may construct one or more RLC PDUs. For example, the one or more RLC PDUs may include the second RLC PDU (RLC PDU 2).

[0243] In an example, after constructing one or more RLC PDUs, the transmitting RLC entity may deliver one or more RLC PDUs to the MAC entity for transmission.

[0244] One or more RLC PDUs sent by the transmitting RLC entity may be successfully delivered to the receiving RLC entity. One or more RLC PDUs sent by the transmitting RLC entity may not be successfully delivered to the receiving RLC entity. For example, the first RLC SDU may be successfully delivered to the receiving RLC entity. The receiving RLC entity may buffer one or more successfully received RLC SDUs in a memory. For example, the second RLC PDU and / or the second RLC SDU may not be successfully delivered to the receiving RLC entity. In order to deliver the second RLC PDU and / or the second RLC SDU to the receiving RLC entity, the transmitting RLC entity may retransmit the second RLC PDU and / or the second RLC SDU multiple times.

[0245] In an example, after several unsuccessful retransmission attempts to deliver the second RLC PDU and / or the second RLC SDU to the receiving RLC entity, the transmitting RLC entity may determine that the transmission of the RLC SDU 2 has failed. The determination of the transmission failure of the RLC SDU 2 may be that the transmitting RLC entity stops the transmission of the RLC PDU 2 and / or the RLC SDU 2. The determination of the transmission failure of the RLC PDU 2 may be that the transmitting RLC entity aborts the transmission of the RLC PDU 2 and / or the RLC SDU 2. The determination of the transmission failure of the RLC PDU 2 may be a delivery failure of the RLC SDU 2 and / or the RLC PDU 2.

[0246] In an example, based on the determination of the transmission failure of RLC SDU 2, the transmitting RLC entity may send delivery information to the transmitting PDCP entity. The delivery information may indicate a delivery failure of a PDCP PDU (e.g., a second PDCP PDU) and / or a delivery failure of an RLC SDU (e.g., a second RLC SDU). The delivery information may indicate that an error occurred in the delivery of the PDCP PDU and / or the RLC SDU.

[0247] In an example, based on the delivery information, the transmitting PDCP entity may determine to discard a PDCP PDU indicated by the delivery information. In an example, based on the delivery information, the transmitting PDCP entity may determine to discard a PDCP SDU (e.g., a second PDCP SDU, a second packet) associated with the PDCP PDU indicated by the delivery information. Based on the delivery information from the RLC transmission entity, the transmitting PDCP entity may determine ADU information associated with the PDCP PDU. For example, based on the delivery information indicating the second PDCP PDU and / or the second PDCP SDU is associated with the second PDCP PDU and / or the second packet is associated with the second PDCP SDU, the transmitting PDCP entity may determine ADU information associated with the second packet (e.g., the identity of the ADU).

[0248] For example, the transmitting PDCP entity may determine that the identity of the ADU associated with the second packet is 1. Based on the identified ADU information associated with the PDCP PDU, the transmitting PDCP entity may further determine one or more PDCP SDUs (e.g., packets) associated with the ADU information. For example, based on the ADU information associated with the first packet and / or based on the ADU information associated with the second packet, the transmitting PDCP entity may determine that the first packet (e.g., the first PDCP SDU) is associated with the second packet (e.g., the second PDCP SDU). Based on the determination, the transmitting PDCP entity may discard the first packet (e.g., the first PDCP SDU) and / or the first PDCP PDU. For example, based on the ADU information associated with the third packet and / or based on the ADU information associated with the second packet, the transmitting PDCP entity may determine that the third packet (e.g., the third PDCP SDU) is not associated with the second packet (e.g., the second PDCP SDU). Based on the determination, the transmitting PDCP entity may not discard the third packet (e.g., the third PDCP SDU) and / or the third PDCP PDU.

[0249] In an example, based on the identification of the associated one or more PDCP SDUs (e.g., one or more packets, one or more PDCP PDUs), the transmitting PDCP entity may indicate to the transmitting RLC entity that the first PDCP PDU (e.g., the first RLC SDU) needs to be discarded, wherein the identification of the associated one or more PDCP SDUs is based on one or more ADU information. For example, the transmitting PDCP entity may indicate to the transmitting RLC entity that the first RLC SDU needs to be discarded. For example, the transmitting PDCP entity may indicate to the transmitting RLC entity based on the ADU information that the transmitting RLC entity needs to discard one or more RLC SDUs. Based on the information of the one or more RLC SDUs to be discarded, the transmitting RLC entity may send an RLC control PDU (e.g., RLC status PDU, RLC sender status report) to the receiving RLC entity. The RLC control PDU may include information about one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs that the transmitting RLC entity does not transmit and / or discards. The RLC control PDU may include information about one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs that the transmitting RLC entity stops transmitting. The RLC control PDU may include information about one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs that the transmitting RLC entity aborts transmission. The information about one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs may include one or more sequence numbers associated with the one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs. For example, based on an indication from the transmitting PDCP entity that the first RLC SDU needs to be discarded, the RLC control PDU may include information about the need to discard the first RLC PDU and / or one or more fragments of the first RLC SDU and / or the first RLC SDU.

[0250] In an example, a receiving RLC entity may receive an RLC control PDU. Based on the received RLC control PDU, the receiving RLC entity may identify one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs that the transmitting RLC entity does not transmit and / or stops transmitting and / or suspends transmitting and / or discards. For example, for the identified one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs, the receiving RLC entity may behave as if one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs are received. For example, the receiving RLC entity may update one or more local variables associated with the operation of the receiving RLC entity. For example, the receiving RLC entity may update one or more local variables associated with one or more sequence numbers (e.g., the sequence number of the next expected RLC SDU and / or the sequence number of one or more fragments of one or more RLC SDUs and / or the sequence number of the confirmed RLC SDU and / or the sequence number associated with the receiving / receiving window, etc.). For example, for the identified one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs, the receiving RLC entity may determine one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs associated with the identified one or more RLC SDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs. The receiving RLC entity may discard the identified one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDU fragments. For example, the receiving RLC entity may discard the first RLC PDU and / or the first RLC SDU and / or one or more fragments of the first RLC SDU. For example, for the identified one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs, the receiving RLC entity may indicate to the receiving PDCP entity information of the identified one or more RLC PDUs and / or one or more fragments of one or more RLC SDUs and / or one or more RLC SDUs. Based on the indication from the receiving RLC entity, the receiving PDCP entity may determine one or more PDCP PDUs associated with the indicated one or more RLC SDUs. The receiving PDCP entity may discard the determined one or more PDCP PDUs.

[0251] Fig. 20An exemplary embodiment of the present disclosure may be depicted.

[0252] like Fig.19 As shown in the example of , a receiving RLC entity may receive a first RLC PDU. The first RLC PDU may include a first PDCP PDU. Based on the first RLC PDU, the receiving RLC entity may recover a first RLC SDU. The receiving RLC entity may deliver the recovered first RLC SDU to the receiving PDCP entity. The receiving PDCP entity may buffer the received first RLC SDU (e.g., the first PDCP PDU).

[0253] In an example, the receiving RLC entity may receive an RLC control PDU. The RLC control PDU may indicate that a first RLC PDU and / or a first RLC SDU needs to be discarded. The receiving RLC entity may indicate that a receiving PDCP entity needs to discard a first RLC SDU (e.g., a first PDCP PDU). Based on the indication from the receiving RLC entity, the receiving PDCP entity may discard the first PDCP PDU and / or the first PDCP SDU.

[0254] Fig.21 An exemplary embodiment of the present disclosure may be depicted.

[0255] In an example, a first transport protocol entity (e.g., a PDCP entity, an RLC entity, an SDAP entity) may receive one or more packets (e.g., SDUs) from a higher layer (e.g., an SDAP entity, a PDCP entity, an IP entity, a TCP entity, etc.). The one or more packets may include at least one or more packet headers and / or one or more packet payloads. The one or more packet payloads may include one or more ADUs and / or one or more bytes of one or more ADUs and / or one or more SDUs (e.g., PDCP SDUs, SDAP SDUs, RLC SDUs). The one or more packets may include a first packet and / or a second packet and / or a third packet. When the first transport protocol entity receives the one or more packets, the first transport protocol entity may further receive one or more associated ADU information together with the one or more packets. The first transport protocol entity may receive a first packet with first associated ADU information. The first transport protocol entity may receive a second packet with second associated ADU information. The first transport protocol entity may receive a third packet with third associated ADU information. For example, the first associated ADU information may indicate that the identity of the ADU associated with the first packet is 1. For example, the second associated ADU information may indicate that the identity of the ADU associated with the second packet is 1. For example, the third associated ADU information may indicate that the identity of the ADU associated with the third packet is 2. For example, the one or more associated ADU information may indicate that the first packet and the second packet are associated. For example, the one or more associated ADU information may indicate that the first packet and the third packet are not associated.

[0256] In an example, a first transport protocol entity may process one or more received packets and / or one or more associated ADU information. After processing, the first transport protocol entity may form one or more PDUs (e.g., PDCP PDUs, RLC PDUs, SDAP PDUs). For example, one or more PDUs may include a first PDU and / or a second PDU and / or a third PDU. A first PDU (e.g., a first PDCP PDU) may include at least a portion of a first SDU (e.g., a first packet). A second PDU (e.g., a second PDCP PDU) may include at least a portion of a second SDU (e.g., a second packet). A third PDU (e.g., a third PDCP PDU) may include at least a portion of a third SDU (e.g., a third packet).

[0257] In an example, a transmitting PDCP entity may deliver the first PDCP PDU to a transmitting RLC entity. The transmitting RLC entity may receive a first RLC SDU (e.g., a first PDCP PDU, PDCP PDU 1, RLC SDU 1). For the received first RLC SDU, the transmitting RLC entity may process the first RLC SDU and may construct one or more RLC PDUs. For example, the one or more RLC PDUs may include the first RLC PDU (RLC PDU 1).

[0258] In an example, the transmitting PDCP entity may deliver a second PDCP PDU to the transmitting RLC entity. The transmitting RLC entity may receive a second RLC SDU (e.g., a second PDCP PDU, PDCP PDU 2, RLC SDU 2). For the received second RLC SDU, the transmitting RLC entity may process the second RLC SDU and may construct one or more RLC PDUs. For example, the one or more RLC PDUs may include the second RLC PDU (RLC PDU 2).

[0259] In an example, after constructing one or more RLC PDUs, the transmitting RLC entity may deliver one or more RLC PDUs to the MAC entity for transmission.

[0260] One or more RLC PDUs and / or one or more RLC SDUs sent by a transmitting RLC entity may be successfully delivered to a receiving RLC entity. One or more RLC PDUs and / or one or more RLC SDUs sent by a transmitting RLC entity may not be successfully delivered to the receiving RLC entity. For example, a first RLC PDU and / or a first RLC SDU may be successfully delivered to a receiving RLC entity. The receiving RLC entity may buffer one or more successfully received RLC PDUs and / or one or more RLC SDUs in a memory. For example, the receiving RLC entity may deliver one or more successfully received RLC SDUs to a receiving PDCP entity. For example, a second RLC PDU and / or a second RLC SDU may not be successfully delivered to a receiving RLC entity. In order to deliver a second RLC PDU and / or a second RLC SDU to a receiving RLC entity, the transmitting RLC entity may retransmit the second RLC PDU and / or the second RLC SDU multiple times.

[0261] In an example, after several unsuccessful retransmission attempts to deliver the second RLC PDU and / or the second RLC SDU to the receiving RLC entity, the transmitting RLC entity may determine that the transmission of the RLC PDU 2 and / or the second RLC SDU has failed. The determination of the transmission failure of the RLC PDU 2 and / or the second RLC SDU may be that the transmitting RLC entity stops the transmission of the RLC PDU 2 and / or the second RLC SDU 2. The determination of the transmission failure of the RLC PDU 2 and / or the second RLC SDU may be that the transmitting RLC entity aborts the transmission of the RLC PDU 2 and / or the RLC SDU 2. The determination of the transmission failure of the RLC PDU 2 may be a delivery failure of the RLC SDU 2 and / or the second RLC SDU.

[0262] In an example, based on the determination of the transmission failure of RLC PDU 2 and / or the second RLC SDU, the transmitting RLC entity may send delivery information to the transmitting PDCP entity. The delivery information may indicate the delivery failure of the PDCP PDU (e.g., the second PDCP PDU, the second RLC SDU) and / or the delivery failure of the RLC SDU (e.g., the second RLC SDU). The delivery information may indicate that an error occurred in the delivery of the PDCP PDU and / or the RLC SDU.

[0263] In an example, based on the delivery information, the transmission PDCP entity may determine to discard the PDCP PDU indicated by the delivery information. In an example, based on the delivery information, the transmission PDCP entity may determine to discard the PDCP SDU (e.g., the second PDCP SDU, the second packet) associated with the PDCP PDU indicated by the delivery information. Based on the delivery information from the RLC transmission entity, the transmission PDCP entity may determine the ADU information associated with the PDCP PDU. For example, based on the delivery information indicating that the second PDCP PDU and / or the second PDCP SDU is associated with the second PDCP PDU and / or the second packet is associated with the second PDCP SDU, the transmission PDCP entity may determine the ADU information associated with the second packet (e.g., the identity of the ADU). For example, the transmission PDCP entity may determine that the identity of the ADU associated with the second packet is 1. Based on the identified ADU information associated with the PDCP PDU, the transmission PDCP entity may further determine one or more PDCP SDUs (e.g., packets) associated with the ADU information. For example, based on the ADU information associated with the first packet, the transmission PDCP entity may determine that the first packet (e.g., the first PDCP SDU) is associated with the second packet. Based on the determination, the transmitting PDCP entity may discard the first packet (e.g., the first PDCP SDU) and / or the first PDCP PDU. For example, based on the ADU information associated with the third packet, the transmitting PDCP entity may determine that the third packet (e.g., the third PDCP SDU) is not associated with the second packet. Based on the determination, the transmitting PDCP entity may not discard the third packet (e.g., the third PDCP SDU) and / or the third PDCP PDU.

[0264] In an example, a transmitting PDCP entity may send a PDCP status report (e.g., a PDCP control PDU, a PDCP sender report) to a receiving PDCP entity. The PDCP status report may include information that one or more PDCP SDUs (e.g., a first PDCP SDU, a second PDCP SDU) are discarded and / or not transmitted. For example, the PDCP status report may include information that the transmission of one or more PDCP SDUs (e.g., a first PDCP SDU, a second PDCP SDU) is stopped and / or aborted. For example, the PDCP status report may include information about one or more PDCP SDUs that the transmitting PDCP entity may or may not transmit. For example, the PDCP status report may include information about one or more PDCP PDUs associated with one or more ADUs. For example, the PDCP status report may include information about one or more sequence numbers that the transmitting PDCP entity may transmit.

[0265] In an example, a receiving PDCP entity may receive a PDCP control PDU. Based on the received PDCP control PDU, the receiving PDCP entity may identify one or more PDCP PDUs and / or one or more PDCP SDUs that the transmitting PDCP entity does not transmit and / or stops transmitting and / or suspends transmitting and / or discards. For example, for the identified one or more PDCP PDUs and / or one or more PDCP SDUs, the receiving PDCP entity may behave as if one or more PDCP PDUs and / or one or more PDCP SDUs are received. For example, based on the PDCP control PDU, the receiving PDCP entity may update local variables associated with the operation of the receiving PDCP entity. For example, the receiving PDCP entity may update local variables associated with the sequence number of the next expected PDCP PDU / SDU and / or a sequence number associated with the receiving window. For example, for the identified one or more PDCP PDUs and / or one or more PDCP SDUs, the receiving PDCP entity may discard the identified one or more PDCP PDUs and / or one or more PDCP SDUs. For example, for the identified one or more PDCP PDUs and / or one or more PDCP SDUs, the receiving PDCP entity may indicate to the receiving RLC entity information of one or more RLC SDUs associated with the identified one or more PDCP PDUs. Based on the indication from the receiving PDCP entity, the receiving RLC entity may determine one or more RLC PDUs and / or RLC SDUs to be discarded. Based on the indication from the receiving PDCP entity, the receiving RLC entity may determine one or more RLC PDUs and / or RLC SDUs that have not been transmitted. Based on the indication from the receiving PDCP entity, the receiving RLC entity may determine one or more RLC PDUs and / or RLC SDUs that the receiving RLC entity does not need to wait for reception. Based on the indication from the receiving PDCP entity, the receiving RLC entity may update one or more local variables (e.g., one or more sequence numbers, once or multiple times).

[0266] Fig. 22 An exemplary embodiment of the present disclosure may be depicted.

[0267] In an example, when a transmitting PDCP entity receives a PDCP SDU (e.g., a packet), the transmitting PDCP entity may start a timer for the PDCP SDU. The timer may be associated with the discarding of the PDCP SDU. If the transmitting PDCP entity receives an indication that a PDCP PDU associated with the PDCP SDU is delivered, the transmitting PDCP entity may stop the timer. If the timer of the PDCP SDU expires, the transmitting PDCP entity may discard the PDCP SDU and / or the PDCP PDU associated with the PDCP SDU. If the timer of the PDCP SDU expires, the transmitting PDCP entity may instruct the transmitting RLC entity to discard the RLC SDU associated with the PDCP PDU. If the timer of the PDCP SDU expires, the transmitting PDCP entity may instruct the receiving PDCP entity that the transmission of the PDCP SDU has failed and / or stopped.

[0268] In an example, a transmitting PDCP entity may receive one or more PDCP SDUs. The one or more PDCP SDUs may include a first PDCP SDU and a second PDCP SDU. The transmitting PDCP entity may also receive one or more ADU information associated with the one or more PDCP SDUs. For example, the first ADU information associated with the first PDCP SDU may include information that the first ADU identifier associated with the first PDCP SDU may be 1. For example, the second ADU information associated with the second PDCP SDU may include information that the second ADU identifier associated with the second PDCP SDU may be 1. For the received first PDCP SDU, the transmitting PDCP entity may start a timer. The transmitting PDCP entity may deliver the first PDCP PDU associated with the first PDCP SDU to the transmitting RLC entity. The transmitting PDCP entity may not receive an indication that the first PDCP PDU is delivered. The timer of the first PDCP SDU may expire. If the timer of the PDCP SDU expires, the transmitting PDCP entity may determine to discard the PDCP SDU. For example, the transmitting PDCP entity may determine to discard the first PDCP SDU.

[0269] In an example, if the transmitting PDCP entity determines to discard the PDCP SDU and / or PDCP PDU, the following may be performed: Fig.17 , Fig.18 , Fig.19 , Fig. 20 , Fig.21For example, the transmitting PDCP entity may behave as if a PDCP SDU associated with an expiration timer (and / or a PDCP PDU associated with a PDCP PDU) may be indicated in the delivery information. For example, if a first timer of a first PDCP SDU expires, the transmitting PDCP entity may behave as if the first PDCP SDU and / or the first PDCP PDU is indicated by the delivery information from the RLC entity. For example, the delivery information may be a transmission failure / stop of the PDCP PDU. For example, Fig.17 , Fig.18 , Fig.19 , Fig. 20 , Fig.21 The behavior of the PDCP entity shown in the example may be triggered by the expiration of a timer rather than receiving delivery information from the RLC entity.

[0270] For example, the transmitting PDCP entity may determine ADU information associated with a PDCP SDU (e.g., a first PDCP SDU) for which a timer expires. The transmitting PDCP entity may determine ADU information associated with the PDCP SDU (e.g., an identity of the ADU). For example, the transmitting PDCP entity may determine that the identity of the ADU associated with the PDCP SDU is 1. Based on the identified ADU information associated with the PDCP SDU, the transmitting PDCP entity may further determine one or more PDCP SDUs (e.g., packets) associated with the ADU information. For example, based on the ADU information associated with the second packet, the transmitting PDCP entity may determine that the first packet (e.g., a first PDCP SDU) is associated with the second packet (e.g., a second PDCP SDU). Based on the determination, the transmitting PDCP entity may discard the second packet (e.g., the second PDCP SDU) and / or the second PDCP PDU.

[0271] In an example, a transmitting PDCP entity may send a PDCP status report (e.g., a PDCP control PDU, a PDCP sender report) to a receiving PDCP entity. The PDCP status report may include information that one or more PDCP SDUs (e.g., a first PDCP SDU) are discarded and / or not transmitted. For example, the PDCP status report may include information that the transmission of one or more PDCP SDUs (e.g., a first PDCP SDU) and / or one or more PDCP PDUs is stopped and / or aborted. For example, the PDCP status report may include information about one or more PDCP SDUs and / or one or more PDCP PDUs that the transmitting PDCP entity may or may not transmit. For example, the PDCP status report may include information about one or more PDCP PDUs / SDUs associated with one or more ADUs. For example, the PDCP status report may include information about sequence numbers from which the transmitting PDCP entity may transmit.

[0272] In an example, the transmitting PDCP entity may indicate to the transmitting RLC entity that the second PDCP PDU (second RLC SDU) needs to be discarded. For example, the transmitting PDCP entity may indicate to the transmitting RLC entity that the first RLC SDU needs to be discarded. For example, the PDCP entity may indicate to the transmitting RLC entity based on the ADU information that the transmitting RLC entity needs to discard one or more RLC SDUs. Based on the information of one or more RLC SDUs to be discarded, the transmitting RLC entity may send an RLC control PDU (e.g., RLC status PDU, RLC sender status report) to the receiving RLC entity. The RLC control PDU may include information about one or more RLC PDUs and / or one or more RLC SDUs that the transmitting RLC entity does not transmit and / or discards. The RLC control PDU may include information about one or more RLC PDUs and / or one or more RLC SDUs that the transmitting RLC entity stops transmitting. The RLC control PDU may include information about one or more RLC PDUs and / or one or more RLC SDUs that the transmitting RLC entity stops transmitting. The information about one or more RLC PDUs and / or one or more RLC SDUs may include one or more sequence numbers associated with the one or more RLC PDUs and / or one or more RLC SDUs. For example, based on an indication from a transmitting PDCP entity that a first RLC SDU needs to be discarded, the RLC control PDU may include information that a first RLC PDU and / or a first RLC SDU needs to be discarded.

[0273] Fig.23 An exemplary embodiment of the present disclosure may be depicted.

[0274] In an example, a first transport protocol entity (e.g., a PDCP entity, an RLC entity, an SDAP entity) may receive one or more packets (e.g., SDUs) from a higher layer (e.g., an SDAP entity, a PDCP entity, an IP entity, a TCP entity, etc.). The one or more packets may include at least one or more packet headers and / or one or more packet payloads. The one or more packet payloads may include one or more ADUs and / or one or more bytes of one or more ADUs and / or one or more SDUs (e.g., PDCP SDUs, SDAP SDUs, RLC SDUs). The one or more packets may include a first packet and / or a second packet and / or a third packet. When the first transport protocol entity receives the one or more packets, the first transport protocol entity may further receive one or more associated ADU information together with the one or more packets. The first transport protocol entity may receive a first packet with first associated ADU information. The first transport protocol entity may receive a second packet with second associated ADU information. The first transport protocol entity may receive a third packet with third associated ADU information. For example, the first associated ADU information may indicate that the identity of the ADU associated with the first packet is 1. For example, the second associated ADU information may indicate that the identity of the ADU associated with the second packet is 1. For example, the third associated ADU information may indicate that the identity of the ADU associated with the third packet is 2. For example, the one or more associated ADU information may indicate that the first packet and the second packet are associated. For example, the one or more associated ADU information may indicate that the first packet and the third packet are not associated.

[0275] In an example, a first transport protocol entity may process one or more received packets and / or one or more associated ADU information. After processing, the first transport protocol entity may form one or more PDUs (e.g., PDCP PDUs, RLC PDUs, SDAP PDUs). For example, one or more PDUs may include a first PDU and / or a second PDU and / or a third PDU. A first PDU (e.g., a first PDCP PDU) may include at least a portion of a first SDU (e.g., a first packet). A second PDU (e.g., a second PDCP PDU) may include at least a portion of a second SDU (e.g., a second packet). A third PDU (e.g., a third PDCP PDU) may include at least a portion of a third SDU (e.g., a third packet).

[0276] In an example, the transmitting PDCP entity may deliver one or more PDCP PDUs to a transmitting RLC entity. The transmitting PDCP entity may deliver one or more ADU information associated with the one or more PDCP PDUs. For example, the transmitting RLC entity may receive a first RLC SDU (e.g., a first PDCP PDU) having first ADU information. For example, the transmitting RLC entity may receive a second RLC SDU (e.g., a second PDCP PDU) having second ADU information. For example, the transmitting RLC entity may receive a third RLC SDU (e.g., a third PDCP PDU) having third ADU information. For example, the ADU information associated with the first RLC SDU and / or the second RLC SDU may indicate that the ADU identity is 1. For example, the ADU information associated with the third RLC SDU may indicate that the ADU identity is 2.

[0277] For a received first RLC SDU, the transmitting RLC entity may process the first RLC SDU and may construct one or more RLC PDUs (e.g., a first RLC PDU, RLC PDU 1). For a received second RLC SDU, the transmitting RLC entity may process the second RLC SDU and may construct one or more RLC PDUs (e.g., a second RLC PDU, RLC PDU 2). For a received third RLC SDU, the transmitting RLC entity may process the third RLC SDU and may construct one or more RLC PDUs (e.g., a third RLC PDU, RLC PDU 3). The transmitting RLC entity may transmit one or more RLC PDUs.

[0278] One or more RLC PDUs and / or one or more RLC SDUs sent by a transmitting RLC entity may be successfully delivered to a receiving RLC entity. One or more RLC PDUs and / or one or more RLC SDUs sent by the transmitting RLC entity may not be successfully delivered to the receiving RLC entity. For example, a first RLC PDU (e.g., a first RLC SDU, a first PDCP PDU) and / or a third RLC PDU (e.g., a third RLC SDU, a third PDCP PDU) may be successfully delivered to a receiving RLC entity. The receiving RLC entity may buffer one or more RLC PDUs and / or one or more RLC SDUs that are successfully received in a memory. One or more RLC SDUs may be delivered from the receiving RLC entity to the receiving PDCP entity. For example, a second RLC PDU and / or a second RLC SDU may not be successfully delivered to the receiving RLC entity. In order to deliver the second RLC SDU to the receiving RLC entity, the transmitting RLC entity may retransmit the second RLC PDU / SDU multiple times.

[0279] In an example, after several unsuccessful retransmission attempts to deliver the second RLC SDU to the receiving RLC entity, the transmitting RLC entity may determine that the transmission of the RLC SDU 2 and / or the RLC PDU 2 has failed. The determination of the transmission failure of the RLC SDU 2 and / or the RLC PDU 2 may be that the transmitting RLC entity stops the transmission of the RLC PDU 2 and / or the RLC SDU 2. The determination of the transmission failure of the RLC SDU 2 and / or the RLC PDU 2 may be that the transmitting RLC entity aborts the transmission of the RLC PDU 2 and / or the RLC SDU 2. The determination of the transmission failure of the RLC SDU 2 and / or the RLC PDU 2 may be a delivery failure of the RLC SDU 2 and / or the RLC SDU 2.

[0280] In an example, based on determining that the transmission of RLC SDU 2 and / or RLC PDU 2 has failed, the transmitting RLC entity may discard the RLC PDU and / or the RLC SDU associated with the RLC PDU. The transmitting RLC entity may determine ADU information associated with the discarded RLC SDU and / or the discarded RLC PDU. For example, based on the ADU information delivered together with the RLC SDU associated with the RLC PDU, the transmitting RLC entity may determine the ADU information. Based on the determined ADU information, the transmitting RLC entity may determine one or more RLC SDUs associated with the determined ADU information. For example, the ADU information of the discarded RLC SDU (e.g., the second RLC SDU) may indicate that the ADU identity of the discarded RLC SDU (e.g., the second RLC SDU) is 1. For example, the transmitting RLC entity may determine that the ADU identity of RLC SDU 1 is 1. Based on the determination of the ADU information of one or more RLC SDUs, the transmitting RLC entity may discard one or more RLC SDUs. For example, the transmitting RLC entity may further discard one or more RLC SDUs (e.g., RLC SDU 1) associated with the same ADU information as the discarded RLC SDU (e.g., RLC SDU 2). For example, the transmitting RLC entity may discard one or more RLC PDUs associated with the one or more discarded RLC SDUs. For example, the transmitting RLC entity may determine that the ADU identity of RLC SDU 3 is 2. Based on the determination of the ADU information of the one or more RLC SDUs, the transmitting RLC entity may not discard the one or more RLC SDUs. For example, the transmitting RLC entity may not discard one or more RLC SDUs (e.g., RLC SDU 3) associated with different ADU information from the discarded RLC SDU (e.g., RLC SDU 2). For example, the transmitting RLC entity may not discard one or more RLC PDUs associated with one or more non-discarded RLC SDUs.

[0281] In an example, for one or more discarded RLC SDUs and / or one or more discarded RLC PDUs, the transmitting RLC entity may send an RLC control PDU (e.g., an RLC status PDU, an RLC sender status report) to the receiving RLC entity. The RLC control PDU may include information about one or more RLC PDUs and / or one or more RLC SDUs that the transmitting RLC entity does not transmit and / or discards. The RLC control PDU may include information about one or more RLC PDUs and / or one or more RLC SDUs that the transmitting RLC entity stops transmitting. The RLC control PDU may include information about one or more RLC PDUs and / or one or more RLC SDUs that the transmitting RLC entity stops transmitting. The information about one or more RLC PDUs and / or one or more RLC SDUs may include one or more sequence numbers associated with the one or more RLC PDUs and / or one or more RLC SDUs. For example, based on the information about the discarded one or more RLC SDUs / PDUs, the RLC control PDU may include information about the need to discard the first RLC PDU and / or the first RLC SDU. For example, based on the information of the discarded one or more RLC SDU / PDUs, the RLC control PDU may include information that the second RLC PDU and / or the second RLC SDU need to be discarded. For example, based on the ADU information associated with the discarded one or more RLC SDU / PDUs, the RLC control PDU may include information of one or more ADUs associated with one or more RLC PDU / SDUs (e.g., the first RLC SDU, the second RLC SDU).

[0282] In an example, a receiving RLC entity may receive an RLC control PDU. Based on the received RLC control PDU, the receiving RLC entity may identify one or more RLC PDUs and / or one or more RLC SDUs that the transmitting RLC entity does not transmit and / or stops transmitting and / or suspends transmitting and / or discards. For example, for the identified one or more RLC PDUs and / or one or more RLC SDUs, the receiving RLC entity may behave as if one or more RLC PDUs and / or one or more RLC SDUs are received. The receiving RLC entity may behave as if one or more RLC PDUs and / or one or more RLC SDUs are received, which may be that the receiving RLC entity may not have any long wait / expectation for receiving one or more RLC PDUs / SDUs. For example, the receiving RLC entity may update local variables associated with the operation of the receiving RLC entity. For example, the receiving RLC entity may update local variables associated with one or more sequence numbers of the next expected RLC PDU / SDU and / or one or more sequence numbers of the confirmed RLC PDU / SDU and / or one or more sequence numbers associated with the receiving / receiving window / buffer. For example, for the identified one or more RLC PDUs and / or one or more RLC SDUs, the receiving RLC entity may determine one or more RLC PDUs and / or RLC SDUs associated with the identified one or more RLC PDUs and / or one or more RLC SDUs. The receiving RLC entity may discard the identified one or more RLC PDUs and / or one or more RLC SDUs. For example, the receiving RLC entity may discard the first RLC PDU and / or the first RLC SDU. For example, the receiving RLC entity may discard the second RLC PDU and / or the second RLC SDU. For example, for the identified one or more RLC PDUs and / or one or more RLC SDUs, the receiving RLC entity may indicate to the receiving PDCP entity the information of the identified one or more RLC PDUs and / or one or more RLC SDUs. The information may include one or more RLC SDUs being discarded and / or not transmitted and / or terminated. Based on the indication from the receiving RLC entity, the receiving PDCP entity may determine one or more PDCP PDUs / SDUs associated with the indicated one or more RLC SDUs. The receiving PDCP entity may discard the determined one or more PDCP PDUs.

[0283] Fig.24 An exemplary embodiment of the present disclosure may be depicted.

[0284] In an example, a first transport protocol entity (e.g., a PDCP entity, an RLC entity, an SDAP entity) may receive one or more packets (e.g., SDUs) from a higher layer (e.g., an SDAP entity, a PDCP entity, an IP entity, a TCP entity, etc.). The one or more packets may include at least one or more packet headers and / or one or more packet payloads. The one or more packet payloads may include one or more ADUs and / or one or more bytes of one or more ADUs and / or one or more SDUs (e.g., PDCP SDUs, SDAP SDUs, RLC SDUs). The one or more packets may include a first packet and / or a second packet and / or a third packet. When the first transport protocol entity receives the one or more packets, the first transport protocol entity may further receive one or more associated ADU information together with the one or more packets. The first transport protocol entity may receive a first packet with first associated ADU information. The first transport protocol entity may receive a second packet with second associated ADU information. The first transport protocol entity may receive a third packet with third associated ADU information. For example, the first associated ADU information may indicate that the identity of the ADU associated with the first packet is 1. For example, the second associated ADU information may indicate that the identity of the ADU associated with the second packet is 1. For example, the third associated ADU information may indicate that the identity of the ADU associated with the third packet is 2. For example, the one or more associated ADU information may indicate that the first packet and the second packet are associated. For example, the one or more associated ADU information may indicate that the first packet and the third packet are not associated.

[0285] In an example, a first transmission protocol entity may process one or more received packets and / or one or more associated ADU information. After processing, the first transmission protocol entity may form one or more PDUs (e.g., PDCP PDU, RLC PDU, SDAP PDU). For example, one or more PDUs may include a first PDCP PDU and / or a second PDCP PDU and / or a third PDCP PDU. A first PDU (e.g., a first PDCP PDU) may include at least a portion of a first SDU (e.g., a first packet). A second PDU (e.g., a second PDCP PDU) may include at least a portion of a second SDU (e.g., a second packet). A third PDU (e.g., a third PDCP PDU) may include at least a portion of a third SDU (e.g., a third packet). For example, one or more PDUs may include one or more ADU information. A first PDU (e.g., a first PDCP PDU) may include a first SDU (e.g., a first packet, a first PDCP SDU) and / or first ADU information. A second PDU (e.g., a second PDCP PDU) may include a second SDU (e.g., a second packet, a second PDCP SDU) and / or second ADU information. The third PDU (e.g., a third PDCP PDU) may include a third SDU (e.g., a third packet, a third PDCP SDU) and / or third ADU information. For example, the first ADU information and / or the second ADU information may indicate that the associated ADU identity is 1. For example, the third ADU information may indicate that the associated ADU identity is 2.

[0286] In an example, a transmitting PDCP entity may deliver one or more PDCP PDUs to a transmitting RLC entity. The transmitting PDCP entity may deliver one or more ADU information associated with the one or more PDCP PDUs. For example, a transmitting RLC entity may receive a first RLC SDU (e.g., a first PDCP PDU) having first ADU information. For example, a transmitting RLC entity may receive a second RLC SDU (e.g., a second PDCP PDU) having second ADU information. For example, a transmitting RLC entity may receive a third RLC SDU (e.g., a third PDCP PDU) having third ADU information. For example, the ADU information associated with the first RLC SDU and / or the second RLC SDU may indicate that the ADU identity is 1. For example, the ADU information associated with the third RLC SDU may indicate that the ADU identity is 2.

[0287] In an example, for a received first RLC SDU, the transmission RLC entity may process the first RLC SDU and may construct one or more RLC PDUs (e.g., a first RLC PDU). For a received second RLC SDU, the transmission RLC entity may process the second RLC SDU and may construct one or more RLC PDUs (e.g., a second RLC PDU). For a received third RLC SDU, the transmission RLC entity may process the third RLC SDU and may construct one or more RLC PDUs (e.g., a third RLC PDU). One or more RLC PDUs may include one or more ADU information associated with one or more RLC PDUs / SDUs. For example, the first RLC PDU may include ADU information associated with the first RLC SDU. For example, the second RLC PDU may include ADU information associated with the second RLC SDU. For example, the third RLC PDU may include ADU information associated with the third RLC SDU. The transmission RLC entity may transmit one or more RLC PDUs.

[0288] In an example, one or more RLC PDUs sent by a transmitting RLC entity may be successfully delivered to a receiving RLC entity. One or more RLC PDUs sent by a transmitting RLC entity may not be successfully delivered to the receiving RLC entity. For example, a first RLC PDU may be successfully delivered to a receiving RLC entity. The receiving RLC entity may buffer one or more RLC PDUs and / or one or more RLC SDUs that are successfully received in a memory. One or more RLC SDUs may be delivered to a receiving PDCP entity. For example, a second RLC PDU, a second RLC SDU may not be successfully delivered to a receiving RLC entity. In order to deliver a second RLC PDU and / or a second RLC SDU to the receiving RLC entity, the transmitting RLC entity may retransmit a second RLC PDU and / or a second RLC SDU multiple times.

[0289] In an example, a receiving RLC entity may receive one or more RLC PDUs and / or one or more RLC SDUs. For example, the receiving RLC entity may receive a first RLC PDU and / or a third RLC PDU. The receiving RLC entity may not receive one or more RLC PDUs and / or one or more RLC SDUs. For example, the receiving RLC entity may not receive a second RLC PDU. Based on the received one or more RLC PDUs and / or one or more RLC SDUs, the receiving RLC entity may identify one or more lost RLC PDUs and / or one or more RLC SDUs. For example, based on one or more sequence numbers of the one or more RLC PDUs and / or one or more RLC SDUs, the receiving RLC entity may determine that one or more lost RLC PDUs. For example, based on the sequence numbers of the received first RLC PDU (e.g., 1) and the third RLC PDU (e.g., 3), the receiving RLC entity may determine that the second RLC PDU (e.g., 2) is lost. For one or more unreceived RLC PDUs / SDUs, the receiving RLC entity may determine ADU information associated with the lost one or more RLC PDUs / SDUs. For the determined ADU information, the receiving RLC entity may discard one or more RLC PDUs / SDUs associated with the ADU information. For example, the receiving RLC entity may determine that the ADU information associated with the lost RLC PDU (e.g., RLC PDU 2) is 1. Based on the identified ADU information and the ADU information of one or more received RLC PDUs / SDUs, the receiving RLC entity may determine that the first RLC PDU / SDU is associated with the same ADU information. Based on the determination, the receiving RLC entity may discard the first RLC PDU / SDU.

[0290] In other examples, one or more PDCP PDUs may include one or more ADU information. One or more PDCP PDUs may include one or more ADU information associated with the PDCP PDU. For example, a first PDCP PDU may include a first PDCP SDU and / or a first ADU information. For example, a second PDCP PDU may include a second PDCP SDU and / or a second ADU information. For example, a third PDCP PDU may include a third PDCP SDU and / or a third ADU information. Based on one or more ADU information of one or more PDCP PDUs, the receiving PDCP entity may determine one or more PDCP PDUs associated with the ADU information of the lost one or more PDCP PDUs. The receiving PDCP entity may discard the determined one or more associated PDCP PDUs / SDUs. This PDCP entity operation may be similar to the operation of the RLC entity, as shown in the previously described example.

[0291] Fig.25 An exemplary embodiment of the present disclosure may be depicted.

[0292] In an example, a first transport protocol entity (e.g., a PDCP entity, an RLC entity, an SDAP entity) may receive one or more packets (e.g., SDUs) from a higher layer (e.g., an SDAP entity, a PDCP entity, an IP entity, a TCP entity, etc.). The one or more packets may include at least one or more packet headers and / or one or more packet payloads. The one or more packet payloads may include one or more ADUs and / or one or more bytes of one or more ADUs and / or one or more SDUs (e.g., PDCP SDUs, SDAP SDUs, RLC SDUs). The one or more packets may include a first packet and / or a second packet and / or a third packet. When the first transport protocol entity receives the one or more packets, the first transport protocol entity may further receive one or more associated ADU information together with the one or more packets. The first transport protocol entity may receive a first packet with first associated ADU information. The first transport protocol entity may receive a second packet with second associated ADU information. The first transport protocol entity may receive a third packet with third associated ADU information. For example, the first associated ADU information may indicate that the identity of the ADU associated with the first packet is 1. For example, the second associated ADU information may indicate that the identity of the ADU associated with the second packet is 1. For example, the third associated ADU information may indicate that the identity of the ADU associated with the third packet is 2. For example, the one or more associated ADU information may indicate that the first packet and the second packet are associated. For example, the one or more associated ADU information may indicate that the first packet and the third packet are not associated.

[0293] In an example, a first transport protocol entity may process one or more received packets and / or one or more associated ADU information. After processing, the first transport protocol entity may form one or more PDUs (e.g., PDCP PDUs, RLC PDUs, SDAP PDUs). For example, one or more PDUs may include a first PDU and / or a second PDU and / or a third PDU. A first PDU (e.g., a first PDCP PDU) may include at least a portion of a first SDU (e.g., a first packet). A second PDU (e.g., a second PDCP PDU) may include at least a portion of a second SDU (e.g., a second packet). A third PDU (e.g., a third PDCP PDU) may include at least a portion of a third SDU (e.g., a third packet).

[0294] In an example, a transmitting PDCP entity may deliver one or more PDCP PDUs to a transmitting RLC entity. The transmitting PDCP entity may deliver one or more ADU information associated with the one or more PDCP PDUs. For example, a transmitting RLC entity may receive a first RLC SDU (e.g., a first PDCP PDU) having first ADU information. For example, a transmitting RLC entity may receive a second RLC SDU (e.g., a second PDCP PDU) having second ADU information. For example, a transmitting RLC entity may receive a third RLC SDU (e.g., a third PDCP PDU) having third ADU information. For example, the ADU information associated with the first RLC SDU and / or the second RLC SDU may indicate that the ADU identity is 1. For example, the ADU information associated with the third RLC SDU may indicate that the ADU identity is 2.

[0295] In an example, for a received first RLC SDU, the transmitting RLC entity may process the first RLC SDU and may construct one or more RLC PDUs (e.g., a first RLC PDU). For a received second RLC SDU, the transmitting RLC entity may process the second RLC SDU and may construct one or more RLC PDUs (e.g., a second RLC PDU). For a received third RLC SDU, the transmitting RLC entity may process the third RLC SDU and may construct one or more RLC PDUs.

[0296] In an example, a transmitting RLC entity may deliver one or more RLC PDUs (e.g., one or more MAC SDUs) to a transmitting MAC entity. The transmitting MAC entity may construct one or more MAC PDUs, including one or more MAC SDUs. One or more MAC SDUs may include an RLC PDU. The transmitting MAC entity may allocate one or more MAC PDUs to one or more HARQ processes. One or more HARQ processes may perform transmission and / or retransmission to deliver one or more MAC PDUs to a receiving MAC entity. For example, one or more MAC PDUs may include a first MAC PDU and / or a second MAC PDU. The first MAC PDU may include a first RLC PDU (e.g., a first MAC SDU). The second MAC PDU may include a second RLC PDU (e.g., a second MAC SDU). One or more HARQ processes may include a first HARQ process and / or a second HARQ process. The first HARQ process may transmit a first MAC PDU. The second HARQ process may transmit a second MAC PDU.

[0297] In an example, a first HARQ process of a transmitting MAC entity may fail to deliver a first MAC PDU to a receiving MAC entity. The transmitting MAC entity may report a transmission failure of a MAC SDU (e.g., a first RLC PDU) to a transmitting RLC entity. The transmitting RLC entity may determine that the transmission of the first RLC PDU has failed. For example, if the transmission of the first RLC PDU fails multiple times, the transmitting RLC entity may determine that the transmission of the first RLC PDU has failed. Based on the determination of the transmission failure of the RLC PDU, the transmitting RLC entity may discard the first RLC PDU and / or the first RLC SDU. Based on the determination of the transmission failure of the RLC PDU / SDU, the transmitting RLC entity may identify ADU information associated with the first RLC PDU and / or the first RLC SDU. Based on the identified ADU information, the transmitting RLC entity may determine one or more RLC SDUs and / or one or more RLC PDUs associated with the identified ADU information. For example, based on the ADU information associated with the first RLC PDU / SDU and the ADU information associated with the second RLC PDU / SDU, the transmitting RLC entity may determine that the first RLC PDU and / or the first RLC SDU are associated. For example, based on the determination, the transmitting RLC entity may determine to discard the second RLC SDU / PDU and / or stop transmission of the second RLC SDU / PDU.

[0298] In an example, based on ADU information of one or more RLC PDUs and / or one or more RLC SDUs, the transmitting RLC entity may indicate to the transmitting MAC entity information of one or more RLC PDUs (e.g., one or more MAC SDUs) to be discarded and / or suspended. Based on the information delivered from the transmitting RLC entity, the transmitting MAC entity may determine one or more associated HARQ processes. For example, the transmitting RLC entity may indicate to the transmitting MAC entity that a second RLC PDU (e.g., a second MAC SDU) needs to be discarded. Based on the fact that the second MAC SDU is transmitted via a second HARQ process, the transmitting MAC entity may terminate and / or suspend transmission via the second HARQ process.

[0299] Fig.26 An exemplary embodiment of the present disclosure may be depicted.

[0300] In an example, a transport entity (e.g., a PDCP entity, an RLC entity, an SDAP entity, a MAC entity) may receive one or more service data units (e.g., SDU, PDCP SDU, RLC SDU, SDAP SDU, MAC SDU) from an upper layer / entity (e.g., an application layer, an intermediate layer, an SDAP entity, a PDCP entity, an RLC entity, an SDAP entity, a MAC entity). The transport entity may process one or more received service data units. The transport entity may construct one or more protocol data units (e.g., PDU, PDCP PDU, RLC PDU, SDAP PDU, MAC PDU) based on the one or more service data units. The transport entity may send one or more protocol data units and / or may deliver one or more protocol data units to a lower layer (e.g., an RLC entity, a MAC entity, a PDCP entity, a PHY entity).

[0301] In an example, the transmission entity may determine not to send or resend one or more protocol data units and / or one or more service data units. The transmission entity may determine to suspend or stop the transmission of one or more protocol data units and / or one or more service data units. The determination may be based on the number of attempted transmissions of the protocol data unit and / or service data unit exceeding a threshold value (e.g., 3 times, 4 times, etc.). The determination may be based on the time that has passed since the availability of the service data unit and / or protocol data unit exceeded a threshold value (e.g., 1 second, 5 seconds, etc.). The determination may be based on an upper layer requesting to discard the service data unit and / or protocol data unit.

[0302] In an example, based on the determination, the transmitting entity may send a sender status report (e.g., a control protocol data unit) to the receiving entity. The sender status report may include information about one or more service data units and / or one or more protocol data units that the transmitting entity stopped and / or suspended transmission and / or discarded.

[0303] Fig. 27 An exemplary embodiment of the present disclosure may be depicted.

[0304] In an example, a transport entity (e.g., a PDCP entity, an RLC entity, an SDAP entity, a MAC entity) may receive one or more service data units (e.g., SDU, PDCP SDU, RLC SDU, SDAP SDU, MAC SDU) from an upper layer / entity (e.g., an application layer, an intermediate layer, an SDAP layer, a PDCP entity, an RLC entity, an SDAP entity, a MAC entity). The transport entity may receive one or more ADU information associated with the one or more service data units.

[0305] The transport entity may process one or more received service data units. The transport entity may construct one or more protocol data units (e.g., PDU, PDCP PDU, RLC PDU, SDAPPDU, MAC PDU) based on one or more service data units. The transport entity may send one or more protocol data units and / or may deliver one or more protocol data units to a lower layer (e.g., RLC entity, MAC entity, PDCP entity, PHY entity).

[0306] In an example, the transmission entity may determine not to send or resend one or more protocol data units and / or one or more service data units. The transmission entity may determine to suspend or stop the transmission of one or more protocol data units and / or one or more service data units. The determination may be based on the number of attempted transmissions of the protocol data unit and / or service data unit exceeding a threshold value (e.g., 3 times, 4 times, etc.). The determination may be based on the time that has passed since the availability of the service data unit and / or protocol data unit exceeded a threshold value (e.g., 1 second, 5 seconds, etc.). The determination may be based on an upper layer requesting to discard the service data unit and / or protocol data unit.

[0307] In an example, for one or more service data units and / or one or more protocol data units (e.g., a first group of units) to be discarded, the transmission entity may identify the associated ADU information of the one or more service data units and / or one or more protocol data units. Based on the ADU information, the transmission entity may determine one or more protocol data units and / or one or more protocol data units (e.g., a second group of units) associated with the one or more protocol data units (e.g., a first group of units) to be discarded. For example, the one or more protocol data units to be discarded (e.g., a first group of units) may include a first service data unit. For example, the first service data unit may be associated with the first ADU information. The first ADU information may indicate that the ADU identity is 1. For example, the second service data unit may be associated with the second ADU information. The second ADU information may indicate that the ADU identity is 1. For example, the third service data unit may be associated with the third ADU information. The third ADU information may indicate that the ADU identity is 2. Based on the one or more ADU information of the one or more service data units, the transmission entity may determine that the second service data unit may be associated with the first service data unit. Based on the determination, the transmission entity may discard the second service data unit.

[0308] In an example, based on the determination, the transmitting entity may send a sender status report (e.g., a control protocol data unit) to the receiving entity. The sender status report may include information about one or more service data units and / or one or more protocol data units that the transmitting entity stopped and / or suspended transmission and / or discarded.

[0309] In an example, a first transport protocol entity (e.g., a PDCP entity, an RLC entity, an SDAP entity) may receive one or more packets (e.g., SDUs) from a higher layer (e.g., an SDAP entity, a PDCP entity, an IP entity, a TCP entity, etc.). The one or more packets may include at least one or more packet headers and / or one or more packet payloads. The one or more packet payloads may include one or more ADUs and / or one or more ADUs and / or one or more bytes of one or more SDUs (e.g., PDCP SDUs, SDAP SDUs, RLC SDUs). The one or more packets may include a first packet and / or a second packet and / or a third packet.

[0310] In an example, a fourth entity (e.g., an RRC entity) may configure the first transmission protocol entity with conditional information. Based on the conditional information, the first transmission protocol entity may identify one or more associated ADU information having one or more packets. The conditional information may include information on how to identify one or more SDUs associated with the same ADU. The conditional information may include information on how to identify one or more SDUs associated with different ADUs. The conditional information may include information on how to identify ADU information associated with an SDU. For example, the conditional information may indicate one or more fields. For example, the one or more fields may include at least one of the following: one or more fields of an application data unit (ADU), one or more fields of an IP packet, one or more fields of an RTP packet, one or more fields of a UDP packet, one or more fields of a TCP packet, one or more fields of an HTTP packet, a timestamp field, a DSCP field, and the like.

[0311] In an example, when the first transmission protocol entity receives one or more packets based on conditional information, the first transmission protocol entity may identify one or more associated ADU information with the one or more packets. For example, when the first transmission protocol entity receives one or more packets based on conditional information, the first transmission protocol entity may identify one or more packets associated with the same ADU. For example, the conditional information may indicate a timestamp field. The timestamp field of the first packet may be 1. The timestamp field of the second packet may be 1. The timestamp field of the third packet may be 2. Based on the conditional information and the one or more packets, the first transmission protocol entity may determine that the first packet and the second packet are associated with the same ADU. Based on the conditional information and the one or more packets, the first transmission protocol entity may determine that the first packet and the third packet are not associated with the same ADU. Based on the conditional information and the one or more packets, the first transmission protocol entity may determine that the associated ADU information of the first packet is 1. Based on the conditional information and the one or more packets, the first transmission protocol entity may determine that the associated ADU information of the second packet is 1. Based on the conditional information and the one or more packets, the first transmission protocol entity may determine that the associated ADU information of the third packet is 2. Based on the determination, the first transmission protocol entity may generate the first associated ADU information of the first packet. Based on the determination, the first transmission protocol entity may generate second associated ADU information for the second packet.Based on the determination, the first transmission protocol entity may generate third associated ADU information for the third packet.

[0312] In the example, Figures 17 to 25 In the example of , instead of receiving one or more packets having one or more associated ADU information, the first transmission protocol entity may determine one or more associated ADU information of the one or more packets, as described above.

[0313] In an example, a first entity (e.g., a PDCP entity) may receive one or more service data units (SDUs, e.g., PDCP SDUs) from a third entity (e.g., an upper layer, an SDAP entity, a protocol entity). For example, the one or more SDUs may include a first SDU. The first entity may generate one or more protocol data units (PDUs, e.g., PDCP PDUs) based on the one or more SDUs. For example, based on the first SDU, the first entity may generate a first PDU. The first PDU may include the first SDU. The first entity may send the first PDU. For example, a first entity of a first network node (e.g., a first device, a UE, a NG-RAN) may send the first PDU to a first entity of a second network node (e.g., a second device, a NG-RAN, a UE). For example, the first entity may send the first PDU to a second entity (e.g., an RLC entity, a MAC entity, a PDCP entity, a PHY entity, a SDAP entity) to request delivery of the first PDU.

[0314] In an example, a first entity may determine that a delivery of a first PDU has failed. The delivery failure of the first PDU may be interpreted as a delivery failure of the first SDU. For example, if the first PDU is not successfully delivered within a threshold (e.g., a configured amount of time), the first entity may determine that a delivery of the first PDU has failed. For example, a second entity may perform a transmission of the first PDU. If the second entity fails in transmitting the first PDU, the second entity may indicate to the first entity the delivery failure of the first PDU. If the second entity does not receive an acknowledgment of the first PDU from a recipient (e.g., a second entity of a second network node), the second entity may indicate to the first entity the delivery failure of the first PDU.

[0315] In an example, if the first SDU is not successfully delivered within a threshold (e.g., a configured amount of time), the first entity may determine that delivery of the first PDU has failed. When receiving the first SDU from the third entity, the first entity may start a timer with a configured amount of time for the first SDU. If the timer expires, the first entity may determine that delivery of the first PDU has failed. If the first entity receives an indication that the first SDU and / or the first PDU was successfully delivered, the first entity may stop the timer for the first SDU.

[0316] For example, if the number of transmissions of the first PDU reaches a threshold (eg, a configured number), the second entity may determine that the delivery of the first PDU has failed. Based on the determination, the second entity may indicate to the first entity that the delivery of the first PDU has failed.

[0317] The first entity may discard the first SDU and / or the first PDU that failed to be delivered based on the determination of the delivery failure of the first PDU. If the first entity does not determine the delivery failure of the first PDU, the first entity may not discard the first PDU and / or the first SDU. If the first entity determines to discard the first SDU and / or the first PDU, the first entity may remove the first SDU and / or the first PDU from its memory.

[0318] In an example, based on the determination of the delivery failure of the first PDU, the first entity may send an indication to discard the first SDU and / or an indication to stop the transmission of the first SDU to the first entity of the second network node. For example, the first entity of the first network node may send an indication to discard the first SDU (e.g., information of the delivery failure of the first SDU, information that the first SDU was not transmitted, information that the transmission of the first SDU was stopped) to the first entity of the second network node. For example, the indication to discard the first SDU may include a status report (e.g., a PDCP status report) and / or a control PDU (e.g., a PDCP control PDU) and / or the like. For example, the indication to discard the first SDU may include identification information of the first SDU and / or the first PDU. For example, the identification information of the first SDU and / or the first PDU may include one or more sequence numbers and / or identity information of the first SDU and / or the first PDU. For example, the indication to discard the first SDU may include:

[0319] - Information that the first entity stops / suspends transmission of the first SDU and / or the first PDU.

[0320] -Information that the first SDU and / or the first PDU needs to be discarded.

[0321] - The first entity may not transmit information of the first SDU and / or the first PDU.

[0322] In an example, the first entity may receive configuration information from a fourth entity (e.g., a radio resource control entity) regarding whether to send an indication to discard the first SDU. For example, if the configuration information indicates that the first entity sends an indication to discard the first SDU, the first entity may send an indication to discard the first SDU. For example, if the configuration information does not indicate that the first entity sends an indication to discard the first SDU, the first entity may not send an indication to discard the first SDU. For example, the configuration information may also include information about one or more parameters associated with determining a delivery failure. For example, the configuration information may include one or more thresholds for one or more parameters (e.g., a configured number, a number of retransmissions of one or more SDUs, a timer value).

[0323] In an example, the first entity of the first network node may receive a response to the indication to discard the first SDU from the second network node. For example, the response may include at least one of: confirming receipt of the indication to discard the first SDU, and / or discarding the first SDU, and / or discarding the first PDU, and / or updating parameters (e.g., receiving window, local variables).

[0324] In an example, the first PDU may include information identifying a first SDU associated with the first PDU. For example, the first PDU may include one or more sequence numbers and / or one or more identity information associated with the first SDU.

[0325] In an example, a first entity (e.g., a radio link control entity, an RLC entity) of a first device (e.g., a UE, an NG-RAN) may receive a service data unit (SDU) from a third entity (e.g., a packet data convergence protocol entity, a PDCP entity) of the first device. The first entity may segment (e.g., format) the SDU into a plurality of protocol data units (PDUs). The plurality of PDUs may include at least one first PDU and at least one second PDU. The first entity may send at least one first PDU to a second device (e.g., an NG-RAN, a UE). The first entity may determine to discard the SDU based on a delivery failure of at least one second PDU or at least one of the SDUs. Based on the determination, the first entity of the first device may send an indication to discard at least one first PDU or at least one of the SDUs to the first entity of the second device. In an example, the delivery failure may be determined based on at least one second PDU not being transmitted within a configured amount of time. In an example, the delivery failure may be determined based on at least one second PDU being transmitted a configured number of times and the first entity not receiving an acknowledgment. In an example, the delivery failure may be determined based on the number of transmissions made for the SDU reaching a configured number. In an example, a delivery failure may be determined based on a sum of the number of transmissions for at least one first PDU and at least one second PDU reaching a configured number. In an example, based on the indication, the first entity of the second device may discard at least one first PDU and / or at least one second PDU and / or SDU. In an example, based on the indication, the first entity of the second device may update one or more local variables and / or one or more timers.

[0326] In an example, a first entity (e.g., an RLC entity, a PDCP entity, an SDAP entity) of a first device (e.g., a UE, a NG-RAN) may receive a service data unit (SDU) from a third entity (e.g., a PDCP entity, an SDAP entity, an upper layer) of the first device. The first entity may segment the SDU into a plurality of protocol data units (PDUs). The plurality of PDUs may include at least one first PDU and at least one second PDU. The first entity may send at least one first PDU to a second device (e.g., a NG-RAN, a UE). The first entity may determine to discard the SDU based on a delivery failure of at least the second PDU. Based on the determination, the first entity may send an indication to the second device to discard at least one of the first PDUs or the SDUs.

[0327] In an example, a receiving protocol entity (e.g., a PDCP entity, an RLC entity) of a first network node (e.g., a UE, a NG-RAN) may receive one or more protocol data units (PDUs) from a transmission protocol entity (e.g., a PDCP entity, an RLC entity) of a second network node (e.g., a NG-RAN, a UE). The one or more PDUs may be associated with one or more service data units (SDUs). The receiving protocol entity may receive sender state information (e.g., a control PDU, a status report, a status PDU) from the transmission protocol entity. The sender state information may include information of one or more SDUs discarded at the transmission protocol entity. The receiving protocol entity may process one or more received PDUs and / or one or more received SDUs based on the sender state information. For example, the receiving protocol entity may discard one or more received PDUs and / or one or more received SDUs based on the sender state information.

[0328] In an example, a first entity of a first network node may receive a service data unit (SDU) from a second entity. The first entity may compose one or more protocol data units (PDUs) based on the received SDU. The first entity may send one or more PDUs to a third entity. The first entity may determine that it stops transmission of the SDU. Based on the determination, the first entity may send information of the SDU to a peer entity (e.g., a second network node).

[0329] In an example, a first entity (e.g., a PDCP entity, an RLC entity, an SDAP entity, an application, a protocol entity, a MAC entity, a PHY entity) of a first network node (e.g., a UE, a NG-RAN) may receive a first service data unit (SDU, SDAP SDU, PDCP SDU, RLC SDU, MAC SDU, PHY SDU, ADU (e.g., IP packet, RTP packet, TCP packet, UDP packet, or application data)) from a third entity (e.g., an upper layer, an application, a protocol entity of the first network node). The first entity may generate at least one first protocol data unit (PDU, SDAP PDU, PDCP PDU, RLC PDU, MAC PDU, PHY PDU) using the first SDU. The first entity may transmit at least one first PDU.

[0330] In an example, the first entity may determine that the delivery of the first SDU has failed. For example, the first entity may receive an indication of a delivery failure of the first SDU and / or at least one PDU associated with the first SDU from a second entity (e.g., an RLC entity, a PDCP entity, an SDAP entity, an application, a protocol entity, a MAC entity, a PHY entity). For example, if the number of transmissions of at least one PDU reaches a threshold, the second entity may send a delivery failure of at least one PDU to the first entity. Based on the indication of the delivery failure of at least one PDU, the first entity may determine that the delivery of the first SDU has failed. For example, the first entity may start a timer when it receives the first SDU. If the timer expires, the first entity may determine that the delivery of the first SDU has failed. If the first entity receives an indication that the SDU was successfully delivered, the first entity may stop the timer. The configured value of the timer may be indicated by a fourth entity.

[0331] In an example, the first entity may receive a second SDU from a third entity. The first entity may generate at least one second PDU using the second SDU. The first entity may transmit at least one second PDU. A combination of the first SDU and / or the second SDU may include a first ADU.

[0332] In an example, based on the determination of the delivery failure of the first SDU, the first entity may determine to discard the first SDU. In an example, the first entity may identify a second SDU associated with the first SDU. For example, based on one or more ADU information associated with one or more SDUs, the first entity may identify a second SDU associated with the first SDU. For example, if the associated ADU information of the first SDU and / or the associated ADU information of the second SDU match, the first entity may determine that the second SDU is associated with the first SDU. For example, the third entity may deliver one or more SDUs and / or one or more ADU information associated with one or more SDUs to the first entity. For example, if a condition is met, the first SDU and the second SDU may be associated. The first entity may determine whether the condition is met. For example, the condition may be that one or more fields of the first SDU match one or more fields of the second SDU. For example, the condition may be that the identification information of the ADU associated with the first SDU matches the identification information of the ADU associated with the second SDU. The first SDU and the second SDU may include a service data stream. The service data stream may be identified by a source address and / or a destination address. A fourth entity (e.g., an RRC entity) may configure the first entity with information of one or more fields. For example, the one or more fields may include at least one of the following: one or more fields of an application data unit (ADU), one or more fields of an IP packet, one or more fields of an RTP packet, one or more fields of a UDP packet, one or more fields of a TCP packet, one or more fields of an HTTP packet, a timestamp field, a DSCP field. For example, the one or more fields may include one or more fields of one or more SDUs.

[0333] Based on the determination, the first entity may determine to discard the second SDU.

[0334] In an example, if the second SDU and the first SDU are determined to be associated, the first entity may send information about the second SDU. For example, the first entity of the first network node may send information about the second SDU to the first entity of the second network node (e.g., NG-RAN, UE). For example, the information about the second SDU may indicate that the first network node may not transmit the second SDU and / or at least one PDU associated with the second SDU. For example, the information about the second SDU may indicate that the second SDU and / or at least one PDU associated with the second SDU is discarded and / or the second SDU and / or at least one PDU associated with the second SDU needs to be discarded. The information about the second SDU may also include information about the first SDU. The information about the first SDU may indicate that the first network node may not transmit the first SDU and / or at least one PDU associated with the first SDU. The information about the first SDU may indicate that the first SDU and / or at least one PDU associated with the first SDU is discarded. The information about the first SDU may indicate that the first SDU and / or at least one PDU associated with the first SDU is discarded. The information about the first SDU may indicate that the first SDU and / or at least one PDU associated with the first SDU needs to be discarded. For example, the information of the second SDU may include a status report (e.g., a PDCP status report, an RLC status report, an SDAP status report) and / or a control PDU (e.g., a PDCP control PDU, an RLC control PDU, a MAC control element) and / or the like.

[0335] In other examples, if the second SDU and the first SDU are determined to be unassociated, the first entity may not send information of the second SDU.

[0336] In an example, if the second SDU is discarded, the first entity may send an indication to the second entity to discard at least one PDU associated with the second SDU. In an example, if the first SDU is discarded, the first entity may send an indication to the second entity to discard at least one PDU associated with the first SDU.

[0337] In an example, the first entity may receive a response to the information of the second SDU.

[0338] In an example, a receiving protocol entity (e.g., PDCP, RLC) may receive one or more protocol data units (PDUs) from a transmitting protocol entity. The one or more PDUs may be associated with a first service data unit (SDU). The receiving protocol entity may receive information from the transmitting protocol entity that the first SDU is discarded. Based on the information that the first SDU is discarded, the receiving protocol entity may update one or more parameters of the receiving entity. The one or more parameters include at least one of a receiving window (e.g., a sequence number of the receiving window, a sequence number of the next data) or one or more timers (e.g., stopping one or more timers, starting one or more timers).

[0339] In an example, a transport protocol entity of a first network node may receive one or more service data units (SDUs) from an upper layer. The transport protocol entity may determine one or more SDU identification information of the one or more SDUs. The transport protocol entity may generate one or more protocol data units (PDUs) using the one or more SDUs. The one or more PDUs may include at least the one or more SDU identification information. The transport protocol entity may send the one or more PDUs.

[0340] In an example, a receiving protocol entity may receive one or more protocol data units (PDUs). The one or more PDUs may include one or more service data unit (SDU) identification information and one or more SDUs. Based on the one or more received PDUs and the one or more SDU identification information, the receiving protocol entity may determine that the one or more SDUs were not successfully received. The receiving protocol entity may determine one or more PDUs associated with the one or more SDUs that were not successfully received. Based on the determination, the receiving protocol entity may discard the determined one or more associated PDUs.

Claims

1. A method, comprising: transmitting, by the first device to the second device, a plurality of packets associated with the data units of the data stream; determining, by the first device, that transmission of at least one packet of the plurality of packets has failed; The first device discards the plurality of packets based on: said transmission of said at least one packet fails; and The plurality of packets are associated with the data unit; as well as An indication that the plurality of packets are discarded is sent by the first device to the second device.

2. A method comprising: discarding, by the first device, a plurality of packets associated with a data unit of the data flow based on a transmission failure of at least one packet of the plurality of packets; as well as An indication that the plurality of packets are discarded is sent by the first device. 3 . The method of claim 2 , further comprising transmitting, by the first device to a second device, the plurality of packets associated with the data units of the data stream. The method of claim 3 , wherein the first device comprises a first wireless device and the second device comprises a second wireless device. 5 . The method of claim 3 , wherein the first device comprises a first entity of a first wireless device and the second device comprises a second entity of the first wireless device.

6. The method of claim 5, wherein the first entity or the second entity comprises at least one of: Packet Data Convergence Protocol (PDCP) layer; or Radio Link Control (RLC) layer.

7. The method of claim 5, wherein the data unit comprises a service data unit (SDU).

8. The method of claim 5, further comprising segmenting, by the first entity, the SDU into a plurality of protocol data units (PDUs), the plurality of protocol data units comprising at least one first PDU and at least one second PDU.

9. The method of claim 8, wherein the discarding comprises discarding, by the first entity, the SDU based on the transmission failure of the at least one second PDU.

10. The method according to any one of claims 2 to 9, further comprising determining, by the first device, that transmission of at least one packet of the plurality of packets has failed.

11. The method of claim 10, wherein the first device determines the transmission failure based on expiration of a duration associated with the at least one packet.

12. The method of claim 11, wherein the first device: When the at least one packet is received, starting the duration associated with the packet; and When the first device receives an indication that the at least one packet is received by the second device, the duration associated with the at least one packet is stopped.

13. The method of any one of claims 3 to 12, wherein the indication that the plurality of packets are dropped is sent via at least one of: Packet Data Convergence Protocol (PDCP) status report; or PDCP control protocol data unit.

14. The method according to any one of claims 3 to 13, wherein the indication that the plurality of packets are discarded comprises information indicating that the second device needs to discard each packet of the plurality of packets.

15. The method according to any one of claims 3 to 14, further comprising receiving, by the first device from the second device, configuration information on whether to send the indication that the plurality of packets are discarded.

16. The method according to any one of claims 2 to 15, wherein the first device receives the plurality of packets from an application.

17. The method according to any one of claims 2 to 16, further comprising receiving, by the first device, at least one of: an acknowledgement of said indication that said plurality of packets were discarded; an indication that the plurality of packets are discarded; or Updated parameters.

18. The method of any one of claims 2 to 16, further comprising removing, by the first device based on determining to discard the plurality of packets, the data units from a memory of the first device.

19. A first device comprising one or more processors and a memory storing instructions, the instructions, when executed by the one or more processors, causing the first device to perform the method according to any one of claims 1 to 18.

20. A non-transitory computer-readable medium comprising instructions which, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 1 to 18.

21. A method comprising: An indication is received by the second device from the first device that a plurality of packets associated with data units of the data flow were discarded.

22. The method of claim 21, further comprising discarding, by the second device and based on the indication, one or more received packets of the plurality of packets.

23. The method of any one of claims 21 to 22, further comprising receiving, by the second device from the first device, the plurality of packets associated with the data units of the data flow.

24. The method of any one of claims 21 to 23, wherein the first device comprises a first wireless device and the second device comprises a second wireless device.

25. The method of any one of claims 21 to 23, wherein the first device comprises a first entity of a first wireless device, and the second device comprises a second entity of the first wireless device.

26. The method of claim 25, wherein the first entity or the second entity comprises at least one of: Packet Data Convergence Protocol (PDCP) layer; or Radio Link Control (RLC) layer.

27. The method of claim 26, wherein the data unit comprises a service data unit (SDU).

28. The method of any one of claims 21 to 27, wherein the indication that the plurality of packets were dropped is received via at least one of: Packet Data Convergence Protocol (PDCP) status report; or PDCP control protocol data unit.

29. The method of any one of claims 21 to 28, wherein the indication that the plurality of packets are discarded comprises information indicating that the second device needs to discard each of the plurality of packets.

30. The method according to any one of claims 21 to 29, further comprising sending configuration information from the second device to the first device regarding whether to send the indication that the plurality of packets are discarded.

31. The method of claim 30, wherein the configuration information includes a value for the duration for enabling the first device to determine a transmission failure based on expiration of the duration.

32. A second device comprising one or more processors and a memory storing instructions, which when executed by the one or more processors cause the second device to perform the method according to any one of claims 21 to 31.

33. A non-transitory computer-readable medium comprising instructions which, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 21 to 31.

34. A system, comprising: A first device, the first device comprising: one or more processors and a memory storing instructions, the instructions, when executed by the one or more processors, causing the first device to perform operations, the operations comprising: discarding a plurality of packets associated with a data unit of a data flow based on a transmission failure of at least one packet of the plurality of packets; and sending an indication to the second device that the plurality of packets are discarded; and The second device, wherein the second device comprises: one or more processors and a memory storing instructions, wherein the instructions, when executed by the one or more processors, cause the second device to perform operations, the operations comprising: The indication that the plurality of packets were discarded is received from the first device.

Citation Information

Patent Citations

  • Method and apparatus for pcdp discard

    CN101965705A

  • Method and apparatus for wireless communication in wireless communication system

    CN111316714A

  • Reassembly of mini-packets in a buffer

    US20110211591A1

  • Media delivery service protocol to support large numbers of client with error failover processes

    US20140281707A1

  • Data transmission method and apparatus

    WO2020061966A1